Answer to the question recently asked by a junior on a forum (putting it here so that i have it for my future reference)
there
are 2-3 ways to about this .. 1) you go about in a polite way, give
them examples of where else it is done as well as maybe samples you find
on the internet to do similar things .. make sure you just give them
hints and not complete solution .. if
the developer is one who is proud of his coding he wont take complete
solutions and would like to research it himself .. if he is one who
likes ready baked stuff then he will be all ears if you give him
references where he can find similar stuff .. 2) you try to figure out
what is it stopping him from implementing it? Is it is time, or the
effort or he just cant understand the need for the feature or he cant
understand how to implement it. If its pure lazyness then you cant do
much .. get it implemented by somebody else. If its the complexity, then
it becomes your duty to break that requirement down into easy
consumable chunks that the developer can work upon .. let it be known
that the development can be iterative .. get out a rough version with
some thing working and then slowly improve upon it. In the end it
depends on the developer you r dealing with, there is no one type of
them. Each has his own incentive that drives him to work .. figure that
out and you might have a better chance of conving them ..
