To the junior engineers who follow me: NO, most senior engineers DO NOT consider you a burden or an inevitable fuck-up. They are happy to have you on their team and are excited to teach you.
-
-
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.
-
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.
-
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.
-
Right. People underestimate how much you can improve velocity by reducing the need to teach people your bespoke workflow when you onboard.
-
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.
-
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.
-
For me they're one and the same. Different IDE sure. Different language versions, databases, etc. nononono Although it can be tricky with some AWS stuff
End of conversation
New conversation -
-
-
Yes and no. A good senior dev is fully aware of what transitory details they don't know (or need to know) and how to align themselves with the juniors that do. Good devs knows the discipline on a deeper level and understand how to deal with the soft parts which matter most QED
-
I don't understand the QED part.
-
quod erat demonstrandum. Google it.
-
Usually it comes after a proof.
-
don't feed the bot, Yehuda
End of conversation
New conversation -
-
-
(this is also another cautionary tale about the dangers of calling things "easy")
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.