Comment by chickensong
3 days ago
What a joke blaming the IT community for not doing better, when most businesses refuse to look past anything but shipping features as fast as they can. "We take security and reliability very seriously", until management gets wind of the price tag. Guess what areas always get considered last and cut first. We all know.
But sure, blame the community at large, not the execs who make bad decisions in the name of short-term profits, then fail upward with golden parachutes into their next gig.
And definitely don't blame government for not punishing egregious behavior of corporations. Don't worry, you get a year of free credit monitoring from some scummy company who's also selling your data. Oh and justice was served to the offending corp, who got a one-time fine of $300k, when they make billions every quarter.
Maybe if we just outsource everything to AI, consultants, and offshore sweat shops things will improve!
Okay cool, good article.
> blaming the IT community for not doing better, when most businesses refuse to look past anything but shipping features
IT != software engineering. IT is a business function that manages a company's internal information. Software engineering is a time-tested process of building software.
A lot of projects fail because management thinks that IT is a software engineering department. It is not. It never was, and it never will be. Its incentives will never be aligned such that software engineering projects are set up for success.
The success rate of implementing software outside of IT and dragging them along later is much higher than implementing it through IT from the beginning.
I understand, but also, IT is an umbrella term for a wider industry that includes your definition of IT, software, and anything adjacent. If you read the article, you'll see it's the latter being referenced, and why I chose that terminology.
> The success rate of implementing software outside of IT and dragging them along later is much higher than implementing it through IT from the beginning.
That's a pretty strong statement. Isn't that the opposite of why the devops movement started?