Remix.run Logo
▲ paulryanrogers 5 hours ago

I wouldn't say reviewing is _very_ different. Someone who can review well can almost certainly imagine and type up similar caliber solutions.

Someone who can imagine and type up good solutions, can review the work of others.

IME good reviewers may be a bit better about being gracious with minor differences in opinion/style and managing emotions and politics of everyone involved.

▲christophilus 5 hours ago | parent [-]

No, I think it is different. My eyes glaze over and my brain turns off when I read code. I find it really effortful, unless I'm particularly interested in it (e.g. reading an interesting paper or Code Complete, whatever). When I write code, I'm in the flow, and it's almost effortless.

▲techdmn 5 hours ago | parent | next [-]

Writing code has always been easier than reading and understanding code (for the majority of people). A common failure case in the old days was an engineer who would go around rewriting things all the time, because they couldn't read and understand the code the team had already built.

▲springtimesun 5 hours ago | parent | prev [-]

It’s definitely different. This was my experience as well. I had to make myself sit down and learn how to review almost the same way I learned to write code in the first place. All the little things I found about coding were there just in different places. Best time of the day to do my most focused work, how to order tasks so I could rest in between will still moving things forward, tools (they are different and like your coding editor setup they benefit from customization), git (I thought I was ok before but it’s a different set of commands I reach for now), the list goes on.

Being a good reviewer takes reps and practice just like writing.

The thing I really miss is the flow state. That is elusive for me so far. I can’t even listen to my coding music. I need silence.