Live data from Hacker News

Drunk Post: Things I've Learned as a Sr Engineer

old.reddit.com

361–370 of 510 posts

Re: Drunk Post: Things I've Learned as a Sr Engineer

#361

Earlier quoted context omitted.

Recruiters are like men on dating apps: spam as many people as possible without reading their profiles, treating people like objects

Who hurt you??

I've personally witnessed friends doing this as a man. A bit sad, and certainly not true of all men, but it's not false.

Re: Drunk Post: Things I've Learned as a Sr Engineer

#362
post #186

> The older I get, the more I appreciate dynamic languages. Fuck, I said it. Fight me. The other ones are quite obvious but this is the one that really resonated with me. People, with experience, tend to get more pragmatic and less "academic".

Pragmatic for me is knowing what’s wrong at compile time, and not being told much much later at runtime that I nested this array in a dictionary in an array wrong, or that my string is an integer. I got older, stopped using python for exactly the reasons above (I just really felt that it was wasting my time for trivial reasons), and found mypy which made it bearable again.

> or that my string is an integer

Have you ever considered PHP?

Re: Drunk Post: Things I've Learned as a Sr Engineer

#363

I disagree with the comment regarding the tech stack. It does matter - it only doesn’t if you’re willing to spend more money scaling worse preforming applications.

yeah, it is referenced later on.. it's a drunken post, so a bit disorganized :D

Whoops lol, should have kept reading. I definitely understand. Drinking and writing software is something I enjoy.

Re: Drunk Post: Things I've Learned as a Sr Engineer

#364

Earlier quoted context omitted.

This is my extreme counter example: What is better (A) a compiled bug free binary, or (B) well written source code that has a few bugs? If you want to keep developing the software, the answer will always be (B).

This is not generally true, but strongly depends on the domain.

I which domains is it practical to add features to software you don't have source code for?

Re: Drunk Post: Things I've Learned as a Sr Engineer

#365

not a single comment in here addressing two of the most important points brought up by the OP. the redditors managed to do it constructively. while gender and racial politics are clearly orthogonal to the concerns of the average HN poster, the tech we build is imbued with them and we are responsible for the issues produced by the lack of their consideration. > There's not enough women in technology. What a fucked up…

I don't think derisive attitudes in the workplace adequately explain it, because there are a lot fewer women in CS/engineering school too.

I certainly don't mean to imply that misogyny (which those kind of attitudes are a specific expression of) begins in the workplace. It's just where I currently am in life and where it has been most apparent to me in the past several years. I agree that it starts much earlier and there is significant work to be done at that level as well.

Re: Drunk Post: Things I've Learned as a Sr Engineer

#366
post #353
post #275

> Good code is code that can be understood by a junior engineer. Great code can be understood by a first year CS freshman. The best code is no code at all. Couldn't agree more

which is why leetcode makes no sense, as it focuses on premature optimization and writing the most advanced code possible which no freshman will be able to understand, at least not without dissecting it for a few hours first.

And every one of the puzzles on there is by definition a solved problem. If the company went under and all of their code and website was lost, I would cheer.

The only sort function I could write is probably bubble sort. Why? Because more efficient ones out there already exist and I could google them and paste 1000x faster than I could write them.

Lazy programmers are efficient. Puzzle solving masturbators waste a ton of time.

Re: Drunk Post: Things I've Learned as a Sr Engineer

#367

> If people are trying to assign blame to a bug or outage, it's time to move on. This is one of my favorite excerpts. I once worked in a lab where we would have frequent catastrophic failures because there was never any disaster planning or contingency management plan. I personally triaged 3 such incidents alone or with people who happened to be there when the problem arose and attempted to disseminate some suggestio…

Quoting what a HN user said in another post a few months back "if a person can break a system, the system was broken to start with".

Re: Drunk Post: Things I've Learned as a Sr Engineer

#368

Earlier quoted context omitted.

I really didn't mean for the comment to come across that way. I fully agreed with "it sounds great because it is great". I just wanted to provide another perspective too.

No, I completely get that. I'm just adding some of my background to show my thoughts. I know there are other areas and other people that command higher prices.

Learn the skills for the job you want, claim you do that stuff on your current resume (within reason), and jump ship. Most prospective employers won't push too hard with needing references from your current place of employment. Find your best mate at your last job, edit that portion of your resume, and fill them in on the details.

Re: Drunk Post: Things I've Learned as a Sr Engineer

#369
> If people are trying to assign blame to a bug or outage, it's time to move on.

Cannot agree more especially if you previously had a blame-free culture and it doesn't look like it's returning in a hurry.

I have seen this happen when new management comes in and don't value root cause analysis and look for a person or team to blame to protect themselves.

Re: Drunk Post: Things I've Learned as a Sr Engineer

#370
post #109

This, and the current “sober” posts on r/ExperiencedDevs, makes me think of Herodotus describing the way the Persians made important decisions - once sober, once drunk, and if the drunk and sober decisions were the same they knew it was a good one.

https://en.wikipedia.org/wiki/In_vino_veritas Is the phrase. Useful if you want to appear cultured at a company party.

or "children and drunks tell the truth"
Post reply on HN