Live data from Hacker News

Ask HN: What huge mistake did you make early in your career?

news.ycombinator.com

281–290 of 505 posts

Re: Ask HN: What huge mistake did you make early in your career?

#281
post #85

I didn't immediately end a meeting to demo a prototype when 2 out of 3 stakeholders were no shows. I got lots of feedback from the remaining stakeholder that the other 2 strongly disagreed with.

Not sure if that's the right lesson. After all, the 1 stakeholder did show up. It would have been a slight to them if you had called off the meeting (basically saying to them that they're not the important one).

I think a better lesson would have been to make sure to check in with the other 2 stakeholders soon after the meeting and provide them with the minutes so they were in the loop.

Re: Ask HN: What huge mistake did you make early in your career?

#282
Frankly, the biggest mistake of my career thus far has been starting it. I didn't get in to a university, so I bumbled around for 6 years at a community college. In the middle of it, I managed to get a 6-month stint at a help desk (which I needlessly proud of, and then promptly fired from). Went back to the community college, burned out on trying to get an associates and transfer, and tried changing course to getting some sort of certification. Ended up with a CCNA (which expires later this year), but it turns out nobody near where I live wants to hire a network technician or engineer without a diploma, and my savings aren't enough to move.

So now I'm in my mid twenties and I've only just managed to get an (unpaid, remote) internship thanks to a sympathetic small business owner whose pet technical project is falling behind schedule. Every time I open the project management tool, I feel a vague sense of unease because I'm socially tone deaf and I can't tell if I'm breaking some unspoken rule about "don't word this message this way because you'll sound too confident for an intern speaking to the senior developer," or "don't make a comment on this task because it's assigned to an intern on a different team and you're not supposed to go out of your lane."

I've been writing code of some sort for 11 years, and using Linux daily for 8. Every day I wake up in my childhood bedroom and send my one remaining friend a message. Sometimes she even replies. Then I have the pleasure of spending most of the day fighting with some stupid self-inflicted issue, like why Ethernet broadcast breaks every week on OpenWrt, or why Pulseaudio uses 200% CPU when I try to get it to communicate with a certain cgroup, or what I'm going to use when Fedora 33 hits end of life and I have to get some other DE set up to replace GNOME.

I've dug myself into a labyrinthine, unsatisfying, inescapable hole. So if I could do it all over again... I wouldn't, because, like a ball on a hill, I'd end up right back in here.

Re: Ask HN: What huge mistake did you make early in your career?

#283
Not believing in myself, having low standards, not being picky enough and ignoring immoral actions and dumb decisions made by CEOs. Those of us who come from poverty often have low self-esteem, it's something that needs to be worked on constantly, like a rotting codebase.

Re: Ask HN: What huge mistake did you make early in your career?

#284
post #176

Earlier quoted context omitted.

That's terrible. What is anyone gaining from all that interview prep?

$400K+ compensation.

Same experience here. I always considered myself poor at interviews even though I've done well wherever I worked.

This time around, I put in 6 months of preparation and it paid off. It's the first job in my 10+ year career where I've felt like I got to choose the job I wanted rather than just accepting what was offered. Although the difference with me is that I feel like this is the first job where I have a strong possibility of staying for more than 4 years.

Re: Ask HN: What huge mistake did you make early in your career?

#285
I put too much effort into work which lead to a severe burnout that rendered me incapable of being useful and productive for years. I'm one of those guys who grew up using computers, every wake minute I was thinking about computer related stuff, everything had a solution using software in my head. I lost this from one moment to the other. Luckily for me it came back after 4 years of the crash. Fun times. Have a life outside of work even if it's just the same you do at work, but do something unrelated. People need to recharge their brains using activities they truly enjoy

Re: Ask HN: What huge mistake did you make early in your career?

#286

Thought that I could replace lower-than-average communication skills with higher-than-average technical skills. The story goes that software engineering is about knowing how to design a system a build it. The truth is: you also have to know how to _sell_ your design, how to document your decisions, how to push forward with your agenda. You won't go anywhere without a team that values you. This means that interpersona…

Similarly, I've tried to power through issues and leverage my ability to focus and grind through hard problems rather than communicate the problems and my situation. Sometimes it impressed people that I 'got things done', but that isn't as great of a gain as the inverse is damaging. People could become frustrated about delays if I didn't manage to power through it in time, or they'd be confused and/or concerned that…

Do you have a blog//email address?

Re: Ask HN: What huge mistake did you make early in your career?

#287
post #76

Earlier quoted context omitted.

That's where we differ on the cause. > "And they took it, and I got back amazing works of art that created all kinds of discordance with our longer term architecture and vision" I interpreted this part as you attributing the cause to the talented folks creating the discordance in your team. For me, it's the reverse. That shows insufficient technical leadership from the top. It's the job of the Tech Lead to convince a…

I think you're probably right and that's definitely part of the issue. However your assumption that people can all be convinced to agree on the technical architecture is part of the problem here. There are so many areas of software engineering where "reasonable experts" can disagree. Static vs dynamic typing, functional vs object oriented, loose coupled messaging based flows vs tightly coupled APIs etc. Successful sy…

Don’t be afraid to say it, the language was Rust wasn’t it? Although Rust usually replaces C or C++, so maybe in your case Go is more likely.

In all seriousness, seems odd that they were able to go so far down this road without anyone throwing up red flags.

Re: Ask HN: What huge mistake did you make early in your career?

#288
Stayed in Canada too long.

It had always been in the back of my mind to move to the US for work but I never did due to not being confident enough.

I realized in my mid-30's that I was approaching a "now or never" scenario and finally made the move to the Bay Area. I really wish I had done it right away at the start of my career rather than spending time at small companies working on small projects.

I know it's better late than never but I know I would have been so much further along in my career by now had I followed my instincts.

Re: Ask HN: What huge mistake did you make early in your career?

#289

Not signing up for ESPP. Doh!

The rational thing to do with ESPP is immediately sell and collect the discount from market value. So if you were fully rational, at best this would have gained you a couple extra thousand per year.

Re: Ask HN: What huge mistake did you make early in your career?

#290

Earlier quoted context omitted.

Depends on the company you’re interviewing with and (IME) region you’re looking for work. In my 26 years since graduating university, I’ve had 13 jobs. So an average of 1.8 years per job. My longest was 6 years at Amazon (ironically enough considering they have such a high turnover) and my shortest was 3 weeks (I knew during the interview it wasn’t a good fit, but I was young and they threw a stupid amount of money a…

> “You’re going to give me a year and then be gone. Why should I hire you?”. Never had a good answer when I was in my 30s. Now that I’m in my 40s, I have a pretty good one. What's the answer?

Usually say it with more tact, but it is along the lines of - “Yes. I’m a professional new guy. I’ve seen and worked on a lot of different types of technology, and I come up to speed quickly. I’m not afraid to ask ‘dumb’ questions when I can’t find what I’m looking for.”

Something along those lines. I lean into it. But as I said, it doesn’t come up too often in the PNW.

Post reply on HN