4,456 karma · joined August 26, 2011
More interestingly, to me at least, is the fact that 31 of the longest 50 are all in China (as are all but two of the 24 in the "under construction or planned").
https://en.wikipedia.org/wiki/List_of_longest_suspension_bri...
Thanks for the heads-up -- I'll pass.
I'm not familiar with current H1B law, but what prevents this from happening today? I've hired away an H1B holder in the past; the process wasn't particularly difficult.
My understanding at the time was that the tricky thing for H1B holders is that they can only have a 60-day gap of unemployment before they need to leave the country (or find a different visa resolution, I guess).
Now, if this new fee applies to H1B transfers as well as the initial application, well, that'll actually make it harder for H1B holders to change jobs.
Face recognition means computing which individual from some other database of people a particular face belongs to.
There’s also face tracking — detecting a face in an image and then tracking the same face across subsequent images. Which is often implemented by using a face recognition approach, but without any predefined catalog of people — you just dynamically fill up your face database as faces appear in the image sequence / video source.
Do tell -- what's it called? Sounds like a great read.
I expect you’ll need to be heads down on the hardware and basic software problems to hit your dates. But I also think it’d be worthwhile to figure out the baseline for extensibility early. Maybe this is just a call-home mechanism so you can advertise updates, so you can do something more in the future.
I also wonder if you could somehow take advantage of ESPHome here, for very basic HA etc integrations (of other functions, to be clear).
Also, what are your thermostat algorithm plans? Are you intending to consume HA thermometers / sensors? Or perhaps expose programmability hooks directly on the device?
Send me an email if you’re interested in more info.
In what way do you think the risk is greater in no-approvals mode vs. when approvals are required? In other words, why do you believe that Claude Code can't bypass the approval logic?
I toggle between approvals and no-approvals based on the task that the agent is doing; sometimes I think it'll do a good job and let it run through for a while, and sometimes I think handholding will help. But I also assume that if an agent can do something malicious on-demand, then it can do the same thing on its own (and not even bother telling me) if it so desired.
We generally found that this worked out fine. Customer-facing limits were numbers measured in hours or days; infra limits were measured in seconds or minutes.
Certainly you wouldn’t want to rely on a central db for infra-oriented rate limiting, in any case.
I'm using a crazy combination of pre-processing in Blender and then post-processing in OnShape today, and feel like I should be able to just use Blender for the whole job.