comment on

It's a balancing act: I want to prove that I'm not a slacker, but at the same time I want to show that I won't work an 80-hour week unless there's a really good reason.

To be honest, the time for sticking by your guns over work week issues is at the interview. If the culture says 80hr weeks are not unexpected, then expect lots of pressure if you don't live up to expectations. I'm just glad Microsoft decided not to hire me out of grad school. :-)

Can anyone suggest a strategy for the first month on the job?

Develop a taste for espresso?

At the beginning you'll be expected to produce fruit. Your first job is to find out what fruit to produce (i.e. what your boss is looking for in order to trust you). Over the long haul you'll want a nice test framework. However, if they really expect to see some concrete progress up-front, then you really don't want to spend all of your initial time on building a nice test framework, but have no working test cases to show for it.

In reply to Re: The New Job by bluto
in thread The New Job by logan

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks