Is No-Code Going To Steal Your Job?
[Spoiler alert: No.] (https://builtin.com/software-engineering-perspectives/no-code-replace-programmers?es_id=b1380061cf)
When I started working as web professional in 2000, there were no “tools.” You used a text editor or you used Macromedia Dreamweaver (current version: 3).
The #1 client request was to be able to edit their own website without having to go through their web designer. That’s because most web designers SUCKED. They were utterly incapable of answering or returning phone calls or emails. The common story was the designer sitting on the client request for weeks at a time.
Then in 2002, along came Macromedia Contribute. Designed to integrate with Dreamweaver templates, this simple(r) software let clients make their own updates to their websites.
Much handwringing ensued. OMG, there would soon be NO WORK for web designers!
Of course, nothing could have been further from the truth. There was plenty of work for web designers. However, if “work” meant fixing typos or updating copy, yeah, you did lose out on some of that. But there was still a ridiculous amount of work for those wanting to build new websites.
Fast forward to 2020. The latest round of no-code tools are allowing people to automate tasks, build forms, create their own simple websites, and integrate technologies without developers.
Much handwringing ensued. OMG, there would soon be NO WORK for programmers!
And just like before, nothing could be further from the truth.
a. Who codes the no-code tools?…
b. Who does one call when one pushes no-code to the limit, or wants that one feature that seems to be nowhere in the no-code space?
c. The power of creation from nothing will still lie with programmers. But the junk work of building yet another form that emails the contents to the owner, or writes it to some spreadsheet? That stuff is going to go away.
Trust me, you won’t miss it.