Live data from Hacker News

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

news.ycombinator.com

371–380 of 505 posts

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

#371

Earlier quoted context omitted.

“ Code: The Hidden Language of Computer Hardware and Software” by Charles Petzold and “The Elements of Computing Systems” by Noam Nisan and Shimon Shocken are both a great introduction.

I have both books but yet to finish The latter book you recommend is Nand2Tetris I believe

I've read both books and done the Nand2Tetris course.

I think Code by Petzold is decent in that it's a book you can read in bed etc. but it spends a long time discussing mechanical relays as an analogue and later discusses various processors in depth.

I think Nand2Tetris is slightly better in that it focuses on what I'd consider to be the most important stuff, but it's an actual course and requires significantly more effort.

Nand2Tetris is probably the best course I've ever done though, including my university studies in Physics and ML. It's fun and you learn loads.

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

#372
Mistakes?

(1) By accident, I had a relatively good career going around DC in applied math and computing for US national security. I thought it would help my career to know more math so got a high quality Ph.D. in applied math. I WAS then better qualified, but I also had broken my career continuity. My brother saw that early on: "After your four years in graduate school, you will be four years behind in your career."

And, I didn't realize that the opportunities in DC were unique or nearly so. I would, could, should have (A) not assumed my career would work away from DC and (B) stayed in DC.

Lesson: If you have a good career going in DC, NYC, Silicon Valley, wherever, don't assume without good evidence that that career will also work in another location.

(2) Near the end of my Ph.D. work, I had a part-time job and did some good things. Then occasionally a person never seen before was in the office for a few hours one or two days a week and wanted to chat with me about whatever, even sports. Eventually he got my opinion on what the US did in Viet Nam. In retrospect I was being recruited for some high end highly secure slot but violated a rule Mom gave me -- never talk about politics, sex, or religion. I had talked about politics. Don't do that. So, being frank and honest about Viet Nam cost me a good career step.

(3) Dad's idea about a career was to get a good education and, then, a good job based on that education. Eventually I concluded that, nope, instead, with or without a good education, it is from important to crucial to own a business and to make it successful, and early in a career near the top of the TODO list is to find a way to own and run a successful business.

(4) I didn't understand an important point about career dynamics: (A) It is tempting to guess that academics is good preparation, maybe the best, for a non-academic career. (B) Instead, for a successful non-academic career, it's important to ride the waves of the hot topics, and, bluntly, academics is largely out of touch with what the hot topics are. (C) While some academics can help, possibly a lot, there is a special way to know what the hot topics are in a non-academic career -- see what work and topics people are getting hired for.

Net, be reluctant to let academics tell you what will be important in a non-academic career and, instead, let a non-academic career tell you what topics are important for you in academics. And if have a good ugrad education, then pursue those topics while on the job by independent study evenings and weekends, maybe partly on the job -- to pursue those topics, don't leave the job to become a full time student.

E.g., when I was in my Ph.D. program, there was a prof, soon famous, who apparently had been hired as a consultant to work on a topic, call it, X. Well topic X was in practical computing, a bit tricky, not at all a topic in academics, and from my non-academic work a topic I knew well. With resentment the prof asked me: "I suppose you know X?" I had a one word answer: "Sure". Really it was a collection of topics such as X that had my career going well, e.g., annual salary six times the cost of a new high end Camaro. For that summer job working on topic X, the prof was about to have a tough time!

(5) One possibly good career direction is to get a job in a startup in its early days and get stock. For the stock, before joining (A) get the stock deal in WRITING, (B) study the details of the stock deal (e.g., vesting), and (C) have the deal reviewed by an appropriate lawyer. Handshake deal? Don't do that.

(6) Applied math and, usually, computing work or don't independent of human emotions. People, however, commonly are driven more by their emotions than what is true in math or computing. It is crucial, then, to pay close attention to the emotions of people.

As a special case, one way to get people to hate you and work against you is to present some work in math or computing that (A) has power important for the organization, (B) is understood only by you, and (C) looks rock solidly correct and, thus, not easily ignored. Then the people who hate you maybe cannot find fault with your work but might be able to arrange to get you fired.

Part of one way to get you fired is gossip -- be aware that you may have to defend yourself proactively, guess what you are secretly accused of and then defend yourself against the accusations.

