Eduards Sizovs:

People rarely talk about it, but in many companies, code review makes developers feel like sh%t. This is a practical guide on how to create a code review process that developers love.

Click through for 8 recommendations from Eduards on making code review an effective, encouraging, and positive activity.

Some of the particulars in this article don’t feel relevant during the coronavirus-lockdown phase of history, but the overarching message is solid:

Companies waste millions on building the environment they think makes developers happy, without understanding what actually makes developers tick.

What does make developers tick? What motivates us? The answers aren’t always the same, but they often aren’t all that different either. Eduards argues that autonomy, mastery, and purpose are at the heart of it.

This post by Eduards Sizvos is loaded with wisdom:

You can escape this crazy hiring race by creating an environment, where experienced developers mentor less experienced developers. Hire for attitude, and teach technical skills. Be the company that says: we are hiring mentoring.

This pairs nicely with our mentorship discussion with Emma Wedekind and next week’s Go Time on hiring and job interviews.

Eduards Sizovs shares advice that changed his life, how that advice helped him to remove all framework books from his bookshelf and in the process shrank his “guilt pile” of books to read from 50 to 0!

Time is the most precious resource we have. Time is limited, nonrenewable and you cannot buy more of it.

Technology, like fashion, is changing at the speed of light. To catch up, we need to run very fast. This race has no winners because it has no end.

Fast forward to the advice part and Eduards shares this from a conversation between with his mentor…

Mentor: “Technologies come and go, but it has a lot in common. Set priorities right. Invest 80% of your learning time in fundamentals. Leave 20% for frameworks, libraries and tools.”