Reddit mentions of Becoming a Technical Leader: An Organic Problem-Solving Approach

Apprenticeship Patterns is a good read for developing a positive attitude toward your work and career.

Becoming a Technical Leader isn't necessarily for people later in their careers. I gained a lot from reading it during my first internship.

Anil Dash's blog has some posts on important topics like diversity within the tech community.

What I've linked above help with the attitude side of 'soft skills', which I think is the most important part. The interpersonal skills come with time, practice, and being mindful of how your communication and behavior affect others.

Edit: Here's another post on how to be assertive and nice.

Radical Candor is good. Extreme Ownership also. I had an old CEO recommend Wooden, by John Wooden, but I didn't get a ton out of it at the time.


https://www.amazon.com/gp/product/0932633021/ref=ox_sc_saved_title_4?smid=ATVPDKIKX0DER&psc=1 Becoming a Technical Leader came highly recommended to me, but I haven't gotten into it yet.

I guess I'm old, but Gerald Weinberg was a huge influence on my development as a programmer and an analyst.

The Psychology of Computer Programming, written in 1971, is still relevant today, even if the coding examples are ancient.

Becoming a Technical Leader was a huge influence on my personal development.

Finally,the Quality Software Management 4 book series belongs in every manager's and developer's library.

Disclaimer : i'm not a recruiter, so my opinion is just that :)

Here are my reactions while reading your resume :

• The only bad thing in your resume, for me, is the general tone of the experiences description. It's a little "smug" (i don't know how to say it).
  
  If you want to shine, that's a thing, but don't crap on others.
  
  "Without direction", "the architects didn't know how to do that but i
  did", "1980 Fortran era" etc.
  
  I would rephrase those with only positive things. You did good things, that's all there is.
  
  
• if you want to be hired as a senior, you should show more examples of how you can lead and make juniors grow.
  
  I see that you made a presentation for all of your team, that's cool. And you helped recruit, also cool. That should be more emphasized, and you need to show more of that.
  
  
• TradeWithMachineLearning.com is down. I didn't see at first that you mentionned it because it's a bit hidden.
  
  Now that the project is defunct, you should put your sources on github and add the link in your resume.
  
  
  
• misc stuff :
  
  You listed C# as a language you own, and yet you put it in the "i want to learn these" section as well.
  
  BTW i like this section, it's a good idea. Add a link to a github account with your fiddlings in these languages / frameworks and that's a winner.
  
  
• Because i like to share cool resources, here's the best book in the world if you want to become senior/lead dev : Becoming a technical leader

Book Recommendation