Show HN: My book for programmers called “Junior to Senior” was published today (opens in new tab)

I do understand the appeal of an online reader but you should perhaps consider making your work available in a number of different channels to suit potential buyers' preferences (i.e. you are probably leaving money on the table by only having an online reader option).

I think learning to identify how engineers could improve, and being able to successfully help them, is a big level-up. Departments will want to trust their seniors to do this proactively - rather than say, just when questions come up - as this helps foster a healthy team with everyone growing.

One other point comes to mind on impact - as this is often seen as a key differentiator for senior engineers. It's good to see the section on improving processes in your book, as this is a nice way to add a lot of value. Another way to make an impact is keeping a close eye on product delivery and cycle time, and identifying any problems. For example, is work getting released often, or is it getting stuck in 'nearly done'? Are there frequent blockers to builds or deployments? How is cycle time looking recently, and are there any lurking issues where work is getting blocked frequently? How do we work around this current setback - is there a short term solution to keep things moving while we work on a proper fix? Are we currently on track for delivery?

Managing complexity is another area which can be tough to navigate as a new senior.

Just some thoughts which came to mind, as we all see things from a different perspective.

Overall, I really like the focus of the book. We need more of this stuff and this will help a lot of people, so kudos on the release!

>> "Senior" will vary depending on the size of company and the scale of problems it deals with.

No matter what company you work for, your role is in a specific context, typically within a group or working on a project. And it's not the scale of problems the company deals with which makes you a senior developer. It's the scope of your assignments and the breadth of knowledge and experience which it takes for you to be able to tackle them.

This book claims to give you the keys to unlock the skills you need to reach the "Senior software engineer" level.

It doesn't tell you it's not for large companies and it doesn't tell you that the "Senior software engineer" level he is talking about may meet the expectations of one class of company but not the other.

The target is specifically "ambitious" software engineers. I'm fairly certain that ambitious software engineers are many to have FAANGs as a target.