Live data from Hacker News

Things I’ve learned in my 20 years as a software engineer

simplethread.com

711–720 of 745 posts

Re: Things I’ve learned in my 20 years as a software engineer

#711
post #62

Earlier quoted context omitted.

Saying 10x programmers are a myth because it's crazy that someone could do in 1 day what another could do in 1 week makes the assumption that both programmers in the example have the same amount of context, background understanding, and experience. The benefit of talented engineers comes from the fact that they avoid costly pitfalls - not that they pump out more code per hour worked. I feel this "10x programmers are…

I always read it as a direct comparison though. It doesn’t matter if I have better experience or I can contextualise intent better; the phrase “10x” means it would take a team of 10 to do it, in the time, scope, budget (whatever). But there are major reasons this could be the case, if I’m on my own and I know the direction then I don’t have to quibble about what framework to use, how to name my variables, what I cons…

The author exactly says this "two engineers with the same experience".

I'm sure there are engineers that can create an architecture 10x better than mine.

But show me someone that can create UI 10x faster and I'll admit they're a God.

Some things can't be 10xed after some point. It just takes work.

Some things can be 10xed and some just can't. I find it silly to think someone can be overall 10xer at everything.

Re: Things I’ve learned in my 20 years as a software engineer

#712

Earlier quoted context omitted.

and also importantly people who have family to take care of. If someone comes to me and asks for time off because they have children or partners or parents to take care off and they take that seriously that certainly deserves some respect would make a better impression on me than someone showing up with a Patrick Bateman business card in hand

Nobody should have to even give a reason for a time off request if it's part of your work agreement.

Sure thing. But I always give reasons. That stuff builds trust.

Even silly things like "hey I'm tired and feeling down, gonna take a couple of days off" builds a lot of rapport.

And unless you're dealing with a huge asshole of a boss, it's never a problem. And if it is, you'd get warned so you can leave faster.

Re: Things I’ve learned in my 20 years as a software engineer

#713

Earlier quoted context omitted.

Mmm, in my experience, it’s more that people don’t believe that something truly valuable to them comes packaged in your arrogance, brilliance, or effortlessness. They’re so accustomed to those things being signs of assholes, or reasons to feel inadequate, that they resist looking at what’s being delivered. The OP’s point about bracing for a long battle means that truly persuading others is not just about making the a…

I'm not at all arrogant in real life. My last boss even told me that I don't stand up for myself enough. Besides, I didn't even say it was about me and merely brought it up to make a point. Imagine constantly improving yourself for 15 years, then after 15 years, everyone you work with only gives you positive feedback and everyone wants to be on your team. You even launch open source projects which get thousands of st…

No offense, and I mean this, but from what you've said I wonder if you suffer from Nice Guy Syndrome.

It is often referred to in the context of dating, but applies to work as well.

There is a book called "No More Mr Nice Guy" that you might find interesting.

Re: Things I’ve learned in my 20 years as a software engineer

#715
post #691

Earlier quoted context omitted.

Interview is not a date. Its a formal meeting where parties are trying to acheive something concrete. Hire a good employee, find a good job. If someone starts off with asking about essential thing that is important factor for them it means that its a dealbreaker issue for them. Whats the point of interview if they know there is no flexi time, and you only look for flexitime jobs?? Its actually a matter-of-fact approa…

If properly delivered? Sure. As many folks seem to be indicating in these threads, as the primary or even sole topic of interest to them? Would you then consider that a plus?

They know what they want, they do go around the bush doing pleasantries and waiting for the script to get to the place where they can ask the question they wanted to ask in the first place.

To me person like that will be first to raise a hand when something is not right in the project. It might also be a good indication of goal oriented thinking, they know whats important and prioritize to achieve goal

Re: Things I’ve learned in my 20 years as a software engineer

#716
post #713

Earlier quoted context omitted.

I'm not at all arrogant in real life. My last boss even told me that I don't stand up for myself enough. Besides, I didn't even say it was about me and merely brought it up to make a point. Imagine constantly improving yourself for 15 years, then after 15 years, everyone you work with only gives you positive feedback and everyone wants to be on your team. You even launch open source projects which get thousands of st…

No offense, and I mean this, but from what you've said I wonder if you suffer from Nice Guy Syndrome. It is often referred to in the context of dating, but applies to work as well. There is a book called "No More Mr Nice Guy" that you might find interesting.

