nurspouse

As an aside, in Islam, people have to pay a 2.5% wealth tax annually for charity.[1]

This does make retiring a tad bit complicated. Say you've saved $3M and are ready to retire. That means each year you're spending $75K just to satisfy this tax.

[1] Depending on how your wealth is structured. Cash is 2.5%, but if you own, say, a business, you pay the tax on the value of the goods, not on the value of the building, hardware, etc. You don't pay Zakat on the house you live on. Agriculture is actually taxed at 10%, etc.

For context:

As a percentage of the population, Hamas's attack on Oct 7th killed 6 times as many people as Al Qaeda did on September 11. If you are an Israeli, you are 6 times more likely to know someone impacted by those attacks than Americans did in 2001. As a result of the 2001 attack, the US invaded two countries, resulting in million(s)[1] dead on the other side.

Make no mistake: For any country that has the means, losing 900 people in one day will always be seen as an act of war, and they will respond. While the Israeli response is certainly "disproportionate", it is not by any means an outlier when you compare with typical conflicts around the world.

I definitely think Israel's response should be condemned, but I will openly say: Our government(s) in the US routinely do worse. Let there be perspective.

[1] Depends on which study you look at.

I've been using xonsh professionally since around 2018 - in both Windows and Linux. Love it. Getting it to run existing bash scripts was a pain earlier on, but has gotten much better.

The one thing I don't do is make it my official shell in Linux. I keep bash/zsh as my shell, but the first thing I do in any shell is launch xonsh. Occasionally it does crash and it's nice to end up in a "backup" shell in case I need to recover anything.

Psst... xonsh!

Relatively terse, and quite readable scripts (they are mostly Python!)

PTD is almost entirely PhDs.

If he was a test automation engineer, he likely had transferable skills. Many/most of the fab folks have almost no programming skills, and are PhDs in things like chemistry[1], etc.

Now some of them do take the initiative and learn SW skills, or data analysis properly, and switch due to that. But the majority of them feel stuck. They have a heavy workload and do not feel they have time to learn new skills.

[1] For a long time, and perhaps even now, the fabs only hired either technicians or PhDs. An exemption would be needed to hire someone with "just" an MS. Of course, almost none of these jobs actually need PhD level skills.

> Intel isn't a great place to work (despite their corporate value claiming it is), but by most accounts, Amazon is much worse unless you really like a place with cutthroat corporate politics.

I used to work at Intel. Some data points:

When the news about how bad Amazon's culture was (e.g. people crying at desk), my thoughts were "This sounds like Intel."

When you talk to Amazon employees, most say "Every team is different. We don't see such behavior in my team, and I don't work long hours (i.e. more than 40)." And the same can be said at Intel. If you're close to the fab, the behavior is crap. Software tends to be pretty chill. And you'll see everything in between. I recall once going in on Saturday and talking to a guy - he said he'd worked every weekend for the last 6 weeks and expects to continue doing so for a month or two more.

Everyone I know who has left Intel to join Amazon is happier at Amazon. Everyone. The most common refrains:

1. Good work/life balance at Amazon (although some had it good at Intel too).

2. Far fewer morons at Amazon. When you're in the non-core parts of Intel (e.g. software), the people around you are fairly poor in terms of talent (e.g. complaining about having to use Git, saying we're using it only because Microsoft owns Git (!), refusing to use branches in Git and insisting on just creating command line arguments for every experiment you want to try).

Intel, though, does have better PTO.

Former Intel employee here. This may be true for their design folks, but the largest portion of the company is related to the fab, and there aren't many jobs for those folks. Moreover, the alternatives (TSMC, Samsung, etc) suck as much as Intel.

Intel hired over 20,000 people this year alone (likely a record for them both in terms of absolute and relative percentage). The freeze is similar to that of other companies: Uncertainty over economic conditions.

While such people may exist at Intel, it's not at all the norm, and to be frank, doesn't improve your chances of getting a job there.

(Worked at Intel and along with fab/process folks for a bunch of years).

This falls more into the electronics domain, which I know is sometimes put under the "semiconductor" bucket, but in universities usually has its own domain ("microelectronics" in my day). It's a lot more focused on the circuit/high frequency model of the transistor, and builds up form it.

Semiconductor theory is more about the transistor and everything below it: Starting from quantum mechanics and statistical mechanics, derive the equations of electron/hole transport in a doped semiconductor, how the material's band structure impacts current flow, etc. The derivation of the transistor equations is often the end point.

The industry doesn't have a talent shortage, which explains the working conditions. There will always be grad students who think "Cool! I get to do research involving quantum mechanics!"

Trust me, I've tried to talk them out of it and never succeeded.

Semiconductor theory is more interesting, but don't even consider it unless you love math and can do standard integrals without having to look up tables.

Also, the mistake I made when I went to grad school: Semiconductors seemed to be a "new" field compared to the rest of EE. One of my undergrad professors said "They still haven't figured out what a standard textbook should contain."

In reality, from a research standpoint, it's a very mature field. Don't expect low hanging fruit. If you're going to focus on theory, expect it'll take a number of years of dedicated study before you get to the frontier. You'll need to know quantum mechanics and statistical mechanics, and some electromagnetics, just to begin studying semiconductor theory. Then a whole bunch of specialized solid state courses. Then you start studying the specific subtopics (reading key journal papers).

> But later I'd want to work as compiler engineer

Why are you wasting time with semiconductors...?

I assume that's because of pay. Working conditions for SW folks is fairly decent at most of the company, except possibly for firmware folks.

I suppose some people didn't like their status in a HW company.