Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>This is a great question, and I think a fairly common situation. Basically, I think what you're asking for is guidance on how to communicate with your boss, and the other people in your organization.</p> <p>This might be a good time to look into the <a href="http://en.wikipedia.org/wiki/Scrum_%28development%29" rel="nofollow">scrum framework</a>, and take from it what seems applicable to your environment. </p> <p>In particular, you mention that you might be in over your head. Or, there is an (implicit) expectation that you'll need to finish this project "tomorrow," when you really don't know how long it will take.</p> <p>I suggest starting with a list. Write down everything you need to do. Include non-coding activities, like "research technology X for doing Y," and give each task a basic time estimate like "1" for short, "2" for medium, "3" for long. Then put the things in an order that you think makes sense. </p> <p>Then meet with your boss, once a week, for like 20 minutes, to discuss what you did, and what you're going to do next week. Out of this discussion, you'll both see what's going on, and adjust expectations (and the list) accordingly. When conflicts of expectation come up, talk it out.</p> <p>Regarding the amount of support to expect as a junior developer, this really depends on your organization, and your supervisor's opinion. As software engineering is still a relatively young profession, there isn't much in the way of industry-standard mentoring programs. </p> <p>I suggest trying the list + meeting thing for a couple months, and observe how your opinion of the support situation changes. Then, go to a large conference as soon as possible; spend the money if you need to. You'll see who is struggling with similar situations, and also who is not, and you'll create your own, more-informed model of "how the industry is supposed to work."</p> <p>Regarding a good approach to communicating, I (seriously) suggest <a href="http://rads.stackoverflow.com/amzn/click/0609805797" rel="nofollow">The Seven Principles for Making Marriage Work</a> by John Gottman, which has a lot of examples of what works and doesn't work when communicating with people. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload