Programming @programming.dev nieceandtows @lemmy.world 4d ago

What do you think about this one?

gizmodo.com A Student Used AI to Beat Amazon’s Brutal Technical Interview. He Got an Offer and Someone Tattled to His University

Roy Lee built an AI system that bypasses FAANG's brutal technical interviews and says that the work of most programmers will be obsolete in two years.

I may be a old man yelling at the clouds, but I still think programming skills are going nowhere. He seems to bet his future on his 'predictions'

You're viewing a single thread.

17 comments

The only thing AI will replace is small, standalone scripts/programs. 99% of stuff companies actually write is highly integrated with existing code, special (sometimes obsolete) frameworks, open and closed source. The things they throw at you in interviews is generic scripts because they aren't telling you to read through 6k lines of korn shell scripts to actually understand and write their code. And they won't have you read and understand millions of lines of code, configs and makefiles to implement something new, in the interview.

He basically cheated on his little brother in Mario Kart and thinks he can now beat Verstappen on the real track. Bro needs to get a reality check in an actual work environment. Especially in a large company.
- I recently needed to implement some batch processing logic in our code to account for some api level restrictions (the code already pulls from the api in pages and date ranges, but if I specify a date range too wide or a batch that would get too many records back, it gets rejected, so we need to break it down and run the date range in batches). I tell this junior developer what the issue is, and what we need to add to the existing class in our codebase. I follow up with him after a week, and this is what he sends me.
  
  Boilerplate code from chatgpt that has almost nothing to do with what we discussed. And how can you even give me a whole 'working' code without even testing it? He didn't even clone our original repo and test it as is to understand why we need what we need. AI sure is making programmers dumb.
  
  I would argue that he is not a programmer
  
  Naw just a Junior that needs guidance.
  
  The junior devs I've worked with don't just send me raw ChatGPT output.
  
  Does it least actually have something to do with PayPal? And is pandas actually useful? lol
  
  I can understand commenting ASM, optimized C code can use some comments too, but commenting python should be a crime, as its function calls document themselves, and you'll usually split data over named variables anyway.
  
  Only chatGPT has these kinds of comments as if you’re seeing code for the first time. 😆
  
  I’m not against adding comments where is needed: in the company I work for (a big bank) my team takes care of a few modules and we added comments on one class that is responsible to make some very custom UI component with lots of calculations and low level manipulations. It’s basically a team of seniors and no one was against that monster having comments to explain what it was doing in case we had to go back and change something.
  
  For 99% of the code you just need to have good names though.
  
  Exactly what I'm saying. Also in a big bank btw :3
- The only thing AI will replace is small, standalone scripts/programs.
  
  For now. Eventually, I'd expect LLMs to be better at ingesting the massive existing codebase and taking it into account and either planning an approach or spitting out the first iteration of code. Holding large amounts of a language in memory and adding to it is their whole thing.
  
  Hopefully we can fix the energy usage first.
  
  I have a feeling that the Dyson sphere will end up powering only the AI of the world and nothing else.
  
  They can context and predict contextually relevant symbols, but will they ever do so in a way that is consistently meaningful and accurate? I personally don't think so because an LLM is not a machine capable of logical reasoning. LLMs hallucinating is just them making bad predictions, and I don't think we're going to fix that regardless of the amount of context we give them. LLMs generating useful code in this context is like asking for perfect meteorological reports with our current understanding of weather systems in my opinion. It feels like any system capable of doing what you suggest needs to be able to actually generate its own model that matches the task it's performing.
  
  Or not. I dunno, I'm just some idiot software dev on the internet who only has a small amount of domain knowledge and who shouldn't be commenting on shit like this without having had any coffee.
  
  I don't think they necessarily need logical reasoning. Solid enough test cases, automated test plans, and the ability to use trial & error rapidly means that they can throw a bunch of stuff at the wall and release whatever sticks.
  
  I've already seen some crazy stuff setup just with a customized model connected to a bunch of ADO pipelines that can shit out reasonably functional code, test, and release it autonomously. It's front-ended by a chatbot, where the devs can provide a requested tweak in plan English and have their webapp updated in a few minutes. Right now, there's a manual review/approval process in place, but this is using commodity shit in 2025. Imagine describing that scenario to someone in 2015 and tell me we can accurately predict the limitations there will be in 2035, '45, etc.
  
  I don't think the industry's disappearing anytime soon, but I do think we'll see AI eating up some of the offshore/junior/mid-level work before I get to retire.

17 comments