When I was a tutor at university I remember one student who I only saw towards the end of the year. I think computer science was their additional course. They came in after apparently spending the best part of a year learning Java, and sat down to complete their assignment.
It didnβt take long before I was called over to help. Their code wouldnβt compile. A fairly standard console application, with some output. And no semicolons.
I was incredulous, and as a young eejit, Iβm not sure how well I hid that. I couldnβt believe someone could have completed the lectures, read the books, and completed the previous 29 assignments without using semicolons.
How could they spend a year on a Java course and not learn anything?
Regrettably, I refused to help them and pointed them towards the obvious and clear error messages that theyβd obviously been looking at before they called me over.
I wasnβt going to build it for them. I couldnβt teach them 1 yearβs coding in 15 minutes.
And yet, they turned up. They asked for help instead of struggling on. Exactly the things Iβd wish for in my new starts when I started leading teams and onboarding staff.
They knew the shape of the solution and they knew where their talents were. If Iβd been a little more patient, I could have nudged them gently on. But I donβt know if that would have been enough.
If you are mentoring or leading developers, are you stepping in early enough? Are you praising effort and being vulnerable enough to ask for help? Can you see their strengths and weaknesses? Are you giving yourself enough time with them?
Are you being the senior that you wish youβd had when you were a junior?
Top comments (0)