Welcome to the Weekly Technical Leadership summary — the articles I read (and shared) this week and more. I normally share ~10 interesting articles every week; follow me of Linkedin if you want to receive notifications.
What I have been reading
How many management books could you recommend? Me, not many. Most of them feel like dumbly selected collections of the most forgettable blog posts on the subject, with probably 1–2 decent ideas followed by 150 pages of nothing.
However, I really enjoyed Managing Humans by Michael Lopp. I feel like I can relate with his contents, and that’s probably because Michael is also an engineer who treats management (i.e. people and organizations) like a developer would do: analyze, understand, see and document the patterns, and provide recipes to fix it.
The book lacks a bit of cohesion, and that’s probably because it’s a collection of his blog posts; but being a developer, he provides great insights on how developer think, work and how to deal with them.
If you like Michael’s contents, you have to join his Slack channel. It’s a community of several thousand of engineers with hundreds of discussion happening at every given time. I regularly hang out there, although I can’t keep up with all the activities! Here you find how to join it.
Topics I talked about this week
Devops Awesome learning on Github is, as the name says, awesome. So many links and resource to learn all about tools, principles, and practices.
I do talk and write a lot on Kubernetes; it’s, to me, a fascinating technology with great potential, but at the same time a difficult one to master (hence the many links). This week I posted
- What Your Kubernetes Security Checklist Might Be Missing
- IBM Kubernetes Learning Path: this is now favorite K8s learning resource together with Kubernetes the Hard Way; but also check Katacoda’s labs on the topic as they are very promising
I particularly enjoyed Migrations: the sole scalable fix to tech debt. What I mostly liked is the idea that migrations are part of the successful life of a product, rather than a result of its failure. Good product go through iterations in which the creators develop simple solutions to customer needs; as the customer base grows (and developers learn from them), new solutions are developed and migrations become necessary. I much rather prefer this path to the boil the ocean approach where you try to build the most scalable, flexible and complete solution at the first attempt.
Hiring Developers at Smart Pension, a no-nonsense process to hire developers that focus on what’s important to find in your next employee.
A couple of good links on Event Sourcing
- Event sourcing essentials you need to know when starting out
- (Video) Commander: Better Distributed Applications through CQRS and Event Sourcing
- (Video) Designing Events First Microservices