3 ms·
I think the backlash is due to two things: the audience and the limitations no/low-code solutions often have. Having worked at Microsoft on VBA-related things,
by strongpigeon 4y ago
I think the backlash is due to two things: the audience and the limitations no/low-code solutions often have.
Having worked at Microsoft on VBA-related things, I can attest without a doubt that no code automation (e.g. record a macro) are extremely powerful. VBA did give you the right tooling allowing someone with no coding experience to start tweaking macros generated by the recorder. The macros created by these often end-up being business critical. After having talked to so many huge customers, I'm convinced VBA powers at least a single-digit percentage of the world's economy.
That being said, the code of the macros often end up being a huge unmaintainable mess. Creating a lot of aversion from actual pro devs to it.
No-code solutions also end up being great for a few use cases, but fail at making complete products. It's the classic 80/20 problem where the last 20% still matters a lot. As soon as you want to step out the the guard rails, you often hit a wall.
I think no/low-code can be great and actually think VBA was awesome (well, not the language, but the platform). But, after having seen so many platforms that can't do anything more than a simple demo, I don't blame people for being doubtful about them in general.