3 ms·

> 1. You must earn respect before you trash the system This is a symptom of an entrenched workforce and quite a red flag. Juniors have to prove themselves - o

• nmcfarl 9y ago
  I've seen great CVs document excellent experience for poor performers. And I've also seen great coders dissolve before my eyes (in the face of personal problems) and turn into very poor performers that routinely caused short and long term technical problems. I don't think you just need to earn respect when you join an org - I think you need to deserve the respect you earn, and work to maintain it.
• notacoward 9y ago
  > This is a symptom of an entrenched workforce and quite a red flag. No, it's a sign that many domains are full of hidden constraints and pitfalls. For example, it's easy to nit-pick a distributed storage system (such as the author seemed to be working with) as too slow and complex, until you actually learn about the consistency/recovery/etc. corner cases that make a simplistic "just do this" proposals non-viable. You could say that's a failure to document the requirements or design. You could also say that people shouldn't need to document things that are considered baseline knowledge in their domain, and that maybe you do need to show some understanding of the complexity before you seek to do away with it (cf. Chesterton's Fence).