Hacker Newsnew | past | comments | ask | show | jobs | submit | alfalfasprout's commentslogin

I really hope you don't actually treat junior devs this way...

This is one reason I think spec driven development is never really going to work the way people claim it should. It's MUCH harder to write a truly correct, comprehensive, and useful spec than the code in many cases.

Depends... not all kinds of trading are THAT latency sensitive.

Of course it's not going away. But like every other bubble, it means that the technology can go back to what it's actually good at vs. just shoved in every single thing imaginable.

If anything it's a testament to human intelligence that benchmarks haven't really been a good measure of a model's competence for some time now. They provide a relative sorting to some degree, within model families, but it feels like we've hit an AI winter.

Sure they do. And during the holiday season too.


Not necessarily. Lots of explanations:

(1) People wait for when they perceive they'll get the best deals to do their shopping. (2) K-shaped economy (data is already bearing this out btw): Spending from the wealthy is driving consumption figures vs. the bulk of the population (3) Anxiety about rising prices cause people to purchase now vs. later. See for example RAM prices.


I would hesitate to call it total dominance. There's a lot of good competition arising in this space. If you haven't already, check out pixi for example. And yeah, pyrefly is fantastic.

Competition is good in this case.


I mean, it's been announced already. Caveat: It's still very far from being competitive with SOTA type checkers like basedpyright.

Still, it's great that this is being worked on and I expect in a year or two ty should be comprehensive enough to migrate over to.


> A good senior engineer is for the most part able to not write bad code from day one, just at a very low speed and with the need to ask other people frequenyly. Even if you do not know the code base or domain yet there are a lot of things you can do to avoid writing bad code. Yes, as someone new you will make mistakes and misunderstand things but a lot of the bad code I have personally seen has not been caused by that. Most bad code I have seen has been caused by people rushing and not having their fundamentals in order. Like not actually doing reviews, not spending a few extra hours to think about architecture, etc. Also a big issue is that people just let the complexity of systems explode for the gain of short term proje

You have a very charitable view of the competency of the typical engineer at big tech nowadays. Ten years ago, sure. But with the advent of people purely studying for coding interviews that's changed.


Maybe, but then they are not "good engineers". A blog post about bad engineers writing bad code is not very exciting.


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

Search: