HN user

_0o6v

686 karma
Posts5
Comments80
View on HN

Always seems to be very popular with a certain type of engineer. I personally prefer to create much better looking diagrams in about 1/10th of the time using draw.io

This was a good read. Many tech companies (and some non-tech companies) talk the talk about hiring from a diverse crowd, then interview them as if they're all CS bros (reverse a tree, "justify the text" bullshit leetcode nonsense, 8 hours of interviews), the exact kind of stuff that people from diverse and non-traditional backgrounds don't know and don't care about.

Having to reverse a binary tree or some other associated nonsense for a frontend UI role meant I turned the interview process at Google down. That and about 6 prospective hours of interviews for my application to then be sent to a "hiring committee" who ultimately decided if I was worthy enough of a job at Google, it just wasn't worth the hoop-jumping.

Zero interest? 99% of people I speak to would have no idea what the "command line" even is, let alone be interested in it.

I look forward to hearing how the mother who has kids to look after, and already has to work far beyond working hours to satisfy psychotic hiring practices focussing on algorithm knowledge and open source contributions, can then afford more time to do "office hours" with people using the software she has BUILT AND PROVIDED FOR FREE.

Alternatively: Tech Bros go ahead!

Why on earth would a passion for gardening make them any more of a better hire for you? You pay them (presumably) in return for their time and skills as a programmer, not a gardener. Would I get a job as a professional gardener with zero experience but a passion for programming?

"You need to be able to answer the "what have you done for our users lately" question with "not much but I got promoted" and be happy with that answer to be successful in Corp-Tech."

Good quote. Although you can extend the lawyers theme out to the rest of the bureaucratic corp too.

I agree. The fact we've invented insane frameworks like Gatsby to create "static websites" is just totally mindboggling to me. We already have "static site builder" technology. It's called HTML and CSS.

For such surgeries, randomized control trials have found that if you make an incision in the knee but don’t do anything, it’s as effective as actually conducting the surgery of the knee.

This is pretty crazy. I would suggest it shows that the vast majority of people having knee surgery didn't need it in the first place, or haven't tried alternatives.

If your knee is genuinely shot to bits and needs replacing with a artificial part, I can't see any scenario where placebo surgery would relieve pain anywhere close to an actual arthroplasty.

This is an attitude that makes absolutely no sense to me. Ask yourself - can I afford to get this wrong?

The risk of your home-rolled auth, with all the edge cases and requirements that go with it, vs. outsourcing to a company who's entire reputation relies on doing it properly with an army of experts, running on enterprise-grade architecture, with round the clock support/updates/ops?

Are you seriously saying that you can roll your own auth better than Auth0, Fusion etc. can do? And that the hours startups spend on setting it all up vs. an afternoon wiring in an auth-as-a-service provider is time well spent?

If you're a small company, don't risk it, don't invest time in it, just buy it it and plug it in and know that it's all enterprise-grade under the hood and you're covered (far more than you could ever afford to be).

If you're a big company, and you've done the maths and figure that the risk/effort vs. expense is worth it, fine.

There are certain fundamental security requirements that don't change, regardless of whether you have 10 users or 10m. If you have a breach, you have a breach. Numbers of repos, databases, servers have very little (nothing) to do with the security requirements of storing personal data.

A sweet spot only is as much as the code is already written, but there's a huge amount of ops and security work that goes into rolling your own auth.

For 99.9% of businesses, don't roll your own auth. Just don't do it. Use an auth service.