Re-thinking developer experience • Product @Gitpod 🍊 Helping folks get their start in cloud • @openupthecloud ☁️ AWS Community Builder 🛠 Replies in GIFS 😃
I also personally add "MoSCoW" ratings to my PR's. I've found since adopting this habit I've seen less friction in code reviews. Something about adding [COULD] or [SHOULD] before a comment seems to diffuse tensions especially when making slightly more pedantic requests, "trivialities" as you call them :). I think it's better to give the small comment but allow the writer to know it's optional / not that important then they are more likely to add it themselves in future.
I started writing software in 1984. Over the years I worked with many languages, technologies, and tools. I have been in leadership positions since the early 2000s, and in executive roles since 2014.
Nice article Lorenzo! :)
I also personally add "MoSCoW" ratings to my PR's. I've found since adopting this habit I've seen less friction in code reviews. Something about adding [COULD] or [SHOULD] before a comment seems to diffuse tensions especially when making slightly more pedantic requests, "trivialities" as you call them :). I think it's better to give the small comment but allow the writer to know it's optional / not that important then they are more likely to add it themselves in future.
Yes, that is a very good suggestion! Details like that matter!!