Matt RobertsFeb 26, 2023
Gergely Orosz

"How can I improve my team's software engineering skills, as a Staff engineer?"

There's stuff like pairing, mentoring, advising you can all do.

But there's something much more impactful: become a pace setter. With your experience, there's little excuse not to do it.

The tradeoff, of course, is that becoming a pace setter means that you will have less time outside of building software. However, this can be a worthwhile tradeoff, when done for a month or two.

Feb 26, 2023 at 8:39pmWeb
Show threadkonst 🇳🇿Feb 26, 2023
@gergelyorosz unfortunately I've seen many do the opposite. "Too busy to do things well", skip unit tests, skip manual testing, heck just do the outline and let the rest of the team polish it off!
Show threadAlessio Feb 26, 2023
@konst @gergelyorosz this is legit firing material 😂
Show threadkluka ❌Feb 26, 2023
@gergelyorosz I always felt like I am doing this as an experienced intermediate engineer and almost no one copied it
Show threadFabrizio SestitoFeb 27, 2023
This is precisely the job that was done in my team. It took more than 1/2 months, about 1 year, and partly impacted other teams in the organization. Doing this while lifting off a greenfield is exhausting, as leading by example can be frustrating sometimes, but totally worth it in the long run. My personal opinion is that being hands-on is the only way to gain the trust of the technical team. A happy accident is that other members are using the same approach and becoming themselves pace setters.