We can all learn new stuff from each other at any seniority level, perhaps the amounts may differ, that's all.
-
-
I learn a helluva lot from less experienced devs every day. Software engineering is not a single axis of improvement.
2 replies 10 retweets 86 likes -
watching the spark of insight on the face of a less experienced person learning something new is one of the greatest things you can experience 'at work'. I hope everyone learns to appreciate it.
2 replies 4 retweets 64 likes -
Explaining something to someone asking the questions from inexperience is also a good way to challenge your existing view, or relearn/refresh. Certainly not a negative or unproductive thing.
4 replies 4 retweets 29 likes -
Quite often the allegedly "junior" developer knows things the senior dev doesn't. "Oh that's easy let me show you" quite often doesn't pan out because of some context the senior dev didn't have but the junior dev knew in their bones.
3 replies 6 retweets 32 likes -
A really good example of this is the number of "senior" devs at big companies who have very little mental model of how the normal github workflow works. While brand new devs know very sophisticated workflow concepts simply because they were exposed to it.
4 replies 8 retweets 49 likes -
The normal reaction from senior devs is "those kids are just reacting to the hype train" which can cost years of not upgrading companies to more standard, more robust workflows than they're used to. This is not a knock on senior devs. Just showing that knowledge flows both ways.
1 reply 5 retweets 17 likes -
Have purposefully standardised a lot of our flow for this reason (easier onboarding, self documenting the builds). Docker compose up and you're good to go. When you're ready look at the yaml to see what's happening. No institutional knowledge requirements.
3 replies 1 retweet 6 likes -
Right. People underestimate how much you can improve velocity by reducing the need to teach people your bespoke workflow when you onboard.
1 reply 6 retweets 15 likes -
Too often it's cobbled together bash scripts by Dave who left 3 years ago that you run in a specific order when Venus is in retrograde for it to work. How do you teach that to a new dev? Or an experienced one either. Hell of a bad practice to propogate too but sadly not uncommon.
1 reply 2 retweets 19 likes
The worst version is this exact implementation but everyone is convinced it's a great workflow and it's considered heretical to question it.
-
-
As a consultant on Docker/Kubernetes stuff, it never seizes to amaze me that people accept standardizing their prod env without questions, but fight improving/standardizing their dev env tooth and nail.
1 reply 0 retweets 1 like - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.