Showing posts with label Philosophy. Show all posts
Showing posts with label Philosophy. Show all posts

Wednesday, June 04, 2008

Mentoring FAQs

Hello all this is a summary of the discussion I had with DR regarding “mentoring” scheme. I have compiled the discussion as FAQ.

Note: To know more about Mentoring please check out: this url

  • What should be the approach towards the technical problem solving of freshers?
    • Typically mentor should not be the problem solver for a freshers because freshers can anyways achieve this using google J. In some ways, mentor is to help fresher find better solution quickly. Moving the fresher aside and writing the code yourself on his desktop is not a very effective way of teaching. Neither is it sustainable. Mentor should tell the freshers the proper approach towards the problems solving so that freshers should be able to solve the similar problems next time.
    • Mentor should guide the freshers to use proper documentation while solving the problems. Trial-and-error approach is discouraged when it delays things and brings about sub-optimal solution. E.g. Use of Java Docs, Specs, Man pages are preferred over google contents and forums.
    • In general, it is a good idea to let the fresher commit mistakes. But this has to be time boxed. We cannot let freshers make mistakes which will affect business. But some mistakes need to be allowed and budgeted for as these are necessary parts for anyone to gain confidence.

  • How to tackle freshers who make same mistakes very often even told 100 times?
    • Very first thing that mentor needs to do is to find out the root cause: why the person is making mistakes. There could be two reasons for two altogether different types of freshers.
      • One who make same mistakes because of their laziness but they have the capability of understanding / recognizing the problem and their solution.
        • To make the first type of freshers mature mentor will have to talk with them in person about their laziness and nature of “taking things granted”. But mentor should make sure that he/she conveys the message in proper way to freshers because keeping voice loud / becoming frustrated / showing anger never helps.
        • E.g. Mentor can tell the fresher that making same - same mistakes again and again just because of his negligence will create trouble for him. Rather being careful will only him to save his time; help him in his grades and hence eventually in his performance appraisals; he will face few bugs in his implementation and will get a change to be shifted to new project/module and will get exciting work and opportunities. In short, always make sure that you are vocal about “what is in it for the fresher” to deliver better solution. If he sees value in it, he will do it.
      • Other who make same mistakes because of their inability to do “pattern-match” for the problem and its solution. This is basically skills and capability issue. People have different capabilities and some freshers just may not have the necessary analytical power, knowledge, or skills to tackle the issues resulting in repeated mistakes.
        • In this case as the fresher is not able to perform well will eventually get simpler work and will be shifted to non-critical tasks.
        • Only thing that we need to ensure is that every one works to the best of her potential. People’s potential will differ. So some will work better at the backend while others will be better off handling front-end etc. Mentor needs to be sensitive to this and should guide the fresher accordingly.

  • How to spend effective and fruitful time with freshers?
    • If the mentor is directly working with that fresher (e.g. same module/project) then his/her interaction with him will be good. But in cases where mentor is in different project/module then mentor needs to setup meetings (typically 3 times in a week (alternate day) of duration 60 mins) with freshers.
    • First few meetings will run for 60 or more mins but quickly – typically after first 2 or 3 weeks, the meetings can be of reduced duration and frequency. This is to ensure that fresher gets lot of attention when she starts – when the anxiety level is high. And later he gets more freedom – as she become more confident and experienced.
    • As the mentor is not working in same module / project mentor will not have the idea about what the freshers are doing. In such cases mentor should ask freshers about the work they did in last 2/3 days; the work they are going to do in next 2/3 days; how they implemented some feature; how they fixed some issue etc etc. Thus mentor can discuss the technical stuff in detail and can figure out whether the person is doing it properly or whether he needs some correction.

  • If mentor is mentoring freshers who are working with different project manager / lead then it might happen that for a given problem mentor will have a different (or better) solution than that of the existing project manager / lead. How to handle such situation because in such cases it’s possible that the fresher will get sandwiched?
    • In such a cases mentor should provide the proper solution no doubt. But should ask the fresher to talk about this approach with the existing project manager / lead and convince him for the solution. After all the delivery responsibility is with the current PM and mentor should not adversely affect that part!
    • It might happen that due to the communication gap or fresher’s limited understanding or some other reason the solution provided by mentor could be unsuitable. In such cases mentor should talk with the existing project manager / lead to reveal such communication gap. But ultimately fresher should implement what his PM tells him to though he must also learn correct things. Such communication gap should be communicated with mentor also otherwise mentor will lose insight for those particular projects / features.


  • Is the mentor supposed to assign work / task to freshers?
    • No. This is the project managers / leads responsibility. Mentor is there to guide the freshers on their technical / analytical growth and to communicate their issues / aspirations to proper person on proper time.


  • How to deal with issues and aspirations of freshers?
    • Mentor should immediately communicate issues of freshers to project manager which he thinks he can handle. E.g. I stay far away so it’s not possible for me to stay late in office. I can come early in office and can finish my work. In some critical cases if I have to wait late in office please make sure that someone will drop me to home etc etc. There is a possibility that due to direct line of command, fresher may hesitate to share such information with her PM. Mentor should facilitate such communication and make fresher more comfortable.
    • Same is applicable with aspirations. E.g. I want to work on better module where I can contribute more. Why don’t we use xyz technology / tool / library rather than this? etc etc.
    • In your project if you are using some old technology (E.g. postgres instead of oracle) which can be easily and sensibly replaced by something new. And if there is no reason that why you are using that particular old technology then you are free to migrate to newer one. However, the decision must be taken by the PM. Mentor has a responsibility to facilitate the fresher’s feelings and to ensure that she gets an answer from the PM.
    • In your project if you are using some third party libraries which can be easily developed in house; you can write a small (one page) requirement specification for the same and sent that to project manager stating its criticality and importance. Such in-house library / component development will create “new and exciting work” for freshers as well as for mentorsJ. Such development should be executed just as another project in organization by the manager otherwise it will loose its criticality.


  • There are mentors of various levels of experience ranging from 1 year to 5 years. Any comments?
    • True. There are various advantages of this approach.
      • Young mentors will get sense of responsibility and will now start improving on their communication / leading / technical skills because now they not only have to face their bosses but also to the freshers ;-)
      • Senior people will also not lose the common touch ;-)
      • Also we have an advantage here that we have given freedom to freshers to choose their mentor. So this adds one more responsibility over mentor’s shoulders.
      • The whole point is to expose freshers to various different points of views. We want to stress the fact that it is “okay” to have different opinion and different approach. What is more important is to be able to respect different opinions and develop skills to decide which (approach / style) works best for which circumstances.


  • Can mentor think independently?
    • Why mentor? Everyone should think independently! The more diverse people the fresher will deal with the more he/she will learn.


  • Whether mentor is supposed to evaluate the freshers?
    • No. This is project managers / leads responsibility.
    • Mentor should understand the strengths and weakness of freshers and should guide him/her accordingly.


  • Last question! How to manage your boss while doing all this?
    • Simple! By communicating with your boss’s boss – when things go wrong! :-) Everyone has to learn. Your boss and boss’s boss as well. Best way to make it happen is to talk, talk, talk! When you talk with your boss’s boss, either you would get some more insight in to why your boss is working in a particular manner. Or your boss will get some feedback about how she should work. Either ways, both you and your boss will form more trusting and comfortable relationship. Your boss’s boss will be facilitator in such a case!

