Ah yes, those precious precious CPU cycles. Why spend one hour writing a python program that runs for five minutes, if you could spend three days writing it in C++ but it would finish in five seconds. Way more efficient!

[–] BCsven@lemmy.ca 32 points 1 month ago* (last edited 1 month ago) (5 children)

Because when it is to actually get paid work done, all the bloat adds up and that 3 days upfront could shave weeks/months of your yearly tasks. XKCD has a topic abut how much time you can spend on a problem before effort outweighs productivity gains. If the tasks are daily or hourly you can actually spend a lot of time automating for payback

And note this is one instance of task, imagine a team of people all using your code to do the task, and you get a quicker ROI or you can multiply dev time by people

[–] _pi@lemmy.ml 1 points 1 month ago* (last edited 1 month ago)

SDLC can be made to be inefficient to maximize billable hours, but that doesn't mean the software is inherently badly architected. It could just have a lot of unnecessary boilerplate that you could optimize out, but it's soooooo hard to get tech debt prioritized on the road map.

Killing you own velocity can be done intelligently, it's just that most teams aren't killing their own velocity because they're competent, they're doing it because they're incompetent.

And note this is one instance of task, imagine a team of people all using your code to do the task, and you get a quicker ROI or you can multiply dev time by people

In practice, is only quicker ROI if your maintenance plan is nonexistent.

load more comments (4 replies)

load more comments (10 replies)