4 ms·
When I was a manager and onboarding a lot of graduates this was something I noticed. We would have explicit training on how git worked or how the build system w
by freddie_mercury 6y ago
When I was a manager and onboarding a lot of graduates this was something I noticed. We would have explicit training on how git worked or how the build system worked or how the messaging system worked.
But there was never any explicit training on things like "you need to accept or reject meeting invites" or "this is how to correctly use Slack/wiki/email ... And all three are different."
I think a lot of it goes back to the current trend of companies not investing in employees and expecting someone else to have done that for them.
- mgkimsal 6y ago> expecting someone else to have done that for them. And then... when someone else did do that investment - as in, you come in to an org with actual real experience - you somehow are "doing it wrong" or "don't get our culture" or whatever the pushback may be.
- BlueTemplar 6y agoWell, can't have it both ways…
- bregma 6y agoThe problem stems from not having it either way.
- npsimons 6y agoThere's a lot of soft-ish or meta skills that don't get taught, mainly because most orgs don't place much value on them (as you have noticed), but also because it's not a well-studied field. I'm different enough from those I work with at the day job that I don't feel a one size fits all approach will work for everyone. I don't want to be a square peg shoved into a round hole. I do take a very eclectic approach to productivity systems, and tend to pick what works for me while leaving behind anything I consider fluff. I've built almost, but not quite, TDD teams this way (organically from the ground up), and it helps us stay lean and agile.