|
New Zealand professor asked to present his work at US event on nuclear physics despite it containing gibberish all through the copy I guess it makes about as much sense as many other physics papers these days
|
|
|
|
|
|
Bartneck said that given the quality of the review process and the steep registration fee, he was “reasonably certain that this is a money-making conference with little to no commitment to science.
And a Microsoft Developer Conference is different how?
(Oooh, that was low, I admit it!)
Marc
|
|
|
|
|
Marc Clifton wrote: And a Microsoft Developer Conference is different how?
Come on! This is the best payed advertisement can ever be! You advertise and the audience pay!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Microsoft has partnered with Acclaim to introduce Microsoft badges for Microsoft Certified Professionals (MCPs) to achieve certain certifications or pass select exams. Badges? We got your stickin' badges.
|
|
|
|
|
Kent Sharkey wrote: stickin'
I believe that the original quote was "Badges? We don't need no stinkin' badges"
Stickin' just sounds... dirty... for some reason.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Joys of entering that one on my iPad. Got auto"corrected " 
TTFN - Kent
|
|
|
|
|
I usually call that 'feature' autoincorrect (or autocowreck or Auto Condom Wrecker, as my iPad once decided to use  )
I love the site Damn You Auto Correct! - Funny iPhone Fails and Autocorrect Horror Stories[^]
Lots of fail there.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
And how exactly you stick a digital badge to your forehead?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: And how exactly you stick a digital badge to your forehead?
With digital tape? 
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
People keep claiming that is because of bad choices of language, but it’s mostly not and static typing will not even slightly help fix it. dim Discuss as new Flamebait()
|
|
|
|
|
davidMacIver = HesGotSomeGoodPoints()
davidMacIver = ButHesAlsoWrong()
Make it more expensive to write broken software - write in a non-static typed language
Make it cheaper to write correct software - write in a static typed language
But because these bugs [those that happen in production] are relatively minor
Now that's where I totally disagree. If a true static typed language had been used, or had been used properly (ie, semantically, which is the next level of strong typing), this case in point[^]
due to ground-based computer software which produced output in non-SI units of pound-seconds (lbf s) instead of the SI units of newton-seconds (N s) specified in the contract between NASA and Lockheed.
would not have cost the taxpayers $327.6 million
Dealing with type errors in a non-static language is not cheaper. I spend time writing unit tests and verifying the runtime by hand to ensure type correctness that I do NOT spend with static typed languages. Running an app only to discover I'm using a duck-typed variable before I've assigned something to it is a time waster. The benefits of static typing far outweight the benefits of non-static typed languages, and I'm sorry David, that's not opinion, but measurable fact.
Can duck-typed languages save time? Sure! I can replace a class instance that interfaces with hardware with a class instance that mocks the hardware as simply as the code above. I can add fields to a class outside of the class simply by making an assignment.
All of which are cheats and laziness, break the "code as documentation" fallback. In other words, duck-typed languages are like pr0n instead of the real thing.
[edit]
Most existing static type systems also come with a build time cost that makes testing in general more expensive.
 And the unit tests that duck-typed languages require often (in my experience with a small Ruby on Rails web app) take longer to run than compiling much more complex web sites. [/edit]
Marc
modified 23-Oct-16 20:40pm.
|
|
|
|
|
The fact that we have === says it all.
cheers
Chris Maunder
|
|
|
|
|
The funny operator of js. 
|
|
|
|
|
Though David is right when he says that "Static typing will not save us from broken software", I mostly disagree with him. Static typing must be done correctly. Many developers don't understand that - see also my post to the Weird and Wonderful: I don't see sharp anymore, ...[^]. And the next level of typing are semantic types, as Marc suggested (and also Simonyi when he introduced Hungarian notation). We need developers who actually understand what they do.
|
|
|
|
|
Mystery company owns a patent created by an IP lawyer and a serial litigant. If only they would turn to stone in the daylight
|
|
|
|
|
It seems that there are countless patents approved by person do not understand a single world of it...
It is sad that there are people who abuse it, but we can't set it right without fixing the patent system...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Do you work in software? Do you have more than a decade of experience? You do? I’m sorry to hear that. "It is the height of madness to learn what you will later have to unlearn."
|
|
|
|
|
That means there’s a strong possibility that much of what you know is already obsolete.
Much of what I have learned in the technical realm is certainly obsolete. I haven't coded in 6502, Z80, 8086, Cobol, Fortran, Pascal, C, or C++ in ages.
But much of what I've learned about writing documentation, debugging, creating flexible architectures, smacking junior devs around, wishing I could smack managers, realizing I love working remotely, making accurate time estimates, designing good UI's, and getting skilled at teaching others, those are things that never become obsolete. Some sadly never.
Marc
|
|
|
|
|
What he said.
The syntax is the easiest part of coding.
cheers
Chris Maunder
|
|
|
|
|
Priority management, clean code, design best practices, problems solved (aka a base of problems for which one can find similarities)... that is experience and it is worth decades of formal education.
Als it depends on the field, many programmers today simply patch things together by using big clunky frameworks and have no real problem to solve: when was the last time you developed an algorithm, instead of pulling a library with an algorithm and integrating it into some kind of monster?
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
den2k88 wrote: when was the last time you developed an algorithm,
in my previous job, every new project (automation)... now... I write a lot of emails  But I see my family every afternoon ![Jig | [Dance]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/jig.gif)
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.
|
|
|
|
|
Something to be said about jumping onto any new bandwagon that comes across - like React mentioned in the article, or LightSwitch, or XAML or ...
Some things though never change - the guy down the hall writing bash scripts have been doing it for 20 years. The Oracle or SQL server DBA job didn't change much in the last 20 years either. The C/C++ I walked away from 15 years ago, I had to get back to with Mobile Games.
So “Stay hungry, stay foolish.” - there is just not enough time in the day, need to use some discretion and prospective.
|
|
|
|
|
To Jon Evans - You are utterly wrong...
Everything! I have learned is important (even I didn't used it for years, like 6502 Assembly or COBOL) as it is the solid base of everything new I will learn tomorrow...
This is the base that enables to me to write PHP for production on the very same day I saw it ever first!
Let see how would you write articles your brain wiped clean (on a second thought it probably will not change nothing - you write BS even with your brain intact)...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I thought my eyesight was beginning to go. It turns out, I’m suffering from design. So maybe you can't read it, but it's responsive!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
