4

I’ve become so indecisive in terms of knowing what I want from my career.
All I know is what I don’t want (to end up a in management)

I’m definitely getting a new job and right now it looks like I’ve got 3 offers on the table

Option 1, a previous company I worked for. Still the same problems with the company there as before but the work was interesting and unusual. and my line manager was a good guy.
They have practically no legacy code.
Not much in the way of company benefits but they’re local and it would be nice to see friends again.
So feels like the pull to this is strong.

Option 2, a fully remote company that I’ve been referred to by an ex-workmate.
They’ve not even tech tested me because they’ve read my blogs and GitHub repos instead and said they’re impress. So just had a conversation with them. I feel honoured that they took the time to look at what I’ve done in my own time and use that in their decision.
Benefits are slightly better than option 1 (more hols)
But they’re using .net 6 and get a lot of heavy use on their system and have some big customers. I think the work is integrations to start with and moving services into docker and azure.

Option 3, even though I’ve got an offer from this one but they can’t actually explain the work until We can arrange a call next week (they recruit and then work out what team your in, but Christmas got in the way of me having a call with them straight away)
It’s working on government systems and .net is their least used stack so probably end up switching to Java. Maybe other tech stacks too.
This place has much better benefits than option 1 and 2 (more hols and more pension), but 2 days a week in office.

All of the above pay the same salary.

Having choice feels almost as bad as having no choice.
It’s doing my head in thinking about it , (even tho I might as well not think about it at all until the call with option 3 happens).

On the one hand with option 3, using a tech stack that’s new to me might be refreshing, as I’ve done .net for 10 years.

On the other hand I really like c# and I’m very good at it. So it feels a bit like I should be capitalising on that and using my experience to shape how the dev is done. Not sure I and I can do that with option 3, at least for a while.
C# feels like it’s moving forward nicely and I’m not sure I can say the same for Java or other languages.

I love programming and learning new stuff but so unable to let things go. It’s like I have a fear that c# will move on without me and I’ll end up turning into one of those devs whose skills are a decade out of date.

Maybe the early years of my career formed me in this way.
Early on I worked at a company where there was a high number of Cobol devs who thought they had a job for life.
But then redundancies came and many left. Of those who stayed they had to cross train to Java and they just couldn’t do it.

I don’t think the tech was hard for them, I think they were just so used to not learning that they could no longer adapt.
Think most of them ended up retiring after trying to learn Java for a few years.

Comments
  • 2
    The .net and Java ecosystems are way more similar than the COBOL and Java ecosystems - if you use one, I wouldn't worry about not being able to catch up with the other if you need to.

    I'd be weary of option 1 personally, it's always human nature to look back on these things with rose tinted glasses somewhat, and you could damage, rather than build your current relationships. Options 2 or 3 sound like they have potential. I'd listen to what option 3 has to say then go from there.
  • 2
    @AlmondSauce cheers man.

    Yeah, I’ve been thinking option 1 feels comfortable but part of that is maybe nostalgia.
  • 1
    Option 2 seems like a no brainer to me. Just use what you know in the latest form until you decide you want to do something new or find something with an attribute that sets it apart
  • 1
    @AlmondSauce

    I'm definitely in the same boat here with my recommendation. Going back to an old job doesn't seem like you're really "growing", but just wanting back an old comfort. Unfortunately for me, I've never really left a company on good terms so it's easy for me to think that way, but my advice is to avoid looking back and to always look forward -- new places bring new opportunities, new networks and people. You can always switch again if it doesn't work out.
  • 0
    what's hols? also i would be very interested in knowing you if you took the opportunity #1 . i often find myself having an urge to just call people at my previous company ans see if they could still provide me a decent pay and i rush to join them. but i resist that urge.

    also ikigai works for me. you can try putting your opportunities in those circles :

    https://encrypted-tbn0.gstatic.com/...
  • 0
    @prodigy214 going back to a previous company is something I’ve done before.
    (It wasn’t at any of these options I’ve got now)
    Second time with them turned out the be the best job I’ve ever had. The company was starting to adopt agile when I went back and were recruiting lots of new people so it was familiar but very different to the first time.
  • 0
    @prodigy214
    Hols at option 1 are 25 forever.
    Option 2, 25 and go up to 30 after 5 years.
    Option 3, 26 and go up to 30. (not sure how fast).

    So all pretty similar to start with.
  • 0
    If salaries are similar, go for the technologies you want your carrer to move towards. Even if you leave in a year or two, the xp will remain in you CV and will count for getting other jobs.
  • 0
    @TrevorTheRat still don't understand the meaning of hols. are you talking about shares, or number of girls there, or something else?
  • 0
    @prodigy214 sorry. It’s just your annual leave entitlement. The number of holidays you can take
Add Comment