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..
>I always start a convo with a question, " what is exciting in your life?"
Sadly, nothing. Stuck on 2 part time jobs, I see more layoffs than job posts, I'm about to be soft evicted from my current dwelling, and my country decided to start yet another needless war.
That question works in good times in a high trust society. Now it just reminds you how little there is to look forward to.
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.
Every good engineer is an excellent communicator. Everyone who is not an excellent communicator is not a good engineer. Everyone hates that this is true but it remains true. A lot of people are very good programmers who have mistaken that for being good engineers, however.
And this is the determining factor to whether a current dev will be replaced by AI or will evolve alongside with it, being the bridge between humans and AI.
Which is not really different to what we're already doing, translating human requirements to machine code. Just that communication skills will become an even bigger part of the job.
Not knowing what's your workflow, Wouldnt this be possible in future for cowork, to read the financial documents and derive insights and build reports and you build your workflow ?
Posts like the one above you just show me how clueless people are who deal with production of software everyday but have little to no idea about the jobs of others outside of their realm.
I find it interesting that we already have patterns established, while agentic approach is still being adopted in various industries in varying maturity.
At some point, we need to begin. My initial thought was that this is a growing and evolving resource, primarily for my own use. We are slowly but steadily learning what makes sense annd patterns emerge. Also, if others find it interesting and contribute, that would be even better.
