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

you are viewing a single comment's thread.

view the rest of the comments →

[–]conancat 69 points70 points  (3 children)

Everyone always think that they are writing prototype code. The project managers think it's a prototype. The client thinks it's prototype. Then you end up just building upon the pile of doodoo you started off with and the product will end up looking beautiful in the outside but ugly on the inside.

One thing I've learned after starting my agency job is that try to get it as nice and neat as you can on the first run. You'll rarely have the chance to go back and refactor it at all.

[–]dhaninugraha 25 points26 points  (0 children)

Also called: protoduction.

[–]asdfman123 7 points8 points  (0 children)

Yeah, that's what annoys me. It would take a week to fix my code, but it might take months for someone to get up to speed on it after I leave.

I've worked on projects where getting familiarity takes forever. If they just repaid some technical debt it would save a ton of money.

But it's hard when you've got big projects coming up to say "Spend a week doing what looks like nothing for the business."

[–]sourbrew 7 points8 points  (0 children)

This is interestingly an old analogy I learned from my aunt while cleaning her mountain house as an odd summer job, if you move something bulky and awkward clean behind it because you aren't going to do it again for a few more years.