I think it’s about software engineers, who are supposed to be impervious about effects of caste structures and hierarchy, judging programming languages from the caste lens.
That is my interpretation, please don’t hold me against it
"I have written this maxim a few different ways, but it is worth writing again: no army can help but recreate its civilian social structures on the battlefield."
Interesting to see Conway's law show up here. Companies tend to ship their org structure in a product.
> I also think we need a high level formal specification language to tell agents what we expect them to do.
Let’s make that specification Turing complete while at it.
Jokes aside, IMO it will be a good natural progression. Specify the problem statement in LLM specification, generate the code in Go/Rust whatever is the language of your choice and review the generated code to make sure it adheres to the architecture/design principles that you have set.
What's the capacity though. Either way this seems extremely high unless we are talking in terms of like 100kw or something. For reference, I recently installed hybrid/net-metered system set up at my home in India; 7kw solar with a 20kWh battery for around $10K. The biggest cost is for the batteries though. The panels themselves have become extremely low price and the prices continue to fall.
It's interesting to see Tesla's solar business getting disrupted by Chinese manufacturers after EV.
I’m building reporting for my company and what you said mirrors my experience nearly 100%.
I’m a backend developer so I know what it takes to build a half decent reporting system. Writing all those queries, slice and dice charts and what not takes real time and effort. All that has been outsourced to Claude Code. I now focus on ensuring that the system is sound architecturally and that useful reports are being surfaced.
I am, thankfully, out of this craziness now but it was fun solving ton of such puzzles from Yashavant Kanetkar books while preparing for campus hiring interviews back in 2000. "Test Your C Skills" in particular. Fun times.
Me and my friends collected, traded and also played a game with stone by staking match box covers. The idea is everyone stakes match box covers in a small circle drawn on an open ground. Everyone then takes turn to throw stone at the pile. Whichever match cover that’s dislodged out of the circle belongs to the thrower. Also played it with cigarette packet covers.
You are spot on w.r.t every assertion you've made. When bean-counters took over the ecosystem they optimised immediate profitability over everything else. Which in turn means, in their mind, every part of the system needs to be firing at 100% all the time. There's no room for experimentation, repair, or anything else.
I've commented about lack of slack on several times here on HN because when I notice a broken system now a days, 90% of it is due to lack of slack in the system to absorb short term shocks.
Apparently it required someone with the personality and product taste of Jobs to rein in Ivy. Cook on the other hand being a logistics/operations guy didn’t have the similar skills and we ended up getting absolute shitshow of hardware products from apple in late 2010s.
Thankfully he was fired and sanity prevailed which coincided with Apple Silicon line professors. The MacBook Pro that was immediate predecessor to M1 series was by far Apple’s worst hardware. It was bad on nearly every count.
They ran out of novel things to say which is expected of anyone because there’s only so many non trivial things one could say. But then unlike normal people they didn’t stop talking because being rich they are bored and they want to be in the limelight all the time. So they end up talking nonsense.
You also changed, you are now wiser and have developed BS detector.