4 ms·
Sure, when you're switching jobs every two or three years, those bad decisions you make to ship now or paper over problems to make a sale don't have the opportu
by douche 10y ago
Sure, when you're switching jobs every two or three years, those bad decisions you make to ship now or paper over problems to make a sale don't have the opportunity to come back around and really bite you in the ass. It's the poor bastard who comes along afterwards and has to maintain or extend the Jenga tower that has that bucket of fun land in their lap.
- ourmandave 10y ago"It's not a problem. We'll just rewrite it for Jenga2." is something else programmers should probably never say.
- scarface74 10y agoThis. I let a lot of bad decisions that "architects" made go at my last job without putting up a fight even though I knew they were bad decisions since I knew I wouldn't be at the company long term. As the newly installed software architect at the company I'm at now, seeing that I plan to be here for a few years. I'm much more likely to fight the good fight about doing things right instead of fast. Actually, I think doing things right and doing things fast is a false dichotomy. You can do things right, fast, and deliver the minimum viable product. I can't think of a single bad architectural decision that would help you in the short term over doing it right.
- PretzelFisch 10y agomaybe, but I shipped the code that earned the revenue that c payies for "poor bastard's" salary/contract.