Top products from r/programminghorror

We found 4 product mentions on r/programminghorror. We ranked the 4 resulting products by number of redditors who mentioned them. Here are the top 20.

Next page

Top comments that mention products on r/programminghorror:

u/Timidger · 3 pointsr/programminghorror

I don't know how much reading you've done, but I've also found The Pragmatic Programmer to be a very good read. It talks about the design of a project abstractly, and has held up well over the years (1999 was the publish year!)

u/[deleted] · 2 pointsr/programminghorror

If someone is at least honest with himself & others, then it can be a cooperative effort. I'd rather work under a software-architect, who was trying and wanted to improve, than one who thought he knew what he was doing and didn't.

If someone throws around the title "Software Architect" like they're some kind of specialist or expert, they better know their shit more than some junior/mid level coder who read the first few chapters of Code Complete.

u/DevIceMan · 1 pointr/programminghorror

> 7

This is an anti-pattern. Even if you were going for hyper-performance code (which is a little silly in Java), the Compiler these days is typically very good at optimizing this type of code.

> 13

This guy hates functional programming. If you used a lambda, or Java streams, would you just automatically flunk the class?


From an overall perspective, I'd say this guy hasn't really learned much about computer science (if anything) in the last 10 years. If he intends to be an educator, code style should be based on a real style guide or well known book like:

u/billy_tables · 1 pointr/programminghorror

Why would companies learn by firing their employees? Companies think they've resolved the situation when they fire an employee. See every CISO officer being fired after a breach ever - and nothing changes.

Nobody goes into work to make a mistake. I'd bet given the training they had, both of those people thought they were doing the right thing, and that anyone else who'd been through the same training with no IT background would have agreed. the book The Field Guide to Understanding Human Error is very good on this topic.

If you fire someone every time they make a mistake, nobody will ever learn. Only when someone who's already made a mistake comes up against the same situation again and does it right can you be sure you've improved as an organisation. If you don't change anything else and just fire people you haven't resolved anything and it's just a matter of time until it happens again.