Live data from Hacker News

A career ending mistake

bitfieldconsulting.com

141–150 of 332 posts

Re: A career ending mistake

#141

Earlier quoted context omitted.

I know exactly how you feel. Wish I’d chosen a different field such as Mechanical or Electrical Engineering to IT.

Don't they have even more meeting to go to and documents to write? Things in the physical world require a lot of approvals and consideration before are given a sign-off to proceed to implementation.

Yeah, there are a ton of meeting for those roles as well (possibly more since they have firm hardware prep needs, usually official standards to get approval for, etc.). Reading through the requirements docs and planning years out for a product release being done by the electrical engineers on a new device, made me thankful software was so agile.

Re: A career ending mistake

#142
post #96
post #79

Earlier quoted context omitted.

I feel like your perspective is very narrow. You’ve had a bad experience at one company that you admit has done well for almost all their employees, therefore all companies are evil and your chance of happiness is zero? That doesn’t seem reasonable or even likely. May I recommend “Feeling Good” by David Burns? It has helped many people in situations like yours.

"therefore all companies are evil" Not evil, but that they lie and screw over employees. Are there any companies on Glassdoor with 100% positive ratings (with n>100)?

Would you ever expect that for anything? There are always going to be disgruntled employees/customers. if I see 100% positive, I'm usually looking for the scam.

Re: A career ending mistake

#143
As unobjectionable as this advice is, it also doesn't feel terribly useful. Consider this quote:

> As software engineers, we already know that a too-rigid plan rarely survives contact with reality.

For me this is understating things quite a bit. As someone pretty much exactly mid-career who has done well, I can't really point to long-term planning as providing any value whatsoever. It certainly doesn't hurt to think about the long-term value of what you are doing now as an impetus for change, but thinking too much about specific destinations starts to veer into day dreaming territory.

Instead, what I've found useful is first and foremost to take risks and keep my options open. For instance, IC vs EM is not something about which I hold a strong opinion. When it comes time to change my role the best opportunity may not fit into a rigid taxonomy of "career goals" and there are more important factors.

All too often I see ambitious young people asking for a roadmap to success. This is especially true at higher tier companies and people that have come up through Stanford/MIT where they have been spent their whole life jumping through rigidly defined hoops. They come into the workforce with the idea if they just do what they're told hard enough they can get promoted on a regular cadence. However doing as you're told has a natural glass ceiling, and personal success has more to do with playing to your strengths and seizing opportunity than playing by the book.

Re: A career ending mistake

#144
post #42

I changed careers at 40+ years old. I'm very happy that I did it. People have all sorts of constructs / ideas about how careers work (based on experience) or how they think it works, or how they want it to work. I talk to some college graduates who tell me what they're planning for and have ZERO clue what industry they're talking about, their description is unrecognizable to me ... even tho I know it is the one I wor…

And it seems to lump tech lead, staff-level individual contributor not leading a team, and architect-level positions that have no direct reports. When I speak about career options to people I lead, I say there is a senior level plateau. At that point, you have to be more intentional about growth. If you want to stay in the field, and you want to progress past senior developer (staying a core contributor is an option!…

Staying a productive IC your whole career is fairly straightforward: I really think it comes down to never "coasting" and always being open to learning new things.

The problem is a lot of older people seem to believe that once they get to a certain point, they're entitled a position and respect. Is it a wonder why younger people, who might be more up-to-date than them, don't want to work with them?

The trick is to never get that kind of "old" and remain a lifelong learner.

Re: A career ending mistake

#145
post #42

I changed careers at 40+ years old. I'm very happy that I did it. People have all sorts of constructs / ideas about how careers work (based on experience) or how they think it works, or how they want it to work. I talk to some college graduates who tell me what they're planning for and have ZERO clue what industry they're talking about, their description is unrecognizable to me ... even tho I know it is the one I wor…

> I changed careers at 40+ years old. I'm very happy that I did it. Would you mind sharing a bit more about that? I.e. what did you do before, what are you doing now? I ask because I'm looking for inspiration; my current job is comfortable and okayish but not leading anywhere. And I really dislike the company that I work for.

Not OP but I would like to give my own version of it, if you don't mind.

I changed careers at 30. Before that, I was a "Mechatronics Technologist" which means basically that I worked on automated machinery. I loved that job and did it for 8 years, and I was pretty good too... and I was actually happy with the money... but in that area of work, when you're pretty good, you tend to stay right where you are for the rest of your life. My peers had been doing the same thing I was doing for 25 years. I just couldn't see myself doing that.

Mechatronics includes a little electricity/electronics, mechanics and a lot of software... and software was always my stronger point, so I decided to become a software engineer. I changed to the night shift and went to university during the day. It was extremely tough, but I was so glad anyway!! I just loved being in the university again, this time as the older guy rather than the clueless teenager. Took classes very seriously, learned a hell of a lot.

Left my job in the last year to start an aprenticeship (yep, they do have those for programmers, just look for it)... getting 1/4th of my old salary , but at this point I needed very little money anyway.

After graduation, I quickly got a high paying job and loved every moment of it... after a few years there was some challenges, like working in shit places with shit people, unfortunately, but after moving around a bit I settled at a small company that has really nice people and who absolutely respect me for what I know and the effort I put into learning and teaching others... they recently gave me the pay rise of my life, over 25% , after I had alreay settled at the usual 4% with my manager :D. Just because they wanted to make sure I won't leave (after 6 years at this company, almost any developer would be thinking about leaving, and they're not wrong, even if I am happy, we tend to want to expand our horizons every few years).

