News for hackers. Stuff that matters.
Re:Letters to Junior Developers by onion2k on Thursday January 22, 2015 @10:35AM (#8929654)
I really don't agree with the final "Present a solution, not just a problem" point. Quite often a developer will be able to see a problem but won't have a clue what the solution is. Having a "Present a solution, not just a problem" approach means that developers won't want to inform you that the problem is there, and then it'll surprise you later at the worst possible time. If you have a solution, great. If you don't, also great. But always communicate a problem exists.
Re:Letters to Junior Developers by greggyb on Thursday January 22, 2015 @10:59AM (#8929809)
I am not disagreeing with your reading of the article, but adding on my own interpretation, as this general advice is tossed around on multiple teams I work with.

The way I see this is not as a diktat, but as an acknowledgement that if you find a problem, you have enough domain knowledge to be able to contribute to a solution, and the fact that you are the first to identify the problem lends evidence to support the fact that you understand (at least a portion of) the source of the problem better than your team.

Don't pass the buck by reporting the problem and assuming it will be fixed. Take the time to fix it to improve things for you and for your team.

Obviously there is a huge range of appropriate responses, but I think keeping this sort of understanding is important. A problem that you identify is a problem in something that at least touches your team's primary responsibility.

Re:Letters to Junior Developers by yaddayadda on Thursday January 22, 2015 @12:11PM (#8930262)
I'd modify it to "Don't present just a problem, present a solution, or all the solutions you've tried and why they didn't solve the problem."

I've also heard some companies have time limits on seeking help, e.g. if you're a junior developer and can't solve the problem on your own within 15 minutes, ask for help.

Re:Letters to Junior Developers by datashovel on Thursday January 22, 2015 @02:49PM (#8931301)
I encourage the 15 minute rule, but not to just ask help from anyone. Another difficult thing to accomplish as a manager is to prevent unnecessary interruptions for anyone on my team. In an ideal scenario all that stuff goes through me. Not because I want that control. It's because I have the responsibility. One of those responsibilities is to get the most out of my team. So if that means interrupt me instead of your teammates that's my preference pretty much 100% of the time, unless I'm unavailable.
Re:Letters to Junior Developers by datashovel on Thursday January 22, 2015 @02:19PM (#8931102)
Having managed teams before, my feeling is that this advice is good in some cases, and bad in others.

For example, if your team is filled with a bunch of newbies who don't really know what they're capable of yet, their default reaction alot of times is to come to you with their issue. If it happens too frequently it can become counter-productive.

On the other hand, some problems can take a long time just to figure out what's going on, and even more it can be difficult to articulate the issue precisely. As long as the problem is well formulated and precise, progress can usually be achieved by bringing the problem (without solution).

Generally speaking, though, it's good to keep in mind that a manager usually has a ton on his plate already and needs to deal with all his team's problems, whereas the developer is only responsible for working on the one problem.

Final point would be that, especially with younger devs, they can get into a "paralysis by analysis" state. I encourage younger devs to not work on a problem for too long so they're not spinning their wheels. So in these cases I want my younger devs to come to me after they've spent maybe 10-15 minutes on a problem, even if at the end they still don't know what the problem is.

Re:Letters to Junior Developers by bejuizb123 on Thursday January 22, 2015 @10:57AM (#8929801)
Agree with your point that quite often a dev might not have a solution. Seeking help should of course be encouraged, but one must also put in some thought for a solution. I think the author had extensive cases of trigger happy devs always coming to him with problems. As dev-s, you should be able to think with different perspectives and not simply go to your manager with the first instance of a problem.