I’ve seen many people asking on the internet whether ChatGPT will take over the jobs of web developers. Let me share a small story of my own. In 2007, when I joined Kashmir Corporation as a graphics designer, the company had already adopted computers.

However before adopting computers, the company faced strong opposition from a few employees who opposed the technology. They gave baseless reasons and excuses like “If the company adopts computers, many of us will soon be jobless,” but after counseling, they understood that computers were not there to replace them, but to help them work more efficiently.

Similarly, when ChatGPT arrived in the world of technology, many developers started fearing it, just as the employees at Kashmir Corporation once did.

I recommend using ChatGPT as an additional tool and using it to write better code.

Remember the rubber duck concept? It’s a concept where programmers have had the experience of explaining a problem to a rubber duck, and then hitting upon the solution in the process of explaining the problem.

Think of it the same way. You can talk to ChatGPT like you would explain a problem to a chatbot who is really good at solving problems. Ask it about how to integrate firebase or how to secure your app from hackers, and it will give you awesome suggestions with examples that a rubber duck couldn’t.

Although it’s impossible for ChatGPT to take your job, let’s assume that in 10 or 15 years, ChatGPT or other AI’s may be trained to the point where they can write small-scale applications. This could potentially take the jobs of some developers, but it will also open up tons of jobs for writing more complex code, which these AI’s can’t do.