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

I have seen a complete project. The project was maintained by one person. Former developer left and transferred his work to the next.

It was a C project, but the second developer was coming from a Java background. So his half is all written with Java notation and naming conventions.

The thing was maths-heavy and had no comments. Instead they were consulting to a documentation book which also had file names and approximated line numbers.

The error tracing was done with function call stacks, so every function pushed some data into a global stack before a critical operation and, popped the same data if everything went without any problems.

Some libraries they were using were ad-hoc patched to taste, and grafted into the code tree. So, debugging was 5x harder and longer.

The functions were not divided into headers in a logical way, they were ad-hoc. So finding something was dependent on an source indexer or a grep sprint.

Last but not the least, the developer was so arrogant that the bugs were resolved by threatening to force him to clone his code and sent it out to another developer to debug and clean. Otherwise he pretended that the bugs were not present, because it was running on his test bed.

... and yes. It was in production.



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

Search: