Will ChatGPT Kill Coders?

by

While building the new GTM360 website, I asked ChatGPT for code for the following responsive design elements:

  1. 3 images side by side
  2. Table with 2 rows, first row with 3 images, second row with 3 links
  3. 3 images side by side on one line and 3 links on the next line
  4. 3 images side by side with linked captions.

ChatGPT responded back with code snippets for all four specs. One of them is shown partially in the following exhibit.

CLICK  IMAGE TO VIEW FULL CODE

All code snippets worked first time. I didn’t need to do any debugging (not that I’m capable of doing any!).

I had a doubt about the following line in the code supplied by ChatGPT:

.image {flex: 0 0 33.33%; /* Adjust this value to change the width of each image */ max-width: 100%;

I asked ChatGPT for clarification.

It gave me a crystal clear reply without any of the mocking / patronizing attitude of the typical StackOverflow user.

By any benchmark, ChatGPT’s performance was superlative.

This raises the following question:

Will ChatGPT kill coders?

This is not the first time people have asked this question.

In the past two decades or so, many technologies that were as revolutionary at the time as ChatGPT is today were predicted to render coders obsolete. Let me go down memory lane and recount some of them.

1. ERP

Back in the day, companies developed their own software. These were typically custom-developed point solutions for sales, purchase, inventory, finance, production, and other functions of a business. They were developed either by a team of inhouse programmers or outsourced to external vendors.

When ERP entered the scene and replaced these custom-developed solutions, people started wondering what would happen to those internal and external coders.

2. RAD / Low Code / No Code Platform

Around this time, I was heading marketing for a global ERP vendor.

Internet was around, my company had a website, and all of us had business email accounts. All marketing collateral was hosted on the website and sales reps could search and download whatever they needed. Oh I’m just joking! The last sentence is not true. I had no idea how to publish my new content on the company website, so I sent it out as email attachments to the field.

One day, I met a coworker in the SMOKING ZONE of my office building. He was a programmer in the engineering org. Lacking any connection at work, I’d never met him at the office. We started exchanging notes about our respective jobs.

I happened to mention to him about my wish to build a portal for hosting marketing collateral. He told me that he’d heard about a tool called Microsoft Frontpage that enabled non-geeks to build simple websites by using a visual editor and drag-and-drop controls. As a power user of Microsoft Visio charting tool, I was familiar with this paradigm.

I went back to my office and tried Frontpage. Lo and behold, I was able to create my marketing collateral portal within a week without writing a single line of HTML code (which I anyway was not capable of).

At the time, Frontpage went by Rapid Application Development (RAD) platform. Today, it would be called low code / no code platform.

Going by this experience, I started wondering about the fate of coders.

3. Code Translators

In my next company, I used to sell a tool that would covert legacy COBOL code to Java. At the time, we used to call it Code Translator. I believe this product category is now renamed as Code Transpiler.

With code transpilers not only being able to translate code from one programming language to another but also clean it up compared to the original, the technology naturally raises questions about the need for coders – and architects and designers – going forward.

4. Workflow Automation

Over time, I’ve used workflow automation tools like IFTTT to automate many workflows e.g.

  1. As soon as I publish a post on the company blog, automatically post a link on Twitter.
  2. Whenever somebody engages with my tweet, automatically add them to a list called skr-engagers.

Again the question arose of whether these workflow automation tools would kill coders?

5. SAAS

Back in the day, companies bought onprem software and engaged tons of resources to build extensions, customizations, reports and fulfill other company-specific requirements.

Then came SAAS. Vendors virtually outlawed customization of their cloud versions.

As a result, SAAS decimated the requirement of coders (and business analysts) for implementing ERP, CRM and other enterprise software products. IT services companies had to slash headcount in enterprise software projects by as much as 80%. More in my post titled Indian IT – Crisis Or No Crisis?.

Around the time I published this post in 2017, I’d met an old coworker who was running a midsized IT company engaged heavily in enterprise software implementation. During our meeting, he was wondering if the end of coders was nigh.

6. Monitoring + Observability

By automating the end-to-end process of detection, triaging and resolution of incidents in IT landscapes, monitoring and observability platforms create doubts about the need for system administrators in future.

7. WordPress + Gutenberg

I recently used WordPress + Gutenberg Block Editor to upgrade my company website to responsive design. I did not write / edit a single line of code. Who needs coders, huh?

I call the aforementioned technologies DEMAND SUPPRESSORS. All of them were revolutionary when they entered the market and threatened to take away the job of programmers.

But none of them did. If anything, there are more coders now than ever before in the history of IT.

What gives?

I attribute this apparent paradox to the emergence of what I call DEMAND STIMULANTS. Comprising a bunch of new deployment models and usage scenarios, they created new coding jobs in hitherto unfathomed areas of computing.

More on this in a follow-on post. Watch this space.