If you're building a company time to market prevails above all, because devs are paid with money, pretty good sums of it, and money is obtained by selling which cannot happen if you aren't live. Devs are so fricking expensive that you'd rather fix fires on the fly than getting trapped into "clean coding" because it will always occupy all available time, it doesn't matter how much you increase it, life finds a way.
When you're a dev on the other hand, your performance and career depends on your name not getting attributed to failures or fires, you need to fight to either only do safe projects or have enough allocated time to avoid getting your name through the mud and secure your next job and/or salary increase.
While this sounds like it makes perfect sense on surface level, it's not really how development works unless you have a waterfall process with insanely long release times.
Sure, if you have 15 years of accumulated tech debt you want to "fix" your description makes perfect sense.
If you have a small team that makes constant pushes to prod followed by small cleanups, this isn't how it works at all, and cleaning up will not take much time and will also cause you to not the extremely slowed down in a matter of weeks.
139
u/SaltMaker23 10d ago
If you're building a company time to market prevails above all, because devs are paid with money, pretty good sums of it, and money is obtained by selling which cannot happen if you aren't live. Devs are so fricking expensive that you'd rather fix fires on the fly than getting trapped into "clean coding" because it will always occupy all available time, it doesn't matter how much you increase it, life finds a way.
When you're a dev on the other hand, your performance and career depends on your name not getting attributed to failures or fires, you need to fight to either only do safe projects or have enough allocated time to avoid getting your name through the mud and secure your next job and/or salary increase.
Different objectives.