About DR:

DR is our SVP Engineering. Apart from usual technical and managerial work in IT industry, DR is also involved in many social activities. He is a trustee of an NGO named Sanvedana. To know more about Sanvedana and participate in its great charity works please visit http://www.sanvedana.org/.

So looking forward to meet you guys at Sanvedana to take its mission ahead by one small step.

Tuesday, March 11, 2008

Mentoring

I remember when I was had just started my professional career with after completing my graduation from PICT; we all batch mates used to meet (a get-together) and used to discuss the interesting industry stuff. Those days many people used to discuss: hey my mentor is xyz and he is really cool, my mentor advised me to read this and don’t read that, my mentor is very fundu and even sometimes I was chatting on yahoo and suddenly my mentor came. Bla bla …

My obvious reaction was what is mentor rather who is mentor and what is mentoring? Unfortunately I have not assigned any mentor till I became mentor ;-)

And then one fine day I got a mentor: DR our SVP Engineering! And then I started knowing about mentoring philosophy. :-)


What I am planning here is to share some of my mentoring experiences. The mentoring that I do to my mentees and the mentoring I receive from my mentor.

Well, let me tell you what mentoring means. To write on this topic I will again take help from the discussion that I had with DR on this topic and his mails on this topic.


Mentoring typically starts with a fresher as he/she joins the organization. A mentor is associated with such fresher since his first day in organization. This association lasts for typical 2/3 quarters. During this tenure following goals are typically achieved

  • To track the output of fresher from the perspective of quality, productivity and efficiency. Such output is observed and improved by fresher by spending time with mentor. E.g. code quality can be improved by getting code reviewed from mentor.

  • To mould the thinking process of fresher in regards to what is the difference between college and corporate. What are changed priorities. Why take initiative and responsibility is important. In short mentor is to educate the fresher about the Dos and Don’ts

  • To keep the track of aspirations of fresher and to see whether these are being addressed or not. E.g. Aspirations could be as small as to participate in design meeting or starting a hobby project or even to write a research paper! In short mentor is the first stop for fresher for all such expectations a fresher may have.

  • Essentially mentor has to make the freshers productive as quickly as he can.

  • On the other hand this relationship has to be mutually beneficial. Freshers will get quick and sensible guidance. Mentors will get first hand experience on how to handle teams, aspirations, how to delegate, how to get best work done from people etc etc. In short for mentors it’s a great managerial education.

