@jahirsheikh8 Writing thousands lines of code is a commodity nowadays if you know what you are doing. Now soft skills are much more important if you want to get people use your stuff.
The leading AI company learning how the biggest challenge in computing is not computers or AI: in the end, it's always: people
More specifically, communicating with other people.
(In software engineering you learn this sooner or later fwiw, or at least I did)
A CHINESE STUDENT BUILT AN AI IN 10 DAYS, MAPPED A UNIVERSITY SCANDAL INTO 352 SOURCES, AND WOKE UP A CEO WITH $4.1M.
One click gave a full summary. One question predicted exactly how public opinion evolves next.
@RoundtableSpace I think it is one of the best use case of AI I have ever seen. If that student tried to do that manually it would consume too much time and probably he would fail because of that.
You might believe you should spend less time thinking about code because of AI.
I strongly disagree! We’re watching this play out live where tons of AI generated code becomes a liability.
At the end of the day, an engineer needs to be responsible / on call for code that gets shipped to production. If you don’t understand the system you’re trying to debug, you’re probably going to have a bad time.
Yes, AI can help with all of this, if you set up the proper systems. You can have agents triage prod logs, look at errors, etc. You can speed up parts of the investigation, but an engineer needs to make the call. There might be serious customer or financial implications from that change.
I expect the trend continue for trimming dependencies, vendoring code so you can modify it directly, preferring simpler systems with fewer abstractions, and spending waaaay more time thinking about system design and code maintenance.
I’ve said this before, but it’s a great time to get familiar with CS fundamentals and some of the history behind what great software looks like. Many parts will be different in the coming years as AI progresses, but also a lot more than people realize will stay the same.