America could import it if the current administration wasn’t so hell bent on repelling global talent through inflicting great cost and uncertainty upon the talent
Even this forum can’t decide whether skilled personnel are a boon because they positively contribute to the local economy, or a negative because they undermine employment prospects for locals.
I don't know about this forum, but mainstream economics (and quite a few of the more niche approaches, too) is pretty much all in favour of open immigration for all skill levels.
I don't think you can say that. They are neither for or against, they make (or try to make) predictions what happens in either case. Who benefits and who loses is not the same in those cases, it's not linear. If you wan to be "for" or "against" you have to take a side. Doesn't mean they don't have opinions too, but two economists that each favor different outcomes may still agree on the methods of their field.
Economists generally point out that the world would be a lot richer with open borders. You can of course argue about whether its desirable to be richer.
Except for the guys receiving the lowered salaries. And all the other problems of migration, when some destinations are WAAYYYY more desirable to live in, even jobless, than others.
You guys are very selective, either not even bothering with links, or carefully selecting that one particular piece of paper supporting your PoV. Which of course looked at only very few if not even just a single variable, and (by necessity) failed to account for the breadth of reality.
Quoting single papers is always a sign of desperation. That's not how anything works, when given a broad question. Studies are extremely specific! In comparison, the question here is as broad as it can possibly get for an economics question.
Discussions such as here are only worthwhile when the parties don't care about "winning" and use debate club methods.
There really is a big difference betwwwn needing to import engineers to create high end chips and WITCH companies using h1B to get cheap contractors to do enterprise dev or any software development except something really specialized
I worked at a US college that had a big semiconductor engineering and manufacturing engineering program. They were about 20-30% international, but the program wasn’t huge.
Frankly, it’s shitty work. Software is where it’s at. Hardware people get paid peanuts and work really hard. When you’re a master of a particular technology, you get discarded when the next thing comes along. Ask the people at Intel or IBM. The best jobs are the execs and the tradesmen.
And attract them away from what? What are these skilled people doing? Does a photolithography skill set enable you to moonlight at some other gig such that they're here and keeping their skills fresh and we're just not noticing?
Software. Talk to anybody in the hardware space, and compare their experience to software.
Hell, the only two people I see in this thread that claim hardware experience are saying that it's a better career move to switch to software.
Software is easier, pays better, and has far better employers. Until hardware companies realize the situation they've created, they will lose their workforce to greener pastures.
Software has also benefitted from a massive tax subsidy relative to hardware, as the latter requires a massive capital investment. Hardware requires expensive real estate, and benefits from saving the spending, whereas software can exist on debt and small footprints.
That may have been the case prior to section 174, when you could invest massively in something, write it off as a loss, and then pivot to reusing it profitably, but now I think that all R&D efforts are equally discouraged.
Seems like everyone forgets that the USA literally invented all these things. In fact some of the Americans who invented these technologies and processes are probably still alive, if not a bit older and retired. Photolithographic semiconductor fabrication was invented in the United States. Americans invented the transistor. Americans invented the integrated circuit.
I’m pretty sure the USA would do fine in the semiconductor industry in a short while if it was economical (i.e it stops being profitable to undermine American workers with cheap overseas labor).
I was a fab tool owner. My last paycheck in a semiconductor position was in the mid-200s. I went into software and make double that in the same metro. Same level of responsibility. I don’t even work in machine learning.
To take your photolithography example though, I know someone who went litho tool owner -> camera team at Apple -> Meta reality labs. FAANGs want semiconductor process engineers just so they can spend all day yelling at underpaid Asian vendor semiconductor process engineers who are doing the actual work.
A lot of highly skilled people are perfectly happy to stay at their job earing 60% of what they "could" be making because they have other priorities that don't involve increasing shareholder value.
> FWIW Deep Research doesn’t run on whatever you pick in the model selector. It’s a separate agent that uses dedicated o‑series research models: full mode runs on o3; after you hit the full‑mode cap it auto‑switches to a lightweight o4‑mini version. The picker governs normal chat (and the pre‑research clarifying Qs), not the research engine itself.
All devs should run open-source trufflehog as a precommit hook for all repositories on their local system. It’s not a foolproof solution, but it’s a small time investment to get set up and gives me reasonable assurance that I will not accidentally commit a secret. I’m unsure why this is not more widely considered standard practice.
This isn't true in practice. Even among well educated high performing professionals, mistakes happen. Checklists save lives - in medicine, in aircraft maintenance, in all fields.
People who believe they know what they're doing get overconfident, move fast, and make mistakes. Seasoned woodworkers lose fingers. Experienced doctors lose patients to preventable mistakes. Senior developers wipe the prod database or make a commit they shouldn't.
>In a study of 100 Michigan hospitals, he found that, 30 percent of the time, surgical teams skipped one of these five essential steps: washing hands; cleaning the site; draping the patient; donning surgical hat, gloves, and gown; and applying a sterile dressing. But after 15 months of using Pronovost’s simple checklist, the hospitals “cut their infection rate from 4 percent of cases to zero, saving 1,500 lives and nearly $200 million,”
I made shameful mistake of submitting private key (development one so harmless) only because it wasn’t gitignored and prehook script crashed without deleting it). More of a political/audit problem than a real one.
I guess I’m old enough to remember Murphy Laws and the one saying "safety system upon failure will bring protected system down first".
Pre-commit hooks are client-side only and opt-in; I've always been a big proponent of pre-commit hooks, as the sooner you find an issue the cheaper it is to fix, but over time pre-commit hooks that e.g. run unit tests tend to take longer and longer, and some people want to do rapid-fire commits instead of being a bit more thoughtful about it.
- enforce them on CI too; not useful for secrets but at least you're eventually alerted
- do not run tasks that take more than a second; I do not want my commit commands to not be instant.
- do not prevent bad code from being committed, just enforce formatting; running tests on pre-commit is ridiculous, imagine Word stopping you from saving a file until you fixed all your misspellings.
I moved all my precommit hooks to prepush hooks. I don’t need a spellchecker disrupting my headspace when I’m deep into a problem.
My developer environments are setup to reproduce CI test locally, but if I need to resort to “CI driven development” I can bypass prepush hooks with —-no-verify.
One good (and obviously bad) thing about Subversion was the ability to change history. As admin I was asked numerous times to change a commit message. To point to the correct Jira issue, for instance.
Also easier to enforce pre-commit, since it was done server side.
Interesting! I’ve faced the same problem where I have a mega PR and spend a lot of time breaking that up into separate PRs. I agree that what you are suggesting is a different but related problem to what this tool currently solves. I’ll start thinking through how this would look, and I’ll go ahead and make a GitHub issue if you or anyone else wants to start a discussion there.
Why do people speak online as if the library is a place anyone goes to? I understand some people still go to libraries, but this cannot be considered a commonplace activity like it once was. Librarians do not hold any meaningful position in society because so few people come in contact with them.
Do you have kids? Virtually every parent I know (myself included) visits the library at least once a week with their kid. In my community the library is very well trafficked.
This sounds like some upper middle class white Boston shit. This is 1000% not the experience of most parents in America, especially the browner and poorer parts of America. Good luck getting one library attendance a year from most American children…
Ex-Founder and software engineer with 5 YOE looking to join a small high-growth company in either a technical product manager role or software engineer role. Will relocate anywhere in the US for the right opportunity.
