I think the second part of that definition is more relevant. Dijkstra was definitely arrogant, no matter how brilliant he was and no matter how much he contributed to CS. Or maybe you can say he was just an ass. But it certainly wasn't that "others are just miffy".
I think fellow Computer Scientist Alan Kay said it best:I don't know how many of you have ever met Dijkstra, but you probably know that arrogance in computer science is measured in nano-Dijkstras.
Which makes the Dijkstra quote on humility in TFA beautifully ironic.
I felt exactly the same way when I learned structured programming after starting with BASIC. On the other hand, I've met some programmers whose thinking was damaged by BASIC, but I suspect they would never have been good programmers regardless of their starting language.
IMHO a better choice is assembly, but BASIC does have the advantage of providing faster rewards.
Assembly's great, but you sort of have to keep re-learning it for different processors.
No, you only have to learn it once, so that you "get it." Then you really understand what is going on under the hood and know how to do unstructured programming. After that you can program in high-level languages the rest of your life but be a good programmer. I agree that it is much better than BASIC for the type of "weight training" the TFA refers to.
I think it would be bit cooler if it got more than 6 feet off the ground. TFA says "can reach 8000 ft (estimated)" but none of the picks or videos show that.
The irony of the whole situation is that the old time communist are sitting back saying 'see i told you so' with regards to how capitalism has brought about the worst in behavior there.
yeah, with old time communism you just got crappy stuff, it wasn't passed off as fake versions of the good stuff.
The dynamic range of human hearing is 120dB, the theoretical CD dynamic range is 96dB, tape and records have lower dynamic range and CDs usually are recorded with lower dynamic range too, so it shouldn't hurt your ears.
120 dB is where damage starts to occur from short term exposure, but some people may feel pain at much lower levels. 85 dB can cause damage over long term and is the OSHA limit for long term occupational exposure (with 0 dB defined as the minimum humans can hear in this case, dB is the logarithm of a ratio and the zero point can be arbitrarily defined).
But I agree that modern recordings are way over-compressed and having a wide dynamic range is good.
Maybe they should use some music whose artists aren't several hundred years dead, then perhaps the artists could have a very interesting discussion as to the use of their music...
Some quakes elevate land which would slow the spin of the earth, but some might lower it, and erosion is constantly lowering the land. After 5 billion years we are probably pretty much in a steady state as far as that goes (earthquakes push it up, and erosion tears it down). Of course other things like tidal forces between the earth and sun are having long term affects which will accumulate overtime (I believe slowing the earth's spin and moving it further from the sun).
Based only on my coursework (and not personal knowledge), it's not been covered. Nor should it have been. CS != Programming.
also BasicSecurityPrincipals != Programming. BasicSecurityPrincipals is a subset of CS. They should know enough to know these things exist and figure out how to handle them in whatever language they are encountering. CS degrees should be about high-level theory, not low-level details, but IMO anyone with a CS degree who implements that kind of vulnerability without thinking about how to avoid it doesn't deserve the piece of paper, and I'd think twice about hiring another new grad from the same school.
Can you even graduate from school with a CS degree today and not know what an SQL injection attack is and how to avoid it? Or are we talking people without degrees? (I graduated before HTTP even existed, so I don't know personally, but it seems everyone should know the basics of security for web based apps).
The GP is talking about column names passed in as variables, which they correctly stated is not doable with prepared statements. I'd use something like an enum or some other fixed set of values that the user input would have to map to, and construct the SQL from that. In any case never inline user input directly into an SQL statement.
It's laughable to equate an outright lack of security (lock-less doors) with subtle programming errors which result in security holes. It's not like a door with no locks. It's like a door with a lock which can be opened by some method that the designer of the lock did not envision. Does it mean the lock designer did a poor job? That depends on the complexity of the hack itself.
I mostly agree. My pet peeve is SQL injection attacks, because they are so frickin' easy to avoid. Any developer that leaves their code open to SQL injection attacks should be held liable (unless their employer insists they use a language that doesn't have prepared statements, in which case the company should be held liable).
You also have to know the frequency for this to work, which involves trusting either TFA or your microwave manual, which makes it much less interesting as a pure science experiment. But still delicious.
Their submarines are good enough to sneak up on US carriers, and they have demonstrated that they can shoot down satellites. Now I ask myself where the US will be with carriers on the bottom of the oceans and no satellites to coordinate communications for combined arms or provide overhead intelligence.
"shoot down satellites" is a bit of a misnomer. The satellites don't head down when shot, they break into thousands of pieces. My point being if they shot down all our military satellites the debris field would destroy all the satellites and no one would have that advantage. And the effect last for decades and centuries. Which would suck for everyone. So they are unlikely to do it under any circumstances. Similarly sinking our carriers would probably result in a full scale nuclear war, so they are unlikely to do that either.
On the other hand, they will kick our ass economically and scientifically.
I currently work for a big bank as a Java programmer and make more than I did at any other company I've worked for. I'm a contractor but still come out significantly ahead after I buy my own benefits. All my other companies were start-ups and I was a FTE, so I don't have a great data set to compare, but for what it's worth I don't think banks are cheap.
This doesn't tell us anything about how people use passwords in important situations. I use crap passwords for crap sites like rockyou.com. For any site I actually care about (banks, gmail) I use really good passwords (well, as good as they will let me use, some banks still don't allow non-alphanumeric characters). So all this study really tells us is what password people use when they don't give a crap.
Slashdot Mirror
I think the second part of that definition is more relevant. Dijkstra was definitely arrogant, no matter how brilliant he was and no matter how much he contributed to CS. Or maybe you can say he was just an ass. But it certainly wasn't that "others are just miffy".
I think fellow Computer Scientist Alan Kay said it best:I don't know how many of you have ever met Dijkstra, but you probably know that arrogance in computer science is measured in nano-Dijkstras.
Which makes the Dijkstra quote on humility in TFA beautifully ironic.
I felt exactly the same way when I learned structured programming after starting with BASIC. On the other hand, I've met some programmers whose thinking was damaged by BASIC, but I suspect they would never have been good programmers regardless of their starting language.
IMHO a better choice is assembly, but BASIC does have the advantage of providing faster rewards.
Assembly's great, but you sort of have to keep re-learning it for different processors.
No, you only have to learn it once, so that you "get it." Then you really understand what is going on under the hood and know how to do unstructured programming. After that you can program in high-level languages the rest of your life but be a good programmer. I agree that it is much better than BASIC for the type of "weight training" the TFA refers to.
I think it would be bit cooler if it got more than 6 feet off the ground.
TFA says "can reach 8000 ft (estimated)" but none of the picks or videos show that.
what if your target shaves down there?
This so needs the whatcouldpossiblygowrong tag
The bumps on my MacBook Pro are on the F & J. I don't think I've ever seen a keyboard where they weren't.
The irony of the whole situation is that the old time communist are sitting back saying 'see i told you so' with regards to how capitalism has brought about the worst in behavior there.
yeah, with old time communism you just got crappy stuff, it wasn't passed off as fake versions of the good stuff.
The dynamic range of human hearing is 120dB, the theoretical CD dynamic range is 96dB, tape and records have lower dynamic range and CDs usually are recorded with lower dynamic range too, so it shouldn't hurt your ears.
120 dB is where damage starts to occur from short term exposure, but some people may feel pain at much lower levels. 85 dB can cause damage over long term and is the OSHA limit for long term occupational exposure (with 0 dB defined as the minimum humans can hear in this case, dB is the logarithm of a ratio and the zero point can be arbitrarily defined).
But I agree that modern recordings are way over-compressed and having a wide dynamic range is good.
Maybe they should use some music whose artists aren't several hundred years dead, then perhaps the artists could have a very interesting discussion as to the use of their music...
They should be using Rick Astley.
Some quakes elevate land which would slow the spin of the earth, but some might lower it, and erosion is constantly lowering the land. After 5 billion years we are probably pretty much in a steady state as far as that goes (earthquakes push it up, and erosion tears it down). Of course other things like tidal forces between the earth and sun are having long term affects which will accumulate overtime (I believe slowing the earth's spin and moving it further from the sun).
Obilgatory TheDailyWTF
they'll give us universal healthcare ... oh, wait, nevermind.
Based only on my coursework (and not personal knowledge), it's not been covered. Nor should it have been. CS != Programming.
also BasicSecurityPrincipals != Programming.
BasicSecurityPrincipals is a subset of CS.
They should know enough to know these things exist
and figure out how to handle them in whatever language
they are encountering. CS degrees should be about
high-level theory, not low-level details, but IMO
anyone with a CS degree who implements that kind of
vulnerability without thinking about how to avoid it
doesn't deserve the piece of paper, and I'd think twice
about hiring another new grad from the same school.
Can you even graduate from school with a CS degree today and not know what an SQL injection attack is and how to avoid it? Or are we talking people without degrees? (I graduated before HTTP even existed, so I don't know personally, but it seems everyone should know the basics of security for web based apps).
The GP is talking about column names passed in as variables, which they correctly stated is not doable with prepared statements. I'd use something like an enum or some other fixed set of values that the user input would have to map to, and construct the SQL from that. In any case never inline user input directly into an SQL statement.
It's laughable to equate an outright lack of security (lock-less doors) with subtle programming errors which result in security holes. It's not like a door with no locks. It's like a door with a lock which can be opened by some method that the designer of the lock did not envision. Does it mean the lock designer did a poor job? That depends on the complexity of the hack itself.
I mostly agree. My pet peeve is SQL injection attacks, because they are so frickin' easy to avoid. Any developer that leaves their code open to SQL injection attacks should be held liable (unless their employer insists they use a language that doesn't have prepared statements, in which case the company should be held liable).
You also have to know the frequency for this to work, which involves trusting either TFA or your microwave manual, which makes it much less interesting as a pure science experiment. But still delicious.
I wish someone had mentioned that to Matt Groening.
I wish someone had mentioned that to Charles Schulz. 40 years ago.
Their submarines are good enough to sneak up on US carriers, and they have demonstrated that they can shoot down satellites. Now I ask myself where the US will be with carriers on the bottom of the oceans and no satellites to coordinate communications for combined arms or provide overhead intelligence.
"shoot down satellites" is a bit of a misnomer. The satellites don't head down when shot, they break into thousands of pieces. My point being if they shot down all our military satellites the debris field would destroy all the satellites and no one would have that advantage. And the effect last for decades and centuries. Which would suck for everyone. So they are unlikely to do it under any circumstances. Similarly sinking our carriers would probably result in a full scale nuclear war, so they are unlikely to do that either.
On the other hand, they will kick our ass economically and scientifically.
I currently work for a big bank as a Java programmer and make more than I did at any other company I've worked for. I'm a contractor but still come out significantly ahead after I buy my own benefits. All my other companies were start-ups and I was a FTE, so I don't have a great data set to compare, but for what it's worth I don't think banks are cheap.
F-ck 4 blades, we're doing 40,000 blades
This doesn't tell us anything about how people use passwords in important situations. I use crap passwords for crap sites like rockyou.com. For any site I actually care about (banks, gmail) I use really good passwords (well, as good as they will let me use, some banks still don't allow non-alphanumeric characters). So all this study really tells us is what password people use when they don't give a crap.
Wasnt sandboxing the cool word about 10 years ago?
Actually 15 years ago, when Java came out.