Discussion about this post

User's avatar
Akos Komuves's avatar

All excellent tips, Raviraj. I'm a self-taught mentor, and I wish someone told me these sooner. I'm guilty of making the 2) mistake early in my mentoring.

I figured the cause for that, so I would add a 6) Not building confidence.

I have to work on this because I felt that sometimes people were afraid of communicating if they were stuck because they had ideas about where they should be and things like that.

Expand full comment
Anjana Patil's avatar

Very insightful article indeed. I wanted to share in case there is a better approach out there. I had struggle with a developer who doesn’t test their work, late on delivery, bugs from past work interrupted current work and so on. At first I helped her navigate requirements, put guard rails to test the work but nothing worked.

I did this next thing and it is on going and give it some time. Since I noticed the QA person had a better hold on the requirements so now I paired her with that QA person. I am thinking that blurry requirements (in developer head) are the root cause of the developer behavior.

Expand full comment
6 more comments...

No posts