←back to thread

628 points kiyanwang | 1 comments | | HN request time: 0.21s | source
Show context
arkh ◴[] No.43629835[source]
> The best devs talk to principal engineers and junior devs alike. There is no hierarchy. They try to learn from everyone, young and old. The newcomers often aren’t entrenched in office politics yet and still have a fresh mind. They don’t know why things are hard and so they propose creative solutions. Maybe the obstacles from the past are no more, which makes these people a great source of inspiration.

That's how you can work against the normalization of deviance. Never dismiss new people commenting on what you may doing wrong for no reason. Yes, you've been doing X in an unusual way and no accident happened still; but there's a reason you should not do it this way and it may cost a lot to relearn it by experiencing it.

And same thing with old rules for which no one has an idea of why they exist but are still followed. Any rule should have an explanation for its existence and their relevance checked periodically.

replies(1): >>43630740 #
1. muzani ◴[] No.43630740[source]
Personally, I think the newer ones ask better, curious questions. The more experienced ones know when not to follow common practice.

Things change really fast, more so with AI tools, so it's important to have people question why we do it a certain way.