Avatar
Mark
4bc6e43c4a86c764208104fc8c2e18cb38a50b4bbe2eaac63aa196f588e97178
One day, I'll be good at producing quality software and will have intelligent things to say about it

I'm also not an exception fan, but not sure what the best way around it is

https://twitter.com/ThePrimeagen/status/1696941040115101881

My current thinking is ORMs are big hulking things that need to handle multiple use cases - more use cases than any individual project will need. So ideally, you would use raw SQL with some lightweight scaffolding around it specific to your project. But that scaffolding must be done right, and that can be a hard problem to solve that probably required significant domain knowledge. If the stakes are high, teams will avoid that risk of a poor custom solution and choose the ORM and the ongoing costs associated with it.

I've little knowledge about this, but sounds like a desperation play to me - maybe HashiCorp are running out of ideas of how to sustainable make money? https://blog.gruntwork.io/the-future-of-terraform-must-be-open-ab0b9ba65bca

I think we cannot currently determine which modern languages offers real extra value. I think there is a bias to exclude things where the flaws are known for things where the flaws are unknown.

My more general thesis is programming is in its infancy and nobody knows what they're doing. Bloodletting was used frequently and unnecessarily in medicine for 2000 years. I wouldn't be surprised if we do something similar with programming. We need the programming equivalent of double-blind studies.

If I'm right and nobody has a clue, maybe it doesn't really matter what language, so just choose whatever you feel like, flip a coin, or whatever. I always try to remind myself that code is just a tool to deliver value, not an end in itself - I'm really not experienced enough to be giving out this kind of advice, but, hey, it's the internet 😛

I'd say depends on what you want. To learn generally about programming, I'd go C/C++ - something without garbage collection. If you're looking to be effective quickly, and have lots of existing libraries and support, I'd choose something like Java.

Rust is too new for my liking and I don't trust all the fanboi proclamations about it - although will be happily proven wrong. I prefer the tried and tested.

"Commands sent to Voyager 2 on July 21 accidentally caused the spacecraft’s antenna to point 2 degrees away from Earth." https://edition.cnn.com/2023/08/01/world/voyager-2-communication-blackout-scn/index.html

Do think the article erects a strawman: "The programmers in the Handmade community had no right to criticize software". Is that what people are really saying?

There are different ways to advocate for change in how we produce software, some more effective than others. If a significant proportion of those who's minds you wish to change are labelling you "toxic", then I'd suggest your approach isn't working.

Someone who is really concerned with change will choose the most effective method, rather than let their feelings of frustration overcome them. If not, then maybe the public outbursts are about sonething else?

"But notice that arguments about technologies—presumably battling for adoption, social acceptance, and popularity—are not only empirically not about rationality, but definitionally cannot be about rationality. A beginner who knows nothing about programming cannot select an ecosystem or technology based on rational arguments, because they’re removed from the technical context which makes such arguments meaningful. They can only select by second-degree metrics of qualities they care for—popularity, what someone seems to produce with said technology, how quickly they produce it, the unique qualities of that production as opposed to those of others, and so on."

https://www.rfleury.com/p/the-marketplace-of-ideals

Read these before, and think they do provide good hints on how to make teams more effective. https://butwhatfor.beehiiv.com/p/simple-sabotage-field-manual-destroy-organizations