Live data from Hacker News

A career ending mistake

bitfieldconsulting.com

101–110 of 332 posts

Re: A career ending mistake

#101
post #11
post #6

Earlier quoted context omitted.

I'm sorry to hear that. I've had many positions where I felt like I belonged including my current. The ones where I didn't were very depressing and stressful. I hope you will find more fulfillment in the future! By the way I never planned anything. I don't think more than a week ahead. Somehow I have fallen into the right places anyhow. I tend to get really bored once I've totally mastered a job so I change a lot. I…

It felt great at first. Once you realize that the company - respected/known as a place that does the right thing - doesn't follow its own policies and screws people over, you realize that every company/job sucks. It won't be better anywhere else. And you wasted your youth on obscure and obsolete tech because the company needed it and you wrongly believed their promises that they would take care of you (retraining, ca…

> you realize that every company/job sucks. It won't be better anywhere else.

The world is a huge place, and the variation out there vast enough to be hard to get your head around. It will always be a mistake to assume you have a good handle on "everything" based only on personal path.

Re: A career ending mistake

#102
post #92
post #84

Earlier quoted context omitted.

I recall thinking that my friend who had decided to gamble on Objective-C as his specialization in '95 was being foolish, because NeXT wasn't doing that well, and the hazard pay for being one of the last N experts was probably fraught. Less than 2 years later NeXT merges with Apple, and Steve Jobs has begun the biggest comeback in tech history, including switching Apple to Objective-C. Well then... This sort of thing…

True, but I don't see Filenet and Neoxam ever getting big.

No, and any framework that your architectural astronaut coworkers created is most definitely not going to ever be used anywhere else you ever work. And in fact the decisions it made may well be counter to industry accepted practices outside of that company.

Re: A career ending mistake

#103
Reminds me of this poem which has always stuck with me:

https://www.poetryfoundation.org/poems/51296/ithaka-56d22eef...

---

Ithaka gave you the marvelous journey. Without her you wouldn't have set out. She has nothing left to give you now.

And if you find her poor, Ithaka won’t have fooled you. Wise as you will have become, so full of experience, you’ll have understood by then what these Ithakas mean.

Re: A career ending mistake

#105
post #5

"It's not surprising, then, that many of us find ourselves in less than fully satisfying jobs, with doubtful or non-existent prospects for advancement." Very true. I can't wait for my career to be over. I don't think I'll ever find the position where I feel I belong, so I'll just be miserable anywhere now that I know how broken the system really is.

> don't think I'll ever find the position where I feel I belong [...] now that I know how broken the system really is

Some people are chalking this up to depression, which is possibly part of it, but honestly I think this is simply the reality of a former idealist coming to grips with the big picture. You can't help but recognize that passion will come & go and it's all castles made of sand in the end. Whatever is most interesting for us to work on, someone else is almost certainly doing it better than you or I could without our help, and everything short of this feels like garbage when you only look at the work for its own sake.

All I can say is that what really makes anything worthwhile comes down to your relationships with people. Working a job which involves putting up with a lot of broken shit isn't so bad when you truly appreciate your team-- and on the flipside, working with the coolest bleeding edge stuff in the world will still suck when you don't. Localizing your focus and reinforcing bonds with the folks you enjoy being around can help a lot in getting through it. My two cents.

Re: A career ending mistake

#106
post #5

"It's not surprising, then, that many of us find ourselves in less than fully satisfying jobs, with doubtful or non-existent prospects for advancement." Very true. I can't wait for my career to be over. I don't think I'll ever find the position where I feel I belong, so I'll just be miserable anywhere now that I know how broken the system really is.

This sounds more like a classic case of depression, and might be solvable from that angle.

I don't think it is. I enjoy a lot of things in life. Work just sucks. I believe there was post here about a questionnaire used in medicine (longer than the typical one during a physical) for screening for depression. I scored low, so I shouldn't have it. Same as when the doctor asks during a physical.

Re: A career ending mistake

#107
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.

High level highlights typed out way too fast:

I dropped out of college early as I just wasn't mature enough / ready for that kind of thing / + I suspect ADD made it kinda hard to manage.

I got lucky and fell into a job where I worked in tech support, for some high end networking equipment for mainframes, later for data center related equipment.

Good career, very good pay, but still tech support. I found I worked with engineering teams really well despite being not the most technically proficient person among the teams I worked in (good documentation and being honest with the engineering teams gets you pretty far with them...). So much so that that I eventually rethought my college experience where I wanted to learn to code but at that time classes were "here's a book on C ... now I'll read from the book at you".

After 20 or so years company I worked for was bought out (that's a whole series of stories) and by then I wasn't so sad to be in the group that was being laid off. I got lucky and got paid out better than most people in the US receive so I felt like I had a chance to make a change.

Honestly I suspect money / comfort in changing is really the biggest factor in serious career changes, for me the payout took care of that to some extent. IMO rando promotion to management is not a "SERIOUS" career change. The changes that involve "starting over" to some extent is where the big changes are.

I wanted to stay in technology but also "make things" not just fix things for customers / sales who couldn't be bothered to config something correctly / and so on. So again I thought of working with the engineering teams and decided to take a shot at coding.

I found web development was surprisingly accessible / tons of resources on the internet compared to my "read the book at you" college experience. I started learning on my own and eventually took a coding bootcamp (oh man that's another series of stories). In the bootcamp class I found that older me responded to classes completely differently than younger me. I was now ECSTATIC to have someone drop some knowledge on me every day, it was a completely different experience than college. I was honestly very sad when it ended I was enjoying it so much. I would have loved going back to college on a more formal track after the camp, but family, income, just don't allow for it.

After the bootcamp I got a job at a fairly small company and have been happily coding away for a number of years now / expanding my skills / doing new things. I get to make things all on my own, apps, services, try new things etc. It's great.

Re: A career ending mistake

#108
post #87

A long time ago, after interviewing for months, I finally landed my first job as a developer. It was VERY hard to get your foot in the door back then. On my first day, I was given someone's old computer that had a bunch of junk on it. While cleaning it up, I accidentally deleted all files on the company's file share. Shortly after, I started hearing murmurs of missing files and then, panicking inside, realized what I…

Do you really think you would have been fired? It sounds like it was easy for you to fix. Sounds like it would have been easy for them to fix. Rather than fire you they could say, "Oh yeah we should make sure that something like this doesnt happen again. It could happen to anyone."

Firing seems like a big leap here.

Re: A career ending mistake

#109
post #23

If you love what you're doing now and don't ever want to change jobs, great: you've reached the end of your career, even if it plays out over many decades. Even if you love what you do and you don't want to change anything, the world around you is going to have other ideas. Especially in tech.

Eh. To some extend yes but largely, no. If you loved COBOL all your life you can still find COBOL work. It's harder now but its out there. You're just not going to be working at a cool start up doing it.

So if part of what you love is working at cool cutting edge companies then yeah you have to keep learning new cutting edge things. But if you just want to bang out code in your preferred language there will almost always be a company somewhere hiring for that.

Re: A career ending mistake

#110
post #25

Earlier quoted context omitted.

If you find a good niche, and develop a lot of domain expertise in that area, you can likely make it to the senior levels of an IC, even if you don't have the most super-awesome technical skills. The trick (and of course there is a trick) is to find a narrow enough niche that you would enjoy working in, where you can get paid well, but isn't so narrow that you have very limited choices regarding who to work for.

I think it's kind of rare to find a company that will promote you to "the senior levels of an IC" on just your technical domain expertise. I mean REALLY rare. At most places I've seen, you can get promoted on purely technical knowledge up to a certain level, but beyond that level, you're expected to show "leadership" and "influence" and "cross-team impact" and all that jazz. Same expectation of social skills as if yo…

+1 to all that. :) Seems to me that being a senior IC comes with risk of (1) having to take part in political BS, (2) rat-race of being compared to aggressively-climbing-the-ladder peers (if in an org that does that kind of performance nonsense), (3) not having enough time to both keep on top of tech and lead/mentor others / get scope-creeped into doing the job of a manager for non-manager pay. Therefore to me it can be a poison chalice. Instead, one can stay as a mid-level, and do it really well especially if one has a lot of years experience, and be seen as a helpful nice coworker without having to do X hours of mentoring a week to meet some kind of bar. And be less stressed, have more time for family, etc. I think the mid-levels who could've been a senior might be the savvy ones. This will probably of course, come at the expense of lower immediate salary. Long term however this may increase career longevity , more time to learn, less burn-out etc, thus salary hit is less than expected. It might be like investing your pension in a safe utility stock or something, you'll never get rich, but you'll be fine and not have to worry. :) As regards grumpy old men, from what I see its the seniors and architects that are stressed and grumpy, while I get to crank out code happily. ;) Maybe if you're grumpy, going back to mid-level is the cure? ;).
Post reply on HN