Not sure if this is actually a serious (but misguided) take, or just the kind of thing you have to write when you need to blog something but don't have a good idea this week?
Software is getting more complex, not less.
No-code, no matter how magically great, won't change the fact that you have to somehow understand and codify your requirements and figure out how to achieve them through available building-blocks. (A no-code solution is just a tradeoff in building blocks -- the more one does for you, the less flexible it becomes. The lack of flexibility has a cost: the degree to which one doesn't exactly fit your system, it pushes complexity elsewhere, blunting or even reversing the value.)
The longer-term effects of a remote-first world are a much more interesting topic, at least (though I think the author stiff completely whiffs. The ideas on why remote work will be bad for the employees are very weak.)
Software is getting more complex, not less.
No-code, no matter how magically great, won't change the fact that you have to somehow understand and codify your requirements and figure out how to achieve them through available building-blocks. (A no-code solution is just a tradeoff in building blocks -- the more one does for you, the less flexible it becomes. The lack of flexibility has a cost: the degree to which one doesn't exactly fit your system, it pushes complexity elsewhere, blunting or even reversing the value.)
The longer-term effects of a remote-first world are a much more interesting topic, at least (though I think the author stiff completely whiffs. The ideas on why remote work will be bad for the employees are very weak.)