>
I can't wait for all the data center fire-sales when the whole "AI" boom goes bust. Ebay is going to be flooded with tech.
I think a lot of the hardware of these "AI" servers will rather get re-purposes for more "ordinary" cloud applications. So I don't think your scenario will happen.
It would be nice to have a way to output a corresponding gear. I can make a gear with small teeth with a wide gap between them, but the same gear wouldn't really work to engage with that gear, on the other gear the teeth would need to fill the wide gap of the first gear.
Only works in a one-way system, which might be okay, but if bidirectional is a requirement then the other gear would be necessary. I suppose then just create a symmetrical gear. Sorry I'm not a gear-head.
If one guy's pot is worth 10 billion, and the other's is worth 100 million, and the first guy got rich from the second guy's work, things seem a little bit upside down. 1% of Jobs wealth is still a lot of money, but the disparity is stark for two people who co-founded the company.
Your take only applies to recent developments. For the entirety of the H visa program, it has brought in very valuable talent, which stayed here to generate incredible wealth for the country. "onlyfans" is a recent thing. The kickbacks are a relatively new thing. Sure immigration is broken, but that's what happens when the government is intent on breaking the country.
The fact that these visas are abused by people in power is completely different and in the end minor issue. I would bet vast majority of EB-1 are pretty out of the ordinary.
This is just derailing the discussion. Visas for privileged individuals bad = immigration bad.
Well you are right about one thing. Government is intent on breaking the country. But rampant immigration immigration fraud and abuse has been around for decades.
In my old age I'm learning that this is rare. I take my projects for granted, because I guess I'm just very creative, I have way more "projects" than I have days remaining. But it seems like most people have no projects, and nothing in their lives but watching television, playing video games, or doom scrolling.
I trust my offshore engineers way more than the slop I get from the "AI"s. My team makes my life a lot easier, because I know they know what they are doing. The LLMs, not so much.
If we cut costs and automate the way China has automated - some factories run without any lighting at all because it's all robots running in the dark - then there aren't going to be a lot of jobs created by on-shoring. And the only way to create a product on-shore that approaches the pricing of the Chinese equivalent is to heavily automate.
"Lights out" has been the big automation meme since before China joined the WTO. Everyone has gotten better over time but it's still "high school sex bragging rules": a few people are doing it but not nearly as many as brag about doing it.
Clothes are nowhere near as heavily automatable as people like to believe they are, is the problem. Unlike many other goods, nearly every article of clothing produced today is still produced with human hands. This does not mesh well with the fact that the modern public has been trained not to value apparel; people expect to casually buy items of clothing for less than they'd spend on a single meal.
It's not like the cost of clothes would be that much more if produced domestically though... the difference is the margins would be lower, a domestic employee would have a job and the domestic economy as a whole would be stronger as a result. Not to mention, the lower margin also means the wealth gap would be more narrow and there would be less incentive to stoke the flames of class warfare.
Why do people assume that clothes (and other goods, mind you) produced in the US are a mere hypothetical? There are plenty of brands that do so, and your general public overwhelmingly ignores them (and, as you have just demonstrated, don't even know they exist) precisely because they are way more expensive than consumers have been conditioned to believe that clothes should cost.
For instance, actual MiUSA jeans from companies like 3sixteen and Raleigh Denim retail for ~$200+, which is a far cry from the $30 to $50 that most people think jeans "should cost" (and that companies like American Eagle, who have long since outsourced their manufacturing, are happy to provide). Sure, it's not as if MiUSA jeans HAVE to be a few hundred dollars (I believe there are some Gustin's jeans you can pick up for $120 or so), and there are offshored jeans like Levi's which are already overpriced. But you'd have to be very naive to think that there would not be a massive and quite frankly unbearable sticker shock for the vast majority of people if you were to somehow force all domestic clothing demand to be met through domestic production. You could maybe sell it with some very effective austerity propaganda, but good luck with that.
Where did I say there are no clothes produced in the US? That said, I do think there's room to compete of most US clothes were produced domestically and that the pricing could come well below the existing US brands.
There's also brands made in China for cheap with Euro brand labels attached that sell for several hundred. Cost is not the same as price.
>Knowing two languages isn’t all that bad. Most developers learn many languages during their careers and switch between them without a thought.
One of the most revered programmers in my circle, who's been coding since the early 1970's asked me once, "how many programming languages do you know?". I started rattling off a few, and he stopped me. He said "I only really know the last 2 languages I used".
Jack of all trades, master of none. If someone asked me to code in PHP, Perl or any of the dozens of languages I've used in the past today, just no way. No thank you. Yeah, I used to be very proficient with lots of languages, but no way am I going dust off those brain cells. Assembly is probably the only language I can really get into on different platforms without a huge cognitive context switch, because it's just straight forward, no kooky abstractions.
That said, I've used Javascript for front-end, back-end as well as database (mongo), and it was absolutely great to not have to context switch constantly. I've also done lots of different systems with a wide variety of other languages glued together, and it hasn't been as effortless as using one language for everything. YMMV.
If he can only remember two programming languages then he wouldn’t stand a chance in today’s dev ops, t-shaped, m-shaped world I’m afraid. Imagine asking him to help setup an CI pipeline, or some infrastructure but he’s worried learning a bit of Terraform will make him forget his second last language. You just can’t be like that these days. You have to be a jack of all trades and a master of all trades. That’s just where we are and it’s not going to change anytime soon.
A lot of language concepts are shared and abstract. It’s not hard to know many languages proficiently.
I do agree a lot of people over estimate how much they know, but I work with multiple people who know at least 5 languages well.
For me myself, only counting things I’ve shipped at scale, I’d know C, C++, Swift, JavaScript, Python, Rust, MSL, HLSL, GLSL, MEL. There’s enough in common between them that I think it’s quite doable.
Shipped !== know. I've touched dozens of languages over my career and every time I've had my ass kicked by some esoteric knowledge of specific quirk in std of %lang%. We have a different definition of "know".
You initially said beyond a surface level and now you’re talking about esoteric quirks.
Pick one. Of course nobody has the same definition as you if you’re shifting the line and simultaneously not defining what you mean.
You don’t need to know every aspect of a languages corners to be proficient in it. If that were true, there’s only a handful of people on this planet who’d be proficient in a single language let alone multiple.
Sure, I can "swim when thrown into the cold water", but you have to be a masochist to like that kind of job. It sucks. I won't do it if I don't have to, and luckily I don't have to.
It pays better than the alternatives and some freedom moving between technologies, which tend to be product development with an expiration date, until the company gets acquired or decides to offshore the team.
Contrary to product companies you also get to jump technologies without having an HR department sending the application into the garbage because one doesn't tick all the boxes on a specific stack.
>For individual use I guess the solution is to set it up once with internet connectivity and air gap afterwards.
That's simply not good enough for some purposes. Once a computer is connected to the internet, at all for any amount of time, the system could be considered to be less secure.
reply