The other reason for AC current is that you can make brushless motors far more easily, at least when the AC/DC war was going on. Of course now it's not hard to get DC brushless motors. (Hell, all the decent motors for RC electric planes and copters are BLDC.)
Admittedly I can't find it.(My GoogleFu is weak today.) I know they lay their eggs at the end of long threads to protect them. I thought I read somewhere that the threads have a chemical repellent to keep ants away (Since you'd think one tiny ant would just climb down and get it) but I can't find anything on Google confirming that.
This is a stupid idea because people are morons. I mean have you ever seen people try to get on the subway in Boston? The rush and try to get off or on even as the doors are closing. I'm surprised more people don't get stuck in the doors because of that. Anyway at least if you get stuck halfway in the door they can keep the train stopped until they get the idiot free. However if both trains are going down the tracks who knows how long they can stay connected while they try to get idiots out of the door.)
I mean I guess they're counting only science courses but my impression of the coursesin the language requirement that was inflicted on me is that more than 30% were engaging in "Classic" Cheating. (IE copying off of others, looking at the book during tests. Having someone else do their homework.) Actually if you count in what I call class 2 cheating (IE taking a class where you already know the subject matter very well and are only taking it for an easy A) then I'd bet at least in the language courses I took cheating was well above 50%. (Man, I should have cheated.)
You have a point there. He probably figured "We've got enough people coming into the physics program as it is, if he can't get up to speed it makes no difference to us." Of course this made me fairly jaded when the school puts out all those brochures that say how they really care about undergrad education. (When really they don't.)
I've mentioned this before. I was going to take a track that required the hardest calc based physics for freshmen that the university offered So I took a pair of tests, a physics and a calc test. I did extremely well on the physics test. (Which basically repeatedly asked to you get Newton's first law? IE stuff goes straight at constant speed.) I pretty much blew it on the calc section since I took precalc as a junior in high school and took stats as a senior. (So whatever calc skills I still had were very rusty and we didn't even go that far since it was pre-calc.) Calc was theoretically a pre-req for this physics class. However the professor who was reading these results and telling us what to take told me that you definitely should take that physics course. (He was a physics professor btw.) So guess what happened, since my math wasn't up to the level they expected for this class this turned into a total trainwreck for me.(Which got made worse when they started breaking out multi-variant calculus and linear algebra. Yes really.) I pretty much couldn't follow along since I didn't have the math skills to understand it. (And let's be honest, physics is applied math. Things in physics make so much sense if you know calc.) My impression after all these years is he really didn't care because there's no way he didn't know. (I mean he was a physics professor for floating spaghetti monster's sake. He had to have know what level of math was expected. I'm guessing he was more worried about his research since it's obvious now he didn't care about undergrad education.) This totally derailed the track I was taking although admittedly I ended up on the computer science track. (Which I guess means I didn't totally drop out. Oh, I took calc based physics years later but made sure my calc was really good, I got an A that time:) )
Oh well, on the other hand one that I really hated in college/uni is all the non science requirements. I mean it was in subjects I wasn't interested before I took them, I wasn't interested in them afterwards and I'm not interested now. (They were a complete waste of time and after being out of school for over 15 years no, they haven't turned out to be useful.) I of course have a special hatred for the foreign language requirement but that's a story for another time. (IE oh how I wish I could have taken nothing but science courses. I didn't even get to take bio or chem when I was first in college/uni because of those requirements.)
On this image of antartic elevation http://en.wikipedia.org/wiki/File:AntarcticBedrock.jpg you can see alot of what we think of the continent of Antartica would actually be open ocean if the ice wasn't there. (As it's below sea level.)
Oh, and that Herbert Hoover guy. He was a mining engineer.
That's putting it mildly. He apparently wrote "The" college text book on the subject and taught classes in it at university. (Oh and he spoke Chinese to some level.)
Ooh, could we have a Maurice Hilleman day too?
on
Dennis Ritchie Day
·
· Score: 1
http://en.wikipedia.org/wiki/Maurice_Hilleman
The guy develops loads of vaccines include 8 of the 14 currently recommended. Some how they forgot to give the guy the Nobel prize in medicine. Seems like it's long overdue. (I mean he's got a couple of buildings with his name on them but nothing that would tell anybody that he probably saved the lives of tens to hundreds of millions of people.)
I mean even if you don't currently don't have any debt you may want to have some for a couple of years because you want to make a big purchase like a house or a car. Actually on top of that even if you're in the black temporary credit is still useful and even I have that right now, it's called a credit card.(IE even if your finances are in the black loads of people still use credit cards since it helps with transactions.)
I guess you could have a "analog" clock that you drag its hand to point at the "wake up" icon or something like as well. (Could you guys wait a few minutes, I need to run down to go out or something. It's not like I need to go to the patent office to patent this idea or anything:) )
It's like they're creating a big holiday for a guy who happened to build a bunch of builds because they were really nice while at the same time ignoring the death of the guy who invented the concrete that is the basis for the construction that everybody uses, including that first guy.(Go ahead everybody, come up with your own analogy, it's fun.)
"He'll probably find a cure for cancer," Sleight said. "Or something bigger."
Umm, last I checked cancers were a class of hundreds of diseases. I can't see how you could find something bigger than one method to cure all of them given the multitudes of really smart people that would be happy to come up with a cure for just one. (Like liver, lung or pancreatic cancers. Hey, did I mention each of those organs has multiple cancers that affect it? Hell, they'd probably be happy to add a cure for one cancer of one of those organs to the tool kit of modern medicine.)
Oh well, guess it's one of my pet peeves when people think cancers are actually one disease.
Well it's not as though I was happy about this.(Really in a perfect world they would be in the bug tracking system.) However the point was that QA had in effect put in the requirement that when you fixed a memory leak the memory had to be released back to the OS so they could check it with task manager. However go check a generic reference for the delete method in C++. It doesn't say the memory gets released to the OS. A specific implementation may do that but many simply don't. (This is stuff I found out when I researched it and really get a general understanding on this.) So basically QA decided on a requirement that could never be satisified for a memory leak. (Since the memory manager wasn't required to release the memory to the OS having that as a requirement on a memory leak bug made them impossible to fix. You could never satisfy the requirement.)
As I've said I could show them in a debug build that the leak was fixed. (Since debug did release the memory to the OS. It did this to help us software engineers get our code working properly and in debug you're not supposed to be concerned about speed.) Once you went to release build however the memory manager wouldn't release the memory back to the OS, it'd cache it. (Since apparently that's faster.) As I wrote in my other post I tried to go to the extra mile and pointed out a way that they could test it but they ignored what I said completely. (Basically take the app and run a pair of tests, one right after the other without shutting down the app. With the fix the memory plateaued because of the caching.) They insisted that they had to do it with Task manager and that the memory had to be released back to the OS. (Which was wrong from a technical point of view. Explaining this more than once made no difference. Yes, I really did this more than once.)
I should point out the main thing I wanted out of them was to run their automated test suite to make sure I didn't break anything else. (Since I already knew the memory leak they were talking about was fixed so I didn't need them to check that. I needed to know if I broke anything by fixing the memory leak.) So I was going to get this anyway.(Because they always ran those tests on all bugs.) Should I mentioned I talked to a senior engineer about this issue. I basically read between the lines afterward that he had gone through the exact same thing. (Since he mentioned QA should really only do the automated tests on a memory leak since to be more precise you can't even definitively diagnose a memory leak if you can't see the code.) Actually he was one that told me to just find memory leaks as you find them. But the long and short of it is as I've said they didn't get caching. Because they didn't get caching they though something was true about the freeing of memory that actually wasn't true. Because they thought this they came up with requirements that were impossible to satisfy for a memory leak and they wouldn't listen when you tried to explain what they didn't understand and why their requirements were impossible. There really wasn't many other options than just cut them out of the loop when you fixed a memory leak.
I still remember at one place I worked they had me clean up a memory leak. Unfortunately I couldn't get it past QA because they didn't understand caching. Basically the deal is that when you free memory it goes back to the memory pool for the process and then the pool decides when to release it to the OS.(Which may be never) So when I freed my memory in debug build the pool immediately returned it to the OS. When QA did that in release the pool held on to the memory and reused it. I even showed them how if you did multiple processes one after the other you could actually see the app use more and more memory while after the fix it would plateau. (Because it was just re-using the memory it had already allocate.) They totally didn't understand, I might as well have explained it to the pavement outside the building. (In the end it just got marked as unfixable. After that if I saw any memory leaks while coding I fixed them as part of other bugs and then didn't mention it to QA.)
The right because they're against cloning. Of course the left will get pissed because it's using genetic engineering so it might be awhile before the rest of us can have something nice from this tech. Why yes, I am a little jaded. Why do you ask?
If you have a cure then more than a few people would continue doing whatever it was that made them sick in the first place. You've got repeat customers right in the waiting. (I mean why avoid eating fatty foods like bacon if I can just take a pill anytime I get sick.)
Really? I mean I know the Andromeda galaxy is normally the furthest naked eye visible object and that's 2 million LY away. (This thing is 10X further and is still naked eye visible? That's amazing.)
Slashdot Mirror
The other reason for AC current is that you can make brushless motors far more easily, at least when the AC/DC war was going on. Of course now it's not hard to get DC brushless motors. (Hell, all the decent motors for RC electric planes and copters are BLDC.)
Admittedly I can't find it.(My GoogleFu is weak today.) I know they lay their eggs at the end of long threads to protect them. I thought I read somewhere that the threads have a chemical repellent to keep ants away (Since you'd think one tiny ant would just climb down and get it) but I can't find anything on Google confirming that.
This is a stupid idea because people are morons. I mean have you ever seen people try to get on the subway in Boston? The rush and try to get off or on even as the doors are closing. I'm surprised more people don't get stuck in the doors because of that. Anyway at least if you get stuck halfway in the door they can keep the train stopped until they get the idiot free. However if both trains are going down the tracks who knows how long they can stay connected while they try to get idiots out of the door.)
I mean I guess they're counting only science courses but my impression of the coursesin the language requirement that was inflicted on me is that more than 30% were engaging in "Classic" Cheating. (IE copying off of others, looking at the book during tests. Having someone else do their homework.) Actually if you count in what I call class 2 cheating (IE taking a class where you already know the subject matter very well and are only taking it for an easy A) then I'd bet at least in the language courses I took cheating was well above 50%. (Man, I should have cheated.)
You have a point there. He probably figured "We've got enough people coming into the physics program as it is, if he can't get up to speed it makes no difference to us." Of course this made me fairly jaded when the school puts out all those brochures that say how they really care about undergrad education. (When really they don't.)
Oh well, on the other hand one that I really hated in college/uni is all the non science requirements. I mean it was in subjects I wasn't interested before I took them, I wasn't interested in them afterwards and I'm not interested now. (They were a complete waste of time and after being out of school for over 15 years no, they haven't turned out to be useful.) I of course have a special hatred for the foreign language requirement but that's a story for another time. (IE oh how I wish I could have taken nothing but science courses. I didn't even get to take bio or chem when I was first in college/uni because of those requirements.)
On this image of antartic elevation http://en.wikipedia.org/wiki/File:AntarcticBedrock.jpg you can see alot of what we think of the continent of Antartica would actually be open ocean if the ice wasn't there. (As it's below sea level.)
You could always hire them as a contractor for 6 months to a year and if they do alright convert them to full time employees.
Oh, and that Herbert Hoover guy. He was a mining engineer.
That's putting it mildly. He apparently wrote "The" college text book on the subject and taught classes in it at university. (Oh and he spoke Chinese to some level.)
http://en.wikipedia.org/wiki/Maurice_Hilleman The guy develops loads of vaccines include 8 of the 14 currently recommended. Some how they forgot to give the guy the Nobel prize in medicine. Seems like it's long overdue. (I mean he's got a couple of buildings with his name on them but nothing that would tell anybody that he probably saved the lives of tens to hundreds of millions of people.)
I mean even if you don't currently don't have any debt you may want to have some for a couple of years because you want to make a big purchase like a house or a car. Actually on top of that even if you're in the black temporary credit is still useful and even I have that right now, it's called a credit card.(IE even if your finances are in the black loads of people still use credit cards since it helps with transactions.)
I guess you could have a "analog" clock that you drag its hand to point at the "wake up" icon or something like as well. (Could you guys wait a few minutes, I need to run down to go out or something. It's not like I need to go to the patent office to patent this idea or anything :) )
Would you want to live to 150?
Of course I would. I mean I have to live to at least 150 to get through my back log of video games and DVDs.
Err, bunch of buildings.
It's like they're creating a big holiday for a guy who happened to build a bunch of builds because they were really nice while at the same time ignoring the death of the guy who invented the concrete that is the basis for the construction that everybody uses, including that first guy.(Go ahead everybody, come up with your own analogy, it's fun.)
"He'll probably find a cure for cancer," Sleight said. "Or something bigger."
Umm, last I checked cancers were a class of hundreds of diseases. I can't see how you could find something bigger than one method to cure all of them given the multitudes of really smart people that would be happy to come up with a cure for just one. (Like liver, lung or pancreatic cancers. Hey, did I mention each of those organs has multiple cancers that affect it? Hell, they'd probably be happy to add a cure for one cancer of one of those organs to the tool kit of modern medicine.)
Oh well, guess it's one of my pet peeves when people think cancers are actually one disease.
Actually he was one that told me to just find memory leaks as you find them.
Slight correction, "Fix memory leaks as you find them." is what I meant to say.
Well it's not as though I was happy about this.(Really in a perfect world they would be in the bug tracking system.) However the point was that QA had in effect put in the requirement that when you fixed a memory leak the memory had to be released back to the OS so they could check it with task manager. However go check a generic reference for the delete method in C++. It doesn't say the memory gets released to the OS. A specific implementation may do that but many simply don't. (This is stuff I found out when I researched it and really get a general understanding on this.) So basically QA decided on a requirement that could never be satisified for a memory leak. (Since the memory manager wasn't required to release the memory to the OS having that as a requirement on a memory leak bug made them impossible to fix. You could never satisfy the requirement.) As I've said I could show them in a debug build that the leak was fixed. (Since debug did release the memory to the OS. It did this to help us software engineers get our code working properly and in debug you're not supposed to be concerned about speed.) Once you went to release build however the memory manager wouldn't release the memory back to the OS, it'd cache it. (Since apparently that's faster.) As I wrote in my other post I tried to go to the extra mile and pointed out a way that they could test it but they ignored what I said completely. (Basically take the app and run a pair of tests, one right after the other without shutting down the app. With the fix the memory plateaued because of the caching.) They insisted that they had to do it with Task manager and that the memory had to be released back to the OS. (Which was wrong from a technical point of view. Explaining this more than once made no difference. Yes, I really did this more than once.) I should point out the main thing I wanted out of them was to run their automated test suite to make sure I didn't break anything else. (Since I already knew the memory leak they were talking about was fixed so I didn't need them to check that. I needed to know if I broke anything by fixing the memory leak.) So I was going to get this anyway.(Because they always ran those tests on all bugs.) Should I mentioned I talked to a senior engineer about this issue. I basically read between the lines afterward that he had gone through the exact same thing. (Since he mentioned QA should really only do the automated tests on a memory leak since to be more precise you can't even definitively diagnose a memory leak if you can't see the code.) Actually he was one that told me to just find memory leaks as you find them. But the long and short of it is as I've said they didn't get caching. Because they didn't get caching they though something was true about the freeing of memory that actually wasn't true. Because they thought this they came up with requirements that were impossible to satisfy for a memory leak and they wouldn't listen when you tried to explain what they didn't understand and why their requirements were impossible. There really wasn't many other options than just cut them out of the loop when you fixed a memory leak.
I still remember at one place I worked they had me clean up a memory leak. Unfortunately I couldn't get it past QA because they didn't understand caching. Basically the deal is that when you free memory it goes back to the memory pool for the process and then the pool decides when to release it to the OS.(Which may be never) So when I freed my memory in debug build the pool immediately returned it to the OS. When QA did that in release the pool held on to the memory and reused it. I even showed them how if you did multiple processes one after the other you could actually see the app use more and more memory while after the fix it would plateau. (Because it was just re-using the memory it had already allocate.) They totally didn't understand, I might as well have explained it to the pavement outside the building. (In the end it just got marked as unfixable. After that if I saw any memory leaks while coding I fixed them as part of other bugs and then didn't mention it to QA.)
The right because they're against cloning. Of course the left will get pissed because it's using genetic engineering so it might be awhile before the rest of us can have something nice from this tech. Why yes, I am a little jaded. Why do you ask?
If you have a cure then more than a few people would continue doing whatever it was that made them sick in the first place. You've got repeat customers right in the waiting. (I mean why avoid eating fatty foods like bacon if I can just take a pill anytime I get sick.)
I mean Glazer just says "Stem cell therapy" as thought it was a specific thing when it could be anything from ESC therapy to a bone marrow transplant.
Really? I mean I know the Andromeda galaxy is normally the furthest naked eye visible object and that's 2 million LY away. (This thing is 10X further and is still naked eye visible? That's amazing.)
The best book on programming for the layman is "Alice in Wonderland"; but that's because it's the best book on anything for the layman.
Could you come by and explain it to some software engineers? I think quite a few of them could do with learning about it too.