I used to need software from vendors. Now, with (for the moment) the exception of primitives, I don't. I can have everything I need (and I can code the primitives manually). The only consideration is how good your product is vs how many tokens it costs me to make it better for my bespoke use case. Remember my rant about this.
In most cases, what this means is disruption, right now. Is Salesforce abstract enough (its one of the more abstract giant softwares) or can I replace it with postgres and some vibed up interfaces and reports? Depends a bit on your skill as a software architect, but generally... postgres wins.
It won when I had teams of great coders implementing my vision and it wins now when I have just Claude and the occasional low level library I code manually. The most annoying thing to me nowadays is when someone fucks up their product by botting too much and then I have to replace their shit (for me, not for you, because I don't care about your use cases. Learn to use Claude?)
However, without fat profit margins, who is going to spend the money to maintain postgres? End users? I think it unlikely. So that's stage 2 and it's ugly.
The real doomsday planning in software right now is to prep for the need to fall back to just a compiler and still get what you need. This is why I'm more and more often writing c++, std only, for my own automation projects. I'm betting that hardware-first companies like Apple will need clang++ to survive.
I used to need software from vendors. Now, with (for the moment) the exception of primitives, I don't. I can have everything I need (and I can code the primitives manually). The only consideration is how good your product is vs how many tokens it costs me to make it better for my bespoke use case. Remember my rant about this.
In most cases, what this means is disruption, right now. Is Salesforce abstract enough (its one of the more abstract giant softwares) or can I replace it with postgres and some vibed up interfaces and reports? Depends a bit on your skill as a software architect, but generally... postgres wins.
It won when I had teams of great coders implementing my vision and it wins now when I have just Claude and the occasional low level library I code manually. The most annoying thing to me nowadays is when someone fucks up their product by botting too much and then I have to replace their shit (for me, not for you, because I don't care about your use cases. Learn to use Claude?)
However, without fat profit margins, who is going to spend the money to maintain postgres? End users? I think it unlikely. So that's stage 2 and it's ugly.
The real doomsday planning in software right now is to prep for the need to fall back to just a compiler and still get what you need. This is why I'm more and more often writing c++, std only, for my own automation projects. I'm betting that hardware-first companies like Apple will need clang++ to survive.