Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

So I've worked on my own all this time, selling software, creating a few web applications on my own. I had an Arts background I was self taught. It was a bit difficult to find a development position after endless trying, I finally landed a LAMP position. What I realized was it was all confidence issue. Before when I didn't know a few things I panicked but after spending such a long time working on my own projects and solving various problems, I felt confident enough that I could fulfill requirements on my own. I hope this helps other people applying for jobs

This is the first time I will be developing with other team members in an office, are there anything I should prepare for my first day at work next week? Any tips and pointers while working as a developer at a company? I'm kinda nervous but excited.

share|improve this question

closed as not constructive by Mark Trapp, Jim G., gnat, Walter, maple_shaft Mar 24 '12 at 15:21

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. If this question can be reworded to fit the rules in the help center, please edit the question.

This might be a good question for The Workplace Currently in commitment phase at Area51. Please go and commit to supporting this community. –  Chad Mar 26 '12 at 13:05

5 Answers 5

up vote 8 down vote accepted

I hate to say it, but be prepared for the worst. You will likely be maintaining someone else's possibly horrendous code. You may not be able to "fix" it the way you want because the person that created it is still there and still calling the shots.

On the other hand it will be very fulfilling to work on larger projects and be part of a team.

Best thing I can say is don't believe the "Guru" and verify anything anybody is telling you about how to code with what you see in online forums etc. Unfortunately there are many programmers out there (way worse than you will be) that will tell you "how it's done"

share|improve this answer
+ 1 for horrendous code - was at two companies and both of them had that kind of "guru" –  SergeS Mar 24 '12 at 12:08
  • Take a deep breath and relax. Things will go at different paces for different reasons.

  • Sometimes things will seem slower, sometimes faster.

  • You'll have people to share problems with - and to help them with theirs.

  • You may be rated as much on how you get on with others as well as the code you write.

  • You'll need to figure out what 'style' the office works in - quiet, noisy, etc. and adjust to it.

  • Listen, Listen and Listen some more. The less you say (initially) the more you'll be heard.

  • Be patient. Many things take a whole to grow but the final rewards are good.

  • Keep studying and don't lose the habit.

share|improve this answer

A daily occurrance of WTFs. Not just in code, but also how people interact with each other, how projects get started and killed, etc. It is possible that you will start in a good environment, but there is always something that does not make sense (which could be good to know, so you know what to avoid).

share|improve this answer
+1 for referencing the dailywtf.com –  Bill Leeper Mar 24 '12 at 1:23

Because as you say the team is all ready there, you job is to fit on that team and be a part of them.

To archive that you need to follow them and not make them try to follow you - what I mean: to follow them, to let them guide you, to let them show you the road, and to make that you need to do what they say to you and not make many arguments.

At the end the complicate thin is to make the team - and this is also not depend from you but from the leader of the team in this company. If the leader is good, then you actually no have to do anything else than decide if you like or not to be part of this team.

By the way, the first weeks you only try to make your workstation, and you going to learn what they work on, so be learn what is the project, what is the database and the data and what you going to do there - you going to learn why the leader of this team hire you.

share|improve this answer

I only have one tip - if the company or any of its projects have an accepted coding style, then try to follow that style, whatever you may think about it. Don't try to enforce your own different style (code formatting and naming conventions) on existing codebases.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.