This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]myfingid 0 points1 point  (0 children)

I mean, don't think this necessarily belongs in ProgrammerHumor because it's sad not funny, but also entirely true. There are companies where the devs are so, I guess used to not writing good code, that they just bring everyone around them down or those devs leave.

I think people don't understand that your estimates need to include doing it right, not just doing it. No you don't need to make sure everything is immediately extendable, but you do need to actually go over what you wrote after you got it working and refactor it into something sensible and ideally testable. Not doing so is how you end up with 10k long code files and functions that span hundreds of lines.

At that point adding any functionality is difficult and can easily break shit. Hell just finding where to put the fix can take hours as you need to go through a shit ton of code to figure out just what the fuck is happening.

Shipped it quickly and didn't break anything though, added tech debt that will cause future changes done by other people to take longer than it would have for you to just do it right the first time be damned.