Welcome to a new monthly series on the blog. In the monthly digest, I will share articles and blog posts that I have read during the month that I found interesting and worth sharing with you!
In the article Don't hire for top talent, hire for weaknesses the author really made me realize there is a different way to look at hiring new people. At companies, we always try to make sure we get the most talented engineers. But what if we hire with the mindset to make sure the teams we already have will be stronger?
Instead of “how can we find the smartest people?” think about “how can we find people who will make our team stronger?”
The article explores the benefits and downsides of both talent-oriented hiring, and weakness-oriented hiring. In general, it is a great in-depth article that really made me rethink the way I see hiring.
The article Understanding bandwidth by Padmini Pyapali explores your mental bandwidth. Mental bandwidth is described as your capacity to execute difficult tasks. There are some hands-on tips on how you can protect your own mental bandwidth, and help you preventing burnout.
A more practical thing I have been trying lately is to be less negative. A fun and interesting challenge that I found is the No complaining challenge by Jon Gordon. It is a great way to bring some more positivity into your life, and how to turn the negative energy around into something positive.
Atomic Habits is a book that is on my to-read list, and I am seeing it appearing on blog posts lately. A great post by Katherine Peterson on how reading Atomic habits can make you a better developer. The blog post dives into the main takeaways of the book and gives you some great insights into how you can use them to become a better developer.
Something that popped onto my feed while I was writing the most important skill for a developer to master. Is an article about setting explicit help timeouts by Shawn Wang. Shawn shares a story of how a task that was supposed to last 1-2 hours, took up 2 weeks of his time. The article explores the idea of setting timeouts for your help requests so you prevent letting a task spiral out of control.
One of the most important pillars of a high-performing team is psychological safety. Without psychological safety, a team will be limited in what it can achieve. David Burkus really dives into How to create psychological safety on teams. He shares 4 methods of creating psychological safety and gives some great examples.
While doing some research on how I could improve the guild meetings we were having internally, I found this article on Google. Getting your guilds going has some great tips on how to start guilds, and how to tackle to most common obstacles you can face starting guilds.
If you are interested in keeping up to date with the monthly digest, consider signing up for the newsletter to never miss another post!