ironically it is your camp that advices to not use microservices but start with monolith. that's what i'm suggesting here.
People seem to think that technical debt doesn't need to be paid back for ages. In my experience bad code starts to cost more than it saved after about three months. So if you have to get a demo ready right now that will save the company then hack it in. But that's not the case for most technical debt. In most cases the management just want the perception of speed so they pile debt upon debt. Then they can't figure out why delivery gets slower and slower.
> ironically it is your camp that advices to not use microservices but start with monolith. that's what i'm suggesting here.
I agree with this. But there's a difference between over-engineering and hacking in bad quality code. So to be clear, I am talking about the latter.
To anticipate your objection: you can get over determinism now, or you can get over it later. You will get over it, though, if you intend to stay in this business.
What are you talking about? If an LLM is a compiler, then I'm a compiler. Are we going to redefine the meaning of words in order not to upset the LLM makers?
1. You are right that we can redefine what is code. If code is the central artefact that humans are dealing with to tell machines and other humans how the system works, then CodeSpeak specs will become code, and CodeSpeak will be a compiler. This is why I often refer to CodeSpeak as a next-level programming language.
2. I don't think being deterministic per se is what matters. Being predictable certainly does. Human engineers are not deterministic yet people pay them a lot of money and use their work all the time.
Human carpenters are not deterministic yet they won't use a machine saw that goes off line even 1% of the time. The whole history of tools, including software, is one of trying to make the thing do more precisely what is intended, whether the intent is right or not.
Can you imagine some machine tool maker making something faulty and then saying, "Well hey, humans aren't deterministic."
Suppose the Go people make a special version of Go for Wasm. What do you think are the chances of that being supported in 5 years time?
As long as warnings are clear I’d rather find out early about mistakes.
Has it though? I'd say it's morphed, not changed. This is still, underneath it all, Hanseatic League and East India Company domination style colonialism, but adapted to and shaped by the digital age.
The US has pretty much all throughout its history had its military-industrial complex and warfare as an economic motor too, and in view of this, it's inevitable that software gets integrated.
Israel, the most recent settler-colonial state (of course some people try to claim it's not using various mental gymnastics, but I'm not fooled), was the experiment and has become a model for how to intermingle the industrial-military complex with society to the degree they two become indistinguishable, and with backing of the West it's been a very profitable and, I hate to say it, successful model.
Here's[1] a review of a book about the subject, talking about the state incubating start-ups and spawning a tech sector for the sole purpose of warmongering.
[1]: https://theconversation.com/the-harvard-of-anti-terrorism-ho...
The engineer who worked with you took ownership of the code! Have you forgotten this?
https://components.news/the-gamer-and-the-nihilist/
that is is, people who are caught in AI FOMO are performatively trying to appear to be productive and that's the opposite of fun.