|
For many of us, if we wanted the computer to do anything, we had to type in entire programs from books To get the full experience, print out the source code and type it in yourself
|
|
|
|
|
For sysadmins responsible for Exchange servers, it’s been a much different story as Microsoft Exchange servers have not been able to properly process the new date, and therefore, can't process mail. Signed int32 ought to be enough for everyone?
There is a patch out, fortunately (and well done Exchange team, sorry about the holiday)
|
|
|
|
|
A St. Louis Post-Dispatch reporter who viewed the source HTML of a Missouri Department of Elementary and Secondary Education website is now likely to be prosecuted for computer tampering, says Missouri Governor Mike Parson. If you take away 'View Source', only outlaws will use 'View Source'
Politicians don't understand tech: this week's edition.
Besides, I thought Missouri was the "Show me" state?
|
|
|
|
|
"I'd rather have a bottle in front of me, than a frontal lobotomy." But give everyone even remotely responsible for prosecuting him the frontal lobotomy - it is obvious they don't use it already. And remove them from all positions of power.
|
|
|
|
|
|
Message Removed
modified 31-Dec-21 7:44am.
|
|
|
|
|
Message Removed
modified 31-Dec-21 7:44am.
|
|
|
|
|
Key services, including network provisioning, will shut down January 4th. "This is the end. My only friend, the end"
|
|
|
|
|
Very sad.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Adding more context to our Pull Requests got them merged two days faster. git commit -m "10 things you won't believe this code will do for you!"
|
|
|
|
|
PR - Pain Request.
|
|
|
|
|
For most of my career, I worked with a proprietary code library. Each file was owned by a group, and you had to get a group member to open the file for your changes, OPEN being an explicit file state in the library. A file rarely got opened unless you were ready to commit your changes soon. All changes had to compile, had to have been tested, and non-trivial ones had usually been vetted in advance by someone in the owners' group. This encouraged would-be changers and code owners to work together. If a file was already open for changes, you knew it was a moving target if you also wanted to change it. You could work on it privately, but once it got opened for you, merging was your responsibility, not that of the code owners.
|
|
|
|
|
The Kyoto University in Japan has lost about 77TB of research data due to an error in the backup system of its Hewlett-Packard supercomputer. Ouch
|
|
|
|
|
|
Those are all a different sort of data lost. The university fubared backups and no longer have copies of the data at all. 4 of the stories you linked to were either hacks that resulted in data being stolen, or cases where a copy was made and list. And unless there's more to the story than in the article you linked, the fifth one (govt sending an HDD with personnel records to a data recovery company) might be the type of error U Kyoto made US (if it was the only copy), or a nothing burger written by someone clueless: Recovering an HDD is expensive enough that you only do it if you've got high value data on it, so the companies involved know how yo keep their customers data safe.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
|
C64 OS has one goal. Make a Commodore 64 feel fast and useful in today’s modern world. Just in case you got one of those spiffy new C64s over the holidays
Why yes, it is a slow news week, why do you ask?
|
|
|
|
|
If schools forced students to develop on vintage platforms (maybe not as old as this, but you get the idea), maybe developers wouldn't fritter away CPU time and disk space and build websites that pull in tons of frivolous things.
|
|
|
|
|
The PC hardware company is in the process of recalling its fiery motherboards. "Me mind on fire, me soul on fire"
Just in case someone here has one
"The boards are defective because a single capacitor was installed backward" <- Let he who has not sinned cast the first stone
|
|
|
|
|
It's not the hero we wanted or needed
|
|
|
|
|
Kent Sharkey wrote: "The boards are defective because a single capacitor was installed backward" Actually based on what I am reading, the polarity indicator code was painted backwards by the semiconductor fabrication plant. Which explains how the boards passed camera based and x-ray quality inspection. Same net result, but deflects some of the blame away from Asus.
I'm not even sure how you would detect this. Should have been caught by the semiconductor fab.
Best Wishes,
-David Delaune
|
|
|
|
|
Randor wrote: I'm not even sure how you would detect this. With magic. Very useful, magic is. I wish mastery came easy.
|
|
|
|
|
Any sufficiently advanced technology is indistinguishable from magic. -Arthur C. Clarke
|
|
|
|
|
Randor wrote: I'm not even sure how you would detect this. A looong time ago, pre SMT. We had an issue with reversed tantalum capacitors. Fortunately, the device in question had a pretty consistent quiescent current when populated properly, and when put in backwards would draw measurably more current, though not necessarily immediately. A fun little addition to the test fixture. Everyone loved that they had to wait 30 to 40 seconds more before the testing would begin so we could detect the extra current draw. But hey, it worked pretty well.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Those tants when installed backward would also tend to explode in a small fireball, usually shooting over your shoulder.
When I worked at a computer manufacturer there was a period of time when we would see at least one board a week, mostly video cards, that would go bang.
The biggest problem with tantalums is that when they failed they always failed short and again, BOOM!
Kelly Herald
Software Developer
|
|
|
|