After a year of trying, coaching, assuming I’m the problem, talking to my skip level, hard convos with my boss, and much more etc I'm finally realizing trying to force myself into something that's simply not going to fit. With all humility I admit it may be me that failed. But life is short, it’s time to move on.
Cool story bro, why are you telling me?
Well I just want to say, the industry has an obsession with "growth" in performance reviews. But the reality is that growth only works when you build on someone's strengths. Trying to ask someone to grow by changing who they fundamentally are, leads to withdrawal, stagnation, and anti-growth. I'm actually getting worse at my job, not better, because I'm being forced to be something I'm not. It's depressing, draining, and frustrating. I can't be who I fundamentally am in my role.
It's important to know when your strengths are fundamentally misaligned with your job, boss, etc and leave ASAP. Don't try to force yourself to fit into it for the sake of "growth". You'll only drain yourself and there are better places for you. You may end up going through a traumatic experience that actually causes you to LOSE skills and abilities.
That is all, thanks.
After he announced it, I had a 1x1 with him and clearly let him know that he was the boss and I'd do my best to accomplish anything he assigned me. I also let him know that the business analyst duties didn't fit well with my skillset and that I would very likely struggle to produce output. We had a good, honest conversation about the situation and I ended up staying 100% as a developer. In the end he was happy and I was happy.
Why am I telling you? It's that I've learned it better to communicate and hopefully work things out then just pack up and head to another place.
If my boss wants to pay me a SWE salary and then insists I clean out the break room fridge on Friday that is his perogrative not mine.
I mean... I can buy this to a point. But for me personally, there are lines. And there are things I'm just not going to do. Period.
I know it's un-trendy to talk about anything being "beneath you", and I'm not sure that's the wording I would use, but there are simply things that I don't consider being in my wheelhouse and that if you ask me to do, I'm going to say "no". Then you can decide if you want to fire me or not.
Case in point: I used to be a parts counter clerk at Advance Auto Parts. We got a new manager and one day he comes in and asks me to go outside and sweep the parking lot. I said "no" and he tells me to do it or I'm fired. So I rip off my Advance Auto Parts shirt, throw it in his face, say "fuck you" and walk out. 30+ years later I feel absolutely no regret about that. I didn't apologize then and I won't now.
There's more to my life than a job and I can find another way to pay the bills. I don't have to take their bullshit.
My main concern, honestly, is not so much that the work is "beneath me" but more that I get pidgonholed doing that work. I know this isn't realistic, but I don't want come review time for people to say "it's great you do this stuff around the office/for the team/for the org" but it doesn't affect your metrics.
In some cases, I think the fear is being asked to do these things in a non-documented way means you have no evidence that you had these "extra-curricular" things you had to complete.
I'm fortunate I haven't had that happen to me, but it's a fear I always have at the back of my head whenever these sort of requests happen.
I love to sweep. If I could get paid as a SWE to just speak and "garden" our office, to make it a more pleasent environment, conducive to peaceful thought and pleasent interactions, I'd take that job in a heartbeat.
Christopher Alexander is a bit of a god-father of object-oriented programming, and architecture: https://dorian.substack.com/p/at-any-given-moment-in-a-proce...
He believes that all work on something new starts with "repairing" the environment in which that new thing is being created. (The codebase, the room, the block).
The first step of repair is to tidy and clean.
Sooooo I can weave a compelling story to others about why cleaning and tidying is in fact _very_ reasonable to do, and some could argue it's some of the more important work someone could do.
If I were employed at a place that did not let me work on high-impact high-visibility roles, I'd move to somewhere that did as soon as possible.
(Unless I was already where I wanted to get in my career)
Cleaning break room fridges would not be an acceptable task. You sure could say yes and comply if you like cleaning fridges but usually people would probably just say no thanks.
If you just exaggerated to make a point I agree with you partially. But you always have to consider your personal growth and satisfaction with your work.
…within the predefined framework of “roles”
>If my boss wants to pay me a SWE salary and then insists I clean out the break room fridge on Friday that is his perogrative not mine.
Your wording here is kind of vague. Are you saying that you would acquiesce to anything a boss requests?
What if it’s not the breakroom but a public bathroom? What if instead of cleaning it’s foot rubs? Would you taste test exotic foods for your boss? Babysit their kids?
If the answer to any of these is even remotely close to “yes”, then to you there is no such thing as a software engineer or a software engineer’s salary. There would only be only servants and sovereigns, and servants’ wages.
I do my best to communicate openly with my immediate superior about the reality on the ground, but if my advice is summarily dismissed, at certain point I just check out.
Maybe I haven’t lucked out and found a manager who not only listens but is actually empowered to change things.
Sure, but why? Why wouldn't you have a direct, honest conversation with your manager?
I'll tell you why.
Because it can be terrifying.
You don't know how they will react, whether you'll be forced off interesting projects, put at the top of the layoff list, or similar. You can watch how they handle other situations and get an inkling, but you don't know.
Good bosses won't react like that and there are many good bosses out there who want you to grow and will work with you to achieve your goals. But there are plenty of bad bosses too.
From this perspective, it's a lot easier to just pack it in, write off the boss and company, and find a new job. It's less satisfying, to be sure, but less terrifying.
It's taken me a long time to realize how important it is to have a boss you can have a direct conversation with. It's also a factor of my experience and knowledge of my self-worth too.
If I were a new developer in my first job, it'd be a lot harder to have a tough conversation with my boss, because my alternatives would be fewer.
Never understood this attitude. I'd have told him that what he was doing was very inappropriate (without buy-in from the team), and if he doesn't back off I'll quit. He can ask around for other opinions so it's not just coming from me but it's a hard line.
Of course this mostly works cause as a developer you don't need to be afraid of finding another job. But that's good. Workers having leverage over bosses is good.
The reason not to do this is that you're very likely to provoke a defensive response and have the other person dig in their heels. A gentler approach is more likely to get results, less likely to create tension in the relationship, and sets the tone of future decision making as adversarial.
If that doesn't work you can try firmer approaches, and you can of course always quit or use the threat of quitting, but 99 times out of 100 leading with that will lead to worse outcomes.
You don't give up any leverage by first trying to resolve conflicts without threats.
The parent is treating it like a job.
No judgement from me on this, but that's the difference.
Why should anyone work for a person like this? If a boss decides to make huge changes like this unilaterally without at least talking to the team, why does he deserve a polite conversation from his team?
Good advice for almost any situation.
Seems like OP did all these things.
One developer actually found that he liked the business analyst work better and continued on that path.
How do you know it was better, in this circumstance, if you don't know what the outcome of packing up would have been? It's impossible to know all the consequences of our actions.
Today's new code is tomorrow's legacy code. It will need updates, security vulnerabilities will be discovered in it, and it will break occasionally or maybe lose data.
Someone will have to maintain it.
People need to have more respect when it comes to new code. It should be treated like unexploded ordnance.
If I want to ship my software, as opposed to just write it, I need to use tech that's a couple of clicks back from "bleeding edge," and spend a lot of time, "polishing the fenders."
B O R I N G
But I get a kick out of seeing my software out there, ready to be integrated into other people's software (90% of the time, I'm my own best customer, but I write all of my software as if it were being adopted by a Fortune 50 company).
It's sort of hit and miss, but sometimes you get a research project where it's the experimental results which make or break the whole thing - your role is to support the experiment with the software you write.
Example, since this may sound too vague: I'm currently in a project that started off as a research paper and associated Matlab code.
Problem is, you can't ship this to people who just want to see the results and don't have the proper computing power on their work laptops to perform the necessary calculations, so we built a whole web app which does all that at scale.
Other times you do a boring compliance/business application, but such projects are usually timeboxed and with unchanging scope.
Example: 9-months, 11 devs and the result was an app where the user clicked a button once a month which made the backend talk to 15 different APIs that in concert created the last section of a 2k page PDF file because regulations said so.
Boring as hell but it was over soon enough and even got an internal award for "least(zero) complaints".
Shameless plug: We are hiring at Jina AI https://jobs.lever.co/jina-ai
Even if you end up at a "Simple Haskell" place, you'll still have all sorts of opportunities to reinvent the wheel (so that you can run yourself over with it, of course).
You get paid to write glue and CRUD apps because that's what actually solves the problems most people and businesses have.
Personally, I've found game engine and graphics programming to fill this void. It's somewhat tricky to learn, but if you're interested I'd check out Handmade Hero to start.
The job market for engine programmers isn't fantastic, especially if you want to work remotely, but there are definitely jobs out there, and very few people capable of filling the roles.
There are many novel projects that work with novel code, (such as UI / features on top of stable diffusion).
And you can drill into the novel code dependencies (such as SD in above example) if you want to write novel code.
Working with teams shipping novel code publicly is probably the fastest way to find work that pays you to do similar.
I disagree. To me, being afraid of new code or refactoring code means you're working with a code base that has a lot of tech debt and also no serious continuous integration infra.
Everytime I have received some insultingly low offer from a startup, they start talking about "growth", "what I can own", "wearing many hats". Meanwhile, the founder is sitting on some 40% equity grant.
How you're supposed to perform at your currently level is pretty well spelled out by your manager - exactly what your expectations are, etc.
However, you're supposed to perform at the "next level" prior to being promoted. Expectations are less clear here.
This leads to you doing a lot of things you think will get you a promotion (most of which is very valuable to the company). However, it gives the company an easy opportunity to say - oh, all that extra work you did was great and much appreciated it - but that is not "next level" work. No promotion. Try again next time. Also, no, we won't tell you what will get you promoted. Keep guessing. Hopefully you guess better next time. Sorry for your loss and our gain. Goodbye.
It is orders of magnitude easier to just get hired at the next level at a competing company. And, on top of that, you'll likely get paid much more, too.
If you're doing the job, you're doing the job even if they won't officially give you the title.
successfully get another job: 30% raise and no increase in responsibility
anybody married to their current management is contributing to the wage gap
I'm at a level now where the next level up just looks miserable. The people I know one level up are the most intelligent productive people I know but almost every single one of them has some bizarre unexplained health issue likely related to stress. The things my boss, her boss, and their peers are able to accomplish is amazing to me but, man, i just don't think that level of suffering is worth the increase in pay.
I've certainly seen this employed as a way to argue against wage increases. "If we're going to pay you 15% more, how are you going to add 15% more value?" Sadly this rhetoric often works on people because it sounds so obviously intuitive at first. Thing is, jobs can become more valuable even if they're exactly the same, and the employee provides exactly the same input from day to day. The market decides the value of a job.
This quote assumes that the employer refuses to acknowledge the employee adds more value than what their compensation represents.
I'm always of the mind that my value to my employer is 1.5-2x what I'm actually getting paid, at the low end. Asking for more money is simply trying to better negotiate the way I'm compensated for the value I'm already delivering. If my employer fails to recognize that, I've learned no amount of loyalty to the employer or flexibility to try to do more can change that.
Jokes aside, if someone tries such manoeuvres it might be time to reevaluate if 15% is enough to stay.
1. Get a role as a junior developer at a FAANG, get 2+ promotions, hope your team has enough scope and resources to let you try out manager duties
2. Get a role as a junior developer at a growing company, be quickly forced into manager duties, then transfer into FAANG
True, some places will use this to their advantage to underpay you, but you should be aware of it as a tool in your career.
It is likely I have failed. I have tremendous empathy for this boss. But I also have to think of my strengths and where I can be successful elsewhere.
If it's truly getting to the point where it's affecting your mental health, the job is no longer what you should prioritize.
>"With all humility I admit it may be me that failed."
One of the conclusions was that, essentially, the normal instinct with Performance Management to focus on improving weaknesses is wrong and leads to sub-optimal outcomes. The best managers actually doubled down on each individuals strengths, and simply accepted weaknesses as something to be smoothed out to the minimally acceptable level. (e.g. someone may not be "good with people", but they can't be openly hostile with co-workers.) Instead the manager would look for another employee which had that weakness as a strength, and manage responsibilities appropriately.
It speaks exactly to what was wrong in OP's experience.
I can't change my project to need more proof of concepts in every case. So, I have two things in my toolbag: I can try to coach someone to know my expectations for this project and help with coaching those behaviors and skills, or I can let them go for being a square peg when we need a round hole.
I wish we had better ways for matching people with the best jobs that rewarded what make them excel.
tank - can soak up damage and keep the big bad focused on them dps - does damage to the target while healer - makes sure everyone stays "alive" through the fight.
Mismatching roles never really works well. You get similar patterns in the "real world". You're people person does well with end users, etc .. It's a more diverse group (sometimes much less defined) but a similar set of ideas to follow.
Thank god they solved that problem!
No, this is typical "The only way to be smarter than everyone else is to do it different so I gotta do it different".
good managers are good because they're good managers, not because of this 1 weird trick.
"good managers are good because they're good managers"
LOL thanks. I guess all these books are pointless because you figured it out! Thank god you solved the problem!
My advice for anyone in this spot is to quit quickly. I've left a number of jobs within the first month because it was an obvious bad fit. They likely weren't happy about it, but we'd all be miserable after 6+ months of me not performing how I know I can. Don't be sentimental about the work that went into getting the job, just go find a good fit.
Sometimes you don't have a choice. If you've been laid off, you may have to jump on the first thing that comes along (will usually be a suck job with high turnover - those always seem to hire quickly) and keep looking for something good.
Even worse, when you have more of those in there.
But if this is not the case then maybe your current skill set is not a good match to what is currently needed. I don't know, maybe someone else is already covering the things that you say you bring to the table, or the team's activity and goals are just a bad fit for you specifically.
> because I'm being forced to be something I'm not
Many managers see this as trying to help you grow, by getting you outside your comfort zone. In the end it's your choice if you want to play along or find a team/boss that makes better use of your contribution.
Anyway, the interest from other teams is a good sign that your skills are still valued elsewhere. Moving on might be the best choice especially if you've been struggling with this for some time.
In reality they wanted me to do change management, negotiate budgets, negotiate dates, coordinate projects, make power point decks…
Because of my excellent track record delivering technical stuff they expected great results from me doing this new stuff. I couldn’t deliver it as they wanted. “You must grow and become a leader, that’s the path forward” they kept telling me. In the end it didn’t work and I left.
Now I’m in a new team and they expect me again to become a leader but this time it’s different, it is truly a technical leadership and I hope this time it will be different.
In particular, they should have hired a seasoned release manager instead of trying to turn you into one.
(Some Dev Ops proponents have some nonsensical argument about continuous release meaning you don’t need a release manager. Those people are incompetent, and don’t know what a release manager does.)
My personal "growth" trajectory will eventually entail starting my own shop, I suspect many other people will have similar paths.
Same thing happened to me. As I've gotten older management has been been more insistent on me taking a 'leadership' role. What they don't tell you is this is 2x the work (and the sort of work you hate the most) for ~ 10% more pay.
10% is the carrot. The stick is that they start telling you you're 'top of band' for a sr dev and that they can't give you raises going forward despite meeting and exceeding expectations. That particular shoe hasn't dropped just yet, but when it does, I might have to make some hard choices to keep my career moving forward.
But then I got a great manager with a great manager over him. Suddenly, I knew what it was like to be supported properly. For the first time in over 10 years things clicked and made sense.
Turns out, mediocre managers do have a real impact on me.
1. It’s been more than a year and I’ve beat myself up, had coaching, and assumed I was the problem
2. This boss / situation is the outlier from almost every other role and I’ve decided to stop beating myself up about it (for context I’m mid career, worked at half a dozen places)
3. I have complete empathy for the boss. This situation is just different from past roles. They just need someone else in the role.
I admit, perhaps I failed, but life is short and I can keep beating my head against a wall trying to “grow” or move on.
The root cause was poor management in every single case I’ve personally witnessed.
n=((y-1920)-a)/(0.25*a)
where y is the current year (e.g., 2022), a is your age in years, and n is the number of careers you have ahead of you.Quit!
2. Achieve them
3. ??
4. Profit
1. Make (semi-)BS metrics/goals
2. Achieve them
3. ???
4. More funding!
After three years, in my last performance review with that manager, they told me to consider whether I really wanted to stay with the company in a nudge to get me to quit. I really did want to stay at the company, though, so I got on the company's internal job board and applied for a transfer to an open role in another department.
After those three years without a raise above cost of living or any consideration for a promotion, within a year in the new role I got promoted and a performance raise. After two years the company gave me an award, performance bonus, and another promotion at an offsite. I'd gone so deep into the self-loathing hole with my previous manager that I didn't even know work _could_ be like that, anywhere, much less at the same company working with many of the same people.
The new role wasn't even all that different - I still spent more than half my time doing the kind of work I'd expected to do when I joined the company, and even spent a significant chunk working across groups with the same people from my previous team. I was just under a different manager who, instead of trying to warp me into a different version of myself, quickly recognized what I was already good at, found what value that could bring to their team, and set me loose on it. I took off like a rocket.
As a nice side effect, I didn't lose vesting on my options and benefits, even if the options ended up being worthless.
Sure. At least for the near-term, get on with it after you've had the discussion. However, if you're being compensated as someone with a lot of experience in an area and you dropped into something quite different, sure you can learn and certainly some skills and experience are transferable--but you may still be performing at a significantly lower level than before for least at a decent period.
Like if your weakness is poor communication leading towards unintentional hostility to coworkers or inability to prioritize work, that weakness is probably worth be developed.
Spot on. Also remember your “boss” is not your owner. Nor are they all knowing. If the “boss” doesnt meet your requirements change the “boss”. It goes both ways.
It sounds like OP is getting on the verge of the brutal honesty and part of that is acknowledging the actual assigned work makes them miserable. That's fine, and if you can't be moved to a better fitting role then it's time to go.
Another alternative approach is to not care about your work reviews, as long as you're not getting fired, and look for your growth outside your 9-5 job. For the 9-5 think of it as just a tool to pay the bills while you do what you want to do. Performing at around the halfway mark compared to the rest of the team is good enough to not get fired. Use your new-found time, mental energy, etc. to focus on whatever personal or professional goals you want. That's how I started my business and it's going great.
In my previous job, I was asked to do QA work. I have never done QA work before - I don't mind doing it, but I didn't want to do only front end (color, pixel etc) QA work. Needless to day, it didn't work out for me and for my manager.
The best thing to do in such scenarios is to just leave, if that is an option. Especially in professional situations. I have had a lot of jobs in my life - some good, some bad, some super bad. The only thing that was common in ALL these jobs was this - nobody gave a fuck about anyone else, beyond using them to get stuff done. Yes, most people are polite and nice - that doesn't mean they care about you or anyone else. This is not bitterness speaking, this is just the reality. So the best thing to do, is just leave and find a better job
Like I never had much interest in DevOps, but previous jobs have put me in a situation where I had to learn it and although I sucked at it at first, I got better at it, and since it seems to have become almost an unescapable part of a full-stack web developer's job nowadays.
Also I haven't cared much about the domains of several companies I've been hired for or clients I've been put to work for as a consultant (like I actively tried to avoid the insurance and finance industry, and ended up doing work for both). Hasn't stopped me from learning that anyway, and I can follow along (mostly) with our client when they talk about wealth management concepts now, when I was totally lost in those conversations when I first started.
And at a previous job I knew nothing about developing phone systems, but did a little work here and there, and eventually became the department's 'phone systems expert' as I became the only person left in the department that knew enough about those systems as people transferred or left. I handled the role just fine until I left for another job. I don't do anything with phone systems now, but I do have a better understanding of how networks work because of that job, which has been useful.
It is an opportunity cost, though. I have lost some of my other skills because of time spent in these roles. Like I think I'd have trouble going back into video game development after spending so much time out of it, at least at the level of seniority that I would kind of need in order to get sort of in the ballpark of the salary I'm currently making.
I'm still making games in my spare time, but I don't have a ton of free time anymore, so progress has been slow and the games I've been working on have been tiny in comparison.
> I have a very different vision for my role
This is the critical piece, and I’m not asking for detail, but the details here are everything and it would be interesting to hear both sides of this mismatch in expectation.
That said, let’s not forget that a job is where we trade our time to spend doing something the company wants in return for money. This is complicated, but we can’t necessarily expect to have our own vision for our role, we can only seek out roles that fit us and hope that it’s an environment that either allows our vision or matches it. Some managers want people to build their own vision, and some don’t. Even though the best people and the strongest growth comes from people who do have their own vision and take initiative to change things, there’s also a ton of work out there where the company just needs something specific done, and that something might not be what you want.
BTW, from experience, a lot of this still mostly true even if you run your own startup; we just trade time for something the customer wants, and it often isn’t what we’d rather be doing.
> With all humility I admit it may be me that failed.
If it’s not a fit, then it’s not your failure. Go find a better fit! Good luck!
We have a tendency to take all the blame onto ourselves. We have a society that tells you to take personal responsibility for everything from your career success to saving the planet. But fact is that if the ship is sinking you will go down too.
Find a better boat. It is the most powerful thing you can do in life.
https://www.marcusbuckingham.com/books/
It's been a good decade since I read some of these, but I recall that there is often a focus of "eliminating" weaknesses instead of avoiding them and focusing on strengths. But his interviews led him to believe the opposite is best - just work around weaknesses, but put most of your effort into expanding upon strengths.
EDIT: See this was mentioned already - https://news.ycombinator.com/item?id=33248487
Ultimately a move was what made my life better.
It happens and it's not necessarily anyone's fault. A new manager comes in with different views of what work needs to be done and what doesn't. For whatever reason maybe transferring internally is hard right now for whatever reason or maybe there just aren't other roles internally that excit you.
(What I have seen though is managers who come in, make changes in roles, and really try to hang onto headcount even if some of that headcount is people they wouldn't have hired. That's on them.)
Depending on a lot of factors maybe it makes sense to hang on for a while. But, at the end of the day, if you're in a job you don't really care for and don't really have the background for--especially if you're supposedly very senior--that's just not a stable or good situation.
I disagree that growth can only come from strength. Like many coders, I was bad at communications, particularly in public speaking space. My boss needed an engineer that can present work at company meetings, he basically tasked me (mainly because I knew the system and business very well). It was 6 months of absolute terror as some of you might know. In the end, I succeeded. I learned more than about me than before, while my technical skills didn't improve, my soft skill improved leaps and bounds. My career also has improved significantly.
What I'm trying to say is, change is hard, especially if it impact the core of who you are. But like everything else in life, stepping out of your comfort zone is important for growth if that's something you desire.
I'm only sticking around in the hopes of transferring to another department where my friend is the group leader.
I would even argue that is why some bigger firms such as stripe have a rotation model where you can explore new jobs and positions within the company.
Have you told your boss about how you feel?
You can’t escape yourself..,
If you want to work in tech yet have little stress work in government IT.
Personally I could never work at places like meta, amazon, google and other places where you are under a heat lamp and those around u are too. Of course there's more money but for me the stress (affects health hugely) isn't worth it!
I totally agree with this. What poor companies do is try to force you into a process no matter what. The process is king and if you don't fit it, get out.
What they should do is go grab a coffee with you and ask you what your desires are on a regular basis. And even to some extent make the company strategy malleable to this (across all staff). That is if employee churn is an issue, which of course it is because hiring is a big hassle!
Obviously the more people in the company, the more standardization of process you need. You may have less need for certain roles that are jacks of all trades and need specialist squads. But there should be always room for asking staff what they ideally want and trying to get them closer to that.
Respectfully disagree. Growth comes from going beyond what you're comfortable with.
Also not sure this is "ungrowth" and more a general misallocation of human capital. Good bosses are proactive, yes, but that doesn't mean randomly messing with team dynamics and roles like you're a chemist trying to find the philosopher's stone.
I like trying to get better at the things I've discovered some way to get progress at, but I hate trying to push myself to try and be perfect at something I can't.
In the last few months I have basically neglected my regular job which is to be a team lead and architect. Other people have picked up the slack to some degree but I feel more and more that my tech skills are going downhill because I am dealing with a software system that shouldn’t ever have been bought.
This is becoming a real career problem. I am learning “skills” that are totally useless in any sane company and neglecting the skills that can get you a good job.
I'm pretty high up the IC chain (the leveling guide even says my level is a natural place for someone to be at for a long time/indefinitely). And I'm not interested in the next level. More, I'm not interested in growing professionally anymore.
That's not to say I'm not gonna keep solving problems and learning new things. But at this point, I'd just like to be Very Good at What I Do for the next years.
I'm busy growing personally on many axes anyways. But they aren't useful to my employer. But I only have so much "self-improvement" juice to give.
Also growth isn't always just building on strengths. It is also knowing where you are short on skill and learning more to at least do that skill ok and then maybe delicate or trade tasks with someone that is better at it. It is about understanding yourself.
One of two things will emerge. The employee has strengths which can be used to benefit both parties (employer and employee) and can be grown which creates a career path. Or the employees strengths are of no use to the company and they part ways amicably.
This is the sensible way to product growth and trying to shoehorn someone into an unsuitable position is damaging to the company and the employee.
https://www.lloydatkinson.net/posts/2022/my-thoughts-on-what...
I'm a founder at a small company, and the current environment has us stagnating a bit
My biggest fear is that our best contributors go elsewhere because we aren't able to fully enable their growth here right now
I've lucked out in terms of how loyal my team is, but loyalty only goes so far, and the business has an obligation to enable the careers of it's contributors
Basically just saying, there are two sides to every deal and if you're not thriving due to environment, you have a responsibility to yourself to find an environment where you will thrive
What do you think your strengths are? Which strengths does the manager want you to grow?
This is how I hire, I look for people willing to adapt and learn, because our field changes constantly you have to be able and willing to adapt to it. That may not be comfortable.
One of the basic principle was you can only be world-class in your natural strengths.
Some of others were: - Try to ask why as less as possible as it's getting your rationalisations and emotional most of the time - Ask what might I do differently instead - Risk, trust, honesty triangle - These need to be equal at all times for teams to be effective - Never judge and never say bad/good. Works/doesn't work are alternatives
Yours truely, A dude on your train.
Always remember failure has no inherent meaning, it only has the meaning we attach to it. This can be a liberating realization.
It's especially hard if you've basically been good at the things you have done in life, not realizing you either got lucky choosing things you were good at, just tended to be drawn to things you were good at without realizing why, or got jobs at things because others realized the good match...
Now if she's being a jerk and forcing you into a corner by learning things you don't want to then leave immediately.
Sometimes jobs change on you too. One position used to be for you, and now they need someone different. You should almost never strive to become that someone different.
2. If it's not a fit, it's not a personal indictment. Move on. Not everything you do in life works out. However, if this happens over and over, it might be you.
But just in case you need to hear this, I don’t know you but I believe in you. It takes a lot of skill to write something tactically useful when you’re in the deep end of shit pool. You’ve got this.
https://www.amazon.com/Case-Degrowth-Giorgos-Kallis/dp/15095...
The world needs a happy version of you. Everybody benefits then.
So, again, thank you for posting this.
This is well articulated and certain something many of us can relate to. Thanks for writing this.
Agree 100% btw.
Just my viewpoint though.
Softskills.audio