zlacker

It has only been in recent years that I have even been able to articulate what the issues are with the code of some junior developers. I was fortunate to find "Semantic Compression" by Casey Muratori and now I have something I can point to and language to use. Before that, junior devs may have perceived the feedback as either an undue imposition of my taste, intimidation or (if any of them had ever been a woman) toxic masculinity.

Should we refrain from giving feedback before we have fully articulated the principles by which we would like our code to be written? What about the abundance of tacit knowledge that we can only hope others to learn by osmosis?

>>mbar84+(OP)
> Should we refrain from giving feedback before we have fully articulated the principles by which we would like our code to be written? What about the abundance of tacit knowledge that we can only hope others to learn by osmosis?

I think these are fair questions. Reflecting back on a younger and more arrogant self, I can see that I was quite more pushy with my opinions. And they were that, opinions. Having them challenged when I was no longer the best coder in the room was how I grew, but that required speaking in clear language, and having clear arguments. I think the sooner you learn to do this, the better, and it might challenge some bad ideas that you've held dear.