1,417 karma · joined December 18, 2021
Such education is COMPLETELY different from the one they offered in school, but closer to those offered in premium schools (MIT/Berkeley). Basically, I'd call it "Software engineering archaeology". Students are supposed to take on ancient software, compile them, and figure out how to add new features.
For example, for the OS kernel branch:
- Course 0: MIT xv6 lab, then figure out which subsystem you are interested in (fs? scheduler? drivers?)
- Course 0.5: System programming for modern Linux and NT, mostly to get familiar with user space development and syscalls
- Course 1: Build Linux 0.95, run all of your toolchains in a docker container. Move it to 64-bit. Say you are interested in fs -- figure out the VFS code and write a couple of fs for it. Linux 0.95 only has Minix fs so there are a lot of simpler options to choose from.
- Course 2: Maybe build a modern Linux, like 5.9, and then do the same thing. This time the student is supposed to implement a much more sophiscated fs, maybe something from the SunOS or WinNT that was not there.
- Course 3 & 4: Do the same thing with leaked NT 3.5 and NT 4.0 kernel. It's just for personal use so I wouldn't worry about the lawyers.
For reading, there are a lot of books about Linux kernels and NT kernels.
> you lay out a huge specification that would fully work through all of the complexity in advance, then build it.
I have tried this a couple of time even for small projects ( a few sprints ), and they never worked out. I'd argue it never works out if you are doing non-system programming projects, and only has a theoretical non-zero possibility to work out for system programming projects, and perhaps a 5-10% to work out for very critical and no patch possible projects (like moon landing).Because requirements always change. Humans always change. That's it. No need to elaborate.
I found it a bit surprising that as a 45-year old chip, there is no public information of its microcode. I guess hardware is indeed much more secret than software.
My understanding is that US is going to shrink back a bit, takes care of its neighbours first, but keep its probing bases intact, so that it can slash some costs and be more flexible in next decades. China is going to reluctantly expand its power base gradually -- but I think it's going to be a slow expansion because any rapid one would either fail, or create a new power group within China, that may threaten the existing players.
Not sure about EU though, it better gear up quickly.
From my experience, the data modelling side is still overwhelmingly in SQL. The ingestion side is definitely mostly Python/Scala though.
I'm still skeptic about driver-less taxis, even when commercial ones like Waymo are already running on the road. But at least taxis run in 2D regulated highways and most of the drivers are sane enough.
I really love this kind of culture. Life is grey without being challenged to the limit.
I spent about 30-60 minutes every day.
I'd like to post some questions for thought:
1. What is exactly the bidding process of that particular transaction the OP described?
2. What is exactly in the contract? Does it force the Chinese company to use a lot of local companies for sub-contracting, at the same time keeping a very low profit? In essence, this basically means the EU companies grabbed the biggest share while the Chinese company just got the job. I'm not saying this is the case, but I highly doubt it IS the case as I heard similar stories from other companies.
That's called manufacturing, the best skills in the world. Yeah it's tough work and pay is not brilliant, but when shit happens that's the thing that is going to save EU.
One of the commenters of your post says "If we legalize it we can better research it". Allow me to be rude -- this is BS. If we follow this logic we should legalize pretty much everything!
I think it is polite to be rude to such dangerous thoughts. Downvote me as you see fit.