|
Maybe because I am too used to opion pieces now (via twit.tv podcasts), that I was expecting to see a comment mentioning Supermicro.
|
|
|
|
|
Software called TextFooler can trick natural-language processing (NLP) systems into misunderstanding text just by replacing certain words in a sentence with synonyms. Beware the Thesaurus, my son. The mandibles that masticate, the talons that appropriate.
|
|
|
|
|
Well, it's good to see that MIT is spending so much time on such worthwhile projects, which will be of immense benefit to humanity. I'll get to work on the biopic.
Genius MIT student 1
Hey, why don't we make a prog that screws with alexa?
Genius MIT student 2
Beer! More Beer! [pukes]
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Now we are going to have man-in-the-middle situations, and my actual words are going to be replaced with the list of DHS monitored words[^], and the CIA is then going to come hunt me down.
Or vice versa... I'm going to have a vocal-reprocessor which will capture my voice and thesaurus-ize the vocabulary into non infractionary notes and then play it into Alexas mic...
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
|
|
|
|
|
A group of experts wants to study the brain waves and eye movements of people playing a video game in order to build an advanced AI that could coordinate the actions of military robots. "Greetings, Starfighter. You have been recruited by the Star League to defend the Frontier against Xur and the Ko-dan Armada."
|
|
|
|
|
Kent Sharkey wrote: "Greetings, Starfighter. You have been recruited by the Star League to defend the Frontier against Xur and the Ko-dan Armada."
+5 for the quote 
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.
|
|
|
|
|
Chowdhury told UBNow: We don’t want the AI system just to mimic human behavior
... We want it to develop tactics that anticipate human behavior, the better to kill them with.Chowdhury told UBNow: we want it to form a deeper understanding of what motivates human actions
... the better to kill them with.Chowdhury told UBNow: That’s what will lead to more advanced AI
... That we can use to murder everyone who doesn't worship us.
First we'll come for the socialists.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
To make it short. The crucial difference between evolution and revolution is if the change is gradual (evolution) or disruptive (revolution). From the primordial soup, they arise (assuming they do make the cut this time)
|
|
|
|
|
In our second look at the HackerRank findings, we focus on variations in pay and developers satisfaction with their pay. "However much I make it out, it's never enough"
|
|
|
|
|
Windows Server 2008 servers will no longer boot if prerequisites aren't installed before applying the out-of-band KB4539602 update released by Microsoft on February 7 to patch a wallpaper bug. Windows 7 won't stop, Windows Server 2008 won't start, and Windows 10 is juuuuuuust right
Because of the wallpaper fix.
A wallpaper fix.
Wall.
Paper.
fix.
|
|
|
|
|
I shouldn't be surprised if it's because of the old "live wallpaper" thing, which was part of IE.
So it's edge that killed weven and server 2008.
... And any last remaining vestige of interest in using ms web browsers.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: I shouldn't be surprised if it's because of the old "live wallpaper" thing, which was part of IE.
Anyone who integrates nice-to-have features such as wallpaper into the security mechanisms of the O/S should be hanged, drawn, and quartered.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
The mythical book, Mythical man month quotes that no matter the programming language chosen, a professional developer will write on average 10 lines of code (LoC) day. Have you written your 10 lines today?
|
|
|
|
|
...removed several hundred, like all true professional anti-developers.
|
|
|
|
|
Kent Sharkey wrote: Have you written your 10 lines today?
Wrote them, deleted them, rewrote them, commented it out, and wrote something different
|
|
|
|
|
One source claimed that the programmers writing microcode for the VAX-780 had an average productivity of one microinstruction a day, 250 µinstructions/year. (Sorry; I don't remember the source.)
In the old days, we had something called "documentation", descriptions of hardware and software systems and how to use them, all printed on paper. (Oldboys will probably remember the phenomenon.) I was working for a few years as a Technical Writer, when we came across a claim that a Technical Writer procduces one page of documentation a day. We questioned it, but surveyed the productivity of our own group. It turned out that we were almost exactly on one page per man day. We dug down in the publication history, and that figure hadn't changed for years.
Regarding code: In my student days, the productivity, in source code lines, about tripled when C took over for Fortran and Pascal. In Pascal, the coding style was like
IF TotalSum > 1000 THEN DiscountPercentage := 10; When C tok over, the new coding style rules required you to write it like
if (TotalSum > 1000)
{
DiscountPercentage = 10;
}But also, since "C formatted code" has so many almost-blank lines, brace-only lines and indentations (e.g. for single-statement "if" clauses) etc., to make a e.g. a loop body more easily identifiable, it became customary to add blank lines before and after the loop. In the Pascal days, a loop body was recognized by the indentation of it. With C, this was replaced by a blank line before the loop control, a semi-indented brace after the loop control, full indentation of the loop body, a semi-indented brace at the end of the loop, and a blank line after the loop.
Percentage of comment lines also became a sign of a valuable programmer. The various open-source blurbs at the top of every single file increased this measure significantly, often adding 50+ lines of a copy/paste comment block to a file containing a ten line function. Or three lines of header declarations. The old style of adding an end-of-line comment, not contributing to the line count, was replaced by a blank line, a start comment marker on a separate line, the half-line comment on the third line, the end comment marker on the fourth, and finally a fifth blank line to make sure that the comment would stand out from the code ...
I think that # source code statements would be a much better measure of productivity than LoC. I have seen too many artificial ways to pull up the LoC count to impressive levels. There are reasons why you today no longer just count source file line feeds, but must split into groups of comment lines, blank lines, and code lines to make it at least semi-believeable. Still, lots of developers want to count brace-only lines as "code lines".
We worked a lot with hardcopy code in the old days. In my first active years, I was coding in a Pascal-like language, with "Pascal-class" formatting, working with a few guys who had picked up the C style. So I made all my code listings double-spaced, to look more like theirs. It was never remarked upon; it was treated as if that was the way I had formatted it, nice and spacious. When I returned to the editor, on my 25 lines by 80 characters screen, I could see 25 code lines at a glance, rather than 12 code lines and 13 blanklines...
I still prefer to be able to see an entire function / method / subroutine / (whatever....) on my screen without having to page up and down, even if that means that my LoC productivity comes out as very poor. When I work in Visual Studio, I can of course adjust the formatting parameters, delete and reinsert the closing brace before I commit, so that my appearent LoC productivity comes out at the same level as my fellow coders.
|
|
|
|
|
|
IF TotalSum > 1000 THEN
begin
DiscountPercentage := 10;
end.
if (TotalSum > 1000) DiscountPercentage = 10; 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Sure, we could have written it in that way, both Pascal and C variants. We did not. The 4-line formatting was never being pushed before C arrived, but when C took over, it was made standard. In lots of SW development environments of today, you are frowned upon if you write a C if-statement on a single line.
Then there are those middle-between ones who allow the space saving
if (TotalSum > 1000)
DiscountPercentage = 10; i.e. indentation of something that is not syntactically a block (i.e. compound statement), which I think is highly inconsistent. Some make it even worse by allowing this newline/indentation style for single-statment if statement only, but not loops.
C syntax sometimes require even single statements to be braced into compound statements, such as a handler. I don't know of any C programmer that condones code following a open brace on the same line, so even the simplest catch requires four lines. So it contributes to the LoC based productivity measure.
|
|
|
|
|
Good explanation, tx 
I'm on of those middle-between's, even for loops; it saves space, and as such I can convey more information using less lines, as it helps when reading the code in printed form (as in, paper).
Member 7989122 wrote: In lots of SW development environments of today, you are frowned upon if you write a C if-statement on a single line.
Yes, since the best practice says that even single statements following the if should be in a block; ohterwise someone who hastily edits might do something stupid.
Which is a stupid reason in the first place.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
I believe it is 10 "bug-free"* lines per day, which have undergone unit, integration and system testing, and all bugs found have been fixed. This would actually mean more lines of code written per day.
* Free of Fatal and Major bugs.
|
|
|
|
|
DOJ said the hackers stole data on Americans and Equifax's intellectual property. "It is said that if you know your enemies and know yourself, you will not be imperiled in a hundred battles"
|
|
|
|
|
OK, are there any security experts in here?
I've done a bit, and I believe I can say in all correctness that there is absolutely no f***ing way that the DoJ could have tracked the hack back to four individuals working on government-owned machines in a foreign state -- they can't even identify hackers on US soil, FFS!
It's much more likely a case of "Hey, Kowalski, pick four Chinese guys outta that hat!"
When the "Department of Justice" of your country starts lying to you so blatantly and obviously, you know you're in the sh1t.
Will you chaps in the US give my regards to the doorman of room 101, given that a fair proportion of you are likely to be visiting him?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I agree. The alternative solution is that the world's best security experts working in a government organisation where secrecy is paramount to protect national interests and not reveal to their enemies how things are done, who have actual access to the specifics of the hack, don't want to jeopardise their national security by giving out all the specific details....but that's just preposterous.
|
|
|
|
|
I think it's safe to say that the degree of hacking required to get into the Chinese military to make such "discoveries" is well outside the range of what is possible. They have a hundred people defending their networks for each person trying to attack them.
If it were the other way around, it would, of course, only take the Chinese six days.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
