Having not seen the blog, it's hard for me to make a guess about how well it would be considered parody.
You can catch it on archive.org.
It's not parody. It's not vaguely related to parody. Anybody who thinks it's parody desperately needs to bone up on their reading comprehension skills.
It is, however, bona fide commentary and criticism for which the pictures are the obviously essential base element. Very clearly fair use.
What would happen is: water would condense on the every surface in the computer after every time you opened the case. And you know how well moisture plays with electronics.
After opening and closing the case, you would need to run the fridge case in a dehumidification mode for several hours before turning the computer on in order to reduce the humidity below the cooled computer's dew point.
In addition to this problem, the contraction and expansion from when the computer runs and stops (stopping the fridge with it) would quickly wiggle stuff out of its socket and create cracks on the boards.
It does not matter what your Software Engineer does at any particular time. Software Engineer is a professional job exempt from overtime rules for a reason: the thing that matters is whether he produces an appropriate amount of quality work.
Do you have any idea whether his work gets done? It doesn't read like you do. That's the question you should ask as you decide whether to keep or fire him.
If you want this IRS exempt employee to work for you by the hour rather than by the task or by the mission, you have that option. It's called "consultant" and you'll pay twice as much or more -per hour-.
Years ago a McDonalds manager conducted an interview a couple tables away as I ate a late lunch. Have you ever worked before? No. Do you have the two items for the I-9 form? No. Do you know your social security number? No. Okay, well get those things and come back.
Then an assistant manager came over. The manager says to her, "If he comes back, we'll probably hire him because he can speak English."
"This is yet another serious example of the need for us to upgrade and better safeguard our city's technology infrastructure," Rawlings said
This is an even better example of the need to downgrade. The sirens weren't always connected to the Internet. What compelling reason requires them to be connected to the Internet now?
Internet security lesson #1: if it doesn't need to be connected to the Internet, don't connect it to the Internet.
Just looking at this, if someone falls in front of it, it'll run them over. That may fly in Slovakia but in the U.S. it would get the police department sued within an inch of their existence.
yeah... display the usual challenges and then reject correct answers two or three times in a row before accepting a correct one. And by the way Linux = suspicious. It's a POS.
Bit-rot is an issue inherent to any storage medium
Here's a quick article which explains how hard disks use error correcting codes so that the user-level experience is no bit rot but rather many many read failures before even a single block of undetectably corrupted data. Next time you can know what you're talking about.
"ZFS isn't even a filesystem for this age" - WTF does that even mean?
It means that even back when FAT was a johnny come lately it already had greater market penetration than ZFS. With decades behind it and broad market penetration today, there's good reason to believe it won't vanish with the advent of the next development in filesystem architecture. ZFS is likely to be a blip on the radar, a pause before the next innovation. Not what you want for an archival format.
Bit-rot is an issue inherent to any storage medium
Bit rot, aka corrupted data, is not inherent to correctly operating hardware. As implemented, you'll see tens of thousands of unreadable blocks on a hard disk before you see a single one in which data has been undetectably corrupted. Every single sector gets a checksum in hardware and if the checksum does not pass you get the famous Abort Retry Ignore. For most storage you get Forward Error Correction coding so that some number of bit errors can be corrected on read before having to throw an error.
When you see bit rot, the storage media is usually not at fault. More often the data passes through faulty non-parity ram, a noisy memory bus or an overheated controller and gets corrupted on its way to storage rather than getting corrupted at rest on the storage. It died when you used an overclocked piece of garbage to copy it from an old hard disk to a newer, bigger one.
He said a filesystem for the ages. While it has wonderful features, ZFS isn't even a filesystem for this age, let along ages to come. FAT32 and ISOFS are your best bets for being readable 20 years from now.
Bear in mind that your hard disk checksums each block and returns an error if the block is uncorrectable upon read rather than give you bad data. So, if you're getting bit rot at all then you have a hardware problem.
With or without a hardware problem you want to be able to recover your data. The answer is par2, such as parchive or QuickPar. Par2 uses a Reed-Solomon code to take a set of source files and produce a set of recovery files such that the original files can be checked for correctness and up to N original files can be corrected where N is the number of recovery files created.
And that's your answer. A filesystem like FAT32 or ISOFS that's likely to still be implemented in future OSes and a recovery files which let you rebuild anything that suffers from bit rot.
Of course you use a binary search to find the insertion point. Then you move the latter half of the array to make room for the insertion. O(n^2).
If it's a linked list instead of an array, you get your insertion as a constant time operation but have to search half the list on average to find the insertion point. Still O(n^2).
Understanding your code's big-oh run time really is important.
Hard to drop something on the planet from orbit at orbital speeds. Momentum doesn't like to take sharp turns. The big rocks that deliver nuclear-level kinetic energy arrive at high speed from -outside- the earth-moon system.
That's an eye chart. Asking someone to catch the greater than sign instead of a less than sign on paper in an interview is a downright nasty question. Of course people get tripped up on it. If it didn't catch my glance, I'd get tripped up on it and I've been programming for 30 years.
If you want to see how someone thinks through a problem, either give them a computer and watch or instruct them to "tell me what you'd do next to try to figure this out. I'll respond with the result you get each time you try."
Here's a better softball for computer science grads:
Your friend writes a program which receives messages. It adds each new message to a sorted array of messages. When a message is retrieved, it does a binary search on the sorted list to find the message.
What's wrong with this solution?
The candidate should be able to recognize that his "friend" has reinvented insertion sort and should be able to explain that the algorithm has a "big-oh" running time of O(n^2).
Converting complex instructions into predefined sequences of simple ones is not writing code. When the machine can fix all my bugs for me, then it'll be writing code.
Actually, the fake news was at CNBC. The article claimed Musk said exactly what Slashdot quoted. It then quoted Musk saying something entirely different.
Slashdot Mirror
Having not seen the blog, it's hard for me to make a guess about how well it would be considered parody.
You can catch it on archive.org.
It's not parody. It's not vaguely related to parody. Anybody who thinks it's parody desperately needs to bone up on their reading comprehension skills.
It is, however, bona fide commentary and criticism for which the pictures are the obviously essential base element. Very clearly fair use.
https://www.copyright.gov/titl...
"the fair use of a copyrighted work [..] for purposes such as criticism, comment [...] is not an infringement of copyright"
ROFL. Mod this guy up.
What would happen is: water would condense on the every surface in the computer after every time you opened the case. And you know how well moisture plays with electronics.
After opening and closing the case, you would need to run the fridge case in a dehumidification mode for several hours before turning the computer on in order to reduce the humidity below the cooled computer's dew point.
In addition to this problem, the contraction and expansion from when the computer runs and stops (stopping the fridge with it) would quickly wiggle stuff out of its socket and create cracks on the boards.
I had my cell phone carrier remove the voice mail feature from my phone. Take that suckers!
It does not matter what your Software Engineer does at any particular time. Software Engineer is a professional job exempt from overtime rules for a reason: the thing that matters is whether he produces an appropriate amount of quality work.
Do you have any idea whether his work gets done? It doesn't read like you do. That's the question you should ask as you decide whether to keep or fire him.
If you want this IRS exempt employee to work for you by the hour rather than by the task or by the mission, you have that option. It's called "consultant" and you'll pay twice as much or more -per hour-.
They belong... just, well, if those are your favorites you're not a real computer guy and are barely a sci fi fan.
Then again, if neither Tron nor WarGames make the top of your list, you're also not a real computer guy.
Years ago a McDonalds manager conducted an interview a couple tables away as I ate a late lunch. Have you ever worked before? No. Do you have the two items for the I-9 form? No. Do you know your social security number? No. Okay, well get those things and come back.
Then an assistant manager came over. The manager says to her, "If he comes back, we'll probably hire him because he can speak English."
"This is yet another serious example of the need for us to upgrade and better safeguard our city's technology infrastructure," Rawlings said
This is an even better example of the need to downgrade. The sirens weren't always connected to the Internet. What compelling reason requires them to be connected to the Internet now?
Internet security lesson #1: if it doesn't need to be connected to the Internet, don't connect it to the Internet.
You did read in the article where it mentioned that the machine was made and sold in Slovakia, did you not?
Just looking at this, if someone falls in front of it, it'll run them over. That may fly in Slovakia but in the U.S. it would get the police department sued within an inch of their existence.
This. So much this.
Hah hah. The "it" referred to Recaptcha not Linux.
Just reporting my experience with the product, so if you're the guy who wrote it then right back at you.
yeah... display the usual challenges and then reject correct answers two or three times in a row before accepting a correct one. And by the way Linux = suspicious. It's a POS.
Bit-rot is an issue inherent to any storage medium
Here's a quick article which explains how hard disks use error correcting codes so that the user-level experience is no bit rot but rather many many read failures before even a single block of undetectably corrupted data. Next time you can know what you're talking about.
http://www.pcguide.com/ref/hdd...
"ZFS isn't even a filesystem for this age" - WTF does that even mean?
It means that even back when FAT was a johnny come lately it already had greater market penetration than ZFS. With decades behind it and broad market penetration today, there's good reason to believe it won't vanish with the advent of the next development in filesystem architecture. ZFS is likely to be a blip on the radar, a pause before the next innovation. Not what you want for an archival format.
Bit-rot is an issue inherent to any storage medium
Bit rot, aka corrupted data, is not inherent to correctly operating hardware. As implemented, you'll see tens of thousands of unreadable blocks on a hard disk before you see a single one in which data has been undetectably corrupted. Every single sector gets a checksum in hardware and if the checksum does not pass you get the famous Abort Retry Ignore. For most storage you get Forward Error Correction coding so that some number of bit errors can be corrected on read before having to throw an error.
When you see bit rot, the storage media is usually not at fault. More often the data passes through faulty non-parity ram, a noisy memory bus or an overheated controller and gets corrupted on its way to storage rather than getting corrupted at rest on the storage. It died when you used an overclocked piece of garbage to copy it from an old hard disk to a newer, bigger one.
He said a filesystem for the ages. While it has wonderful features, ZFS isn't even a filesystem for this age, let along ages to come. FAT32 and ISOFS are your best bets for being readable 20 years from now.
Bear in mind that your hard disk checksums each block and returns an error if the block is uncorrectable upon read rather than give you bad data. So, if you're getting bit rot at all then you have a hardware problem.
With or without a hardware problem you want to be able to recover your data. The answer is par2, such as parchive or QuickPar. Par2 uses a Reed-Solomon code to take a set of source files and produce a set of recovery files such that the original files can be checked for correctness and up to N original files can be corrected where N is the number of recovery files created.
And that's your answer. A filesystem like FAT32 or ISOFS that's likely to still be implemented in future OSes and a recovery files which let you rebuild anything that suffers from bit rot.
The document was unreleased because it was a factually wrong draft. A corded phone produces a weaker EMF than a wired headset? Really?
O(n) to add one entry. O(n^2) to add n entries.
Sounds like you are adding to end of array
Did you enjoy trying to troll me?
Of course you use a binary search to find the insertion point. Then you move the latter half of the array to make room for the insertion. O(n^2).
If it's a linked list instead of an array, you get your insertion as a constant time operation but have to search half the list on average to find the insertion point. Still O(n^2).
Understanding your code's big-oh run time really is important.
Hard to drop something on the planet from orbit at orbital speeds. Momentum doesn't like to take sharp turns. The big rocks that deliver nuclear-level kinetic energy arrive at high speed from -outside- the earth-moon system.
That's an eye chart. Asking someone to catch the greater than sign instead of a less than sign on paper in an interview is a downright nasty question. Of course people get tripped up on it. If it didn't catch my glance, I'd get tripped up on it and I've been programming for 30 years.
If you want to see how someone thinks through a problem, either give them a computer and watch or instruct them to "tell me what you'd do next to try to figure this out. I'll respond with the result you get each time you try."
Here's a better softball for computer science grads:
Your friend writes a program which receives messages. It adds each new message to a sorted array of messages. When a message is retrieved, it does a binary search on the sorted list to find the message.
What's wrong with this solution?
The candidate should be able to recognize that his "friend" has reinvented insertion sort and should be able to explain that the algorithm has a "big-oh" running time of O(n^2).
Converting complex instructions into predefined sequences of simple ones is not writing code. When the machine can fix all my bugs for me, then it'll be writing code.
Actually, the fake news was at CNBC. The article claimed Musk said exactly what Slashdot quoted. It then quoted Musk saying something entirely different.