Likewise. A Fields medalist deserves better. In fact, the first female Fields medalist.
1 karma · joined December 4, 2019
Also, I don't see how their design avoids hot keyspace issues. Traditionally this is the main problem with partitioned designs because you move the problem one level up to properly designing the key that will be used to distribute the load across partitions.
I'm certain if we saw actual numbers it would not be a pretty picture.
For the truly motivated it is much better to go to recurse.com or join a learning Meetup. Get a day job to pay the bills and learn at your own pace. Programming is not going anywhere even with all the fancy AI startups. In fact if I was just starting out I'd just learn Python and R.
> (idiomatic) To raise a false alarm; to constantly warn others about an imagined threat, thereby failing to get assistance when a real threat appears.
The imagined threat is the level of quality in patches. He consistently raises false alarms about the quality of patches. The false part being the absolute terms he uses about the character of the people that proposed the patches. Calling someone an infantile moron qualifies as falsehood in my book and counts as raising a false alarm. Now that he is complaining about grsecurity I'm not inclined to listen because the level of alarm he has used previously has been incommensurate with reality, as in he has said "here is a wolf" (this patch is the worst thing ever and the person that wrote it is a moron) when in reality there was no wolf (patch was actually fine and the person was not a moron). Less alarmism would have helped everyone involved get along better and make a more secure kernel. Instead I'm arguing about how comparing his alarmism to crying wolf is or isn't idiomatic. FML
The grsecurity stuff could be bad but I sure as hell am not gonna get my analysis from Linus. If he acted more like a grown up then maybe but he doesn't. He character assassinates and then says you are doing silly pointer arithmetic. Can just mention the pointer stuff without shouting and screaming at author of the patch.
The drama in kernel dev is a direct result of his abrasive approach. He screams and shouts so grsecurity screams and shouts. Everyone else loses. The kernel dev space needs less drama and more grown ups.
If done properly this could even feed into code dynamics to capture information on the runtime information. So that at every point in the program you could start asking questions like how many times did this line execute, what was the type of this variable at this point, how much memory was allocated, and so on and so forth.
I could see maybe EE or robotics being something that a good university would have an edge over your local community college. But even here you could get by without access to a good lab if you were motivated enough. Going into debt is almost never the answer.
Those companies go out of their way to reduce as much bias as possible. In the long run we are all better off if we rely on data instead of anecdotes and fancy resumes.