Live data from Hacker News

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

news.ycombinator.com

321–330 of 505 posts

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

#321
post #57

At my first real technology job I worked at an early web hosting company. Cutting edge stuff in 1996. We hosted full domains for $60/mo and tilde domains (e.g.; domain.tld/~myname) for $25 or $30 per month. We hosted on BSDi, a proprietary BSD and every domain customer had their own sub-directory with user and group ownership. As an aside, BSDi would happily let you run `rm -rf . ` and would walk up to root and back…

I had a similar screwup, different outcome.

Was working for a brokerage as an intern, IT gopher stuff, pretty much my first office job.

A month in, I’m told by my boss to delete a directory on the file server. Which I do. I scurry off and rm -rf it, think it’s taking a while, so saunter out for lunch.

Turns out that that directory was an active mount point for the root of the filestore on which they kept all of their user drives, legal documentation, everything. rm had got about halfway through wiping it before they pulled the plug on the machine.

Turned out they didn’t do backups, because “nothing like this ever happens”.

My boss’s boss flipped his desk over the incident, hurled a monitor tree at me like a battleaxe while purple and screaming, incandescent with rage. My direct boss of course fired me. I was literally booed out of the office by the traders, who chucked cups and bottles and crap at me as I did the walk of shame. Grown-ass men. I was 18.

I learned then that most people everywhere just want someone to blame for their own shortcomings, and being that person can be a valuable service if correctly structured.

Edit: I lie. I learned no such thing at the time. It dented my confidence and gained me a reputation in the city - and not a good one. It was however one of the formative experiences that led to me starting my own business, and never, ever treating anyone (or allowing anyone in my business to be treated by anyone else) in the fashion I was treated.

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

#322
post #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…

[deleted]

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

#324
I built our CI and tested failures and deployments. I never tested someone intentionally stopping CI while it was in progress. Two days after the team started using it, we realized we needed an immediate revert but the code was currently being built. So we just hit “stop” on the TC job. No big deal right? The current step was stopped, but it moved onto the next step like it passed. It deployed terribly broke things to production.

This is when I learned TC sent SIGKILL on a stop and not SIGTERM, which my scripts were expecting.

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

#325

Earlier quoted context omitted.

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

I mean, that’s cool, but you haven’t actually adressed the problem, which is that I’ll spend 3 months training you, only to have you quit after 9 more. That’s not really a good investment

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

#326

Taking a job as a solo "lead" developer at a startup for my first job out of school. I picked up so many bad habits and it took a while to figure out how to collaborate with others on code. If I had to take that same path again, I would get involved with an open-source project to solidify the fundamentals.

Can you talk about some of the bad habits you picked up (and maybe how you could have avoided them at the time)?

Sure, here are a few off the top of my head:

- My Git commits/changesets were huge. There were so many code changes to so many files that it was very difficult to review. I learned how to write better commit messages and streamline my commits a few years later.

- I ignored best practices for the sake of getting things done. Programming wisdom and best practices seemed like overkill at the time, as I only measured my work by the number of lines of code I wrote. I needed to find the middle ground between quality and productivity.

- I organized projects/files inconsistently. This was because no one else had to work with the repo at the time.

- I was bad at managing expectations of stakeholders and estimating tasks. Because I was inexperienced, I would over-promise and under-deliver at times. As I went along, I realized better ways of communicating what could and couldn't be done within a sprint. Now, I think when someone asks for a feature -- the answer should generally be yes, with whatever caveats/blockers that are foreseen at the time.

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

#327

I worked at a really toxic job at a hedge fund where I let them burn me out in a year and then they fired me. Several mistakes were made: 1) I failed to realize the importance of face time/asses in seats time. I was spending tons of ime working late nights and weekends solving hard problems outside of trading hours where nobody could see the hard work I was putting in. Also, being the only hourly, all of my coworkers…

> he spent that few minutes kicking me in the ribs as hard as he could while I was under his desk hooking up the new keyboard.

For real?

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

#328

Earlier quoted context omitted.

We all hate it, but it pays the bills. It's ultimately better to be in this position as a thoughtful person aware of the consequences of your work, since they would just replace you with someone less conscionable otherwise.

The harm done to your psyche when you work on something you know makes the world worse is… hard to recover from.

> The harm done to your psyche

Are you being serious?

https://www.youtube.com/watch?v=GaGQ3KGOMto

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

#329
post #57

At my first real technology job I worked at an early web hosting company. Cutting edge stuff in 1996. We hosted full domains for $60/mo and tilde domains (e.g.; domain.tld/~myname) for $25 or $30 per month. We hosted on BSDi, a proprietary BSD and every domain customer had their own sub-directory with user and group ownership. As an aside, BSDi would happily let you run `rm -rf . ` and would walk up to root and back…

I had a similar screwup, different outcome. Was working for a brokerage as an intern, IT gopher stuff, pretty much my first office job. A month in, I’m told by my boss to delete a directory on the file server. Which I do. I scurry off and rm -rf it, think it’s taking a while, so saunter out for lunch. Turns out that that directory was an active mount point for the root of the filestore on which they kept all of their…

A monitor tree?

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

#330
It was my third year of my first job, I was alone working on the live database. I ran the following SQL command in SSMS:

DELETE FROM TABLE WHERE ID = something

And the table had a million records. Guess what!

In SSMS, the DELETE FROM TABLE was selected.

It took an hour to restore from backup, it stopped a lot of people from working, many new records was lost, they had to keep pile of papers to enter into syatem again.

Post reply on HN