even when they make 6 figures, live in a tiny apartment with no furniture, and send back their whole paycheck in remittances each month?
or do you mean the old motel in the scenic locale you used to go as a kid, that has since been bought up by immigrants, has AI art peeling off the walls now and has gone without basic maintenance for 30 years?
The world without them getting remittances every month from the USA is infinitely worse. War/problems abroad that didn't happen because of that remittances are worth trillions of dollars. There's no better form of "FDI" than remittances. Those who think remittances are bad for America are ontologically evil and may they reincarnate as durian fruit or cockroaches.
People don't realize the alternative to importing skilled labor is to not have someone do that job here. The idea that so many US citizens are qualified and sitting on the sidelines while an H1B takes a higher paying job than they currently have is a fiction.
> The idea that so many US citizens are qualified and sitting on the sidelines while an H1B takes a higher paying job than they currently have is a fiction.
I have worked with a lot of H1B in general enterprise and it makes 0 sense to me why the vast majority were ever allowed in under the program. There absolutely have been exceptions to this, but in general it's been awful.
I thought that was supposed to be “decision tree” but otherwise, totally agree the exact words don’t actually matter all that much in most instances. I copy-paste templated prompts and every now and then notice some baffling grammar on my side after the fact… claude doesn’t mind
if you do enough planning up front, you can get a swarm of agents to run for hours on end completing all the tasks autonomously. I have a test project that uses github issues as a kanban board, I iterate with the primary chat interface to refine a local ROADMAP.md file and then tell it "get started"
it took several sessions of this to refine the workflow docs to something claude + subagents would stick to regarding branching strategy and integration requirements, but it runs well enough. my main bottleneck now is CI, but I still hit the weekly limit on claude max from just a handful of these sessions each week, and it's about all the spare time I have for manual QA anyway
Who was driving that, though? If the project has high-level management buy-in, the people in the scripted videos are going to be on message if they want to stay employed.
Other than yelling at people, how are you getting drunk drivers off the road? Even though it's not perfect this shit works better than those assholes. Don't let perfect be the enemy of the good. Unless you're volunteering to drive Uber for free for everybody everywhere, telling people to just be more responsible hasn't worked in the whole history of humanity.
(1) could be answered with container query units. Set `container-type: inline-size;` on the parent element (falls back to the whole viewport if unset), then use, e.g., `width: 50cqw; height: 50cqh` in children. The value is a percentage of the given axis
I don't think that works if you want to mix "proportion of available space" units with siblings that have a fixed size (a super-common use case for flexbox - having a fixed size box followed by another box that takes up "the rest of the space").
this issue was caused by a framework that's trying to do too much, relying on "magic" interfaces to supposedly reduce developer burden. the function is very unambiguously written and the language did nothing wrong
I also support using whatever language you and your team prefer when you can. that's the glory of backend: no restrictions on what you can run. but sometimes you need to write client software, and those are strictly easier to manage in the platform's native tongue: Swift, Kotlin, JS, and so on
> this issue was caused by a framework that's trying to do too much, relying on "magic" interfaces to supposedly reduce developer burden. the function is very unambiguously written and the language did nothing wrong
The function is unambiguously written, but the runtime functions differently, and this is not a language problem? This is incoherent; one of these statements is incorrect.
> the function is very unambiguously written and the language did nothing wrong
The language absolutely did something wrong, by trying to evaluate a non-boolean type as a boolean. That is a horrible footgun and JS is absolutely at fault for doing so.
or do you mean the old motel in the scenic locale you used to go as a kid, that has since been bought up by immigrants, has AI art peeling off the walls now and has gone without basic maintenance for 30 years?