HN user

PainfullyNormal

824 karma

painfullynormal@fastmail.com

https://painfullynormal.substack.com/

Posts8
Comments192
View on HN

I'm also interested in this, but I'm more interested in what you need to say and do to convince other people you're an expert.

everything else frontend is pretty much resolved

Has it? The technologies will change again. Pretty soon, if I have to guess. What's valuable here are the concepts that are universally applicable and have been since it was called client programming in the 70s: state management, rendering, API integrations, architecture.

This happens at the end of every hype cycle. People are dissatisfied, everybody is looking for the next big thing, and a bunch of people and companies throw spaghetti against the wall to see what sticks. A winner will eventually emerge, but it can take some time. A good example from the last generation: who remembers OpenLaszlo or YUI?

We had stuff like that all over the place in the last React codebase I worked on. Naming things is hard, especially when you have to name them four times: once for the hook, once for the function that can potentially be called outside of the hook (non-react code), once for the API call, and once again for the graphql query.

I doubt that was the deal breaker. I always question the company's business model in the interview. If they can't defend their business model to an applicant, how can they possibly do so to investors, customers, and/or other companies looking to make strategic partnerships? Their due diligence is far more severe than mine (or the author's).

I asked the question because it's not the first time I've heard something similar to "learn to talk like other staff engineers". I've heard it a few times, I've read/heard other people being told some variation of it, and it even shows up in the Staff Engineer book by Will Larson. I was hoping to get more insight from people either hiring Staff engineers or other Staff engineers themselves.

You will need to run a ARM Linux VM on the Macintosh - even on ARM-based Macs. Why? Apple. That's why.

I'm going to need a better answer than that. The whole reason I want to learn ARM is to get closer to the machine I'm actually using, not to get closer to a linux virtual machine that I will never use again running on the machine I'm actually using.

I used to hate the grind, too. But, as somebody who's been out of work longer than he thought he would be and is starting to wonder how he's going to pay the rent, I long for a bit of the grind right now.

You know, I've been contemplating whether I should lose the pseudonyms and start using my real name for all of my online activity. This story has convinced me that it's something I need to do. That's such a crazy sequence of events that would have never happened if you had been playing under a pseudonym that's hard or impossible to connect back to your resume. All these years, I've been sabotaging my "luck surface area" with my stubborn insistence of online anonymity.

Goodbye Spotify 4 years ago

What will I gain?

The big bonus for me is I can create playlists and sort my music by beats per minute. Vital for creating workout or "evening chill" playlists.

None of these techniques is relevant anymore given that all the hardware has Z buffers, obviating the need to explicitly order the polygons during the rendering process. But at the time (mid 90s) it was arguably the key problem 3D game developers needed to solve. (The other was camera control; for Crash Andy Gavin did that.)

In your opinion, What is the key problem 3d game developers need to solve in 2022?

Only show code that is non-confidential.

Back in the day, it was normal to get your former boss to sign off on showing a piece of code in your next round of interviews.

This may work for somebody who has an anxiety disorder, but that's not what the OP is talking about. He's basically talking about stage fright. It's a physiological reaction to "performing".

It's hard to understand if you're not affected by it. You've heard the term "Stage Fright"? This is the same. Something about being put in a "performance" situation triggers the fight or flight reflex. At first, you're a deer in the headlights. Then, your body floods with adrenaline. The whole thing makes higher level thinking extremely difficult. I don't agree with the parent poster that it's "damaging to people's health", though. It's just something that happens. You recover pretty fast afterwards.

Every job hunt for me is still around 100 applications : 10 interviews : 1 offer. These ratios have remained pretty reliable through bull and bear hiring markets.

Same here. But, I'm horrible at selling myself.

I suspect people for whom "jobs are falling off trees" are rarer than HN commenters might have you believe.

I don't think so. The people for which jobs are falling off trees are those who have spent at least 10 years building their brand and their network. It reminds me a bit of this comic I see on occasion: https://pbs.twimg.com/media/DRwe2qaU8AAwLE5?format=jpg&name=...

And it's accurate for me. I'm lazy. That's why I became a programmer to begin with.