Polymath Engineer Weekly #15
Just open some more tabs and enjoy the reading.
Links of the week
Some people let the DRY philosophy go too far and create a bunch of leaky abstractions on the systems they work, only to avoid typing a few keystrokes.
Our code needs to be easy to change more than it needs to be generic for problems we don’t have.
Network partitions are some of the largest sources of nasty bugs on distributed systems. When dealing with a permissionless network, things get a lot harder to reason about.
I have not read the Gasper Protocol paper, but after this deep dive I think it is worth the effort.
After some years designing systems with stability as a requirement, I see how being conservative with dependencies may influence the maintainability of software in the long term.
“The essence of DOP is that it treats data as a first-class citizen. It gives developers the ability to manipulate data inside a program with the same simplicity as they manipulate numbers or strings.“
Customers don’t buy products because of bullshit marketing strategies, they put money on companies that solve their deepest problems. The JTBD framework is an interesting approach to monetize on those needs.
“Therefore, we can improve reliability by increasing the time between failures, decreasing the time-to-detect or time-to-repair, and of course, reducing the impact of the outages in the first place.“
Developers should read this and assess where the company they work is positioned on this down market. With so many layoffs lately, maybe it is a good time for you to look for a new job instead of being fired from surprise.
Book of the week
The Manager’s Path
This is a great resource for all career levels. With this book you can understand where you are, what responsibilities to expect and how to get to the next step based on what you want.
Do you have any more links our community should read? Feel free to post them on the comments.
Have a nice week. 😉