I’ve been thinking lately about how I should develop myself to future-proof my knowledge as a software developer.
In the past couple of years, the industry has changed so much that I struggle with the thought of self-development that makes sense in the long term.
In the past, learning and knowing programming languages, frameworks, memorizing them, and knowing what to use when and how to do it efficiently had value.
It still has value, but with AI, we don’t need the muscle memory anymore. Also, the skills we need, because of AI, are so short-lived; it does not make sense to invest in tools unless someone is already on a project, knowing what language, framework, and tools are going to be used.
It has both a good side and a dark side.
Good, because AI helps so much; sometimes it feels like cheating. Basically, AI can teach us how to use new tools. We just have to confirm the directions about code changes, and AI can figure out the rest.
We have to understand that the AI-written code is doing what we asked it to do.
It is more of a communication challenge than a technical one.
On the dark side, how do you sell your value on the market? How can you invest in yourself so you have an advantage over others in the job market? And how much does it trigger someone’s impostor syndrome?
In the past, I enjoyed diving deep into technical details. Reading through documentation from start to finish, like a book, while also playing with the code to follow the documentation.
It worked out for me well. I always had work to do and always knew how to solve issues to meet business needs.
I still know, but it is more like collecting details about a project and delegating programming to the AI. Once it is done, I am like a quality gatekeeper and a DevOps after that. Also a tester.
On the job market there is also a challenge that some companies are investing heavily in AI, while other companies are refusing to adopt.
And the job interview will be the total opposite between the two.
While an answer is good in one interview, in the other it falls on the total opposite and fails you in the interview.
How do you know what to answer?
Is there a good answer at all, or is it all about the chemistry now?
Do we spark each other?
Can we communicate well while having a good time during the process?
Is it all about communication once you reach a certain technical level?
What is your experience and opinion?
You can read Part 2 about the direction I am taking here.