Though mentoring talks more about the relationship between fresher and his senior (2/3 batches senior); mentoring can actually happen at any level. I mean in my case it’s a 6 years experienced person is a mentee of a 20 years experienced mentor! ;-)

One last thing as the mentoring progresses please don’t forget to get the bi-weekly feedback from your mentees. So Happy Mentoring … ;-)


One more important thing I would like to share with you about my mentor is: Apart from usual technical and managerial work in IT industry, DR is also involved in many social activities. He is a trustee of an NGO named Sanvedana. To know more about Sanvedana and participate in its great charity works please visit http://www.sanvedana.org/.


So looking forward to meet you guys at Sanvedana to take its mission ahead by one small step.

Saturday, May 19, 2007

Demophobia

Demophobia. They say its "Fear of crowds". I say its fear of Demo.
Why one should be afraid of Demo ? Rather who should be afraid of Demo. I will say everyone around Demo.
Hey come on Demo is not a Tiger or Dinosaur or even not a stinking sox.
Actually yes ?
  • We in software industry keep giving Demos to various people; client, directors, managers, venture capitalists ... Everyone is afraid of this : We as well as They.
    • My manager asks me to setup a Demo for our Director. I and my colleagues all work hard and hard, we don't sleep the night before Demo and the next day the Director say he don't want this.
    • Next time my manager work even harder (of course this means we work hard ;-) ) and we give so called a controlled Demo. Wow ! this time it worked. After this what? Now its our so called moral responsibility to convert the Demo to a all time running, bug free system.
    • After Demo what ? My manager start preparing for next Demo. Hey man what about that bug free system that we were supposed to build after first Demo? don't know.
    • After 4 months. We have a 15MB of code for 4 different Demos! which will never work together a an integrated product.

Thursday, July 28, 2005

Manish’s story of small boy and his color box

This story has been told to me by Manish… I found this very helpful as a young programmer/designer

Scene1:
One day a dad gives a brand new camlin color box to his son as a gift. The small boy becomes very happy by seeing 12 fresh colors in the box and asks dad “Which picture shall I draw first?” Dad said, “Son, go ahead with my picture!” Without wasting a single minute the boy takes pencil and draws his dads picture and paints it. He was so excited that was willing to use all 12 brand new colors; so he made dads face red, one arm blue other black, shirt green, pant brown and so on…

Scene2:
Some other day some other dad gives a brand new camlin color box to his son as a gift. The small boy becomes very happy by seeing 12 fresh colors in the box and asks dad “Which picture shall I draw first?” Here again dad said, “Son, go ahead with my picture!” But this boy thinks for a while; takes pencil and draws his dads picture and paints it. He thinks on body color and create the body color shade by mixing red and some other color, paints all body parts with that color; paints blue shirt and black pant. Thus he uses only 3-4 colors from his new color box!


