3 ms·
It's an anti-pattern to call abrasiveness an "engineering" habit. It's an orthogonal axis. "saying things are 'unreadable' or 'bad'" is not efficiten -- that's
by gowld 8y ago
It's an anti-pattern to call abrasiveness an "engineering" habit. It's an orthogonal axis. "saying things are 'unreadable' or 'bad'" is not efficiten -- that's not actional feedback. Skip the "this code is bad", and the unsupported univeral claims of "unreadable" (obviously the author and the compiler could both read it, and get directly to the point of your concern with the code -- this code has a logic bug, or is inneficient, or you can't follow the changing state or don't know what this variable refers to, or what have tou.
- tashian 8y agoI agree. I think talking about code is a critical skill, but not everyone has a strong practice of doing it. When I was first learning to code I never had anyone to talk to about my code, so I didn't get to learn the vocabulary until later.