Same as if the radios stopped working or otherwise communication fails. Execute the planned procedures (which vary).
Often Approach will take over the "tower" and operate in crippled mode (no clearances to cross active runways, you must go down to the end kind of thing).
Some airports are uncontrolled at various times and would revert to that. Some airlines would require the pilot execute a missed approach and deviate to a towered airport, others may allow them to land.
I admit I'm incredibly naive on this subject, but what makes it so hard to track an object as large as an aircraft carrier when starting from a known position such as a naval port?
You certainly can't do continuous observation but even just with commercial satellite offerings you can get pretty close.
For example nowadays Planet Labs [1] offers 30-50cm resolution imaging at a rate of one image or 120sec video stream every 90 minutes over a given 500 km^2 region. There is no situation where an aircraft carrier is going to be capable of evading a commercial satellite offering with that frequency and resolution. Once you know approximately where it is or even where it was in the semi-recent past, it's fairly trivial to narrow in and build a track off the location and course.
> Planet Labs PBC, a leading provider of high resolution images taken from space, said Friday it would hold back for 96 hours images of Gulf states targeted by Iranian drone attacks.
Break out the pocket book and pay Planet Labs to do it. You could do it with much less frequent visits than this probably the search area for it every 2 hours isn't very large and image recognition systems are pretty good. The big threat is cloud cover.
Note that that article is from 2020. Nowadays the frequency is actually down to 90 minutes/1.5hr. The resolution is up as well and they can do massive image capture (~500km^2) and video (120sec stream) from their passes.
Also nowadays they provide multi-spectal capture as well which can mostly see through cloud cover even if it takes a bit more bandwidth and postprocessing.
The problem then is the black out zones themselves reveal a lot as well if adversaries can find their bounds. That narrows the search area for their own observation satellites immensely even if it's too large to respond to IRL.
Well in that case congratulations. You've just made it easier. Now you don't even have to track them. You just have to look for the blacked out box, the "error we can't show you this", reused imagery from their long running historical imagery dataset, or improperly fused/healed imagery after alteration.
So now you don't have to do the tracking, just find the hole.
And then you can use a non-US provider to get direct imagery now that you know exactly where to look.
If the restricted area is large, a carrier is regionally disabling for an imagery provider. If it's smaller (and therefore must move over time to follow the carrier group) as soon as the imagery provider starts refusing sales in an area, any customer can test and learn its perimeter with trial purchases, find a coarse center, and learn its course and speed. You don't care about anything else until there's actual hostilities.
...literally yes (to the latter)? Is that not exactly why modern warships have to implement things like measures to reduce their radar cross section? If you could actually just rely on "ocean too big" then there would be no need for that.
It is in part for small crafts (frigates and corvettes) but for pretty much anything larger there's no concealing those ships.
The primary reason however for minimizing radar cross section and increasing radar scatter is to harden protections against radar based weapon systems during a conflict.
Even if the ship is still visible in peacetime operations, once electronic countermeasures/ECM are engaged, it gets an order of magnitude harder for guided missiles to still "see" the ship.
Depending on the kit, once missiles are in the air the ship and all of their friends in their strike group/squadron is going to start jamming radar, popping decoys, and trying to dazzle the missiles effectively enough for RIM-174/SM-6, RIM-66/SM-1, and RIM-67/SM-2s to intercept it without the missiles evading. And should the missile make it to close-in range then it's just praying that the phalanx/CIWS takes care of it.
And if everything fails then all that jamming and dazzling + the reduced radar cross section is going to hopefully result in the missiles being slightly off target/not a complete kill on the vessel.
So they still serve a purpose. Just not for stealth. Instead serving as compounding increases to survival odds in engagement scenarios.
But what you're describing is stealth. "Stealth" doesn't mean "invisible". Humans wearing combat fatigues aren't literally invisible either especially when moving, they're just harder to track/get a visual lock on to aim at.
The point still stands that you cannot rely on "ocean is too big for anyone to find me" because it very much is not.
I think you are sim-interpreting what I was saying (and if you see what I've posted elsewhere in the discussion thread I'm very much in agreement with you).
I was just saying that stealth is a component of ship design for small crafts (i.e. those that would generally stay close to the coast) but that it's not the case for larger ships and even for those smaller ships it's just not the primary purpose for radar optimized hulls.
Close to the coast, non-coastal radar won't be able to detect ships nearly as well as out at sea where they stand out like a sore thumb. And of course coastal radar will still light up any ship so stealth there is of little value on foreign shores.
But really outside of some niche cases for small crafts, radar "stealth" is all about survivability and not the traditional view of stealth.
Every PC I’ve ever tried to repurpose as a gaming console of any sort has had way more jank to it than I’d ever tolerate in a console, in the 25ish years I’ve been hooking computers up to TVs. Even the Bazzite box I’ve got is pretty bad by comparison. Hell, my actual Steam Deck has a lot more undesirable “enthusiast” behavior to it, let’s say, than I’d want out of a Nintendo product for example, even though it’s just about the best I’ve seen (the actual best is Retroarch with a skin mimicking the PS3’s menu, on a dedicated distro that could take it from cold boot to interactive in like three seconds flat even on an rpi2… but that won’t play actual modern PC games, just emulated consoles and such, so it’s not a fair comparison)
A common failure is the controllers. It’s hard to get a combo of OS stack, Bluetooth chip, and controller that Just Works like they do on consoles. Something always needs fiddling-with.
Video or audio out are also often a problem. Glitched audio or audio mode-switching, trouble switching video modes, screwed-up HDR, all kinds of stuff. Maybe fine on your monitor with headphones. Not fine on a TV or projector with 5.1+ audio receiver.
The UIs also bug out or crash more often, and usually aren’t that great at being a TV UI in the first place (even Steam IMO is worse than most consoles, as far as the Big Picture UI)
It also gives devs a stable target with a known market, which is nice for both the devs and the owners of the devices.
There's something to be said for having a standard, known SKU, both as something for developers to target if enough people own it, and for users to troubleshoot if they're e.g. having an issue running X game.
This kind of already exists with the "Deck Verified" label on Steam games.
That said, this sounds similar to Valve's upcoming Steam Machine and I'd much prefer that to be the standard console/PC hybrid to keep the Linux gaming momentum going, and perhaps one day I can ditch Windows for good.
The main goal is money, an Xbox branded windows PC has potential to drive sales.
Microsoft can also hopefully target a smoother user experience than a typical windows PC provides. They want this to be a valid console competitor, but just slapping xbox brand on a windows PC isn't enough to do that.
Having a first party hardware device to target for PC games can also help devs with having a clear performance target for PCs, similar to how the Steam Deck is currently a minimum spec performance target for a lot of games.
1. Console-like living room ready experience. It's surprisingly hard to get a PC made with off-the-shelf parts to integrate cleanly with a home theater system (think features like HDMI CEC, One Touch Play, etc). A custom SoC can solve this, something we are seeing Valve also do with the Steam Machine.
2. As the target hardware for basically all Xbox games, end-users who don't want to fret over system specs can easily just buy this and know they are getting the intended experience.
Whether that's enough to move units remains to be seen.
If this is true then the reason that a console would be better than a custom PC is that it would also be designed to work better for that purpose. Turning on the device when the controller turns on and sending CEC commands are two huge things that aren't well supported outside of the console space. Also it would likely run a trimmed down version of Windows and would be set up to "just work" in a way that a system that can have any arbitrary set of hardware will never be able to do.
But the really nice thing about the concept of treating a PC and console as the same platform is that you don't have to worry about why people might prefer to go the route of buying the console. You can go with a regular gaming PC if that's what you prefer and your library will have all the same options.
Microsoft are in a tough spot (as far as Xbox hardware goes at least). PlayStation is selling much better on the console side, and Valve with the Steam install base has a good shot at making a non-Windows OS a serious platform for gaming.
Their hand was forced in the end. They have to consolidate PC and Xbox users to compete.
The idea of a machine with a locked down mode that can boot legacy Xbox titles and probably run competitive games with very little chance for cheating is interesting. But given Microsoft's track record with consumer devices I await to be convinced.
Valve should be worried if they do turn out something good, maybe this will mean the Steam machines are pushed more aggressively price wise. We can hope...
It's a device with a fixed, known-good set of hardware for developers to target, which is all that any of the major consoles is. Your question applies just as much to the Steam Deck and upcoming Steam Machine.
I mean, at that point it is a pre-configured gaming PC. Hardware that's uniform across millions of units provides advantages, both for developers and users. IMO that's a big part of why the Steam Deck outsells more powerful competitors: there are so many of them that it gets targeted by developers, so more people buy them, in a virtuous cycle.
Not OP but from my experience, the LEGO I had in a bin since I was a kid still fit perfectly with LEGO I'm buying for my kids 30 years later. That's unbelievably impressive to me.
Lego from my youth, which was a hand-me down at the time, doesn't fit well with new lego. So it might be 40 years old, (which seems like a long time until you actually reach that age!)
I think it's more likely do to plastic aging than the original tolerances though.
To add even more - I was handed down Lego that belonged to my mom in the 60s, played with them through the 80s and 90s, and now my kids have them today. I wouldn’t be able to tell you which were hers and which were mine.
I am constantly amazed at how many people blatantly run red lights now. It used to be that people would sometimes press their luck on a yellow a little bit, but now it'll be red for several seconds and people will still just drive right on through.
I'd love if the police enforced this insanely dangerous behavior instead of trying to catch people going 10 over on the highway.
I see this a lot too here in Australia now, and yes it used to be pretty unusual but now I see it every day. I've sometimes wondered if it's just a frequency illusion but I'm sure it has got much worse, maybe since the COVID times?
It depends. Traffic lights are just mutexes. They are there to stop traffic so that other traffic may pass safely. There's no point if there aren't any other cars.
Obviously anyone running a light on a busy intersection deserves to get fined but if you know the terrain, have good visibility into the road where the other traffic comes from and can clearly see there are no vehicles present, running the red light is utterly harmless.
In my city, certain traffic lights literally turn off at night. There's not enough traffic flowing to justify them.
Use your eyes, your situational awareness and your best judgement. The traffic light is not god's word.
In my neighborhood there used to be a traffic light that would be red for a long time despite not usefully regulating any traffic whatsoever. It stopped traffic despite the fact no other traffic could possibly conflict with it. People realized this and routinely ran that light with zero consequences. At some point the city realized it too and redesigned the traffic controls so that the light would be green in this situation.
I understand the desire to act holier than thou and pretend that going through a red light with no traffic is murder in the making, but the situation they advocate for (running when clear) is even written into law in some states (at least for motorcycles/bicycles). Some vehicles don't trigger the sensors and the lights never change, so you are allowed to go after a full stop. I would not be surprised in the least if there were some states where the wording of the law applied to cars as well.
The correct action is to understand why certain barriers were erected in your way before attempting to demolish them. If you don't understand, just respect the barrier. If you understand, you know if, when and under which conditions it can be safely bypassed. Use your judgement.
Jaywalking laws were also written in blood. People break them every single day regardless because they have eyes and can look both ways to determine if it is safe to cross the street before actually doing it.
And yet, jaywalking pedestrians get killed daily, despite their best attempts at determining whether it's safe to cross. The problem with allowing drivers to use their best judgment as to whether it's safe to continue through a red light (after stopping) is that a non-zero percent of those drivers will fail to judge the situation correctly, especially during an edge case they rarely encounter.
It's impossible to get hit by cars if there are no cars around you. Vehicles are not going to materialize out of nowhere and crash into you. They are going to be funneled into your path by the roads. If you look at the road and see zero traffic, then you cannot be hit by traffic. Even if you run a red light.
Obviously, if you can't see the road where the cars will come from, then you cannot know if there are any cars coming towards you in a potentially intersecting trajectory.
In my city there are segments where I can see several kilometers ahead, including the traffic lights and their associated roads and traffic.
If you can't understand the fact it's safe to run a red light when you can see the roads are clear for several kilometers ahead of you, then I simply don't know what else to say.
Even police does this while roaming about on patrol.
Honestly, these arguments sound like cartoon logic. Guy looks both ways and sees the roads are clear but on the exact second he starts to cross the street 10 cars materialize out of nowhere at 200 km/h and nearly run him over just to teach him a lesson. This isn't how the world works.
>A vehicle will materialize out of nowhere and crash into you.
God I hate these sort of responsibility shirking opinions and their peddlers.
I do this several times a day in a major US city for close to a decade now and I've never had a close call closer than the "two people trying to pass each other in the hallway" routine with a driver trying to take a right on red.
Vehicles and everything else on this rock flying through space obey the same laws of physics.
If the traffic on a road goes X miles per hour, then simply don't cross it where you don't have a sufficiently long line of sight. If crossing where the lines of sight are sufficient is not tractable due to traffic volumes or road construction then cross at a marked crossing, intersection that interrupts traffic flow or use proper body language and someone will stop for you.
Sure, you might get exceptionally unlucky and choose to cross at the exact minute some car that's a few standard deviations above the norm but you might also get hit by lightening.
> I do this several times a day in a major US city for close to a decade now and I
I, I, I
> Vehicles and everything else on this rock flying through space obey the same laws of physics.
Yes. Yes they do.
That's why some countries (e.g. Sweden) actually have this in drivers ed: how fast a vehicle travels, how long it takes for the driver to react, what the stopping distance is for a vehicle etc.
They even teach things like "parked cars are a double problem because you can have people especially kids suddenly appear from behind them".
Or things like "at night you only see this far, and judging distance to things becomes harder".
But all that, including laws of physics, is invalidated by a litany of "I, I, mine, my, me".
I'm not special. I'm fairly normal. Hundreds of millions of people manage to walk and drive as uneventfully as I do. The presence of some few number of people who can't manage to jaywalk decently and not run reds when it matters doesn't justify saddling the literal entire rest of society with some automotive flavor of 1984 anymore than some small number people robbing convenience stores to pay for their drug addiction justifies subjecting all of society to pervasive surveillance and the war on drugs fueled police state.
Obviously. Don't take risks near pedestrians, near schools, near parked cars. Don't make assumptions in low visibility conditions where you can't actually see what's ahead of you. Use your judgement.
well, if they weren't doing something that would've otherwise been deemed illegal, then why would they consider it self-incriminating to have to follow KYC/AML rules?
You sound like a helpful world citizen. The other problem the US has is that it is illegal for a US Citizen to pay a bribe but there's no realistic enforcement. Luckily you can help solve this. Whenever and wherever you travel you can keep
some forms with you and every time you are pulled over you can fill them out with the police in quadruplicate so that each of you can mail them to Washington. At some later point the US can try to cross reference and determine who didn't mail theirs and then whether anyone was actually under US jurisdiction during the incident.
The right to a fair trial fundamentally requires the government to do 100% of the job of proving you guilty, and it shouldn’t force you to generate evidence against yourself while going about perfectly legal things
"Well I would probably go home and work on my resume because that's a fool's errand."
I hate going to work and reinventing wheels all day because the company I work for thinks it's so special that every business function needs a 100% tailored solution to solved problems. I much prefer working somewhere that's able to tailor business processes to conform to existing standards.
I’ve interviewed a few hundred people. Probably approaching a thousand, if not already. An interview is a scenario, and if you aren’t willing to engage in the scenario that we all agreed to partake in, that’s a huge warning sign that you’re going to be difficult later down the line. The point of the question is to have something remotely understandable for both sides to talk about, that’s it.
I'd call it an interviewer failure, not an interviewee failure.
I absolutely want people I hire to be "difficult" when the moment calls for it. If the scenario is one where the right business/user choice is "let them keep using Google Sheets", then the answer I want is "Google Sheets seems fine to me", no matter what people with more power start out wanting. Too many developers have been encouraged to be minions, not professionals.
Ditto for ones who act like everything is a nail for their coding hammer. A developer who can save a company a couple hundred thousand dollars by not turning something simple into a big coding project is a rare and precious commodity. Or should be, at least.
The thing to do isn't to give demerits for "being difficult". The thing to do is to then add something to the scenario where they get into the thing you want them to get to. "For this, we need better access control than Google Sheets allows us." Or, "We need this to be more closely integrated with our accounting system."
Unless, of course, what you're hiring for is the willingness to roll over for unreasonable requests from people with more power. Which, honestly, a lot of places are.
Humans are primates, and primate dominance dynamics are going to be the default absent some conscious choice otherwise. Our whole executive/worker dichotomy is a descendant of the British class system. (E.g., note that airlines specifically have a "business class".) And MBA-driven business culture is focused on short-term managerial interest, not societal value or long-term business success.
I think all of those tendencies come to the fore at any organization that doesn't have either a strong sense of mission or a sufficiently desperate need for success that they pay attention to material reality rather than social reality. With a possible partial exception for things like co-ops and other places where the culture is fundamentally different enough. E.g., Mondragon, or Zingerman's.
I think Google, back in its don't be evil/organize the world's information era, probably qualified. They started with a very strong mission-driven culture rooted in academics and engineering. It took a fair bit of time for MBA dogmas to make it like most other places. But from everything I hear, what once felt almost like a calling now is just another job.
> MBA-driven business culture is focused on short-term managerial interest, not societal value or long-term business success.
This is a common refrain I also believe in and there's an interesting open question that comes up here about whether or not an engineering department should or shouldn't execute an order that intentionally destroys the product for short term gain.
Agreed. To me that's related to the question of minions vs professionals.
If I go to a doctor and say, "Hey, please prescribe me a lot of morphine," the answer will be some version of "hell no". That's because doctors, even if you pay for the visit, have responsibilities to the patient, the profession, and society at large. Responsibilities that should not be overridden by money or power.
The same is true for actual engineers, like the ones that build bridges. But although we often call ourselves engineers, a lot of us don't act like it. We're often more like the minions in a supervillain's volcano lair: whatever the boss says, we do.
We could, as a profession, agree to follow those. We could build an organization that supports people who do the right thing in the face of managerial pressure. We could censure those who don't. I'd love to see it happen, but I'm not going to hold my breath.
>The same is true for actual engineers, like the ones that build bridges. But although we often call ourselves engineers, a lot of us don't act like it.
Because software is the wild west. Maybe there's some exceptions in medical tech, but there's no license at risk nor ethics assossiation to be ousted from (nor to vouch for us) if one day we receive something like: "hey, we need you to triangulate and calculate the parameters needed to bomb this children's hospital. Get to it".
Either we do it and go along with our day. Or we don't and get moved or fired.
In an interview when you’ve been explicitly asked to discuss a topic to have a technical discussion about something is not when the moment calls for it. Doubly so if you’ve been asked twice. If you’re not willing to put aside being technically correct when you’re trying to show off your best self, it’s pretty likely that when things get tough, you’ll behave the same.
> unless of course what you’re being for is the willingness to roll over for unreasonable requests from people with more power
D, do you think that someone saying “can we please talk about a technical topic, here’s an example we’re both likely familiar with” is looking for yes men? I actively want my team and coworkers to challenge me, but I absolutely don’t want to work with that person who appears at every meeting with a list of reasons why we shouldn’t do X.
When I ask an interviewee a technical question, what I want is an answer that is correct technically.
If I want them to give me a different kind of technical answer, then I think it's on me to ask a question that actually requires what I'm looking for. It's not hard! All the Stripe interviewer had to say is, "Ok, great. It sounds like you have a good sense for system capacity. Now let's add another zero to all the load numbers." And then keep increasing orders of magnitude until they learn what they're looking to learn.
I am, just to be clear, not defending people being willfully obtuse or contrary jackasses. But that's not the scenario being described in either the Stripe story or the Google Sheets story I'm responding to. Two apparently reasonable people were asked technical questions and they gave answers that were the right thing for the business.
I think that's good and I like to hire people like that. I get lots of others don't, and I get the POSIWID reasons behind it. But I'm not going to pretend I think it's a healthy way to run an organization. And I also get that the people who like pretense and deference in interviews are not going to like me saying so. ¯\_(ツ)_/¯
I read that as being his emotional reaction, not something he'd say in an interview context. This being an internet forum and all.
What I think he's sincere about is not wanting to work at a place that builds unnecessary stuff. And if people are asking for answers that require building unnecessary stuff, I think it's a reasonable inference that the place is not right for him.
I think interviewing is always a two-way street. If I got the feel that a place was going to have a lot of over-complicated code for me to deal with, or expected a lot of status-driven deference against actual user and business need, I wouldn't just give an interview-ending tart reply. But I would politely finish out the interview and then write them off unless there were other signals that redeemed the bad interview questions.
>do you think that someone saying “can we please talk about a technical topic, here’s an example we’re both likely familiar with” is looking for yes men?
Probably. You say "likely familiar with" but interviews are conducted as if it's a pop quiz. Which I never understood.
If you want to have a decently technical discussion, why not just tell me ahead of time what topic and I come to the interview with research? Why do I have to guess that we're talking about dyanmic programming and be punished if you really cared about graph traversal? (meanwhile the interview is for an embedded programmer. Definitely reflects what you'll really do on the job).
I really hate how few initerviews really felt like they were testing my knowledge related to proper fundamentals and not treated as some pseudo-SAT schlock.
> You say "likely familiar with" but interviews are conducted as if it's a pop quiz. Which I never understood.
Sure - the point of being familiar with it is so that we don't have to spend a chunk of the very limited time we have explaining a problem space, and we can talk about the technical stuff.
> If you want to have a decently technical discussion, why not just tell me ahead of time what topic and I come to the interview with research?
I try really hard to design interviews to not require take home work. I don't have stats to say whether this is right or not, but my goal as a HM is to try and keep the process to recruiter/HM call, 1/2 tech interviews and an interview with someone else on the team who is not a programmer (I hire in games so you're pretty much guaranteed to be working with Artists/Designers).
but also maybe its a green flag in that this employee might see the wood for the trees and save the company a lot of money later down the line. In my experience, a lot of engineers can waste a lot of time dicking around re-inventing wheels and whatnot.
While you consider it a huge warning sign, have you ever employed someone who would answer that way or are you assuming that you're not capable of making hiring mistakes? I can't help but think this "huge warning sign" might simply be a cognative bias where the interviewer is misdirecting their frustration in the poor design of their own process at the candidate [0].
For reference, I think both answers are fine and both perspectives (its a positive or a negative) are equally valid. Its just that I don't think we can confidently state either way.
> While you consider it a huge warning sign, have you ever employed someone who would answer that way or are you assuming that you're not capable of making hiring mistakes? I can't help but think this "huge warning sign" might simply be a cognative bias where the interviewer is misdirecting their frustration in the poor design of their own process at the candidate
Yes, I did. More than once. I always regretted it. Sure it could be a cognitive bias, but the entire interview process is essentially trying to figure out “can I work with this person”.
> I think both answers are fine and both perspectives are equally valid
I disagree - refusing to engage with the interview because you don’t like the question is perfectly valid to do, but don’t expect me to want to work with you over it. We’ve only got an hour, maximum, so any scenario we come up with is going to be contrived and simplified - if you can’t accept that then I’m going to make my decision based on that.
> Yes, I did. More than once. I always regretted it.
Fair.
> I disagree - refusing to engage with the interview because you don’t like the question is perfectly valid to do, but don’t expect me to want to work with you over it. We’ve only got an hour, maximum, so any scenario we come up with is going to be contrived and simplified - if you can’t accept that then I’m going to make my decision based on that.
Sure but lets not forget the other perspective. Candidates have to interview for a cumulative many hours over the course of a job hunt, only to have many interviewers batter them with an array of 1337code, pop quizes or contrived examples, none of which reflect the day to day work of the position they will fill. From their perspective their answer could well be a good one, albeit I agree that having some level of willingness to engage in the theatre is a positive sign.
In an auto-interview I recently did, I was given extremely limited time to "refactor" a bunch of code that was clearly broken. I chose not to refactor and instead fix the brokeness of the code, however I entirely expect to fail the interview because I fixed the problems instead of removing a couple of obviously duplicated code blocks. I can see why I would fail by not "following orders" but their async code was broken and the awful exception handling botched all their telemetry. From a "big picture" perspective I did do the right thing but it might be the case they're too stupid to know that I was doing the right thing (they're a multi-language company, so I assume they're less good at the language I specialise in).
Personally I think due to lack of industry organisation around certification or any sort of guild or union, we have a seriously difficult problem around hiring across the industry. In response to the extremely challenging task of vetting programmers I feel like orgs are simply fishing for reasons to disqualify candidates, as a reaction to this problem.
The rare positive experiences I've had interviewing were Amazon, who act like they want you to succeeed instead of fail or orgs that just half-ass it with low bar challenges, who seemingly accept that they're not capable of perfectly vetting a candidate.
and if you hire only based on solely on employee compliance then you are also probably missing the wood for the trees. I've worked in such orgs and they're extremely vulnerable to cargo culting.
I’m not hiring on compliance. I’ve accepted that his answer is correct but asked for the purposes of the exercise if he can put that to a side so we can talk about it. I’ve worked with and hired people like this and they tend to turn every molehill into a mountain, which is just killer on a small team.
I think you missed the point in GP's post. Not all organizations optimize for problem solving. Some organizations prefer subordinates who follow orders (or better, is able to read the mind of the boss to decipher what order he is actually making) than those who breaks out of the box and says ”just use gsuite, boss."
sure but if its not a privately held business then using gsuite is better for the shareholders. Ultimately its the bosses choice, but for the board to fire them its worth knowing they were aware of being able to use gsuite instead of pissing away resource on a needless project.
and if you don't understand my position then you've failed to interview. Some people just seek reasons to disqualify candidates and I think that's a pretty basic approach to interviewing. Remember, we all have a cognitive bias to hire ourselves and part of improving interviewing process is about trying to mitigate that by creating an environment where the interviewee can show the best of themselves, which may not necessarily reflect our own strengths. This is why pop quiz questions are kinda crap and while 1337code is better, its still kinda crap
> What would you do if two different people were emailing a spreadsheet back and forth to track something?
> I’d use google sheets
> Excellent answer, that is what I would do as well, now what if we wanted to build it in-house?"
> Well I would probably go home and work on my resume because that's a fool's errand.
I’ve not failed to interview. The candidate has been a jerk. Could I have asked a better question? Sure. Could the candidate not have sneered at it and thrown a strop - definitely.
Most real-world scenarios aren't so arbitrary, and hardly any have a "right answer". If I had a candidate that broke out of the box of our interview to give a good answer, and that's not the answer I "want", I'd be more likely to believe the interview question is the problem, not the candidate.
remember that we already did the "Excellent answer, that is what I would do as well, now what if we wanted to build it in-house?" part.
the "good answer" was already acknowledged, the "real-world scenario" answer was accepted.
the second part ("what if we wanted to build it in-house") is purely hypothetical to gauge how the interviewee would approach the specific technical challenge (shedding some of the "real-world" constraints so that the focus is technical).
if they again say "well that is dumb i would just use sheets", that is absolutely an interviewee problem.
Depends on the dyanmic. If you have an excellent candidate you're trying to poach, it becomes an intervewing problem because you're wasting both you and their time.
If they are a dime a dozen, then it becomes their problem. Whether or not they care it's their problem depends on their circumstance.
I'm not OP but - an interview typically has a power imbalance. They have a job and you want the job, therefore the balance tips in their favor. If the candidate is a headhunted candidate (imagine a video game studio trying to hire a creative director from another studio) rather than a cold application, then the power is flipped and the company is trying to convince the candidate to join them.
I also feel it's very easy for a good interviewer to bring the conversation back to the desired scenario.
Anything from "imagine we are in a parallel universe where Google Sheets has not been invented yet" to "how would you design a google sheets competitor" would do the trick.
Yeah - for sure. When I’m interviewing I want to give the candidate the best chance of success and to show off both what they know and how they will work with me.
I generally give it three goes with questions like these - the initial ask, and two clarifications. If we’re not getting anywhere I move on.
Depends on the dynamics here. Remember that an interview is 2-way.
Someone giving an answer like "that's a silly, unrealistic scenario" is more likely than not someone who isn't in need for that job to begin with. I'm sure it's something many wish they could say, because the interview pipeline can be very grating. But not everyone needs to play that game.
> The point of the question is to have something remotely understandable for both sides to talk about, that’s it.
I think a lot of people miss this point.
Real projects are complex and have tons of context at the historic layer, political layer, and technical layer. If I have one hour to do the interview, I need to get to some shared context with the candidate quickly, or else it'll just be an hour of me whining about my job. And I usually don't need someone who is already a senior subject matter expert, so I'm not going to ask the type of question that is so far down the rabbit hole that we're in "wheels haven't been invented yet" territory.
Fundamentally, that's why I'm asking a somewhat generic design question. I do also dig into how they navigated those layers in their past experience, but if I don't see them in action in some way then that's just missing signal I can't hire on, and that helps neither me nor the candidate.
In another company or timeline perhaps I could run a different interview style, but often you're working within the constraints of both what the candidate is willing to do and what the company standardized on (which is my current situation).
I think the contrived scenarios you come up with need to not have a trivial solution. Everything about my brain is optimized for KISS, it breaks everything to turn down simple solutions to reach for something more complex.
Think of it this way: they're paying you lots of money to build something boring that has a lot of prior art/research available to you for free. This could be the easiest money maker in your life.
It's not your problem they're hellbent on building a new wheel. They're willing to pay you!
Chances are, you've thought of your own pain points in whatever they've asked you to build and you've now got an opportunity to shine by solving them and demonstrate your expertise.
There is a tool invented lately, that's very good for solving problems, that are well-researched and had been solved multiple times already.
This tool is actually why there is a RAM shortage in the world right now.
Some even say, this tool will replace a lot of workers soon(sic!).
> Makes me a bit less terrified that untested vibe coded slop will sink the economy.
The difference is those spreadsheets were buried on a company internal fileshare and the blast radius would be contained to that organization.
Today vibe coders can type a prompt, click a button, and their thing is exposed directly to the internet and ready to suck up any data someone uploads.
reply