Five skills no course teach you, but matter more than your tech stack.

Franco Fernando is a software engineer and technology enthusiast known for his expertise in web development and mobile applications. Readers can learn about coding best practices, software architecture patterns, and emerging technologies. With articles, tutorials, and code samples, Franco Fernando shares  insights and expertise for building modern and scalable software solutions.

The Polymathic Engineer

Technical skills get you hired, but five non-technical traits determine long-term success as a software engineer: patience (debugging is inherently slow and iterative), determination (roadblocks are inevitable and quitting is always tempting), a student mindset (the industry never stops changing so neither should you), accepting criticism constructively (code reviews and feedback are growth tools, not attacks), and communication (explaining ideas clearly to humans is as important as writing logic for machines). These meta-skills underpin all learning and career progression, yet no course teaches them.

What Really Makes a Succesful Software Engineer

Thanks for sharing, Franco Fernando! Great read!
I totally agree with the necessity of those skills for SWE to be “good at it”.
I didn’t see much of it related to the “product” on itself so I would like to emphasis it a bit.
As a software engineer myself, I believe that communication holds a big place (maybe I would even go as far as to say “the biggest” place, but that would be presumptuous of me).
Because we’re not designing architectures and solutions and writing logic just to do it. We build a solution with an end-user in mind, a use case, or several! And as such, I believe it is primordial to be able to communicate seamlessly with the business to get a good understanding of “what is the goal, the intent” behind what I produce. And getting a hold of that specific intent, understanding the business and being able to adapt it into an architecture or logic, is what I believe brings the most value to a project and to the customer.
It doesn’t overshadow the importance of all the other soft skills you mentioned, as those skills altogether form the “starter pack” for personal and value growth.
Don’t be satisfied with being a developer good at coding, be a software engineer who builds designs, for the products!

Through well-structured sentences you comforted (prepared the newcomers) engineers who endured more moments illustrating each of your highlighted points.
Well done and thank you

As you mentioned in the post key concept is to be adaptable developer and consistently evaluate yourself by asking simple question what can I do better next time?