Starting a new job next Monday

Slow Eddie

I start a new job Next Monday, working as part of a three-man team. I have been working solo since 1985. I was looking for advice / thoughts on what it is like. Particularly, what are the pitfalls, etc. I have already met the other 2 guys when they interviewed me for the job. They both seem to be really good guys. I really don't want to screw this up. It is a permanent position, with an excellent salary and benefits. Any recommendations?

ed

PIEBALDconsult

Can you make coffee? There is no such thing as a permanent position.

Marc Clifton

The usual - chill and listen and learn for the first few weeks. Ask questions, like about processes, testing, procedures, etc.

Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a Domain

Amarnath S

IMHO, lesser the number of people in the team, lesser the chances of office politics. Three should be fine.

Super Lloyd

Congratulation man! Take it easy, you can do it, I believe! :)

A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!

Mike Hankey

Good ;uck

The most expensive tool is a cheap tool. Gareth Branwyn JaxCoder.com

V 0

be yourself. either it clicks or it doesn't :)

V.

CPallini

Congratulations! Start with: "I am a genius, you dumbasses", or something like that. :-D

"In testa che avete, Signor di Ceprano?" -- Rigoletto

dan sh

Everything here is so wrong. We need to start over my way. This has always worked for me.

"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[^]

CPallini

:laugh:

"In testa che avete, Signor di Ceprano?" -- Rigoletto

Slow Eddie

My mother raised some stupid children. I am not one of them. :)

Slow Eddie

I bet it has not.

ed

MikeCO10

Congrats! I've done both solo and small team, alternating over the past 30 years. Obviously, it depends on the team but one of the things that I like is the concept of bouncing ideas off of each other. You got the job for a reason and you're bringing a lot of experience to the mix. I'm the OGIC (old guy in charge) but I love listening to new ideas and kicking them around. And sometimes you have to do the dog work whether you like it or not, if it is needed by the team. (We've been together a few years so I can whine and post the funny dog gifs on Teams, but still have to do it) It'll be fun, roll with it and be ready to change up some of those things you might have been doing for the past 37 years, lol. Don't look for the pitfalls, it's just life.

Lost User

Don't talk unless spoken to?

"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I

rnbergren

awesome news. Just be humble. I have started two new jobs in the last 2 years. I find that going in with a humble attitude works wonders.

To err is human to really elephant it up you need a computer

SkysTheLimit

Moving from working solo to a team environment requires a change in perspective as well as in process. For example, when working solo, it is easy to rearchitect things and change function signatures but not so much in a team environment especially if there are other moving parts to consider. There is also a tendency to find things wrong with the code or ways that you would have done it differently/more efficiently and then be quick 'to fix things that ain't broken'. Take time getting to know the code and the history behind some of the design decisions (if that applies in your instance) before offering advice on how to improve things. Your advice and experience may well be helpful and lead to good improvements so don't not suggest things at all :-) Since it is a team, you will likely spend a bit more time collaborating and sharing statuses which, at times, will feel like a waste of time (if you're like me and want to get things done). This helps identify potential issues and clear up any false assumptions so focus on those benefits and don't let time wasted be a frustration. You'll just need to factor these in when giving effort estimates for your tasks. It sounds like you're going into this with the right attitude so that's a good start. Good luck and hope you enjoy working on a project that is bigger than just you :)