Decisions, decisions
-
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
-
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
So it's basically down to whether you want the security of a safe and still good job. Or if you'd like a new challenge. Only you can answer that. But if you believe you will get bored some time in the future, you better go for it. Otherwise you shouldn't.
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
How close to retirement are you? It sounds like you can stay where you are till then (I know I did that and stayed in the same position for 15 years after 20 years of being a consultant/contractor). It really comes down to comfort and do you want to accept the challenge of starting all over again with a different company.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
-
How close to retirement are you? It sounds like you can stay where you are till then (I know I did that and stayed in the same position for 15 years after 20 years of being a consultant/contractor). It really comes down to comfort and do you want to accept the challenge of starting all over again with a different company.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
I'm more than prepared to move if I thought it was the right thing to do. Pushing my limits and setting myself challenges has defined my entire career. I even moved my family early on in my career to be nearer to a role. Normally I would have instinctively have made up my mind by now either way. This time the decision seems more difficult as the pros and cons are so evenly matched.
"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
