Common weaknesses in code

Common weaknesses in code(cwe.mitre.org)

57 points by ns8sl 9 years ago | 13 comments

PKop 9 years ago |

The title was encouraging and intriguing.

The website was amazingly confusing and discouraging. Not sure how to proceed from main page...

This is one of those websites that drives you away immediately just because the styling and layout is so ugly that you conclude whoever is running it is like 20yrs out of date on everything. Stayed for like 4 seconds. That was all I could take.

BuuQu9hu 9 years ago | |

For me it is the opposite, flashy new websites make me think they are all style and no substance.

ClayFerguson 9 years ago | |

But i'll reply to myself and admit that I don't give a damn about styling either in my own site, meta64.com, because I'm just working on back end functionality at this point. Let the hypocrisy accusations begin. I plead guilty in advance.

ClassyJacket 9 years ago | | |

Apart from the grey background yours is alright.

junke 9 years ago | |

Click on development view, and then you have a tree; for example: Location, Code, Error Handling, Error Conditions, Return Values, Status Codes, Unchecked Return Value (https://cwe.mitre.org/data/definitions/252.html).

ktRolster 9 years ago | |

If it helps, there is a single diagram that charts the entire thing: https://cwe.mitre.org/about/images/lg_consensus.jpg

If you can figure it out, let me know :)

andrewl 9 years ago | |

I agree, which is disappointing. MITRE has an interesting history, and they've done a lot of very advanced technical work since the 1950s.

kalu 9 years ago | |

and yet, this posting got enough up votes to reach the front page.

kyberias 9 years ago |

I'm sure the site contains a lot of useful data but the presentation is so ugly that it's hard to get motivated to dig in deeper.

Compare it to this, for example:

https://sourcemaking.com/refactoring/smells