|
Pretty sure that's December 14th, 2004. Yahoo died a long time ago.
Social Media - A platform that makes it easier for the crazies to find each other.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
The side-effect of being innovative is that some rather strange and unphysical ideas sometimes escape from NASA. This probably explains the Helical Drive. "In this house we obey the laws of thermodynamics!"
|
|
|
|
|
Newton, Maxwell, Einstein, Feynman, etc. - all dead, white, males, out to prevent NASA reaching for the stars. The necromancy, race, and feminist conspiracy theorists must be having a field day!
</irony>
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I spent my schooldays ignoring physics and can confirm that it did not leave me with near-infinite specific thrust.
I'm a small sample, though, so who knows what's (im)possible?
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
A new Windows SDK will not be issued in conjunction with this version of Windows, since this release doesn’t introduce new APIs. That means there’s no need to target Windows 10, version 1909 or modify your project files. Grief
Is there ever another answer?
OK, in this case it sounds surprisingly limited. It hardly even sounds like a Service Pack level of discomfort.
|
|
|
|
|
They should call it "Vienna" - after all, it means nothing to me[^].
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Audio .WAV files are the latest hiding place for obfuscated malicious code; a campaign has been spotted in which malicious content was secretly woven throughout the file’s audio data. "Turn me on, dead man"
Or the slightly more obscure: "The ultimate sound. And a message from Satan if you turn it around"
|
|
|
|
|
Microsoft's Desktop Analytics is designed to help business users check their app-compatibility levels and mitigate issues involving the latest Windows 10 feature updates. Find out if your apps are compatible with Win10, before the apps find out for you
|
|
|
|
|
OAM is a specification for describing applications so that the application description is separated from the details of how the application is deployed onto and managed by the infrastructure. Because we always need one more standard
And yes, there is an xkcd for that[^].
|
|
|
|
|
> OAM is a specification for describing applications so that the application description is separated from the details of how the application is deployed onto and managed by the infrastructure.
Wow. So it's a description for describing descriptions that have no information on deploying and managing the application.
Is there a YouTube video I can watch instead?
|
|
|
|
|
Cybercriminals have multiple markets to get illicit goods and prices on these underground forums are likely driven by supply and demand, just like in the legal economy. So, I'm not worthless?
|
|
|
|
|
Kent Sharkey wrote: I'm not worthless? Don't get confused... you are worth the same... it is your data what has value for them
But for what is worth... you are very valuable for us. Life would be a bit more boring without your news and comments
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Not totally worthless.
You contain a few liters of water, a few kilograms of common organics, and a few kilograms of even more common inorganics. I'd set your value at $4.99 (Canadian dollars, that is).
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
My credit is so bad that I get sent a bill when someone steals my identity
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
|
|
|
|
|
Gilbert Levin, a NASA engineer who worked on the Viking missions, says he’s “convinced we found evidence of life of Mars in the 1970s.” "Oh man, wonder if he'll ever know, he's in the best selling show"
|
|
|
|
|
Note that extraordinary claims require extraordinary proof.
The Viking landers did find signs of life, but the results were ambiguous. Of the four separate experiments designed to detect life or disprove its presence, one (Labeled Release, or LR) was a strong positive, one (Gas Chromatography/Mass Spectrometer) was a strong negative.
In 1980-81, I was a lab assistant on a NASA-sponsored project that tried to see if the LR results could be produced in other ways. To summarize and simplify, we discovered that finely-ground clay, with no organic matter whatsoever, could cause a similar release of CO2. Given that Mars has regular dust storms that would create such finely-ground particles, this introduced enough "reasonable doubt" that they could not say that life had been discovered.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Daniel Pfeffer wrote: The Viking landers did find signs of life, but the results were ambiguous. Well they did first visit the north of England...
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Mars was not called the red planet because of Eric the Red.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Novel algorithms are secure like blockchains, but simpler, faster, and more energy-efficient Is it just a linked list?
|
|
|
|
|
I thought Bitcoin Mining was going to be the new heating for the house of the future...
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
“BriansClub,” one of the largest underground stores for buying stolen credit card data, has itself been hacked. "There's no honor among thieves."
Seems a pretty big, "good news/bad news" situation, but I guess more good news?
|
|
|
|
|
Finding #3: Developers spend more time maintaining, testing and securing existing code than they do writing or improving code. "You need not wonder why there's no time left for you"
|
|
|
|
|
Thanks God they didn't consider CP in that list...
we are safe (for now )
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Writing new code - most of the time, we can't write new code because management can't "quantify a business need", unless and until they realize that the current code stack is a steaming pile of crap.
Improving existing code - 95% of the time, optimization results in errors because the improvement didn't account for subtle (and cumultaive) side-effects. Side effects occur because they architecture isn't designed/implemented properly (concerns that were separated have reconciled and are living like hippies in a commune, intermixing and interbreeding to produce the hell spawn that is your existing code base).
Fixing bugs (maintenance) - any semi-significant change to an app that deviates from the original intent/design is guaranteed to break something. This is a direct side effect of "writing new code" or "improving existing code.
As the code quality degrades, the time spent in meetings increases. When a project first starts, you may have a weekly 15 minute status meeting. Once it's deployed, you have 1-2 hour meetings every day, discussing the problems (because testing was not thorough enough) or your "code improvements" went sideways on you.
Security issues arise because some assh*le in some 3rd world shith*le has discovered an obscure exploit that makes the security nazis go into a frenzy of "omg! are we doing this? omg!". The result is that someone higher up decides you need to take "proactive steps" to prevent "security issues", and plunks down a crapload of cash for apps like Fortify. Using Fortify takes time away from devs because they have to write memos and attend meetings defending their code and explaining why the Fortify scan is full of sh|t.
After more than 40 years as a dev, all this crap is pretty obvious to me, and I don't need some snot-nosed kid to conduct a pointless survey to illustrate why devs don't spend enough time writing code. The truth is that they're piling on non-dev tasks and concerns (DevOps), and we don't have the f*ckin time to write code. And don't get me started on employee retention.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 16-Oct-19 8:16am.
|
|
|
|
|
You do know that there's a "Rant" button, right?
It's difficult to rewrite software because the cost of doing so has to be recovered over the product's remaining lifetime. Its lifetime might be extended by rewriting it, but it's difficult to prove this to management. If the existing code isn't too hopeless, it may be possible to improve it through refactoring rather than totally rewriting it.
Customers also want new functionality, so the product will require two teams: the first one to support the existing software and add the critical features that customers demand, and the second one to do the rewrite. The second team will also have to catch up to what the first team manages to add.
The team rewriting the software may also have no adequate product specification from which to work. They will then inadvertently change some of the product's behavior, resulting in customer complaints when it eventually rolls out.
How much will the rewrite improve quality and time to market? The organization already created one mess, so what will prevent the rewrite from becoming a second one? The culture and process may need to change, and there must be a visionary (or a few of them) with a clear idea of what the design should be, with the ability to keep it on track.
All of these issues make rewrites challenging, which is why so many of them fail. Before embarking on a rewrite, a team needs to have a good idea as to how it will address these issues.
|
|
|
|