agreed and One thing resonated for me in this article was code reading would be great skill to have. reading a lot and thinking a lot will help drive AI to the destination effectively.
I always start a convo with a question, " what is exciting in your life?" - it brings out good things out of people and positivity to the conversation that is following... It brings in perspective. My past leader once said, "understand the people first before you start to work with them"... it is what I believe is missing.. trying to learn about people around us and sometimes taking a chance and strike a conversation with a stranger.. we will learn a great deal even from a small talk..
Great article. Moment I finished reading this article, I thought of my time in solving a UI menu problem with lot of items in it and algorithm I came up with to solve for different screen sizes. It took solid 2 hrs of walking and thinking. I still remember how I was excited when I had the feeling of cracking the problem. Deep thinking is something everyone has it within and it varies how fast you can think. But we all got it with right environment and time we all got it in us. But thats long time ago. Now I always off load some thinking to AI. it comes up with options and you just have to steer it. By time it is getting better. Just ask it you know. But I feel like it is good old days to think deep by yourself. Now I have a partner in AI to think along with me. Great article.
One of thing I have noticed of good software engineers is while they are trying to solve problems, they also communicate with clarity to upper management chain. The clarity they bring to the table was always appreciated and also puts them in the career growth path easily.
To use a tool well, you have to understand how the tool works rather than outsourcing everything.
Good athletes know how their muscles work, good racers know about the springs and tires, and same goes for coders.