It's the better experience. The limits are way higher (I almost never burn through my $200/m plan), and the output is better than Opus 4.8 (Opus 5 is completely unusable for me).

I would fully expect a brand new college grad to call these things out. There's nothing in here that requires extensive experience to understand. These are basic principles any SWE should know. Nonsense comments are common sense to pull, if the LLM is pulling in a framework you should look into that framework and understand how it works. Don't know the framework during the interview? Say that. Tell the person interviewing you "looks like it's pulling in XYZ. I'm not entirely familiar with that. I understand at a high level what it's doing, but I'd want to dig deeper and understand if the LLM is doing this part right"

This was not my experience in college. A lot of it was VERY applied. Granted, that was 13 years ago.

But even so, if you're at a college where you feel that you're not getting enough exposure, that's why I also called out "Have done dozens of projects" and "Have done several (at least 2) internships".

Shouldn't this be a pretty fundamental part of a degree? If you're in school right now for a CS or SWE related degree, I would imagine you're learning how code actually works, how the math actually works, etc.

If an LLM makes a mistake, you should be able to call that out.

You might be arguing that a junior engineer may not have the RWE to make those judgements, but by the time you've completed a 4-5 year degree, you should have done the following:

- Completed coursework where you've learned the fundamentals of programming and software engineering

- Have done dozens of projects (building everything from basic web apps to more advanced pieces of software) where you've seen what works, what doesn't work, etc. This also gives you real world exposure to the latest and greatest frameworks, tools, etc.

- Have done several (at least 2) internships where you've worked at a real company writing real code, and have seen/been mentored into what AI is good at, where it fails, etc.

Comments URL: https://news.ycombinator.com/item?id=49037322

Points: 2

# Comments: 1

1.) Vercel - having a bad month

2.) Supabase - having a bad month

3.) Railway - now having a bad month

I'd even go so far as to say that any competitors that are direct (windsurf, kiro, etc.) aren't even in the same universe. Cursor is just so much better, faster, has better features (plan and debug mode), and squeezes much better results/code out of the same models. They absolutely have some secrete sauce that the other options just don't have.

I would make this the focus for 90% of the first 2 years of their degree.

I would then have them spend 75% of their last 2 years learning how to use and program with AI. Aside from knowing how things actually work, there's no more important skill now than mastering AI.

If you ask 100 people in 1969 what humans would be doing in space in 57 years I can guarantee not a single person would guess that we've done nothing of substance. And that the most exciting thing we have done that involved human space travel is simply flying around the moon, people wouldn't believe it

Apple and specifically MacOS is significantly worse than it has ever been, but again, still far better than the alternatives.