As someone who has learned both spoken languages and programming languages to fluency (whatever that might mean in this case) I can tell you that allowing CS to replace the requirement for 2 years of a spoken foreign language is a huge mistake. As if we don't have enough narrow minded jingoistic Americans running about scarcely aware of the cultures outside our borders. If you want a good IT job learn both. It is entirely possible. I took two years of both in high school, no problem. You may have to give up your goof-off elective for a couple semesters but it is certainly doable in most schools.
Slashdot videos: Now with more Slashdot!
'Houston, we have a problem...What's bitcoin?"
...only once the rods of cooled sufficiently (a few years). Until then they must stay in the pools.
The radiator in the car requires a pump and, of course, a radiator. I think evaporative cooling (the current method) is the best way to go. If you seal it and pump it you must have the pump working and airflow over the radiator at all times. It is more complicated.
Are you talking about San Onofre here? I live within tens of miles of it. The fuel is currently NOT removed. In fact there are 4 decades worth of spent fuel sitting in pools at the site. And it will remain there indefinitely until we figure out another place to store it OR pull our heads out of our asses and reprocess and recycle this fuel. Letting such a valuable commodity sit there is just silly.
Even though I live nearby the thing I am disappointed they are giving up on it. Looks like we're in for another summer of rolling blackouts in SoCal.
Compress the file then print it out in easily OCR'able format (QR codes, perhaps), then physically carry it out of the country.
"You can't stop the signal, Mal."
My job requires me to spend a lot of time with stuff in my ears: Headsets, earbuds for music, bluetooth for phone calls... They would always fall out or not isolate well. Then I found out about custom ear molds. You go to an audiologist (same guy who makes hearing aids) and they put this putty like stuff in your ear which hardens after a couple minutes and takes an impression of the ear canal and area just outside your ear. Then you send that impression off to a place that makes custom ear molds and you tell them what device you are going to be attaching it to.
I highly recommend Avery Sound: http://www.averysound.com/.
I have no financial interest in them, I'm just a very sastisfied customer. I have their custom ear molds on my Etymotic ear buds for music, on my Clarity Aloft aviation headset, and on my Jawbone Prime bluetooth headset. Perfect fit, great isolation, and have never once fallen out of my ear due to the way they lock-in by following every curve of the ear.
My only complaints about them might be that I have accidentally pulled the earmolds off my Etymotic earbuds a few times while listening to music because the low surface area of the part of the earbud that sticks into the earmold doesn't leave much to grab onto. But my Jawbone and Aloft are stuck on there very solidly. The Etymotic earmold is also probably the least well fitting of the three although it still fits very good. It's just that if I swallow hard or chew it breaks the airtight seal with the outside (which is what gives the awesome noise isolation coming in and music isolation going out) which causes a popping noise. A very minor thing, really. But that's how good these things are.
I'll never use standard non-molded earbuds again.
I have noticed that whenever I see people approached with comments about the quality of their code (by myself or others) they often say things like "You just don't understand what this code is supposed to be doing."
That is always a red-flag to me. If your code is good the person should be able to tell what the code is doing.
What are this person's specific objections to your code?
There are no absolutes or hard rules and much is subjective and language dependent but as general rules of thumb:
Does your organization have a style guide? Does your code follow it?
Does your code have comments? I like to see at least one comment per functional block of code (function, loop, branch, new level of indent, whatever, depending on language).
Are the lengths of your function limited to no more than a page of text, preferably half a page?
Do your line lengths not exceed 80 columns?
Do you make some effort at making the code visually nice to look at? Is it formatted so like elements line up for easy comparison of lines? I'm a big fan of lining up = and parens etc. to make the code look orderly. It makes it easy to spot differences or errors. It sounds shallow but I also find that when someone has done this it means they care.
Without seeing a sample of your code to tell you if it IS bad there's no way we can advise you. If all you want is a polite way to tell the little twerp to shut up and mind his own business that won't get you fired I'm afraid I don't have much to offer.
God wants peace
God wants war
God wants famine
God wants chain stores
What God wants God gets
God wants sedition
God wants sex
God wants freedom
God wants semtex
What God wants God gets
God help us all
Mining isn't the only way to get bitcoins.
This sounds like Return Oriented Programming, used in some exploits to thwart countermeasures. But it is a long way from stitching together code to do trivial things all the way to making code which replicates, has a payload, AND can stitch together code to do all Of this. The Halting Problem makes me wonder if it is even theoretically possible.
> In one remarkable case, a participant in an antidepressant drug trial was given placebo tablets — and then swallowed 26 of them in a suicide attempt.
This reminds me of the James Randi talk on homeopathy: Part of the theory of homeopathy is that the more dilute the solution is the stronger it is. Randi told the hypothetical story of someone who forgot to take his "medicine" thus causing an overdose and DIED.
No Tom Servo or Crow T Robot? I am disappoint.
Amateur programmers discuss syntax. Professional programmers discuss semantics.
Amateur generals discuss tactics. Professional generals discuss logistics.
I bet there are a lot of these...