More generally, whenever you start to be especially successful, you will attract attacks like some piles attract flies.

(7) There is discrimination in the US. Not often mentioned is that there are some cases of severe discrimination in the US against native born Christian males of European descent. So, it can be important to realize that fact.

(8) Try to keep confidential and not to report on work in progress: If your work looks good, your enemies will try to kill off your work before it starts to show its power or arrange to take credit.

(9) There can be corruption, e.g., people getting quite secret financial kickbacks. So, you can get a bitter enemy if, even without realizing it, you threaten their corrupt money. So, at least try to guess who might be corrupt and how, and then try to avoid that person or their source of corruption.

Of course, if there is someone corrupt in the part of the organization chart you manage, you will likely want to get this person moved out. Of course if the corrupt person has some close, say, family, connection with, say, a member of your BoD, then you have to be careful!

Point: Be aware that corruption exists.

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

#373
post #200

I was a teenage intern, and my software engineering team was crunching in the evening on a project, when there was a problem on a workstation. The sysadmin was gone for the day, so I was asked for help. I saw the root filesystem was full, partly due to a bunch of junk files in `/tmp/`, including some files/directories that started with `.`... You might guess where this is going, when someone hadn't yet developed good…

As an aside, I've never used '-f' in 'rm'. I've lived a happy life without it.

Of course I know of its existence, but it was just never necessary in any of my usecases.

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

#374

Earlier quoted context omitted.

Yep, never ever quit with a list of what you did not like. You gain nothing from it.

I don't know about this one. Sometimes it's important to take a principled stand. I was at a stocks company for all of two weeks, hired by a former friend. The very first day I was told not to email the security team directly and that all my emails from then on must be approved by my team lead. Within a week, I was told to lie to the security team. I spent most of those two weeks either in meetings or as a glorified…

This is not good advice for most people. You should always leave on good terms regardless of how much you hate a job. As an employee you often don’t know the constraints or risks of a project so you can’t make a firm judgement on ethics or transparency. It’s a small world and you’ll likely run into former colleagues again or rely on them for a reference (even without your knowledge). Under game theory there is no advantage with being a being a difficult leaver.

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

#375
post #284

Earlier quoted context omitted.

$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 po…

I get why you would do it. But what do they get out of only hiring the best at interview prep. Is the correlation really that good between good engineers and those who can leet code for six months?

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

#377
post #116

My biggest mistake, that I made again and again, was not leaving a job when it was time. I thought I had something to prove, but there was never any point to it. You don't owe anything to an employer. You can't prove anything to an employer. They have absolutely no loyalty to you, and care less than nothing about what is right or wrong, wise or foolish. So: If you ever think things might not turn out as well as you h…

This is largely true but I know there are employers who do care and who are loyal to their employees. It's all a matter of people and who you are dealing with.

The problem is where to find these companies. Job review sites are either turfed by companies who tell their employees to leave a good review, or by disgruntled leavers who want to unload.

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

#378

In '98 I uploaded an index.html for a subsection of the corporate site to the root, squashing the corporate home page in the process. We didn't have any source control or backups. I had a colleague who had the page open, and I was able to copy the code from his browser. Learned a lot that day!

Haha, oh my god.

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

#379

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?

You can also mention how companies encourage disloyalty by paying new starters significantly more than existing employees. I’ve seen great people working hard towards a promotion, putting in the hours, playing everything right - only to be passed over for a promotion due to management politics and a boss that was looking out more for herself than her team. Meanwhile, another employee simply just left and walked into…

Probably better off responding more along the lines of:

I bring a wide array of industry experience, that you'll benefit from. I'm hoping for a longer term engagement, but even if it's a shorter one, I typically leave them better than I found them.

In your own words, ofcourse.

P.S. I suspect your statement will get you rejected from companies that know they have the same problem but can't fix it. If you don't need a job, be as honest as you want, if you do, you're better off going with the positive spin.

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

#380
I would say, not letting go when I disagreed with some decision I knew was wrong. Younger me would tend to tenaciously fight those, to my detrement. You end up getting a reputation for being argumentative or hard to work with. Later I learned waiting things out and more subtle ways to affect change.
Post reply on HN