169 karma · joined November 7, 2012
The length itself is not an indicator per se, but you can sense when it is not honest. If others do not have a sense for it, it seems like complaining about something new.
So how can you keep generating disposable software on this layer?
And what you mostly want to change in software, is new features or handle more usage. If you do that, it needs in most cases changes to the data store and the “hand crafted core”.
So what part in practice will be disposable and how often will it be “generated again”?
Maybe for simple small stuff, like how fast Excel sheets are being made, changed and discarded? Maybe for embedded software?
They planned to support the new regulations before, but pulled the plug last Friday.
https://www.computerworld.com/article/1561181/excel-error-le...
For the fancy streams and frames you need some extra headers being sent from the server, but also that is doable from PHP.
But I agree that a lot of companies are so big and so faceless, that they do too much bad stuff and lots of people in the company would just shrug it off with “it is not my job to say something”.
I think it is very sad the moral standards are so low. I find that even harder when mixed with “why does the government get involved in everything?” attitude.
I also don’t lead my company of 27 people that way.
If you cannot make a clean monolith, I have never seen any evidence that the same team can make good microservices. It is just the same crap, but distributed.
The last 2 years I see more and more seasoned devs who think the opposite: monoliths are better for most projects.
Sorry for no direct link, but he has so many and very long videos that it is hard to find the exact spot.
I could get used to act on press, but this is my current muscle memory after 30 years of computers.