Live data from Hacker News

A career ending mistake

bitfieldconsulting.com

131–140 of 332 posts

Re: A career ending mistake

#131
post #123
post #94

Earlier quoted context omitted.

Right? I teach college students going into IT, and this feels like something they would write. Offhand, I can't think of too many people (myself included) who are a) very happy in their jobs and b) planned very diligently to get to that exact space. Mostly the opposite, "A lot of random stuff happened, I followed through on some stuff that felt right at the time, and just kind of did that over and over."

When you say "the opposite", do you mean that not only were their paths random, but they are not very happy? Can you think of and describe anyone you know who belongs in xor(a, b)?

WOO MATH.

Among the happy people I see, most have the "randomness" I talk about. Among unhappy people, I see a mix of both.

Re: A career ending mistake

#132
post #20

Earlier quoted context omitted.

Yes, we're completely open to having partners and kids around at our events. We actually encourage it. I myself have a child now and am looking forward to taking her to our next event. We're also looking into options of having a nanny. Depending on where we go and what we do.

What about employees with physical disabilities? I've got ten screws in my spine and never thought when deciding to work in computing that I'd be expected to be able to ski and surf.

This is a problem we have had at my company too, how can we be inclusive to everyone with "fun" type events? Some people don't want alcohol, some don't want physical events, etc.

I think the best we can do as companies is know the team, have a variety of activities (inside normal working hours!), and not require 100% attendance since there is never going to be one activity that works for everyone.

Re: A career ending mistake

#133

As it so happens, this resonates with me. All through my professional life, I lived frugally, saved as much as I possibly could, made conservative, yet not "bunker mentality," investments, and avoided personal debt like the plague. Being exactly where I am today, has always been a goal. I also made sure that every job I did, shipped . I sometimes had to " hode by dose ", as it passed by, on its way out the door, but…

> I was fortunate to work for a company that is absolutely crazy about Quality

I crave this. Move fast & break things mentality is a plague. Shipping the proof of concept is a plague.

Re: A career ending mistake

#134

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

Re: A career ending mistake

#135

What such articles lack is that they assume anyone could do anything, but that's just not true. To become a really well-paid, influential developer (IC called here, I think), you need to be smart, so that others that are also smart acknowledge you as a very skilled developer. Plus, it's probably not enough to be very smart (which in itself most people are not), but you need some level of politics that is always neces…

I disagree. We are conflating being smart really with being self-motivated. Also being in the right environment is very important. I do believe that anyone can do almost anything (I'm not going to be an NBA player in my 40s). Certain things though become harder as time goes on given education or industry requirements but are still not impossible - you have people become medical doctors in their 50s. It fair to state that the privilege of time and money also make career transitions far more easier for some folks. But if you are willing to put in the time and effort and stick with it, you can learn anything and make the jump career wise.

If you want to break into a technical field from a non-technical background, the better indicator of success will be grit, perseverance, and self motivation. Learning becomes easier if you are motivated to learn and when its hard still stick with it. I used mentor at a nonprofit web-dev bootcamp that aimed to help students from under-estimated and non-traditional backgrounds (no college education) become software developers. Most of the students did not have traditional STEM backgrounds and were learning to program for the first time. The program was free and deliberately designed to be hard with multiple places where students would be kicked out if they didn't keep up with the work. There were no traditional tests and coding exams. All assignments were project based with a clear deliverables (website, backend database, full stack javascript applications, etc).

Most of the students (over 80% graduation rate and 99% employment rate) who finished the program got well paying dev jobs (avg salary of 90k). Of the students I mentored, the ones who were most successful were the one willing to put in the extra hours to learn and ask for help (often doing 80-100 hours weeks of learning) and genuinely curious to learn outside of the scope of the curriculum. At the end of the day the program was not filtering on general "intelligence" (whatever that means) but really the perseverance of students to put in the work and produce something each week. At the end of 8 weeks

Re: A career ending mistake

#136

Earlier quoted context omitted.

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.

OK. That seems like all the due diligence I'd recommend.

Re: A career ending mistake

#137
Another oldie but goodie in the career planning vein:

https://pmarchive.com/guide_to_career_planning_part0.html

This is Marc Andreessen's guide to career planning, and I've found it exceptionally useful. In particular, he backs off from the narrow "decide what track you want to be on" approach to frame the problem as developing a set of skills that will make you more valuable to any enterprise you choose to be a part of. Then while you do that, watch for the most valuable opportunities to apply those skills.

The other great thing about Marc Andreessen's guide is that it acknowledges the role of risk and opportunity in how your career will shape out. So instead of tracking yourself into a path based on how the world looks today, you stay alert to how the world is changing, and then use the downtime to improve yourself. Despite being a guide for "high-potential people who are not interested in work/life balance", it feels like it puts less pressure on individuals than feeling like there's a set of steps you must hit to be on your chosen track.

Re: A career ending mistake

#138
I'm still in very beginning of my career but I hope to eventually work on something open source. Something that is being used by many. Be it software library, business software or games industry.

Would be very cool to help the Linux gaming push that is happening and help to push it even more. But I don't think I have skills for that yet..

Re: A career ending mistake

#139

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 have meetings, I write documents. I offer sage advice on best practice. That's it. It's not IT anymore, it's just make-work.

My careers have followed a similar route. When I graduated from college, I took a particular job because I didn't want to sit in an office all day. But as I got better at that job, my work increasingly became telling other people how to do the work, and ten years later I ended up in the office most of the time.

I quit that job to start my own company, again, so I could have the freedom to do things outside of an office. And again, as more people joined the company, I spent more time managing the company and writing reports and doing things other than being hands-on with the thing I started the company for. After another ten years, I closed the company.

Now I'm happy writing code. And another ten years in, my job is increasingly not about writing code anymore, but about ideas and processes and meetings and telling other people how to do things. The heads of departments completely unrelated to mine invite me to their meetings just so I can listen and write reports about what I heard later. Now, no matter how hard I try, I spend more time in Microsoft Word than writing code.

There seems to be something about the business world that removes people from the jobs they're good at. Sure, lots of people strive to be the Senior Lead Corporate Upstairs Middle Manager Grade IV. But some people are just happy doing work, and at some companies it's hard to stay in those roles.

At this point in my life, I'd rather be Lazlo Hollyfeld than Professor Hathaway.

Re: A career ending mistake

#140
post #57

Feels like the "senior IC" role described in this article corresponds mainly to today's "3-5 years of experience 'senior' engineer" roles. The reality that I've seen and experienced is that advancing beyond that on an IC track means a lot more people/political work, rather than constant "hands on keyboard" coding as described in the article. It's not the same as management, but it's inevitably more meetings and evang…

The answer to this for me has been to transition to something more specialized: from full stack developer to working in robotics. The previous skills are still relevant and all the new domain knowledge keeps me interested. The combo of domain knowledge and software skills is more rare, so it feels a bit more satisfying than working as a senior IC the way I did 10+ years ago 5 years into my software career out of coll…

Could I contact you about how you made this transition? My email is Anthony at yesrobo dot net
Post reply on HN