Whoa, thanks for the flashback. I remember reading about your work in some of Abrash's columns.
Slashdot videos: Now with more Slashdot!
how about writing music that can be played on a rested grass lawn with minimal overhead and a four-piece band?
Well, some musicians don't like playing to a crowd fully of hippies.
Upsample to 24/96 while you're at it and you can compete against Neil Young!
It's a great idea to wear loafers and stop periodically to tie your shoes; people will go out of their way to avoid your personal space. No one wants to collide with a crazy person.
Do not spend your time synthesizing literature studies.
There are plenty of examples of both usages of slower, showing that it is ambiguous across popular usage. For example, there's a whole 800% slower "genre" on Youtube where songs are played at 1/8 of their original speed. When popular usage is so sloppy, it's better to avoid the phrasing altogether in favor of something precise instead.
No, that dude has been on Slashdot for longer than any 12 year old has been alive. You can tell from both his uid and the terrible car analogy.
Clueless defense contractors are numerous. But since the core of the US government purchasing is Open Source First, there is little hope of Microsoft regaining any serious hold in that market.
In your interview process, ask obscure low-level architecture questions, like "What is a trap?" or "What does the BEQ/JEQ/JE opcode do?" These questions will rule out anybody who hasn't ever worked with any form of assembly language.
No, it will just make you a trivia-based interviewer. You need to be a serious authority on every aspect of a thing before you can create a comprehensive question like that. These two both have problems. I can tell how old you are from how you asked them.
The i386 processors that are all many people use now call those interrupts, not traps. And there are over 30 branch instructions in that set. JE is one of them, but I wouldn't expect people with only a small amount of assembly language background to remember that particular combination. You can easily write non-trivial 386 programs and never use JE.
This is not that hard: ask "have you ever written anything in assembly language?", and if they say yes, ask how it worked. No opcode trivia is necessary.
Web development now is all about plugging components together as quickly as possible to ship code. Anyone who pauses to try and actually learn how things work is at a disadvantage. While you're doing that, your competitors have already shipped something that worked well enough for people to use it.
Also, there's little sense really digging into things like libraries when they change so quickly. I'm doing this project right now that's all Go based. People who did a deep dive into learning how their previous tools are again regretting that.
Databases are an abstraction level on top of filesystems. You effectively said that you build a filesystem by using a filesystem.
Audrey Tang? Really? Your lead example is someone known primarily for their epic failed project?
See office password protection. The encryption of Excel version before 2007 was laughably weak. The last such file I had to crack took minutes. And that's still what you get if you use the older file formats.
The encryption starting with Office 2007 is as strong as your password. It's still possible to break weak ones, but you need to apply a fair amount of brute force. Here's a typical cracking program. The way it advertises support for multiple cores and GPU acceleration is a clue it's not trivial to crack.
But the question was how to compute the range of addresses it allows. Knowing the subnet mask isn't enough to do that. You also need to know the rules for what numbers you can't use in each subnet block. Not even all the calculators out there get this right. The first hit I got back from searching for one didn't; here's one that does. For the example here, "Usable IPs = 192.168.0.1 to 192.168.0.254".
Even a hardware failure can be automatically migrated away from before it takes down the server and fixed without any down time.
The history of automatic fail-over software says that when you add some, in addition to the old issues you now have bugs in the fail-over software as a new problem.