Agree. I haven't seen any examples of ChatGPT that might make me want to use it for my job. Yes if you are an inexperienced programmer (or just not very competent) then it might help you get something working I guess?
Jonathan Blow is full of it. Seriously. The amount of time he spends self promoting and telling everybody how to do things is jaw dropping. He is a good puzzle game designer. That doesn't mean that he is good at anything else.
You have to be really arrogant to assume that you know within 5 minutes of looking at somebody else's code that you know how to do it "better".
I am sure you know how to do it differently, and more like how you prefer to do it, but that is not the same thing at all.
Legacy software is successful software. You are never asked to maintain failed software. Only software that is successfully generating $ years after it was originally developed.
So be humble. Show a bit of respect. And don't automatically assume that you are some super genius who knows how to do everything better.
And remember that other equally unenlightened developers will look at your code and go WTF and complain about how crap your code is. Don't be like them.
Who cares what Malcolm Gladwell thinks? @dang is this really worthy of HN? There is nothing new here. Just the same old WFH discussion that we have had so many times on HN.
I suspect so. There is more and more anecdotal evidence that Alzheimer's and other similar diseases are cause by insulin resistance in the brain. However there is unfortunately no gold standard double blind research out there to confirm/deny it yet.
9 in 10 businesses fail within the first year. And another 9 in 10 fail the following years. The odds aren't great. Also now your customers are your boss. You don't necessarily have more freedom.
Nothing magically makes microservices good or bad. Nothing magically makes monoliths good or bad. It all depends on how good the developers are. However it is objectively a fact that microservides are inherently more complex than monoliths. You basically take a monolith and add encode/decoding, network latency delays, no global commits, potential timing issues, partly-failed system scenarios, new types of distributed error conditions etc. to the mix. So there is zero upside to using microservices IMHO.
Microservices can most definitely be tightly coupled. The same way that most OOP code I have seen is a spiderweb of tight dependencies. I bet that code you think is loosely coupled probably isn't. Most developers have no clue what "loosely coupled" actually means.
Everything you claim is unproven and pure speculation. However what is proven to be true is that thousands of developers all over the world can effectively work on massive monoliths (like Linux and Windows) without using microservices.
Nope. Each team is responsible for a library. The monolith is composed by combining those libraries into a single application. It gives you all the benefits without the disadvantages (no encode/decode/network latency, easy rollback, easy transactions management etc. etc. etc.)