HN user

Tao3300

2,337 karma

Hi. In case you forgot, the entire crypto "space" is bullshit and we need to cut it out already.

Posts0
Comments1,256
View on HN
No posts found.

I'm saying it was an anonymous story, lacking verifiable detail, spread in a public forum. Whether it's your personal truth or not is irrelevant to the fact that it's a rumor by definition.

Are you scared of definitions? Do you feel like dictionaries are written to gaslight you? Don't blow it out of proportion.

Who knows how old we can be in the future

Read as "who knows how much more entrenched future politicians will be able to be? who knows how many more favors they will owe, how many more donors will have their ear?"

That's what we call racism. Even if the anecdotes are from your own experience, you're still drawing broad ethnic conclusions from them.

What do we call anonymous stories, lacking in detail, being circulated in a public forum? Yes, those are rumors.

And that's what we call racism.

scholarly work stating that they were warmly welcomed 4 centuries ago

Yeah, that doesn't sound legit. Any general sentiment from that time period is lost, and the best your scholar can do is project the lens of the present onto sources from the past. To be fair, all histories are done that way.

Propaganda. The two major deficits stopping otherwise qualified people from being individually effective are (1) money and (2) time. If those are taken care of, any persisting problems are organizational.

He's not wrong. 90% of coding interviews are completely unrelated to the job. Here are some experiments for you to try in your next one:

- if it's a super difficult problem, remark how fascinating it is and ask the interviewer how often they're doing this stuff

- if it's FizzBuzz or something else that is solved and has a known value, propose hardcoding the answer as a constant and printing it without doing any computation, and see how that goes over

- if it's not one of these, you might be in a 10% case

My favorite was when I applied at, let's call it "StoreJogger" at as entry level engineer. This guy comes in for the technical interview and asks me a question that basically boils down to "how would you make StoreJogger?" and I remember thinking that if I knew the answer, I sure as shit wouldn't be in there. Yeah I guess it was technically a relevant question.

I ran into that one hard once.

"Hey, money isn't coming out of this function correctly. No, really, here's the math..."

"PACK UP YOUR DESK NOW."

The interview process should resemble this then. IIRC it mostly doesn't, but it's been a while since I've had much experience past the "thank you your interest" e-mail signed "Sincerely, (name of company)" from a no-reply address.

Maybe the author doesn't want to lower his standards. Fine. He's got the rent to worry about. I've got a lot more than that on the line and I'm more than willing to fill that role if they'd just let me get my foot in the door.

Right now I'm in this goofy spot where I'm probably walking away from it. Nobody wants backend and API-layer Java devs anymore. They probably need them, but they don't know it in the midst of the AI bubble.

Your desire to handle that all in-house by organic, corn-fed, English-as-their-first-language meat-bags is lovely but you'd be bankrupt in a week.

Nah, the C-suite fat cats just need to take a few million less for running a shitty business, and use the money to hire people who actually have to do stuff for customers.