One person tells me my problem is that I might be an asshole and you tell me my problem might be that I'm too nice... Why is it so far fetched to suggest that maybe the problem is not me? What if the problem is that most people in power have impostor syndrome and they feel jealous and/or guilty when they see a competent person who didn't achieve as much as they did. It makes them doubt their own success narrative. People don't want to be reminded how lucky they are; as an employee, I would be a walking reminder of that. That's the best explanation I can come up with to explain my experience in recent years why I struggle to find opportunities. I had many more opportunities 5 years ago back when I was far less skilled.

CTO types wants to be mentors to starry-eyed juniors, they don't want to improve themselves anymore, they think they're already as good as they can be, they don't want to be schooled by some low rank person.

Re: Things I’ve learned in my 20 years as a software engineer

#717
post #691

Earlier quoted context omitted.

If properly delivered? Sure. As many folks seem to be indicating in these threads, as the primary or even sole topic of interest to them? Would you then consider that a plus?

They know what they want, they do go around the bush doing pleasantries and waiting for the script to get to the place where they can ask the question they wanted to ask in the first place. To me person like that will be first to raise a hand when something is not right in the project. It might also be a good indication of goal oriented thinking, they know whats important and prioritize to achieve goal

As long as they’re not just talking about nothing but what they want, then they aren’t the problematic cases I was referring to.

The few times I’ve had someone do that, the last thing those folks did was (as one put it) “look for problems” by raising project issues or really doing anything but the bare minimum. A bare minimum that had to be clearly articulated several times to the several people I’ve run across - who one then specifically asked EXACTLY what I meant by ‘keep the system running’, so they could exclude a bunch of long term maintenance work from that minimum shrug

IMO, if someone is curious and cares about what they are working on, it shows, and we would never even have this discussion about them - even if they did ask about EXACTLY what the vacation policy was.

Re: Things I’ve learned in my 20 years as a software engineer

#718
post #474

> No one is going to tell you in an interview that they are going to be unreliable, abusive, pompous, or never show up to meetings on time. People might claim they have “signals” for these things… I had a great interview with one of the FAANG companies. The technical interviews, 6 of them in a row!, felt more like they were wanting to see me fail spectacularly rather than focus on my approach of solving whiteboard pr…

>> I struggle with work-life-balance and working on it. If I can overcome that and learn how to take breaks timely I might be more productive.". .. HR didn't like it because it was not one of the canned responses she was expecting ¯\_(ツ)_/¯ Just curious, how do you know that (a) you failed in HR (b) that it was this question and (c) for this reason? I ask because it's unlikely that this was literally the feedback giv…

> (a) you failed in HR (b) that it was this question and (c) for this reason?

A very close friend on the same team (the one who referred me but he didn’t do the interview, obviously) but yes according to him that’s exactly why I failed. The recruiter told me exactly the same thing when he gave me the “bad news”.

> “in your head” Maybe but almost all of them were being very condescending. And I have been on the both sides of interviews a few times so I’d know.

Re: Things I’ve learned in my 20 years as a software engineer

#719

Earlier quoted context omitted.

We really need a new standard. Unlimited PTO Min 20 days/year. If you don’t put a number then it’s assumed to be 0

In Norway you're required by law to take four weeks and a day vacation every year. Almost everyone has five weeks vacation time in total. Both you and your employer can demand that three of those are continuous during summer, and most of the country shuts down three weeks in July.

In Australia it is 4 weeks minimum (and 10 days for sick/carers leave). The leave accumulates if you don't take and have to be paid out as per your finally pay if you leave the company. Since it is a liability on balance sheet most companies will demand you to take leave if you have accumulated over 20 days. You can also ask to cash out any leave more than 20 days.

Re: Things I’ve learned in my 20 years as a software engineer

#720
post #543
post #487

Earlier quoted context omitted.

He didn't misrepresent or disagree with the author. He added extra commentary on something the author brought up.

That is not how quotation marks are designed to work. The words offered up as a quote are meant to represent the views of the person being quoted. In this instance that is clearly not the case. This is a perfect example of how quotes can be used to misrepresented a view.

To be fair, they used `>` to quote the article, and then included the article's `"` to indicate that the article itself quoted someone else.
Post reply on HN