Moral of the story – As a programmer/designer we have a lot of technologies in front of us, but this does not mean that we have to use all these; lets think/study them, see which ones our application really demands and use those or combination of those only and be the second clever boy!

Monday, July 25, 2005

Shikha on my ‘PST’ (preetam’s standard time) timings!

It’s half past-eight in the office and the lights are still on, computers are still running, coffee machines are still buzzing. So, who’s this, still at work?
Almost all the ‘workaholic’ specimens are 20-something males of the species.
A close look reveals that almost all of them are bachelors. The question then arises, why are they sitting late?
Working hard? Not by a long shot! Any guesses?
On second thoughts, let’s hear it from the horse’s mouth.
I quote – “Arey yaar, what’s there to do after going home. Idhar to net hain, AC hain, phone hain, khaana hain, chai-coffee hain… toh jam ke khaao, jam ke piyo (burps), jam ke chatting/phone karo aur thak jaane par ghar jaao… aur boss bhi kush thinking that I am working late…(burps again) aur khaane ka paisa bhi bachtaa hain.”

This is the scene in most software companies and other off-shoring company offices. Bachelors killing time during late hours in the office just coz they’ve nothing else to do, is more the norm than the exception.

So, what is my point, you might ask. Well, the consequences of such ‘unfair practices’ can be quite drastic, especially for the other employees.

  • “Working” (for the record only) late hours soon becomes a part of the company culture.

  • With bosses more than eager to provide support to those ‘working late’ in the form of conveyance reimbursement and food vouchers, of course the much sought after pat on the back. (Oh, he’s a hard worker/sincere employee… goes home only to change!), things don’t get any better.
    It’s the rare perceptive boss who understands the difference between ‘sitting’ late and ‘working’ late!!

  • Very soon, the managers start expecting all employees to put in extra hours.

Most bachelors are completely oblivious to the fact that life changes when one gets married. Work does not remain the be-all and end-all of one’s existence and one is kept busy juggling work and family commitments.

Many bosses are not able to digest the fact that, the erstwhile ‘hardworking’ guy gets transformed into an ‘early leaver’, even when he leaves an hour beyond regular working hours, and more importantly is able to get the same amount of work done.

Employees leaving on time after doing their tasks for the day are labeled work-shirkers.

Women who, with good reason, generally (its changing now-a days… though) leave on time are labeled “not up to it”. All the while, the bachelor as snug as a bug in a rug carries on ‘working’, not realizing that he’s spoiling the work culture, which is sure to boomerang on them some time.

So, what’s the moral of the story??
  • LEAVE ON TIME!

  • Never put in extra time unless it’s really needed.


Don’t stay back un-necessarily and spoil your company work culture, which will in turn cause inconvenience to you and your colleagues. There are lots of things one can do to make good use of his leisure. You could, for instance, learn music or a foreign language; take up sporting activities; get yourself a girlfriend and take her around town; also, cyber surfing rates have dropped to an all-time low (and there are no firewalls there); try cooking for a change.

Take tip from the Smirnoff as: “Life’s calling, where are you??”

Please pass on this message to all your colleagues including those who stay back in the office for everything other than work.

And please do it before leaving time, don’t stay back till midnight to forward this!

Regards,
Shikha

Wednesday, June 15, 2005

"Hello World" blog !

I seen my friends’ blogging on web and then I thought what this blog is? Lets give it a shot! And here is my blog … u r reading!

I was always thinking of having my own home page but till date I have not managed that L. So lets blog first!

Life moves very fast, a lot of things happen in our day-to-day routine, we laugh, shout and even cry … I think this is all Life … lets take it as it comes; its very exciting and lets make it more. I always say, “Are yar life main kuch excitement hona chahiye!” Lets share that excitement here!
I can see/feel excitement literarily in anything… let it be my bug free program, let it be a sat-sun at Deccon or even let it be a travel by PMT or my rejected BITS application!

After all somewhere I had read “Great Minds Are Open”…

What I will be posting? Anything! Starting from experiences/thoughts/fundas to tech/hot/cool stuff! (And even nothing)......