No Code Is NOT New

No-code and low-code tools have been part of the software development landscape for several decades, evolving to meet the needs of businesses and individuals who require application development without deep programming knowledge. Over the last 25 years, I’ve used many of them. Here’s a very brief history of some key milestones:

1. Early Beginnings (1960s-1980s)

• Query By Example (QBE) – 1977: Developed by IBM, QBE allowed users to build database queries by filling out a template (example) rather than writing SQL code. This concept was an early form of no-code, enabling non-programmers to interact with databases. QBE was also available in Microsoft tools.
• Integrated Data Store (IDS) – 1960s: One of the earliest database management systems, IDS, laid the groundwork for later tools that would allow more user-friendly database interactions.

2. Business Objects (1990s)

• Business Objects – 1990: Business Objects introduced a way for business users to create reports and queries without needing to know SQL. The tool’s Query Designer allowed users to drag and drop fields to build complex queries, representing an early form of no-code data analytics.
• Microsoft Access – 1992: Microsoft Access provided a visual interface for database management and query building. Its introduction of forms, reports, and queries that could be created without extensive coding knowledge made it a popular tool for small business applications. It should be noted that Access was an Office tool and was intended to be used by non-developers, though it could be extended by writing code.

3. Model-Driven Development (1990s-2000s)

• IEG / CA Gen – 1987: Originally known as Information Engineering Facility (IEF) and later as CA Gen, this tool from Computer Associates (CA) allowed developers to design applications using a high-level, graphical interface. It was an early example of model-driven development, where the focus was on business logic rather than code.
• Visual Basic – 1991: Microsoft introduced Visual Basic as a way for developers to create Windows applications with a drag-and-drop interface. While still requiring some coding, it significantly reduced the complexity compared to traditional programming languages. Now I know this one is pushing the envelope a bit, but VB did have UI and CRUD tools that did not strictly require programming. However, as far as I saw, VB was in reality used as a development tool by programmers.

4. The Rise of Web-Based No-Code Platforms (2000s)

• Salesforce – 1999: Salesforce introduced a no-code environment for building custom applications on its platform, primarily through its AppExchange marketplace and later through its Lightning App Builder. This marked a shift towards cloud-based no-code tools.
• OutSystems – 2001: OutSystems became one of the pioneers in the low-code space, providing a platform that combined visual development with coding when needed, aimed at accelerating enterprise application development.
• WordPress – 2003: WordPress, initially a blogging platform, evolved into a content management system (CMS) that allowed users to create and manage websites without needing to code, thanks to its extensive library of themes and plugins. As of August 2024, WordPress powers approximately a whopping 43.5% of all websites globally. This translates to more than 478 million websites worldwide that use WordPress as their content management system (CMS). WordPress has maintained its position as the most popular CMS, dominating the market with a 62.7% share among all sites using a recognizable CMS.

5. Modern No-Code Tools (2010s-Present)

• Zapier – 2012: Zapier enabled users to automate workflows by connecting different apps without writing code. It popularized the idea of “automation without coding,” becoming a staple in the no-code movement.
• Bubble – 2012: Bubble emerged as a fully-fledged no-code platform for building web applications. Users could create complex web apps with a visual editor, handling everything from the frontend design to backend workflows.
• Airtable – 2012: Airtable combined the simplicity of spreadsheets with the power of databases, allowing users to create custom applications to manage various types of data without coding.
• Webflow – 2013: Webflow brought design and development together in a no-code platform, allowing designers to build responsive websites with a visual interface while also generating clean code underneath.

6. No-Code Today

Today, the no-code movement continues to gain momentum, democratizing application development and allowing more people to create software solutions. The rise of AI-driven tools, like GPT-4 integrated no-code platforms, is pushing the boundaries further, enabling more complex applications to be built without traditional coding.

No-code and low-code tools have evolved from simple query builders to powerful platforms capable of creating sophisticated applications, illustrating that this concept has deep roots in the history of software development.

7. Perfect Is The Enemy Of Good

In my experience, no-code tools generally meet resistance from software developers, which I suppose is to a certain extent to be expected. A recent YouTube video declares “No-Code Will Fail” which ignores the very successful history of various no-code tools like those listed earlier.

Why the resistance? Software developers are like fine woodworkers. They care about their handiwork and they know the benefit of finely crafted code. A complaint often heard is something along the lines of “WordPress writes horrible code!” But to that I say “So what?” WP has a specific use case, one that it fulfills spectacularly. Almost half a billion websites agree. If there weren’t a tool like WP available, many of those individuals and businesses could not afford to have a web presence. Is it the most performant code? No. But it is good enough for their needs. Perfect is the enemy of good.

8. Conclusion

No-Code tools are not new. They’ve been around for a long time and now when combined with AI, their future is brighter than ever. For businesses and individuals that is a good thing. It is a good thing for developers as well but they’ll need to learn to adapt to the changing paradigm.