4 ms·
PM: "We promised higher management that feature X would be done by The Date(tm)" DEV: "We can only do that by cutting corners, reusing code for purposes we sho
by sirwhinesalot 5y ago
PM: "We promised higher management that feature X would be done by The Date(tm)"
DEV: "We can only do that by cutting corners, reusing code for purposes we shouldn't, and making it not extensible in the future"
PM" "Yeah but we promised higher management so it needs to get done"
some time later...
PM: "Hey can we add feature Y by The Date(tm)"
DEV: "It doesn't fit with the rushed work we did for feature X, we'll need to rewrite quite a bit of code to make those two fit"
PM: "Yes but we promised feature Y by The Date(tm) to this customer, so it needs to get done"
DEV: "Well we can hack something together which does 90% of Y on a full moon and breaks otherwise, I really don't recommend doing this."
PM: "We have no choice"
some time later...
PM: "Why are all features taking so much longer to complete than they used to"
DEV: "Massive technical debt"
PM: "Ah yes, the software industry's way of euphemistically describing their incompetence."
- wellpast 5y ago> DEV: "We can only do that by cutting corners, reusing code for purposes we shouldn't, and making it not extensible in the future" This is an inexperienced dev talking. If s/he was more self-aware, it would be DEV: I'm not very good at architecture so whatever date you need it by I'm probably going to make a relative mess of it. If you give me more time, at least my rate of introducing mess into the codebase will slow down, so there would be _that_.