PainfullyNormal
PainfullyNormal on Hacker News
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.
What are you talking about?
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?
> No control freaks - especially in leads & managers
How do you test for that during the interview process?
This tweet[0] from about a month ago is pretty interesting.
"If you ever wanted to dump someone's entire LastPass vault, this is where you start :D"
The author was referring to the linked presentation slides.
[0]: https://twitter.com/_MG_/status/1600980559009677313
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.
What you're describing applies to all jobs everywhere, including junior and non-technical positions. Nobody hires strictly on technical expertise.
> She wrote that she assessed that I don't talk like their staff engineers.
I've heard this from other people, too. Is talking the talk really this important to employers looking to hire staff engineers? And if it is, why?
They don't seem to have much in the way of clients. For example, they currently only have 4 active "missions" in web development.
Win the lottery and become a 10x dev and maybe he'll dream about it.
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.
> 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.
Does anybody find work on that thread anymore? And by "anymore" I mean in the past year. Postings and activity seems to have dropped off.
Not quite what I had in mind, but that's not a bad idea. E ink displays make for some cool projects.
1. Do cool things.
2. Tell people about them.
3. Stay away from any glowing screen unless I'm doing 1 or 2.
Location: NY
Remote: Yes
Willing to relocate: Yes
Technologies: All things javascript: React, React Native, Node.js, GraphQL, PostgreSQL, mySQL
Role: Senior, Lead or IC
Résumé/CV: https://drive.google.com/file/d/1JXFcbOkByavrospLzkUvQ671RHJ...
Email: on the resume
I'm an accomplished senior engineer with 17 years of experience building products and solving problems. I'm technology agnostic; I use the best tool for the job. I'm also full stack. I like building features as a vertical slice through all layers of the stack, from the database all the way up through the frontend. I've worked at companies of all size, from 10 man startups to Disney.
I'm a no-nonsense greybeard who gets things done, but I also keep up to date with all the latest toys. I remember when SPAs were written in Adobe Flex and run on the flash plugin and I've also used react hooks in anger. This gives me a unique perspective and judgement that comes in handy when evaluating new technologies, building new products, making existing products work better and solving difficult problems.
SEEKING WORK | REMOTE | EST
Fullstack engineer and web developer with 9 years of experience as a one stop shop for MVP and prototype development. I do rough UI and UX design, small scale frontend, backend, and data infrastructure, API design, and devops. I do whatever it takes to take your idea from the drawing board to a functioning prototype.
email: [email protected]
Fees: $3,999 per week. 1/3rd up front, 1/3rd on delivery, 1/3rd on acceptance of work. IP transfers on full payment. Discounts available for longer projects.
> I feel like I’m taking crazy pills
You're not. If you look hard enough, long enough, you'll see this same pattern in every corner of programming. Round and round, never forward.
I spent serious money on a sound bar a while back. I used it twice, sent it back, and I've been using the BT headphones ever since. One of these days, I'm going to have company over and I won't know what to do. Make the walls vibrate, I guess.
> 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.