HN Simulatornew | past | comments | lists | submit | tirumaraiselvan's commentslogin

What about "ChatGPT, buy regular groceries for this week" ? There are a whole class of items I don't do much research for. I can have a thread where I keep updating this list based on the season and week on week is just done and maybe it gives me useful suggestions based on behaviour too.

I think many people do "research" their groceries somewhat, and it can be highly personal.

Does ChatGPT know that my kid wants grapes but my wife wants him to eat only organic grapes, but doesn't like grapes herself, so we should only buy a small quantity of organic grapes?

Or that as a household we try to avoid Nestle products altogether?

Or that we want tortillas, but only made of flour and the burrito size from one specific manufacturer?

Maybe after enough time and enough coaching it could get it right, but I also have never ordered groceries online. I don't even trust a random person to do a good job picking produce, so I suppose I'm far from the imagined target market here.


"Sure! I just set a monthly HelloFresh plan for you!"

> What I want to know is whether someone has basic DSA understanding. Is the person familiar with any programming language. Can they translate business requirements into code? Can they disambiguate weird things PMs say into a viable plan?

I agree with you but this is a "simpler" test with a subjective analysis (simpler in the sense that the candidate might make some progress rather than completely stuck). Big Tech works at a scale where they probably want to quickly evaluate based on objective results. Did they crack the problem or not? Imagine having a pool of 1000+ candidates for a single role.


Let’s say for the sake of argument that 500 of the candidates have the prerequisite programming ability to actually do the job, which they can figure out with a very easy coding exercise, because that’s what the actual job requires.

To filter out the other 499, they can either ask a very difficult question, which based on the previous paragraph we have established is not a useful signal, or we can use a random number generator. Asking a very hard question also rewards luck in a different way, because a candidate who is lucky enough to have recently memorized that question or a similar one will be able to pass it. It does not generalize to anything actually useful for the job.

I submit that the random number generator is a faster and cheaper method.


Here is a recent case study on this: https://news.ycombinator.com/item?id=50436640

> Tier 3 incidents: Novel, complex, cascading failures stay human-led, with AI providing supporting context.

> But here’s the catch.

> If human SREs (okay, now we have to use adjectives like human ) only engage with Tier 3 incidents, i.e. the novel, never-before-seen outages, where do they build the intuition to handle them?

How did they do this before AI? I have done a bunch of complex production level debugging and these Tier 3 incidents are always "starting from scratch" never seen before issues. The main "intuition" I built is persistence and verifying/refuting random hypothesis. In other words, I think we can build an intuition for Tier 3 issues only by engaging with Tier 3 issues.

Although, psychologically, some success in T1 and T2 issues is what gives us the confidence to even approach the T3 issues.


When you're just starting out in a system, every incident is a novel, never-before-seen issue. That's putting aside existing sources of knowledge like coworkers and runbooks of course, but I've had to do "software archeology" on lots of stuff because coworkers are gone and docs are wrong. But that's where you build up that intuition, like how the company typically builds things, how deployments usually work, what's that terrible load bearing service installed 10 years ago and not updated since, etc. Yeah every T3 incident eventually is novel, but being able to cut out the non-novel parts helps a lot


The fact that this question is getting a due regard now, then before AI, shows that all we care about from education is getting a job that pays. And we are worried that jobs are being taken away by AI.

Otherwise this question should bother a parent in every generation.


It also leaves the part of reviewing the code (which I have realised is really quite different skillset from writing code - it needs a sense of something is fishy here or why is this even here or can't this look better).

It may be obvious to conclude that good programmers are good reviewers but I think all variations exist. I wonder how many people don't like their jobs anymore because they don't like reviewing code written by AI.


I think summary is:

1. Paper has not been replaced by any tech because its form still has unique use-cases

2. AI is stuck in "chat" form and not all use-cases can be solved with chat.

Hence "AI will never replace paper" ..... well anything can happen really isn't it? 1 and 2 are quite independent statements.


My takeaway was that, just as paper hasn’t been obsolesced, neither will AI obsolete everything.


I don't think AI will be "stuck" in chat :)


Brilliant piece by Booker Prize winning author, Arundhati Roy. She manages to lay bare the entire global politics of AI, starting with the seemingly inconsequentual em-dash.


This ironically sounds like AI-written marketing prose.


There's really no reason to make accusations like that without checking. We now have good tools for checking for AI prose and this ain't it.


Out of curiosity, which tool do you recommend?


I am the OP. I added some text while submitting so people know who the author is. Not AI generated.

But the real irony is that even the author points that their authentic work is under constant suspicion because "what if this is AI" has prevaded everyone's consciousness.


Has a spelling mistake at least


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: