4 ms·
At work there's often new tools and processes being built and used and I've been noticing that many of my co-workers struggle to figure out the new stuff. Its f
by TheGRS 11y ago
At work there's often new tools and processes being built and used and I've been noticing that many of my co-workers struggle to figure out the new stuff. Its frustrating to have them go back to old ways when we're in a time crunch too, since it means that new tool isn't taking shape. I've long abandoned the "brown-bag meeting" as a way to share with my peers, because it never seems to work. What's been much more effective has been one-on-one time with others, when I can carve it out.
Obviously this isn't very scalable to a larger group though. I'm depending on the grassroots effect to take hold at some point and for others to spread that knowledge. Its effective, but not as quickly as I'd like. I may have to try some sort of workshop style like this in the future to get us to the point faster.
- greggman 11y agoNot a substitute for your suggestion but what I found one thing that spread best practices at my last job was code review. I do something, the reviewer points out I could do it more efficiently, or use some library or solution in the project that already exists, or explains how the build system works and how my new rules don't quite fit and how to make them fit. etc....