Live data from Hacker News

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

old.reddit.com

291–300 of 510 posts

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

#291

"Sure, $120k + bennies + pension sound great, but you'll be selling your soul to work on esoteric proprietary technology." It sounds great because it is great. I don't make that much and I work on boring systems. I guess those numbers also explain why the author can recommend maxing out the 401k. People supporting a family on less than $100k don't have $19.5k per year to put into it.

This rings home for me as well. I remember my (now ex) wife saying she was going to quit working and be a stay at home mom the day I hit $100k salary. Effectively cutting it in half economically. I feel like folks who say these kind of recommendations also need to preface the fact that not everyone can afford to. I couldn’t afford to put anything in a 401k for years.

My prior manager said something about everyone should be contributing the max. Easy for him to say as a manager... with a physician as a wife.

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

#292

Earlier quoted context omitted.

There was an old xkcd about this, though I will admit I have never experienced this: https://xkcd.com/323/

Oh the Ballmer peak definitely exists for POCs, school work and side projects. A couple beers in and then you lose the fear of doing something stupid and start cranking out code. Not sure about producfion code though, the values are different

I'll admit to banging out v0.0.0 code with a buzz. Mostly it's comments and shit-code as documentation. Sober eyes and test cases before production.

So maybe write drunk, edit sober does work

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

#293

> The older I get, the more I appreciate dynamic languages. Exactly the opposite for me. I just can't stand hovering a variable or a parameter and not getting its exact type, or typing "." after a variable and not having my editor gives me all the available methods on that variable, or running my code just to discover that it instantly crashes because I made a typo or forgot an argument or passed the wrong argument o…

The ideal for me would be some strong static typing mode for the main code providing all the guarantees you want and some dynamic typing mode for the tests which lets you test everything well. The main downside for me of the static typing is that it's close to impossible to provide a good testing experience, DSLs, mocks and spy objects kind of require some form of dynamic typing to be usable.

That is demonstrably false.

You can absolutely write DSLs, mocks, and spies in a statically-typed language.

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

#294
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.

Yeah, I'd be on board with that if 99% of the people talking about typed languages at the moment weren't using Typescript for use cases where you literally get instant feedback from hot reloading as you code.

Every time I see an example of a bug that TS would solve, it's something that I routinely find in 2 seconds by looking 10 degrees to the left at my second monitor and noticing the screen is white and there's some red text in the dev tools. "Compile time" doesn't mean anything if it consistently happens 0.5s before "run time".

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

#295
post #257

Earlier quoted context omitted.

Reminds me of Hemingway's "Write drunk, edit sober."

Not for code tho. I've never seen booze help make good code

Alcohol really does not help me with code either (except maybe a relaxing beer), but Marijuhana works(occasionally). But you really, really need to do the sober clean up part. Otherwise it becomes a mess.

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

#296

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

I keep getting downvoted on Reddit for stating that I personally hate TypeScript to the max. It ruined the beauty of JavaScript (once you know it, anyway, I understand there are difficulties for JS-novices) and I honest to goodness 100% do not EVER find myself thinking: "Gosh, thanks TypeScript!" - on the contrary, it's always: "For fuck's sake you stupid POS TypeScript, you're wasting my time for no benefit at all."

Strong-typed languages (especially in the damn browser) make no sense to me. It's not like we need to manage memory or anything.

20+ Years of experience here, and I hate TS with the passion of a thousand suns.

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

#297

> Hacker news and /r/programming is only good to get general ideas and keep up-to-date. The comments are almost worthless. Maybe he is on to something.

I think HN is big enough that you're not going to beat the averages with advice from the comments here. They're filled with the kinds of opinions that are more popular on big company teams than good startup teams.

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

#298

> The older I get, the more I appreciate dynamic languages. Exactly the opposite for me. I just can't stand hovering a variable or a parameter and not getting its exact type, or typing "." after a variable and not having my editor gives me all the available methods on that variable, or running my code just to discover that it instantly crashes because I made a typo or forgot an argument or passed the wrong argument o…

I've been doing TypeScript for 4+ years and been a web developer for 20+ years. And I experience literally zero benefit from TypeScript. Never has it given me anything useful. To me, it's a massive pain in the ass that slows down myself and my team, even if they think it doesn't. They just don't know JavaScript or have shitty quality of code to begin with.

That, and TypeScript generics can get so freaking complex that the code does NOT become simple to read at alllllll. It's a massive waste of time.

Also read: https://medium.com/javascript-scene/the-typescript-tax-132ff...

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

#299
post #94
post #8

Probably people are honest when they are drunk. There is nothing to argue with any of those comments. But this one stood out for me! > Titles mostly don't matter. Principal Distinguished Staff Lead Engineer from Whatever Company, whatever. What did you do and what did you accomplish. That's all people care about.

That's true unless you get acquired. At that point, your title is what your new overlords will use to determine your role, salary, and even whether to lay you off.

I mistakenly asked to be called the "Staff Engineer" as employee #1, I think I'm going to correct to "Principal Engineer" as soon as I can.

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

#300

Earlier quoted context omitted.

How was the interview process before you got hired on? Any warning signs that seem obvious now in retrospect?

The hiring process for the company wasn't special. Of course half the stuff they claimed in the interview changed later (was hired as a Java dev but was assigned to Filenet, they said rhet dont outsource or layoff but have started doing both). This was an internal transfer. There were definitely warning signs in that interview. I was desperate because they were outsourcing my job in an obscure tech (Filenet) and we w…

The issues in your earlier post point to a problem with the company as a whole. It is surprising that the issue is with a specific role.
Post reply on HN