Anyway, I am really happy working with software, I work on my own software even on my spare time because I just can't stop :D and it's really fun for me. Now that I am getting quite a lot more than on my old career, I am really happy just where I am (and I am not in management or anything , but what makes me happy is that I basically don't report to anyone: they trust me a lot and let me do whatever I want, which is great). I am well aware that finding a job like this is not easy and it took me many years to get it... but I thought that if you needed inspiration, this story might help you. Good luck to anyone reading and just thinking of starting a career change now! It's worth it!

Re: A career ending mistake

#146
post #42

I changed careers at 40+ years old. I'm very happy that I did it. People have all sorts of constructs / ideas about how careers work (based on experience) or how they think it works, or how they want it to work. I talk to some college graduates who tell me what they're planning for and have ZERO clue what industry they're talking about, their description is unrecognizable to me ... even tho I know it is the one I wor…

And it seems to lump tech lead, staff-level individual contributor not leading a team, and architect-level positions that have no direct reports. When I speak about career options to people I lead, I say there is a senior level plateau. At that point, you have to be more intentional about growth. If you want to stay in the field, and you want to progress past senior developer (staying a core contributor is an option!…

My advice is keep pursuing whatever energizes you, and aim towards being "T-shaped", not "jack of all trades, master of none", rather "jack of many trades, master of 2 maybe 3".

Re: A career ending mistake

#147

I hate my job. I don't know how I got here. Like many I started out in small scale IT just as desktop computers were becoming a thing. I transitioned from mainframe support to desktop support, from there I worked through several desktop support roles, wishing I was server support but never managing to get there... over time I became a desktop architect, and then infrastructure architect, and now well.... I just don't…

I went to university, went to grad school, got a PhD in a hard science, saw that science was a dead end career choice and tried to change career.

I have ended up in IT, although I have never written code for my role, or actually done anything technical for my job. It was immediately into the writing documents, architecting infrastructure and systems that I have no fucking clue about. At no point have I gained any experience about using or building anything, it's all bullshit designs and documents that I pull out of my ass so I can keep my job and not end up homeless ( I make under 40k being a non american). I spend my evenings desperately studying things that I HATE so I can at least have some grasp of what the hell they are before I have to design some complex system using different pieces of tech BUT AT NO POINT HAVE I USED THE TECH. I hate it so much and get rejected for any and all job applications to actually do something and solve problems that I apply for.

I sometimes wish I had never gone into IT, never gone to uni, and just carried on with the unskilled manual labouring job I had on weekends before uni. At least I would be doing something.

I hate IT and I hate tech. If I could do this for a few years and have the fuck you money of a few hundred k in the bank then I would put up with it, but that's not the case.

Re: A career ending mistake

#148
post #73
post #42

I changed careers at 40+ years old. I'm very happy that I did it. People have all sorts of constructs / ideas about how careers work (based on experience) or how they think it works, or how they want it to work. I talk to some college graduates who tell me what they're planning for and have ZERO clue what industry they're talking about, their description is unrecognizable to me ... even tho I know it is the one I wor…

The conclusion I think is missing from the 10k hours theory of mastery is that there is more than enough time in a full lifespan to master 4-6 things, depending on how good you are at managing your time. People who are only good at one thing may find that they aren't good at anything because of it. Don't neglect your passions, even if you don't see how you could ever make money from it, experience in other verticals…

We're making a huge mistake when we see mastery as an end goal.

I played band in grade school, pushed myself hard, burnt out, etc. Learning classical piano as an adult has been a MASSIVELY instructive experience.

Here's why: I'm never going to be a professional classical pianist. Ever. It's far too competitive, I'm probably not talented enough, and it's not worth the effort.

Therefore, the ONLY reason I'm doing it is to find enjoyment and engage in the process of discovery. So it's clear to me that if I find my ego seeping in, it means I'm missing the point and sabotaging my real goals.

Enjoying the process is such a better way to engage with a skill. I'm having a great time and still getting much better (because getting better is simply a matter of consistency and good practice).

But saying "I'm going to practice 10k hours and then I will be happy" is like saying "I am only going to enjoy this hike after I've completed it." Friends: there's nothing enjoyable about the end of a journey, beyond reminiscing on the fun you had along the way.

Re: A career ending mistake

#149
post #122

It's completely unsurprising to me that HN likes to take career advice from someone who doesn't know the difference between 'careen' and 'career'.

I thought this too, but google backs him up as being correct.

Yeah, c'mon. GP, it took 5 seconds to confirm the definition of the word. If you're going to be cynical at least be correct.

Re: A career ending mistake

#150
post #74

A couple things that come to mind with this article. My own journey has been quite nonlinear both in terms of roles (business systems analyst -> data analyst -> technical project manager -> data scientist -> AI research scientist) and environments (F100 -> academia -> startups). My undergrad (creative writing and social sciences) would not have predicted my current role (Senior AI researcher focusing on deep learning…

It sounds like you have had an amazing adventure so far, and it's really inspiring to see that you've been able to have such a fluid career. Could I contact you to learn more about your adventures? My email is Anthony at yesrobo dot net
Post reply on HN