Hacker News new | past | comments | ask | show | jobs | submit login

A developer should be judged by does it work and not fail that often (and fail in safe ways) - I dont care how "purty" the code is.

I can recall when using mixed case in your FORTRAN IV Hollerith statements was considered a bit flash.




Good code is more than how it looks. Is it fault tolerant? Does it handle edge cases? Does it scale? Does it lend itself to being tested? Does it lend itself to being extended? Is it legible by other coders for when they inevitably need to fix bugs and/or refactor / extend it?

"it works" is actually a very small part of good code, since implementation is usually dwarfed by maintenance and extension.

Note, none of what I mentioned is about clever or "purty" code.


But I bet my code that was the core of one of BT's billing systems (and sold world wide) would not be perceived as very good quality.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: