and I never had a student that could not be inspired to keep learning and brought to "black belt level", regardless of his talent. "Black belt" in quotes as many westerners have a weird idea what a "black belt" is.
Well, a lot of people who research these things recently have been saying things like, "innate talent.....the thing that separates those from the rest, is extreme motivation to learn." Some kids have it , and some kids don't.
Although you did pick up on the important word "obvious," you missed another important word: "should." Notice that it isn't "must." It's more of a goal than a hard-and-fast rule.
Dude, you're the guy who can't read your own code. You're not one to be philosophizing about what a programming language "should" be.
Even before I found Python, I became disenchanted with Perl for the fact that I found that I had to a comment on nearly every line of my own code to be able to read it later
Do you realize this makes you look like a sucky programmer, and invalidates your expertise in the rest of the program? Seriously, if you had to comment every line to understand your own code, the problem was you. You should have looked at your code and said, "What was wrong with me?"
Yes, and always causing bugs. "If you add a thread, you add a bug."
Anyway, the generics had cut down on a lot of the horrendous casting mush that used to go on to just use a container. I think that will have cut down a lot.
Here's an interesting one to me.......logically, what you say makes sense, that casting is a potential source of bugs. In practice, I've never accidentally cast something to the wrong thing (and had it go to production). Is that a type of bug you've seen from time to time? I'm genuinely curious.
Well, I don't know whether it's inborn, although if sometimes seems this way. But without taking a position on whether programmers are born or made
This says no. In short, if you claim it is inborn, you need to be able to make a test that distinguishes between those who "have it" and those who "don't have it." Alan Kay has good things to say, too as usual.
instructors try to sell students on how easy it is to do things so they show students the simplest way of producing a particular result -- not the way that a proficient programmer should produce that result.
That's kind of true.....it took me a couple years as a programmer to figure out how to write decent C, and several more to figure out how to make things easy to write in C. Sometimes I wish it were easier for people to learn.
simply because people have had access to much more modern versions of the languages and compilers than the "average" java and C++ code out there that's been long lived.
Maybe. I expect to see more bugs out of the modern Java stuff, when people have threads and enclosures with mutable variables.
Actually, maybe the reason is because in Android code you don't see many threads (the android app has a 'threading' model by default), whereas in Java server code you tend to see many threads? The article doesn't really clarify.......in both Java and Android the biggest cause of bugs is listed as "Code Quality."
In the C++ world, the #2 cause of bugs is buffer overflows, and yeah, modern C++ should mostly fix that. The #1 cause of bugs in C++ is error handling, which is understandable since every project in C++ has its own method for handling errors.........
But how many of these critical flaws are SQL injection flaws?
If only there were an article you could read that had this information. Then you could read it and avoid making ignorant questions.
As the article points out, code injection and XSS faults are much more common in PHP than SQL injection flaws.
Of course, it doesn't mean that PHP is the worst language......for example, it could be that the worst programmers most often use PHP. More research is needed.
Something like 75%-80% of the web runs on php (Wordpress, for example.) Naturally if you examine a large number of sites, most of which run on php, you're going to see more security problems coming from sites that run on php.
Seriously man? You don't think the researchers thought of that? If you had even clicked on the article, you would know that they did.
In any case, here is the full list:
Classic ASP - with 1,686 flaws/MB (1,112 critical flaws/MB)
ColdFusion - with 262 flaws/MB (227 critical flaws/MB)
PHP - with 184 flaws/MB (47 critical flaws/MB)
Java - with 51 flaws/MB (5.2 critical flaws/MB)
.NET - with 32 flaws/MB (9.7 critical flaws/MB)
C++ - with 26 flaws/MB (8.8 critical flaws/MB)
iOS - with 23 flaws/MB (0.9 critical flaws/MB)
Android - with 11 flaws/MB (0.4 critical flaws/MB)
JavaScript - with 8 flaws/MB (0.09 critical flaws/MB)
The models [tomwoods.com] where so-called insurance has been abandoned are where the costs are lower and the care level is higher.
If you're going to link to a long podcast without a transcript, you ought to at least summarize the point you are trying to make so people don't have to suffer through it. Are you promoting a single-payer system there, or do you have something different in mind?
Start a business that sells your idea. You can sell schematics, or something. Once you start having decent sales, contacting large companies will be easier. If you make enough, you won't have to contact them, they will contact you.
The reality is Apple and Microsoft are not likely to be interested in paying you if it doesn't increase their own profits. And lets be honest, the way most people view electrical-related fires is "not at all." You're not going to revolutionize it. So in your case, you may have a business plan to lobby the California government to pass a law that all devices include your safety feature.
When I use postgresql, every once in a while I learn about some feature that is kind of nice, and might make my life easier (though sometimes at the cost of compatibility).
When I use MySQL, every once in a while, I learn about a feature (*bug*) that is kind of annoying, and definitely makes things more complicated (and sometimes at the cost of compatibility).
There is no question in my mind which to use. If a hosting platform only supports MySQL, I won't use that hosting platform.
And Watson is totally amazing. People who dismiss it in hindsight do not realize how impossible such a system seemed in the 1980s.
Impossible? People envisioned it long before and started building it in the 80s. The problem was how to get the data into the system in a way that was searchable? IBM solved that, thanks to all of us uploading things onto the internet.
In the 80s, it was thought that the AI problem would be simple to solve if you had a large enough database of human knowledge. The cyc project showed that such a database is necessary, but not sufficient.
Slashdot Mirror
Assembly code? Maybe not (although modern assemblers are a lot easier), but seriously, if Perl code is hard to read, it's the author's fault.
Are people still dumb enough believe they can force anyone to abandon nuclear weapons research or that's even what was agreed to.
Why not? It's happened before. It's clear that Iran's nuclear weapon program can be stopped, the only question is at what cost.
and I never had a student that could not be inspired to keep learning and brought to "black belt level", regardless of his talent. "Black belt" in quotes as many westerners have a weird idea what a "black belt" is.
That's really great, your story is inspiring.
Does this sort of thing really get non-MS employees to contribute to the project?
Getting people to contribute is kind of like starting and running a community. It's a different skill set than writing code.
In their post, Microsoft claims that they want people to contribute, but how they run the community is what will determine if people actually do.
Well, a lot of people who research these things recently have been saying things like, "innate talent.....the thing that separates those from the rest, is extreme motivation to learn." Some kids have it , and some kids don't.
Although you did pick up on the important word "obvious," you missed another important word: "should." Notice that it isn't "must." It's more of a goal than a hard-and-fast rule.
Dude, you're the guy who can't read your own code. You're not one to be philosophizing about what a programming language "should" be.
Even before I found Python, I became disenchanted with Perl for the fact that I found that I had to a comment on nearly every line of my own code to be able to read it later
Do you realize this makes you look like a sucky programmer, and invalidates your expertise in the rest of the program? Seriously, if you had to comment every line to understand your own code, the problem was you. You should have looked at your code and said, "What was wrong with me?"
Python 3 has been a resounding success
It's fractured the community for years, and probably will continue to do so for years to come.
Yeah lol. I read that and thought, "not paying their bills, but haven't been disconnected? How do I get in on that??"
Weren't threads always there?
Yes, and always causing bugs. "If you add a thread, you add a bug."
Anyway, the generics had cut down on a lot of the horrendous casting mush that used to go on to just use a container. I think that will have cut down a lot.
Here's an interesting one to me.......logically, what you say makes sense, that casting is a potential source of bugs. In practice, I've never accidentally cast something to the wrong thing (and had it go to production). Is that a type of bug you've seen from time to time? I'm genuinely curious.
Well, I don't know whether it's inborn, although if sometimes seems this way. But without taking a position on whether programmers are born or made
This says no. In short, if you claim it is inborn, you need to be able to make a test that distinguishes between those who "have it" and those who "don't have it." Alan Kay has good things to say, too as usual.
t. However I would bet that there are certain types of projects that are mostly handled by people with formal training.
The stereotypical answers are creating a regular expression parser and a compiler. Hard to do those without a lot of CS theory.
Also knowing about Big-Oh is really helpful in a lot of areas of programming.
instructors try to sell students on how easy it is to do things so they show students the simplest way of producing a particular result -- not the way that a proficient programmer should produce that result.
That's kind of true.....it took me a couple years as a programmer to figure out how to write decent C, and several more to figure out how to make things easy to write in C. Sometimes I wish it were easier for people to learn.
simply because people have had access to much more modern versions of the languages and compilers than the "average" java and C++ code out there that's been long lived.
Maybe. I expect to see more bugs out of the modern Java stuff, when people have threads and enclosures with mutable variables.
Actually, maybe the reason is because in Android code you don't see many threads (the android app has a 'threading' model by default), whereas in Java server code you tend to see many threads? The article doesn't really clarify.......in both Java and Android the biggest cause of bugs is listed as "Code Quality."
In the C++ world, the #2 cause of bugs is buffer overflows, and yeah, modern C++ should mostly fix that. The #1 cause of bugs in C++ is error handling, which is understandable since every project in C++ has its own method for handling errors.........
ok, here's a question.......
Since Android is written in Java and C++, why (in your opinion) did Android get such a low bug count compared to Java and C++?
Yeah, I was wondering about that too. It might have something to do with the automated tests they use?
But how many of these critical flaws are SQL injection flaws?
If only there were an article you could read that had this information. Then you could read it and avoid making ignorant questions.
As the article points out, code injection and XSS faults are much more common in PHP than SQL injection flaws.
Of course, it doesn't mean that PHP is the worst language......for example, it could be that the worst programmers most often use PHP. More research is needed.
Something like 75%-80% of the web runs on php (Wordpress, for example.) Naturally if you examine a large number of sites, most of which run on php, you're going to see more security problems coming from sites that run on php.
Seriously man? You don't think the researchers thought of that? If you had even clicked on the article, you would know that they did.
.NET - with 32 flaws/MB (9.7 critical flaws/MB)
In any case, here is the full list:
Classic ASP - with 1,686 flaws/MB (1,112 critical flaws/MB)
ColdFusion - with 262 flaws/MB (227 critical flaws/MB)
PHP - with 184 flaws/MB (47 critical flaws/MB)
Java - with 51 flaws/MB (5.2 critical flaws/MB)
C++ - with 26 flaws/MB (8.8 critical flaws/MB)
iOS - with 23 flaws/MB (0.9 critical flaws/MB)
Android - with 11 flaws/MB (0.4 critical flaws/MB)
JavaScript - with 8 flaws/MB (0.09 critical flaws/MB)
The models [tomwoods.com] where so-called insurance has been abandoned are where the costs are lower and the care level is higher.
If you're going to link to a long podcast without a transcript, you ought to at least summarize the point you are trying to make so people don't have to suffer through it. Are you promoting a single-payer system there, or do you have something different in mind?
But they ran tests! That means everything must be perfect, and what doctors think is pointless! Right?
I'm not sure why everyone is hung up on the tax structure of a billionaire's charitable doings - judge him by what he does instead.
This is everything that needs to be said on the topic.
Start a business that sells your idea. You can sell schematics, or something. Once you start having decent sales, contacting large companies will be easier. If you make enough, you won't have to contact them, they will contact you.
The reality is Apple and Microsoft are not likely to be interested in paying you if it doesn't increase their own profits. And lets be honest, the way most people view electrical-related fires is "not at all." You're not going to revolutionize it. So in your case, you may have a business plan to lobby the California government to pass a law that all devices include your safety feature.
PostgreSQL supports transaction DDL statements (e.g. ALTER TABLE, CREATE TABLE). MySQL doesn't.
Even SQLite3 supports transactional DDL statements. That MySQL doesn't is a cloud of shame hanging over them.
When I use postgresql, every once in a while I learn about some feature that is kind of nice, and might make my life easier (though sometimes at the cost of compatibility).
When I use MySQL, every once in a while, I learn about a feature (*bug*) that is kind of annoying, and definitely makes things more complicated (and sometimes at the cost of compatibility).
There is no question in my mind which to use. If a hosting platform only supports MySQL, I won't use that hosting platform.
And Watson is totally amazing. People who dismiss it in hindsight do not realize how impossible such a system seemed in the 1980s.
Impossible? People envisioned it long before and started building it in the 80s. The problem was how to get the data into the system in a way that was searchable? IBM solved that, thanks to all of us uploading things onto the internet.
In the 80s, it was thought that the AI problem would be simple to solve if you had a large enough database of human knowledge. The cyc project showed that such a database is necessary, but not sufficient.