|
don't know where this comes, but ...
1969:
-what're you doing with that 2KB of RAM?
-sending people to the moon
2017:
-what're you doing with that 1.5GB of RAM?
-running Slack
I'd rather be phishing!
|
|
|
|
|
Today we released a prototype of a C# feature called “nullable reference types“, which is intended to help you find and fix most of your null-related bugs before they blow up at runtime. string? int? Why?
Mental note: need a macro for
if({foo} != null){}
|
|
|
|
|
Oh goody. More warnings to turn off.
(Actually, I treat warnings as errors, but some of these warnings seem a bit over the top, particularly if the inputs to the method have been validated beforehand.)
|
|
|
|
|
ReSharper introduced the [NotNull] and [CanBeNull] attributes, and will issue warnings if you are about to run into a NullReference. They were faster.
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
|
|
|
|
|
The blockchain hype is real, and it’s become the talk of C-suites around the world. Quarterly reports and conference calls that mention “blockchain” are running at an all-time high this earnings season. And guess who will get to implement it?
|
|
|
|
|
Bill SerGio!
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: Bill SerGio! He who shall not be named!
FTFY
System.ItDidntWorkException: Something didn't work as expected.
C# - How to debug code[ ^].
Seriously, go read these articles.
Dave Kreskowiak
|
|
|
|
|
Jeremy Falcon
|
|
|
|
|
Blockchain; yet another solution in search of a problem. And which WILL fail spectacularly.
|
|
|
|
|
Hmmm,
Joe Woodbury wrote: Blockchain; yet another solution in search of a problem. And which WILL fail spectacularly.
I disagree. There are other 'information protection' benefits to blockchain technology. Let me give some examples:
1.) If a bad guy could get into the codeproject SQL database they could edit your old posts and make you look like a complete idiot back in 2004. With blockchain based storage this would be much more difficult.
2.) If a bad guy could get into the 'Internet Archive[^]' they could rewrite historical context for dozens of websites. A hundred years from now those changes might not be detected and become a future falsified fact.
3.) Corporations (such as Equifax?) that store information in a flat or relational database could potentally have tens of thousands of undetected/untracable database edits. Blockchain information storage makes it much harder to perform such an attack.
Development of information storage utilizing blockchain technologies will harden information temporally. I can assure you that this will become increasingly important over the next few decades. Nation states are already utilizing sock puppets and internet activists to influence international politics. The ability to edit the tweets and posts of real people would be a force-multiplier and some industries (such as the financial sector) need to consider implementing protections against such potential attacks.
Best Wishes,
-David Delaune
modified 20-Nov-17 11:50am.
|
|
|
|
|
Your post reminds me of the old adage; "When your only tool is a hammer, every thing is a nail."
The problems you list could be solved with easier, faster methods or make no sense. (A hundred years from now ALL encryption today will have long been broken as will have ALL current blockchains.)
|
|
|
|
|
Hi,
Joe Woodbury wrote: A hundred years from now ALL encryption today will have long been broken as will have ALL current blockchains
Keep in mind that blockchains do not need to be financially related. It has many other real world applications for protecting information outside of digital currency.
For distributed blockchain databases it actually doesn't really matter if the algorithm is weak. With most implementations of blockchain-based data storage each new entry contains information derived from all previous records/transactions. So if you have millions of records and attempt to change 1 entry... you would need to change every data record created after your target.
So using the examples I gave in my previous post.. you would need to change each and every SQL record since 2004 to edit a single 'Joe Woodbury' codeproject post from long ago... if we were using blockchain based storage here on the codeproject.
Of course nobody really cares if someone edits your old codeproject posts... but what about financial records? I can think of many other examples where data should have a high level of integrity.
Best Wishes,
-David Delaune
|
|
|
|
|
Sounds like a rebase in GIT.
If there is something computers are good at, it is automation.
|
|
|
|
|
Randor wrote: you would need to change each and every SQL record since 2004 to edit a single 'Joe Woodbury' codeproject post from long ago... if we were using blockchain based storage here on the codeproject.
Which is easy right now, let alone ten years from now. Just because something is time consuming, doesn't mean it has integrity.
Another problem is storage. Tracking all that information eventually uses up more storage than is available.
Plus, is storing extensive history really that necessary? Even with a lot of financial data, what matters is rolling window of past data. Outside that window, the data may be interesting, but isn't otherwise required.
|
|
|
|
|
This article describes 1) several techniques that can improve your pair programming experience, 2) strategies on what to do when things get frustrating or go wrong, and 3) concludes with success stories of converting difficult pair-programming relationships into successful pair-programming relationships. Always say 'please' and 'thank you' when telling your partner that their code sucks
|
|
|
|
|
Pair programming requires hiring twice as many bad developers.
|
|
|
|
|
I prefer std::tuple programming.
I'd rather be phishing!
|
|
|
|
|
While coding cutting-edge tech in Visual Studio is cool, it's not enough in today's environment of communication, collaboration, agile methodologies, DevOps and so on, said experts in a panel discussion at the Live! 360 conference in Orlando. It also involves compiling!
|
|
|
|
|
Kent Sharkey wrote: It also involves compiling!
Followed by bugs, blaming, CYA, and for those who do CYA best, promotion to management.
Though, that's so 20th century. Here's the 21st century version:
Followed by product delivery, followed by management still not happy and wants to use some new fangled technology, followed by senior developers raising objections, followed by management hiring hotshot young kids, followed by senior developers leaving to start their own contracting business, followed by product delivery (by the young kids) that misses schedules, has cost overruns, and is delivered with bugs, followed by management still not happy.
It's a brave and complicated new world!
|
|
|
|
|
"heads-down coding is a commodity"; only if you're talking about sh*t code. Quality code is a vanishing thing.
|
|
|
|
|
A team of researchers with the University of Southern California and the Wake Forest School of Medicine has conducted experiments involving implanting electrodes into the brains of human volunteers to see if doing so might improve memory recall. Will this help me to remember not to get wires shoved into my brain?
It does make me wonder if it would be possible using non-wire means though. Magnets or summut.
|
|
|
|
|
Cool. One of the people involved in this project is an acquaintance of mine.
I knew he was working on this and had been expecting results 'soon' earlier in the year; but I hadn't heard he'd published yet.
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
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
The first was to use the implant to listen for and record electrical activity in the brain while the volunteers engaged in memory exercises. The second part involved mimicking the signals that had been recorded in the first part
So, I immediately see several new applications:
1) Even if you have forgotten your password, your brain can now be stimulated to remember it.
2) Authentication by brain electrical pattern
3) "Dial a memory" - how does this work in Python? What are all those obscure docker command line arguments? What's my mistress' name again?
And of course the inevitable negative applications:
1) Upon entering your place of work, all memories unrelated to work will be suppressed.
|
|
|
|
|
In a keynote at the SecTor security conference, Bruce Schneier makes a case for more regulatory oversight for software and the Internet of Things Or: 'A well-regulated thing being necessary to the security of a internet-connected refrigerator'
|
|
|
|
|
The new study from the Brookings Institution used government data on work tasks to track how use of digital tools changed in a wide range of occupations between 2002 and 2016. Because even the robots don't want to mess with those macros?
|
|
|
|