Trust corporate America to take something as simple as loading a text article into a digital “experience”. What the hell even is that? (Its marketing jargon for ads, I know). Talk about a circle jerk around the marketing table though.
Trust corporate America to take something as simple as loading a text article into a digital “experience”. What the hell even is that? (Its marketing jargon for ads, I know). Talk about a circle jerk around the marketing table though.
You’re right, no one is hiring a plumber to redo their entire plumbing in a home…but they are hiring them to fix leaks and unclog drains (patching) that’s what most programming is. Patching.
And most patching is fixing leaks (exploits/vulnerabilities) that can destroy your house.
A key difference is that engineering standards have grown to the point where we don’t hire a plumber to come multiple times to clear drains and patch leaks. The drains were built large enough and with proper materials to last for years without maintenance. We don’t have people constantly shoring up bridges either.
This is why some people don’t consider software engineering to be engineering.
Too many people justifying their existence by shipping unnecessary and poorly thought out features leads to unreliable, complex software that needs constant maintenance to keep it running.
We absolutely make sure bridges are looked after and maintained.
Software patches aren’t just because they are being required to put out new features. A lot of it is security patches and bringing aging software to work on the latest kernels and OSs.
I think you’re simplifying this a bit to much.
Usually that’s on management, not the devs.