What do you mean by easy? Do you mean FAANG or equivalent salary? What level of seniority?
Can speak to my experience that if you are a senior engineer in London the market is relatively easy at the moment (or was at the beginning of the year) even with no connections.
I have no comment on sound mixing in general, but just to add context here, Chris Nolan intended[0] for the dialogue in some of the scenes to be inaudible over the score.
I think this is often difficult for people who treat films as logical instead of experiential.
Nonetheless, it is inaccurate to characterise it as poorly mixed, since the goal was for the score to somewhat drown out the dialogue, and the mixing achieves that goal. You can disagree that this is a desirable outcome for the viewer, but art is ultimately subjective.
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.
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.
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?
I think it's beneficial to hear this, as I've definitely been on the other side of this before now. So, thanks for sharing.
As much as we can fault the technology and the hype around it, this as much a people problem as anything else. Before AI, this same problem happened with architecture/PoC to implementation hand-offs.
AI is a new tool that a lot of us are still figuring out, but that doesn't excuse poor communication.
Can speak to my experience that if you are a senior engineer in London the market is relatively easy at the moment (or was at the beginning of the year) even with no connections.