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

> Firstly, I'd suggest the author look at this differently; perhaps "For Want of a Code Review". Especially code from a relatively recent graduate, on a piece of code for which the engineer in question has little experience.

I assume the story is made up, but if we were to take it at face value the title would be "For Want of Basic Human Decency"; the author is saying that they saw this whole easily preventable train wreck happen in slow motion and did not lift a finger to prevent it, instead laughing, taking notes and thinking of the fabulous snarky blog bost that would have come out of it.



The way I read it, they accepted the decisions of those higher in the hierarchy, after providing their feedback. It wasn't clear if lots of money was lost, just lots of time. I didn't think it was made up.


Eventually you learn it's not always a great idea to stop your employer from getting burned. Some people don't learn until it hurts.


From the article:

> I’d definitely commented on the JOIN statements during the initial code review


How about when it became a problem? Or the second time? The third?




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

Search: