Dev is a large financial drain and a ton of companies accounting departments(or whoever) don’t see the value. Ok the IT department is responsible for the website? The website is ‘done’ though so why are we still paying all these IT/Dev people? Cue massive IT layoffs…wall street/investors are super happy.
No new features/bug fixes/security updates. Customers are unhappy(who cares?, they’re still spending money!). Oh…massive data leak from some unpatched security vulnerability. All the sudden IT budget blows up…
The damage to reputation and future business deals are hindered. The amount of promising you’ve identified the problem and mitigated that from happening again etc. The requirements of other companies that you follow xyz audits to do business with them etc(which can be a good thing, it’s just very costly to a business).
Then a handful of years later they forget it all and repeat…
The “now the tech is done can we rationalise the dev team?” fallacy just drives me up the wall. Mostly because I’ve actually worked in environments where those questions were seriously pondered and had to defend against it.
Then a handful of years later they forget it all and repeat…
They don’t forget, they never learned in the first place. In their minds the original engineers messed up, and that’s why there was a vulnerability, or a missing feature. “We need a quick and cheap vendor to fix the mistakes of our awful engineering team that we laid off a year ago”.
The requirements of other companies that you follow xyz audits to do business with them etc(which can be a good thing, it’s just very costly to a business).
I secretly enjoyed getting on the phone (one-on-one) to explain this one to leaders.
“Previous decisions have made us a complete laughing stock among our peers. How would you like me to write that up for the audit report? Okay. I’ll use my judgement.”
Dev is a large financial drain and a ton of companies accounting departments(or whoever) don’t see the value. Ok the IT department is responsible for the website? The website is ‘done’ though so why are we still paying all these IT/Dev people? Cue massive IT layoffs…wall street/investors are super happy.
No new features/bug fixes/security updates. Customers are unhappy(who cares?, they’re still spending money!). Oh…massive data leak from some unpatched security vulnerability. All the sudden IT budget blows up…
The damage to reputation and future business deals are hindered. The amount of promising you’ve identified the problem and mitigated that from happening again etc. The requirements of other companies that you follow xyz audits to do business with them etc(which can be a good thing, it’s just very costly to a business).
Then a handful of years later they forget it all and repeat…
I work in IT/Dev…oof.
The “now the tech is done can we rationalise the dev team?” fallacy just drives me up the wall. Mostly because I’ve actually worked in environments where those questions were seriously pondered and had to defend against it.
They don’t forget, they never learned in the first place. In their minds the original engineers messed up, and that’s why there was a vulnerability, or a missing feature. “We need a quick and cheap vendor to fix the mistakes of our awful engineering team that we laid off a year ago”.
I secretly enjoyed getting on the phone (one-on-one) to explain this one to leaders.
“Previous decisions have made us a complete laughing stock among our peers. How would you like me to write that up for the audit report? Okay. I’ll use my judgement.”