For real. I just spent a decade in academia working dog hours with little pay keeping services running wondering how the true devs and sysadmins do it.

I recently switched to the corporate world and have peeked behind curtain of competency: headless chickens running around, patching failing products rather than spending time to properly fix them because immediate results are the only metric that counts.

Stability, scalability, reproducibility? Forget it, that's someone else's problem apparently.

That's why the no warranty clause is by far the most important in any license granting access to the public

Wait RIF was reanimated? In what way?

Same for Apollo and now Voyager. Probably the best-designed and -implemented apps I’ve ever used.

I have no clue how much British Gas is worth, but that is the worst app ever. Doesn’t update your bill/balance in anything approaching real time. Frequently doesn’t let you log in.

Wait wait wait... RiF ain't dead?!

And Linux/BSD are so good proprietary developers rip them off to whatever degree legally permissible.

And Firefox, git, Dia, gimp, etc...

Proprietary OS's like Windows and macOS lack package managers too that tools like chocolatey and homebrew provide.

Blender had a reeeeaaally long way though, I remember a time where Blender was quite big already but Maya just was miles ahead in terms of usability. Nowadays they are not only even, Blender is probably used more often since it's not only free but more people know how to use it than Maya

“What one programmer can do in one month, two programmers can do in two months.”

Counterpoint: 'The Brooks's Law analysis (and the resulting fear of large numbers in development groups) rests on a hidden assummption: that the communications structure of the project is necessarily a complete graph, that everybody talks to everybody else. But on open-source projects, the halo developers work on what are in effect separable parallel subtasks and interact with each other very little; code changes and bug reports stream through the core group, and only within that small core group do we pay the full Brooksian overhead.'

Source: http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s05.html

It absolutely fucking BAFFLES me that Brooks' Law isn't known by every software manager on the planet.

I've quoted it so many times at work, even in engineering focused teams in at least two big tech companies. It's not a concrete fact, but it explains why so many teams are hilariously shit at delivering software.

I follow the 80/20 rule recursively. as soon as I've gotten 80% of the way there for 20% effort I immediately stop, and start a brand new project for the remaining 20%. Bam! 96% complete for only 24% effort.

taps forehead

Minetest*

CAD Software?

Well, sometimes it happens. Lemmy was semi-broken during the APIocalypse, and there still isn't such a thing as a FOSS Facebook, or search engine backend for that matter.