318 karma · joined February 1, 2023
When I used to work in a similar environment we would develop code, then we would give it to a QA team. They would test it and give it to an Ops team. The Ops team would schedule a maintenance window and roll out the new code on each server. This happened maybe once a quarter because testing and releasing was a week-long process.
Racking new servers and provisioning them also required some manual labour. We had a process to use PXE to provision the machines but it was still toil. Virtualization was a big benefit because you could at least create and blow away VMs without having to re-image a whole server from scratch.
"Running your own cloud" implies that developers can treat instances like cattle and interact via an API. But it also means there's a standard set of tooling for fleet management. None of this stuff is entirely new but in small or mid-sized orgs it was out of reach 10 years ago.
Arrow is absolutely designed for Interop between languages - often devs want to develop their core in something like Python, and the platform devs want to work on Scala. Arrow lets you write all the distributed system and data shuffling in Scala, but then users can access the same records in their user-defined code with minimal overhead
> A child free from the guilt of ownership and the burden of economic competition will grow up with the will to do what needs doing and the capacity for joy in doing it. It is useless work that darkens the heart. The delight of the nursing mother, of the scholar, of the successful hunter, of the good cook, of the skilful maker, of anyone doing needed work and doing it well, - this durable joy is perhaps the deepest source of human affection and of sociality as a whole.
- Ursula Le Guin
I have some terrible news for you.
I've watched these failsons get promoted to senior director/VP, leave before they were ever accountable for their bad decisions, and then bring all their cronies over to the new place at the same levels.
If we compare today to the Industrial Revolution, this seems like a cycle - eventually the organized labour backlash occurs, some of the excess value from automation gets passed to the workers in the form of shorter hours and higher pay. The environmental harms are recognized and the externalities are regulated by the government.
Since I've been in the industry I've often thought of myself as a Luddite - someone who opposes the constant race to the bottom that technology is driving. The original Luddites were skilled artisans who protested cheap, low quality cloth woven by machines. They knew that unskilled, automated work not only produced worse goods, but it was bad for the souls of the workers. To quote Ursula LeGuin in The Dispossessed:
> A child free from the guilt of ownership and the burden of economic competition will grow up with the will to do what needs doing and the capacity for joy in doing it. It is useless work that darkens the heart. The delight of the nursing mother, of the scholar, of the successful hunter, of the good cook, of the skilful maker, of anyone doing needed work and doing it well, - this durable joy is perhaps the deepest source of human affection and of sociality as a whole.
The spec for evolving schemas is also full of ambiguity and relies on the canonical Java implementation. I've built an Avro decoder from scratch and some of the evolution behaviour is counter-intuitive.
I sympathize with the desire for a Jewish state but the United States has supported them to the hilt in human rights abuses, war crimes and expansionism that aren't related to that goal.