The majority of interviewers pick their favorite algorithm from the data structures class. The stereotypical question is some variation of a graph problem that damn near no one uses professionally. So, the most senior of engineers haven't dealt with it in 10-30 years unless they grind Leetcode. That gives the advantage to the junior engineer fresh out of university who studied it in depth just a couple years ago. Giving advantages to junior engineers in your hiring process isn't how you get the best people.

Further, most interviewers tend to care primarily that the candidate solves the problem in the time allotted. That used to mean writing pseudo code on a white board. Today, that means writing code that compiles, runs, and passes all the tests, including the hidden tests. If a candidate doesn't actually solve the problem, no one cares about the structure of his solution. Any time spent understanding and structuring the solution is wasted.

Secondary consideration is provided to all the traits you listed: decomposing problems, abstraction, structure. Good luck getting an accurate read on all that given the limitations of an interview. Your candidate is working in a high-pressure, high-stress, time-limited situation that's completely artificial and alien to most developers who nearly always have access to their IDE, the internet, and now AI.

You've made a completely artificial situation and think you get genuine results? The thought is laughable. Well, except that you're likely not hiring good candidates due to some BS interview process.

I've only been paying attention since 1990 but every single time a feature they don't offer "is stupid" until they offer it.

Even when I liked the company this Cluster B behavior always bothered me.

If there's an example of "that's a really nice feature our competitor has but we don't offer it yet" I haven't seen it.

The closest I can think of was offering WebObjects for Solaris. Not sure if that ever shipped or we just had a beta. I bailed from that Healthcare IT team when the CIO pulled funding for two-phase commit among disparate patient medication systems with the rationale "even if medication errors kill someone it'll be cheaper to settle the lawsuits than pay for the license." Enough people left that they outsourced and everybody still hates that replacement system.

I learned too late that MBA's don't care about quality.

Darn vague memory but - Yes. Keypunch machinesâ"such as the IBM 026, IBM 029, and IBM 129â"allowed operators to duplicate an existing card up to a specific column to correct errors or edit data without re-entering the entire 80-column sequence.

> everything you do has fucked the consumers

Say more ... how has suing to end the Play App Store monopoly 'fucked consumers'?

Let them do their thing.

I remember in High School the Camaro guys couldn't stop talking about how their Camaros were better than Mustangs but the Mustang guys never felt the need to denigrate the Camaros.

It's a matter of nature.

unrelated: Tailscale is so fooked today:

https://www.bleepingcomputer.c...

Some people here may need to panic right about now.

Let me spell it out very plainly because you don’t get it. It’s my car. It’s my battery. When I plug it into the wall, I expect the charge in my car to go up, not down. That battery is part of my car that I need to use to drive around town. At no point do I want the electric company to commandeer the power in my car to reduce my range.

MF’ers need to stop using my car, my battery, and my electricity like their own personal infrastructure they can control as they prefer.

I plug my car into the wall in order to charge it and increase range. At no point do I want to supply power back to the house and decrease my car's range. That defeats the purpose of having a car: to be able to drive around.

Cars are not meant to be temporary batteries to supplement the power from the electric company.

The right way to do this is to hire a group of developers and have test volunteers report workflow problems - then FIX them - then iterate. That's the point of choosing an open source solution.

Eventually there would be no problems remaining.

But so many possible scenarios exist that it's impossible to guess what happened here.

PS _NSA_KEY

There are apparently other unpatched vulnerabilities that are known but 'too busy':

It sounds like this fix got done because it was 'accidentally' posted as a public PR.

https://github.com/tianocore/e...

Yeah, the threat actor would need a foothold on the PXE network, which is a private VLAN (or better) in the competent case.

That's why we worry about APT's and such.

Granted, you'll find people on certain cloud providers who do far too much on a public IP.

"Meanwhile even questioning if the earth is flat will have you downmodded to (-1) Troll."

What you might as well have said.

What if someone has fifty windows open with fifty tabs each?

Asking for a friend.

Solid effort - good job.

It's a bummer if any of the employees got rug-pulled but many of the best employees will strike out on their own, form new companies with working conditions they value, and likely hasten Skydance's demise.

nah, a RS code can correct a tiny bit of loss but two metadata copies can correct a bad sector or even track if you're lucky.

Different requirement spaces.

The idea this guy has might make embedded devices slightly more long-lasting.

They usually have quantity one of a cheap storage part and a bad block in the wrong place could brick the whole thing.

It would only be useful in the case where maybe the build is 12MB and the chip is 16.

Most vendors won't ever pay extra for this.