So, the reviewer made some comments on a code review and what? Is it clear to your team what happens afterward?
Author: Bartek (Page 5 of 5)
Well just Bartek, you're a wizard
In his “Clean code” Uncle Bob univocally condemns boolean arguments.
Recently I’ve come across my Ruby code from 13 months ago. The code regarded my very first task in a project, while I was about to leave the project. Those 13 months were enough to spot right away that the code was, well, bad.
I might be the only developer in my company enjoying code reviews (from both sides, actually). On reflection, the main reason for that is that they make a great opportunity to learn something new. Which is cool, even if it’s someone else’s point of view on programming.
People are so excited about working remotely.
My experience is 4 month of working remotely on daily basis a few years ago, plus an occasional home office for the last 2 years. It’s enough to realize that it’s not my thing. At least when speaking about working from home, which doesn’t exhaust the possibilities.
Comments are always failures.
What a perfect example of a wise sentence (by Uncle Bob) that feels wrong when taken out of context.
(See continuation – 10 more communication quick wins for developers)
I like a quote from Uncle Bob:
…other than health & look.
Recent Comments