4 ms·
Not OP, but fwiw I think there are 2: Having the communications skills and domain knowledge to understand what problem needs to be solved and why, and having th
by Raidion 3y ago
Not OP, but fwiw I think there are 2: Having the communications skills and domain knowledge to understand what problem needs to be solved and why, and having the technical skill to do that in the most direct manner that closely matches those constraints.
Sometimes you need to get better technically, sometimes you need to get better at figuring out the problem (solving the wrong problem isn't worth a lot. regardless how "clean" it is). Sometimes you need to get better at figuring out what you need to get better at.
- matthewfcarlson 3y agoI’d add the ability to communicate that problem to your first pillar. Code reviews are really just a forum to discuss and communicate the solution to a specific problem