So… What Do you DO Exactly?

The week before I began my first job as a web developer, I scoured the internets looking for the experiences of other junior devs: What would a typical day look like? What would be expected of me? Did I just get in way over my large(ish) head?

Surprisingly there were few examples of what a your day to day looks like as a dev, and unsurprisingly, similar to looking up symptoms for your cold on Google, I left more afraid of my first week than if I had never done that search.

I crammed as much information about prototypal inheritance, C# and data structures in my head as I could and walked in to the office (un)prepared for whatever was going to come my way. I sat down next to our lead developer and watched him punch through code on an IDE I’d never seen at break neck pace, throwing around javascript terms I pretended to know and spewing off business jargon that I wrote down to google later. My notebook swelled to 15 pages within the first week and I went home afraid he and the team would figure me out as a charlatan, a fraud a phony!

You don’t understand the nuances of protoypal inheritance? What a noob!

I didn’t get outed as a noob developer in my first month, in part because I didn’t actually code… Most of the time was spent learning the applications we were making, practicing on our IDE and watching much better developers create code.

After a month of shadowing, gaining confidence and doing small tasks here and there I was finally ready to break out on my own and contribute to the exponentially growing number of bugs our team creates. Here’s what my day looks like now:

Our morning consists of a short meeting where we each summarize what we did the day before, what we will do for the current day and bring up any issues the team should know about, like a critical bug in our app.

After meeting I walk to my desk, put my earphones on and code out to the illest country and gangster ass rap music Spotify has to offer. Before I get too deep in my playlist, I’ll look over the user story for the feature I’m responsible for working on. A user story will outline what the feature does, a mock up to help us as we design the layout and an estimate of the hours it should take complete.

While we have a lot of user stories, we have more bugs. This is the reality of coding; I’ll spend about a quarter of my week or more fixing these pesky critters.

In between user stories, I’ll inevitably get an email asking me to update the intranet site our company uses or a software support ticket from one of our users that may require a phone call, a code update or walking someone through uploading Adobe Acrobat.

I’ll leave work, go home and work on side projects and usually spend my mornings thinking about how to attack a bug before I get in.

While my dev job is at a mid-sized established company, my experience seems pretty typical based on conversations I’ve had with other developers. Is it sexy coding? Yeah, sometimes. I mean creating API’s and developing apps people will use with real world consequences is just cool. Software support… is well, software support and this part of the job has forced me to develop a better understanding of how customers use our apps and gives me the needed human contact that is often devoid when you’re staring at a screen with earphones on for most of the day.

So if you’re reading this, freaking out about your first day, week, or month as junior dev, hopefully this has calmed your jittery nerves and once you survive your first few months, hopefully you’ll contribute to the blogosphere and share your (hopefully) less than awful experience as well.

3 thoughts on “So… What Do you DO Exactly?

  1. Your description of hoping not to get outed as a phony… that made me laugh. I had spent a year or two learning C for my own purposes; and my first “real job” as a software developer, I spent the first 6 months (at last) worried about the same thing.


      1. I think it does, actually. While not always the case, I’ve found that often the ones that talk the most and do the least are the worst at their jobs. And in this field, it’s probably better they don’t do much… because you’ll just have to clean it up later. (Which is why, if your idea is shot down, you shouldn’t throw it away… you may get to implement it later).


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s