Timeless advice for any software engineer!<p>The one thing to add (related to 1 and 3) is:<p><pre><code> *do not focus completely on the technology. learn what's around it also*.
</code></pre>
I once worked for a company where 1 week/month the managers would work in 1 department (as regular team members). With the hands-on feedback, they would improve the process/team/business. Needless to say, that company was making profits in the 2008-2009 "dark-age period".<p>The main lesson for me is that software is the business where you learn about & improve other businesses. The value is that you get to understand better the world (business) around you. That way you can avoid building "innovative products" that no one needs.
<i>1. Look for jobs that will let you program. ... You want your job title to be ‘software developer,’ ‘software engineer,’ ‘programmer,’ ‘coder</i><p>Followed by<p><i>Goranka Bjedov is a capacity engineer </i><p>Hmm.
Reading code always worried me. That was always my biggest deficit in school - I couldn't just pick up someone else's code and dive in, it took a lot of effort to understand anything more than the most basic code.<p>Of course, now I'm not in a programming job, so I can only imagine I've gotten worse.
in fact, these are valuable lessons for any position. Specially, the last one.<p>1. Look for jobs that will let you <do whatever you want to do>.
2. Don’t give up on becoming <whatever you want to become>.
3. Learn how to take charge of your career.