3 ms·
What's important is that people have the shared language of Clean Code (or some other repository of best practices, could be integrated into your company styleg
by phendrenad2 4y ago
What's important is that people have the shared language of Clean Code (or some other repository of best practices, could be integrated into your company styleguide, for instance). I.E. If Uncle Bob said "Don't do X" then we can have a conversation in that context if, in this scenario, doing X is acceptable. Without that logical reasoning, people will debate the very existence of "not doing X" as a best practice.
- DanielVZ 4y agoExcept having these discussions is really hard. It ends up being you against uncle bob and you are not gonna win that argument against a senior-er engineer.
- leftbit 4y agoDon't think so. If the senior engineer is worth his salt he should know that programming is always about finding a balance between several aspects of a given problem - some of them technical, some of them human. As long as the code does what it's supposed to do the rest is mostly up to personal taste - so yes, you can have an insightful discussion, but there's only to learn, nothing to "win" for all participants.
- DanielVZ 4y agoYep, but in practice Seniority comes either from experience or time in the industry. So you'll undoubtedly meet seniors that won't try to find that balance.