3 ms·

First I just wanted to say I loved the doggo and the general tone of the post. Also wanted to say that there's a lot of parallel between code reviews and "work

First I just wanted to say I loved the doggo and the general tone of the post. Also wanted to say that there's a lot of parallel between code reviews and "work review" in Investment Banking. Tooling aside, the underlying concept behind your tips is likely true for a variety of sectors, so I do wonder if one could dig a level deeper and find that essential truth in how to properly manage write-review workflows. Just some food for thought in case you want to jump into that rabbit hole.

mtlynch 6y ago
Thanks for reading! That's interesting about "work review" in Investment Banking. I've never heard that term and Google isn't helping me out much. Do you have a recommendation on where I could learn more? I have noticed that things like this aren't too far removed from other fields. When I wrote my article about reviewing code from the reviewer's side[0], I got feedback that most of the techniques apply to giving feedback in other domains. And while I was writing my guide to hiring writers,[1] I realized that the process is 80% identical to my process for hiring developers and graphic designers. The thing that's tough about going more abstract is that it becomes hard to convince any particular group that the content is worth reading. Focusing on code review appeals to HN because a large percentage of the audience is developers, but if it was a more general guide to improving review workflows, I'd have a harder time convincing HN readers that it was relevant to them. [0] https://mtlynch.io/human-code-reviews-1/ https://mtlynch.io/human-code-reviews-1/ [1] https://mtlynch.io/hiring-content-writers/ https://mtlynch.io/hiring-content-writers/