Why enterprise software is bloated • Hacker News Board

Re: Why enterprise software is bloated

#141

Post by icedchai » Sat, Mar 05, 2022, 4:18 AM UTC

Silhouette wrote: post #122

commandlinefan wrote: post #71

Earlier quoted context omitted.

> wouldn't ask the manager to approve every small refactoring It becomes an issue if it takes more than a day. Scrum, Kanban, RUP, XP, waterfall - whatever "methodology" they say they're following, it boils down to "tell me how long this is going to take and I'll check to see how close what you said was to the time it took". If you can make a change in an hour, sure. If it takes a day, it's going to break your "commi…

Or... Management could choose not run their software development organisation with the kind of micromanagement strategy that requires everything to be allocated in units of one day or less. It's another red flag that has become disturbingly common in the industry and suggests managers more interested in "visibility" and "metrics" than actually doing a good job, sustainably, by trusting their technical people to do th…

I love how "story points" aren't supposed to represent days, yet conveniently everyone winds up with 10-ish over their 2 week sprint, and it is totally micromanaged. Meanwhile none of the non-technical "product people" are ever asked to account for their time like this.

Re: Why enterprise software is bloated

#142

Post by xorcist » Sat, Mar 05, 2022, 1:40 PM UTC

redleggedfrog wrote: post #67

The article didn't mention what I have observed as the worst cause of bloat - what I call the "New Toys" problem. For example, you need a process to export data every 4 hours, with some visibility of success and failures. I could have written a cron job/scheduled task in 4 hours and be done. What I found instead is Kafka with node.js and couch.db. Yes, for that one export. Not only that the were paying monthly for th…

> stitch together some byzantine Frankenstein's monster from existing tech,

Or, you could stich it together from new tech.

It wasn't long ago I was surprised to discover a Hadoop installation at my current professional setting, complete with Zookeepers and everything. After some sleuthwork (which wasn't that bad as they keep everything in git, in a future when everything is api calls to some Kuberentes clusters we're all smoked) it turned out that all it does it move data between two systems.

Literally. It could be replaced with a periodic rsync run. Instead someone has to maintain and monitor a whole suite of software, prepare, test and run upgrades and so on.

Re: Why enterprise software is bloated

#143

Post by teakettle42 » Sun, Mar 06, 2022, 12:24 AM UTC

igouy wrote: post #94

teakettle42 wrote: post #69

Earlier quoted context omitted.

> I challenge you to find a major bloated software where the main source of overhead is Python interpretation In every piece of non-trivial software I’ve written in python, the main source of overhead has been Python interpretation. I don’t think it’d be hard at all to meet your challenge.

If it wouldn't be hard at all, we're left to wonder that you don't seem to have tried.

Performing a legitimate performance benchmark of even one piece of enterprise Python software — much less across a representative survey — is well beyond the reasonable scope of a comment board reply.

Re: Why enterprise software is bloated

#144

Post by igouy » Mon, Mar 07, 2022, 4:54 PM UTC

teakettle42 wrote: post #143

igouy wrote: post #94

Earlier quoted context omitted.

If it wouldn't be hard at all, we're left to wonder that you don't seem to have tried.

Performing a legitimate performance benchmark of even one piece of enterprise Python software — much less across a representative survey — is well beyond the reasonable scope of a comment board reply.

So, too hard.