by dglass on 10/11/22, 3:18 PM with 38 comments
I truly believe that soft-skills are what makes the difference between a good programmer and a great one. I also believe that anyone can learn the soft-skills needed to accelerate their programming career.
I wish I’d had better resources to learn these things in the early years of my career and I’m hoping this book will become a useful resource for the next generation of programmers to build successful careers.
What this book covers:
Choosing a career path: generalist vs. specialist
What makes you a senior engineer?
How to deal with feeling like an impostor
How to build trust and work with your manager
How to recover when you make a mistake, and what to do during incidents
How to ask better questions
How to read and understand unfamiliar code
How to add value to your team and company
How to identify and manage risk
How to deliver better results
How to communicate more effectively with both technical and non-technical audiences
The importance of a healthy work-life balance
How to ask for a promotion, and how to prepare for it
I wrote this book because these soft-skills are rarely taught in coding bootcamps or computer science degrees, yet they are critical to every programmer’s career trajectory. Almost every programmer I know, including me, had to learn and develop these soft-skills on the job. It took hard work and a lot of trial and error to learn how to communicate my ideas effectively, navigate office politics, manage risk, and so many other things that programmers encounter in their jobs today.
Get instant lifetime access at holloway.com. Use this link for a launch discount:
[0]: https://www.holloway.com/b/junior-to-senior?vip_code=JTSLAUN...
by mooreds on 10/11/22, 3:52 PM
And we need more on this topic to help more developers get better at building software faster. (The tech is part of that, but so is the communication.)
So, again, congrats!
by gtirloni on 10/11/22, 4:28 PM
by WarChortle on 10/11/22, 4:46 PM
by Simon_O_Rourke on 10/11/22, 6:47 PM
I would be interested to know how you found self-publication? What did you use to write it, and where did you market it apart from HN?
How many are you hoping to sell?
by swyx on 10/11/22, 6:53 PM
by ArcMex on 10/11/22, 3:29 PM
by labarilem on 10/11/22, 4:39 PM
by redleggedfrog on 10/11/22, 8:28 PM
by reidjs on 10/11/22, 4:28 PM
by mattcristal on 10/12/22, 1:03 PM
Once the Kindle version will be available I will buy it!
by dashtiarian on 10/13/22, 6:35 AM
by manv1 on 10/12/22, 5:08 PM
A senior reads an API to figure out what can be done.
That there one the major differences between he two.
by thedangler on 10/11/22, 9:03 PM
by oidar on 10/11/22, 5:48 PM
by luisegr149 on 10/11/22, 6:40 PM
by iLoveOncall on 10/11/22, 4:44 PM
"Years of experience" VS "Technical ability" is at best reductive, at worst completely wrong.
I encourage you to look at large companies and how the levels are defined (https://www.levels.fyi/blog/amazon-leveling-progress.html here for example, for Amazon) and the nuance that there is.
The different parts you cover are commendable ("How to build trust and work with your manager", "How to ask better questions", etc.), but they are bare minimum requirements for an engineer that has a couple of years of experience, they're not what is needed to reach the senior software engineer level.
Junior to not Junior anymore? Sure. Junior to Senior? I don't see it.