Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Nice.

These are reasoned, common sense measures, most of which I have seen in one form or another in the coding guidelines of the companies I have worked for as an embedded SW engineer.

Some of them are easy to enforce (no dynamic memory allocation, no recursion), other less so (using asserts, limit function size).

The worst is adding your rules-compliant code to messy and bloated legacy code :)



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: