Deep Work by Cal Newport is a must-read for knowledge workers that struggle with focus, concentration and output. Even more nowadays, when COVID-19 imposed a work-from-home policy to many, forcing us to work from a generally distracting environment – our own homes. The book is written in a bit lengthy, but unambiguous and easy to read style. It doesn’t have any groundbreaking discoveries, yet the clear structure and intelligently gathered facts convey the point very effectively – Deep Work is needed for long-term success in many knowledge fields. (more…)
Atomic Habits by James Clear was recommended to me by so many people, and was so highly praised, that I was afraid my elevated expectations will leave me disappointed when I finally read it. This couldn’t be further from the truth! The book just resonated with me (and with lots of other people judging by the positive reviews in Amazon, Goodreads, etc). Style is clear and straight to the point. Action-packed read where I wanted to highlight half of the book as “important” to review later. Atomic Habits should definitely make your reading list for the coming months. (more…)
Every once in a while you might encounter a flaky unit test. I know, unit tests can’t be flaky by definition … but also life comes in the way, so sometimes it happens. Such a test will consistently pass on most developer machines, but fail in a CI environment every once in a while. In this post I’ll share how I go about fixing such problems.
Most of the world is told to stay at home. Many IT companies are working remotely and are introducing changes / reduction in working agreements and hours. If anything, this has freed-up extra time for a lot of people. What better use of it than to sharpen your skills, catch-up on great learning materials and prepare for the rainbow coming after this
storm virus? Here are some of the resources I can’t wait to indulge in this #StayHome April.
I’m a firm believer in the practice of code reviews. When done correctly it can significantly improve the quality of software and is among the most effective knowledge-sharing tools in a team. In the previous article I shared a few tips how to create a great pull request. Following them as a team will make everyone’s life easier, so keep them in mind at all times. In this article, I’ll focus on effectively reviewing PRs.
TL;DR — Be nice! Your attitude and approach will be mirrored by your peers when they are reviewing your pull requests! Remember the common goal of your team – to achieve business value while writing great code you will be proud of.