What are some technical books that changed the way you think, brought you to a much better understanding of an idea or you think are quintessential for every software developer?
I am trying to find some books to help me improve.
This is the highest value to time spent read that you will ever experience for programming.
If you read through the rest of the guy's justification for these points (by clicking the headings and then if you want more trawling through older blog posts) you will start to see the matrix.
You might have taken a class that said "high coupling in your software is bad," but it's an entirely different experience to see the common patterns that result in high coupling (or the violation of scopes via accessing global state etc) and pragmatic ways to re-write them.
Making programs a recursive 2 steps per object life time (lifetime of server, lifetime of request, etc):
1. Draw the object graph by instantiating objects of the current lifetime and giving them references to eachother
Feel free to adjust the date range for recency. When I was young, it took me a while to learn that 'newer' did not necessarily mean 'better', but also note that a lot of initially 'great' books didn't age well.
* The DevOps Handbook - Lots of tactics for improving the productivity and effectiveness of engineering teams
* Extreme Programming Explained - Solid guide to agile ideas
* Staff Engineer and The Manager's Path - Helps you understand your career path and the expectations that come with positions like Tech Lead, Staff Engineer, Engineering Manager, etc.
This is the highest value to time spent read that you will ever experience for programming.
If you read through the rest of the guy's justification for these points (by clicking the headings and then if you want more trawling through older blog posts) you will start to see the matrix.
You might have taken a class that said "high coupling in your software is bad," but it's an entirely different experience to see the common patterns that result in high coupling (or the violation of scopes via accessing global state etc) and pragmatic ways to re-write them.
Making programs a recursive 2 steps per object life time (lifetime of server, lifetime of request, etc):
1. Draw the object graph by instantiating objects of the current lifetime and giving them references to eachother
2. Call run(), which executes the object graph
Felt like an epiphany to me.