from Hacker News

I started with a SQL question. He said "that's a dumb question."

by keepamovin on 6/7/25, 11:35 AM with 66 comments

  • by bgwalter on 6/7/25, 2:19 PM

    Calling someone a "disagreeable asshole" just for saying that something is a dumb question is a bit strong. So he went out for challenging management on an internal document and he was 100% correct according to that tweet.

    Seems to me that the actual assholes are still employed in that company. Perhaps he was just hired to fix the mess. Once the job was done, he was no longer needed.

  • by remram on 6/7/25, 2:41 PM

    Asking dumb questions has become one of my moves in interviews. This is to expose LLM users, as LLMs are extremely unlikely to answer a "how do I do X" question with "you shouldn't do X", or "how would you replace Y" with "you should keep using Y".

    I guess now I have an additional reason to ask, so that I can screen out the assholes that will say it's a dumb question...

  • by viraptor on 6/7/25, 2:52 PM

    I'm surprised they didn't follow up with "why it that a dumb question?" It would likely lead to an interesting answer on its own, in the context of the interview.
  • by millzlane on 6/7/25, 2:23 PM

    It's not my <insert company name>. Has been my mantra lately. If I mention that a quarterly update cycle for mission critical software is too long in the context of security and the desktop enginners don't agree...I just repeat my mantra. I did recently develop a fix to a stupid bug a company said was working as expected. So I don't always stick to the mantra. But I'll disagree once. But then I commit to whatever management wants no matter how boneheaded. They're smart enough to see their dumb idea failed without me rubbing their noses in it.
  • by afavour on 6/7/25, 2:31 PM

    For anyone who doesn’t want to have to register:

    https://nitter.net/ryxcommar/status/1930985076965142918#m

  • by laweijfmvo on 6/7/25, 2:59 PM

    I interviewed an individual with similar sounding experience/background. Said my first question was silly and insulting. I apologized but said our interview process is standardized, and please just entertain me. They proceeded to spend the rest of the interview giving the absolute worst answer I’d ever heard in any interview to any question. Did not make it past the initial interview.

    Jerks come in all sizes.

  • by wenc on 6/7/25, 5:28 PM

    The SQL question (mentioned in the thread) was:

      "It was very benign and was probably the most practical question I asked him! Let's say you want to randomly sample 1,000 users out of a table with a user_id column, e.g. so you can get a list of IDs to send a customer feedback form to. How would you do that?"
    
    To me, that's not a dumb question. I mean, there is a simple answer but there are also complicated answers (especially if your table size is large, and performance matters):

    1. SELECT user_id FROM table LIMIT 1000 -- this gives unordered results, but is not truly random (it's dependent on database retrieval patterns)

    2. SELECT user_id FROM table ORDER BY RANDOM() LIMIT 1000 -- this is uniform random, but it's expensive for big tables.

    3. SELECT user_id USING SAMPLE reservoir(1000 ROWS) -- this is a fast and memory-efficient streaming method, i.e. Reservoir Sampling [1] in which n is treated as large and unknown (DuckDB supports this sampling method and others: https://duckdb.org/docs/stable/sql/samples.html) Reservoir sampling (https://en.wikipedia.org/wiki/Reservoir_sampling) was a hot topic among data scientists on Quora circa 2011.

    Sometimes simple questions have deep implications.

  • by crazydoggers on 6/7/25, 2:33 PM

    If I were on the board / an investor of the company, I’d let the managers go and hire back that engineer.

    The goal of a company is to serve its customers and make a profit, not stroke managements egos.

    And it sounds more like this guy pointed out what was wrong and maybe embarrassed people, but that doesn’t make him an asshole. It’s one thing to be mean or call people names, that’s an asshole. But this guy was an “asshole” because he was right and it embarrassed people? I’ve seen the type of management that is so insecure they can’t be pointed out what they are doing wrong, sounds more like what happened here.

    A good company has management that has a thick skin and acknowledges its missteps and raises up talent. If you can’t admit an employee “lower” than you can point out your flaws and give you criticism, then you’re the problem.

  • by keepamovin on 6/8/25, 12:24 AM

    Being an asshole is a right ordinarily reserved exclusively for managers and is somewhat correlated with their insecurity/incompetence.

    So the corporate principle is often not against assholery per se, it's against who's permitted by the hierarchy to do it.

    I've seen this a few times. There's more assholes among those who have a "manager"-type title. But by no means are all managers assholes. I think it oftens comes down to: 1) emotional immaturity, where people don't know how to execute the duties of the office (getting others to do something) without some kind of abusive coercion / intimidation; 2) also likely comes down to people reflecting the authority style they were raised with - so those who were traumatized by abusive asshole parents are probably going to have that as a model of authority and reflect that when they have authority; 3) finally, I often observed it correlated with obvious insecurity, in that it seems to be a defensive mechanism where people who fear themselves to be incompetent/unworthy will compensate by trying to shore up their position with abuse of their colleagues.

    Ideally, promotion should prevent/remediate such behavior, but I guess that the selfish-streak often displayed by assholes is mildly adaptive for the power dynamics involved in getting promoted. As a last point, often I think there's something else, that people tend to trust that "abusive/coercive" assholes will be able to "get shit done" (by, roughly, intimidating their team) - which there is probably some "truth" to, unless a team wholesale revolts against such behavior. Overall this last points reflects some room for improvement in human organizational dynamics in general.

    As a counterpoint to the prevailing "assholery" discussion in this thread, it would be really cool I think to see counterexamples in detail of managers who greatly succeeded by being stellar people and really good managers. I think ideally the "asshole manager" trope will become a true relic of history, something antiquated like the tolerated alcoholic hothead, or whatever.

  • by buggy6257 on 6/7/25, 2:17 PM

    Honestly if I was interviewing, even if you told me the future and this was the outcome of hiring the guy, I still wouldn't hire him.

    It's clear he's brilliant, and experienced, and seems like he's just refusing to "play the game". Speaking truth to power works if you know when to also NOT do it, or how to do it in a way that gets people to listen.

    It doesn't really matter how brilliant a guy is; if he's not capable of "playing the game", then he's going to be (and WAS) out on his ass within a short timespan. That's a sink on my team's resources having to hire AGAIN and train AGAIN so short after his hiring. I don't want brilliant jerks, I'd rather have someone decent who can stick around by not getting himself fired for saying the wrong thing to the wrong person.

  • by localghost3000 on 6/7/25, 2:11 PM

    Maybe I’m not reading the post right but the dude sounds like a dick? What am I missing here?
  • by jinushaun on 6/7/25, 7:04 PM

    Sounds like they fired the wrong person.

    Sure, on a case by case basis, it’s easy to make the argument that the smart asshole should’ve been more agreeable and tactful. But in the long term, keeping these managers hurts the company more and it’s how you end up with zombie orgs that scrape by.

  • by senthil_rajasek on 6/7/25, 2:06 PM

    Moral of the story, you can be a star but still have to "work with" your managers.
  • by bravesoul2 on 6/7/25, 12:48 PM

    Share is name so half of HN can hire him!
  • by ayhanfuat on 6/7/25, 2:35 PM

    Brilliance doesn’t balance out being a jerk. The net result is always negative.
  • by dedicate on 6/7/25, 3:21 PM

    Honestly, this whole story feels like a massive red flag for the company, not the data scientist.

    They loved his attitude when it challenged broken systems, but the second he aimed that same energy at management's BS, he was out. Makes you wonder... is "culture fit" just code for "won't call out your boss"?