Would Github Copilot AI replace the Developers?

Less than a week ago, the GitHub Copilot (OpenAI) was released and with it, an old discussion resurfaces: will AI replace the workforce? In this specific case: will the copilot replace the developers?

I can tell you, without too much fuss, that this won’t happen soon. What we see, and which in my opinion should actually happen, is automating repetitive everyday tasks. That’s right! You know that Copy and Paste you do several times? Those parts of code that you type over and over without having to think too hard? So, this is where Artificial Intelligence must initially enter: “to assist the developer in repetitive tasks.”

No more repetitive tasks! The time has come to invest our day in other tasks like analyze logic, create new solutions, work as engineers that we actually are!

This technology, recently launched by Github + OpenIA, is being broadcast as a pair programming virtual assistant, a colleague who helps you write codes. This technology is really a very powerful weapon and one that must be used.

See how this works below. Basically, this tool, is still only available for integration with Visual Studio Code, uses learning from an open knowledge base, GitHub, and learns from your way of programming. It analyzes the initial comments you declare before starting your lines of code and it suggests code compositions that solve the problem. Based on your feedback, the copilot learns even more and improves its suggestions over time. Isn’t that great?

As the launch is very recent, OpenAI is making a registration, as a waiting list, and then authorize you to use this platform. If you are interested in more information, go to the official website at https://copilot.github.com/ and if you are interested in testing, register for the copilot waitlist. It promises to be a great ally.

But then, will this tool replace me in the future? Look, I really hope not and I am fully aware that for now, we are still suggesting solutions, providing opportunities for learning, evolution, and automation of small tasks. The next step, according to my crystal ball here :), is a more complete automation of code. But it will still need Developers able to tell it: where to place this logic…, how it is built… and mainly: for what purpose...

Those subjective questions, which translate a customer’s needs into a solution, will take a long time to be automated. I’m sure about that. So don’t lose focus and hope: study logic, understand the business, know how to communicate with both your client and your team and your job will be guaranteed for a long time.

Success in your career!!