This is a US-centric take, in Europe, particularly in cities, we walk everywhere.
There is perhaps some relevance to the analogy however, because the US is designed in such a way that makes walking difficult to impossible. I am already seeing this pattern in vibe-coded areas where engineers will just use AI because it's too difficult to parse and edit by hand.
Depends on seniority and market, but my experience has not matched this. In my recent search I even had a company change their process at my request. Too many companies just copy the FAANG approach without considering if it suits their team(s).
We have some responsibility as candidates to tell HR departments and recruiters that some stuff doesn't fly.
I guess you can make the argument that legislating repairability will raise the price floor for devices because it increases the cost to the manufacturer. This isn't a problem for most of us in tech, but affordability can be an issue for many.
Making devices un-fixable often costs more than just building them in the most straightforward way. In either case, I don't think a few dollars more or less in manufacturing costs will impact the consumer prices in any way. Let's not pretend that Apple (or other computer / phone companies) has thin margins.
IME tok/s is only useful with the additional context of ttft and total latency. At this point a given closed-model does not exist in a vaccuum but rather in a wider architecture that affects the actual performance profile for an API consumer.
This isn't usually an issue comparing models within the same provider, but it does mean cross-provider comparison using only tok/s is not apples-to-apples in terms of real-world performance.
Exactly. Really frustrating they don't advertise TTFT and etc, and that it's really hard to find any info in that regard on newer models.
For voice agents gpt-4.1 and gpt-4.1-mini seem to be the best low latency models when you need to handle bigger data more complex asks.
But they are a year old and trying to figure out if these new models(instant, chat, realtime, mini, nona, wtf) are a good upgrade is very frustrating. AFAICT they aren't; the TTFT latencies are too high.
More often than not I've seen this be the case. Refactoring as "rewrite using my idiomatic style, so that I can understand it", which does not scale across the team so the next engineer does the same thing.
I like guns and cars, but not sports. How exactly is it performative? Both are engineering marvels and fascinating to watch videos about, and they also happen to be a load of fun.
I watch hours of videos on both with nobody else around and don't really talk about those topics with others much. So in the spirit of HN, I'm actually curious to know what about those interests is performative?
There is perhaps some relevance to the analogy however, because the US is designed in such a way that makes walking difficult to impossible. I am already seeing this pattern in vibe-coded areas where engineers will just use AI because it's too difficult to parse and edit by hand.
reply