AI writes code, but software engineers who think deeply will architect, guide and lead it.
No. The speaker says software engineers remain essential for three reasons: they understand AI under the hood, the models, data pipelines, limitations and risks; they use AI to build production-ready software that is scalable, reliable and maintainable; and they fine-tune models, optimize performance and improve usability, so the next generation of AI is still built by engineers.
It still doesn't understand the why behind the tasks it is given, and needs human input for real-world context and scenarios. It may not prioritize long-term business goals or assess trade-offs well. It is not reliable: it hallucinates and sometimes gives wrong answers. It also struggles to communicate and collaborate with human beings.
AI generates thousands of lines of code, translates between programming languages, creates user interfaces and fixes bugs. It excels at repetitive tasks and pattern recognition. GitHub Copilot completes code and fixes bugs for you, and ChatGPT can create an entire project within seconds. All these tools are available to anyone.
Master the foundations: data structures, algorithms and programming concepts. Think about systems like an architect and meet senior-engineer expectations as soon as possible, designing reliable and scalable systems. Go full stack and across disciplines such as design, product, data and project management. Practice communication and collaboration, use AI as a creative partner, and stay adaptable.
Think of AI as a brilliant junior developer you hire onto your team: it can do a lot of jobs very quickly and efficiently, but it is up to humans to define the vision, validate the results, and ensure what is being built is good for society. The strategic thinking stays human.
The statistics cited say 55% of developers today are starting to use Copilot, but only 30% of them accept the outcome without any changes. The speaker's reading: if you are not in the 55%, you are not using AI and you are in trouble; if you are in the 30%, you trust AI too much.
Understanding what the user needs, collaborating across roles, and making tough decisions with empathy and responsibility. Engineers are not just task executors: the best engineers are not the ones who code the fastest but the ones who think the deepest, taking messy problems and guiding machines toward structured, meaningful outcomes.
No. The speaker says the days when a software engineer could focus on either the front end, the back end or the database are gone, and the future of software engineers is all full stack engineers. You should also get into design, product, data and project management, and be prepared to wear multiple hats.
Just last month, the CEO of GitHub said that the future of programming is natural language. The speaker comes back to that quote near the end and says it is not reality yet: it is still up to software engineers to improve AI and make it happen.
Asked to create a project, a dating app like Tinder in Python, ChatGPT within seconds created a complete application with user profiles, the swiping logic, and even a sample database. The speaker jokes that the only thing it did not do was find him a date.
“Just last month, the CEO of GitHub said that the future of programming is natural language.”
“The only thing it didn't do for me is find me a date.”
“But if you are in the 30%, that means you trust AI too much. You may be in bigger trouble.”
“And you can think of AI as a brilliant junior developer that you hire to your team,”
“The best engineers are not the ones who code the fastest, but the ones who think the deepest.”
“We're actually building the future intelligence itself.”
“Learning Software Engineering During the Era of AI | Raymond Fu | TEDxCSTU.” https://www.youtube.com/watch?v=w4rG5GY9IlA. Transcript summary by WhipScribe, https://whipscribe.com/transcript-pages/learning-software-engineering-during-the-era-of-ai-raymond-f.html.