i like to come into work early. Occasionally, this means that i’m here when trade folk are doing repairs or otherwise making the workplace ready. It’s nice because it offers less distraction for both parties, normally.
This morning an apprentice and journeyman were inspecting some work on a segment of HVAC, and it was eye opening. The apprentice had come in the day before and done some work on a pump that was making noise, and asked the journeyman to stop by and inspect the work. The journeyman spotted a few problems, fixed an issue, and discussed things.
All the while the apprentice peppered the journeyman with questions like:
“Ok, so how did you spot that problem?”
“Was there a specific tool that could be used?”
“How would i get that tool?”
“Are there techniques that i can learn to help me spot that sort of thing?”
The journeyman gave him the answers without judgement in clear, straight-forward words. He noted that the problem was due to a confusing bit of wiring that had two similar colored links, with very different usage and admitted that it was an easy mistake to make. He offered a way to test, but noted that sometimes, “you make that mistake, so you have to come back, just make sure you schedule a follow up”.
The apprentice knew he didn’t understand, the journeyman knew he needed to teach. Even the extra stories told were all about the problem. They wrapped things up in about 10 minutes and left.
What i just witnessed was a properly done peer review/post-mortem along with a mentor program, and it made me realize something.
Computer science people absolutely suck at this.
Granted, CS has yet to become a proper trade. There’s no history of the sort of on-site training that actual tradesfolk have. In most cases, no company that is hiring an HVAC engineer or plumber will force that individual to sign an NDA requiring that they not plumb a different building the same way that they plumbed that particular building, nor am i aware of any IP restrictions on wiring a workspace, but the fundamentals should be the same. Honestly, there’s little reason why your mentor should work at the same place as you, or just be a single person. Peer reviews aren’t a pain in the ass, they’re opportunities to learn and teach, in both directions.
If you’re not critically evaluating your skills and tools every opportunity, are you really as certain that you have the best? Be proud of what you create, but be prouder of who you’ve helped. Likewise, be open to learning at every opportunity. If i was a “typical” computer nerd, i would have slapped on my headphones, lit up the laptop and tuned out the “distraction” of two workers dealing with some other problem.
And i would have missed learning something important.