Decisions, decisions
-
I was approached recently for a role with a local software house. As it was local, and the job spec sounded interesting I agreed to an interview. I recently had a second meeting to go into the role in more detail. I'm now really confused. The role sounds great, the MD (who interviewed me) was a really great guy and they want the role to guide them technically going forwards (so will have a lot of say in their technical decisions). On the other hand though, I'm happy where I am. I've built up the proceses, technical stack, architecture, build / release pipelines etc from scratch. I have made a huge difference since starting here 3.5 years ago. I have a personal investment and feel reluctant to just walk away from what I've built here. I have a lot of autonomy and decision making responsibility here too. I'd be interested to hear other people's thoughts.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
I was approached recently for a role with a local software house. As it was local, and the job spec sounded interesting I agreed to an interview. I recently had a second meeting to go into the role in more detail. I'm now really confused. The role sounds great, the MD (who interviewed me) was a really great guy and they want the role to guide them technically going forwards (so will have a lot of say in their technical decisions). On the other hand though, I'm happy where I am. I've built up the proceses, technical stack, architecture, build / release pipelines etc from scratch. I have made a huge difference since starting here 3.5 years ago. I have a personal investment and feel reluctant to just walk away from what I've built here. I have a lot of autonomy and decision making responsibility here too. I'd be interested to hear other people's thoughts.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
Which one pays the most? :doh:
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark Twain -
Which one pays the most? :doh:
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark TwainIf money were my only motivation I'd spend an hour commuting to London on the train every day. The role I interviewed for is paying slightly more than my current role (they're not going to offer me less).
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
Both my current role and this role are local to me. In fact, the new role is based literally across the road. So the commute will be identical.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
I was approached recently for a role with a local software house. As it was local, and the job spec sounded interesting I agreed to an interview. I recently had a second meeting to go into the role in more detail. I'm now really confused. The role sounds great, the MD (who interviewed me) was a really great guy and they want the role to guide them technically going forwards (so will have a lot of say in their technical decisions). On the other hand though, I'm happy where I am. I've built up the proceses, technical stack, architecture, build / release pipelines etc from scratch. I have made a huge difference since starting here 3.5 years ago. I have a personal investment and feel reluctant to just walk away from what I've built here. I have a lot of autonomy and decision making responsibility here too. I'd be interested to hear other people's thoughts.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
Some points to ponder over:
- Is the new job going to be reasonably more challenging and/or rewarding? Are you going to be learning anything new in your current role? Compare this to what you may learn in the new role.
- What are the things that you want in your job? Now, what are the things that you don't have in your current job, that will be offered to you in your new job?
- Now for the corollary - what are the things that you have taken for granted in your current role that you don't know will get in the new role?
- All else being the same, what about the other factors/privileges? Like being able to work flexible time, or working from home, miscellaneous allowances like bonuses and perks, working hours, paid holidays, etc.
- Will the existing role want to match the new benefits in order to retain you? If yes, is this something that you will want to consider?
-
If money were my only motivation I'd spend an hour commuting to London on the train every day. The role I interviewed for is paying slightly more than my current role (they're not going to offer me less).
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
I'm not saying that money is the only motivation, and commuting time is certainly important. The things that you mention are not, though (To me anyway. I respect that other people may feel differently). As long as you're happy with the company, the environment, the collegues, the pay, the commute etc, whatever you do shouldn't matter much.
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark Twain -
I was approached recently for a role with a local software house. As it was local, and the job spec sounded interesting I agreed to an interview. I recently had a second meeting to go into the role in more detail. I'm now really confused. The role sounds great, the MD (who interviewed me) was a really great guy and they want the role to guide them technically going forwards (so will have a lot of say in their technical decisions). On the other hand though, I'm happy where I am. I've built up the proceses, technical stack, architecture, build / release pipelines etc from scratch. I have made a huge difference since starting here 3.5 years ago. I have a personal investment and feel reluctant to just walk away from what I've built here. I have a lot of autonomy and decision making responsibility here too. I'd be interested to hear other people's thoughts.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
No one but you can really make that decision. Personally, I've never been anywhere for 3.5 years and still like it there. Even my first job where I had to learn programming from scratch and everything was new. I left there after four years, which was a year too late in hindsight. A new job always means you'll learn new things because they do things differently. You'll get to meet new people who know and do different things. And if you later regret your decision your current employer will likely want you back (provided you don't shit on your boss' desk on your way out ;p).
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
I'm not saying that money is the only motivation, and commuting time is certainly important. The things that you mention are not, though (To me anyway. I respect that other people may feel differently). As long as you're happy with the company, the environment, the collegues, the pay, the commute etc, whatever you do shouldn't matter much.
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark TwainWhen I was younger money was probably more of a factor. I'm older now *cough cough* and am paid well for the work that I do. So for me the things I've listed are important. I want to be happy where I work. I've had a few roles in the past where I wasn't happy due to things like the culture, people etc. So for me personally, happiness is more important than money.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
Some points to ponder over:
- Is the new job going to be reasonably more challenging and/or rewarding? Are you going to be learning anything new in your current role? Compare this to what you may learn in the new role.
- What are the things that you want in your job? Now, what are the things that you don't have in your current job, that will be offered to you in your new job?
- Now for the corollary - what are the things that you have taken for granted in your current role that you don't know will get in the new role?
- All else being the same, what about the other factors/privileges? Like being able to work flexible time, or working from home, miscellaneous allowances like bonuses and perks, working hours, paid holidays, etc.
- Will the existing role want to match the new benefits in order to retain you? If yes, is this something that you will want to consider?
Some good points of consideration :thumbsup:
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
Both my current role and this role are local to me. In fact, the new role is based literally across the road. So the commute will be identical.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
When I was younger money was probably more of a factor. I'm older now *cough cough* and am paid well for the work that I do. So for me the things I've listed are important. I want to be happy where I work. I've had a few roles in the past where I wasn't happy due to things like the culture, people etc. So for me personally, happiness is more important than money.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
What you say now is exactly what I said in the post before this. But in your OP you only talk about the actual work tasks, and THAT is completely irrelevant - in my humble opinion - unless of course you take a job where you don't actually know what you're doing. In that case it's definitely stressing (not that I would know, of course ;) ).
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark Twain -
No one but you can really make that decision. Personally, I've never been anywhere for 3.5 years and still like it there. Even my first job where I had to learn programming from scratch and everything was new. I left there after four years, which was a year too late in hindsight. A new job always means you'll learn new things because they do things differently. You'll get to meet new people who know and do different things. And if you later regret your decision your current employer will likely want you back (provided you don't shit on your boss' desk on your way out ;p).
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
I went through a period of about 5 years before this role of having several different roles one after the other, and felt the need to settle down for a bit. It's not like I haven't already worked for a wide variety of different people, environments, tech etc already in my 20+ year career. I feel I can contribute to the development team and business more now due to my greater understanding of them both. By always being on the move you never really get to know the software in any great detail. You're always the new kid on the block. I've always left every employer on good terms. Never burn your bridges has always been an important adage for me (that person you bad mouthed may be your next colleague or manager).
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
I went through a period of about 5 years before this role of having several different roles one after the other, and felt the need to settle down for a bit. It's not like I haven't already worked for a wide variety of different people, environments, tech etc already in my 20+ year career. I feel I can contribute to the development team and business more now due to my greater understanding of them both. By always being on the move you never really get to know the software in any great detail. You're always the new kid on the block. I've always left every employer on good terms. Never burn your bridges has always been an important adage for me (that person you bad mouthed may be your next colleague or manager).
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
Sounds like you made up your mind about staying? ;)
Dominic Burford wrote:
that person you bad mouthed may be your next colleague or manager
There are two people I really can't think of anything good to say and I warn people for them and if any of those people become my coworker again I'm quitting asap X| I have no need for such toxicity in my life.
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
Sounds like you made up your mind about staying? ;)
Dominic Burford wrote:
that person you bad mouthed may be your next colleague or manager
There are two people I really can't think of anything good to say and I warn people for them and if any of those people become my coworker again I'm quitting asap X| I have no need for such toxicity in my life.
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
I wish I had. This new role sounds really interesting and has got me really confused. One minute I think I've made a decision, then the next I've changed my mind. Both roles involve challenges, interesting work and a good managers.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
I wish I had. This new role sounds really interesting and has got me really confused. One minute I think I've made a decision, then the next I've changed my mind. Both roles involve challenges, interesting work and a good managers.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
Here's some generic, semi-deep nonsense wisdom that may pull you over the line. "Never regret the things you didn't do" :D
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
Here's some generic, semi-deep nonsense wisdom that may pull you over the line. "Never regret the things you didn't do" :D
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
I like that :)
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
I was approached recently for a role with a local software house. As it was local, and the job spec sounded interesting I agreed to an interview. I recently had a second meeting to go into the role in more detail. I'm now really confused. The role sounds great, the MD (who interviewed me) was a really great guy and they want the role to guide them technically going forwards (so will have a lot of say in their technical decisions). On the other hand though, I'm happy where I am. I've built up the proceses, technical stack, architecture, build / release pipelines etc from scratch. I have made a huge difference since starting here 3.5 years ago. I have a personal investment and feel reluctant to just walk away from what I've built here. I have a lot of autonomy and decision making responsibility here too. I'd be interested to hear other people's thoughts.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
1. Pay : Almost Same 2. Commute : Almost same 3. Autonomy : Almost same So it narrows down to 2 things. Are you ready to move from your comfort zone and start a new Job with various unknown factors which you cannot predict now?
cheers,
Super
------------------------------------------ Too much of good is bad,mix some evil in it
-
I was approached recently for a role with a local software house. As it was local, and the job spec sounded interesting I agreed to an interview. I recently had a second meeting to go into the role in more detail. I'm now really confused. The role sounds great, the MD (who interviewed me) was a really great guy and they want the role to guide them technically going forwards (so will have a lot of say in their technical decisions). On the other hand though, I'm happy where I am. I've built up the proceses, technical stack, architecture, build / release pipelines etc from scratch. I have made a huge difference since starting here 3.5 years ago. I have a personal investment and feel reluctant to just walk away from what I've built here. I have a lot of autonomy and decision making responsibility here too. I'd be interested to hear other people's thoughts.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
- What can you foresee about your career in the current company? Do you think it's probable that you will rise in position or do you foresee a stable career in the same position? And in the other company? An engaging career is often more important than other things, static places become narrow quite easily. A new position in a company usually gives more chances to gain a prominent role. 2) What can you know about the new company in terms of annual revenue, accumulated debt, size and year of foundation? Going from a place that will stand up for long to one that in a couple of years risks bankruptcy ain't good.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
-
I was approached recently for a role with a local software house. As it was local, and the job spec sounded interesting I agreed to an interview. I recently had a second meeting to go into the role in more detail. I'm now really confused. The role sounds great, the MD (who interviewed me) was a really great guy and they want the role to guide them technically going forwards (so will have a lot of say in their technical decisions). On the other hand though, I'm happy where I am. I've built up the proceses, technical stack, architecture, build / release pipelines etc from scratch. I have made a huge difference since starting here 3.5 years ago. I have a personal investment and feel reluctant to just walk away from what I've built here. I have a lot of autonomy and decision making responsibility here too. I'd be interested to hear other people's thoughts.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
If you're happy where you are, and pay and commute are the same. Why do you want to change?
Wrong is evil and must be defeated. - Jeff Ello
-
If you're happy where you are, and pay and commute are the same. Why do you want to change?
Wrong is evil and must be defeated. - Jeff Ello
I wasn't really looking to change. I got approached by an agency with the role, and it seemed interesting. I get approached all the time from agencies, and 99% of the roles don't interest me. But this one was local, matched my skills set, was paying well etc. So I agreed to an interview, which went better than I was expecting. So I have a good offer in front of me, as well as being happy in my current role. Hence the confusion.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
