Okay, I've been getting some flak about Theorem 1.0, so I'm here to clarify a few things that I guess I thought were just 'given'.
If a bug does not eat a smaller bug, it doesn't count as a bug. It's just an insect. 'Bug' is a subset of insects. Well, maybe it wasn't before, but it is now. They were just redundant words before today. So another example:
You have 5 ants and 1 large bug in a jar. If the large bug doesn't have a jones for eating smaller bugs, it's just an insect, and you're doing it wrong. Otherwise, the sum of the bugs is 1.
You see, you can't just take someone's carefully calculated theorems and just insert whatever crap you have lying around into it. Like, I wouldn't take the second law of thermodynamics and just replace the word 'heat' with 'barnacles'. It doesn't work if you just crap it up like that. This is why I can't have nice scientific awards.
Also, while it might work if you have small bugs in a jar and then put in a lizard, that is a gross extrapolation of the theorem. You can't just make things up. These theorems undergo rigorous scientific testing, and the scientific method. That might make a good Theorem 1.1, but I'm not just going to jump out there and claim things that haven't been proven.
Thursday, August 31, 2006
Wednesday, August 30, 2006
Theorem 1.0
My work is generally overlooked by the scientific community, but I think I've hit paydirt this time. I present to you, Theorem 1.0, The Sum Of Bugs:
Theorem 1.0, The Sum Of Bugs:
The sum of a set of n bugs is equal to the number of the largest bugs.
Example 1:
There are 10 ants in a jar. All the ants are of equal size. The sum of those bugs is 10.
Example 2:
There are 9 ants and one spider in a jar. The spider is larger than the ants, so the sum of the bugs is 1. This is because the larger bug, the spider, will consolidate the smaller bugs into its own bug body.
Example 3:
There are 3 ants, 2 spiders, and one big ugly bug with 2 sets of wings and big jointed legs in a jar. Since the largest bug is the big ugly one, and there is only one of them, the sum of those bugs is 1. This is because the spiders will consolidate the ants into their bodies, and the big ugly bug will consolidate the spiders into its body.
The implications of this theorem are far reaching, from space exploration, to medicine, and bug-studies, but mainly bug-studies. If anyone runs a reputable scientific publication and needs some filler, let me know.
Theorem 1.0, The Sum Of Bugs:
The sum of a set of n bugs is equal to the number of the largest bugs.
Example 1:
There are 10 ants in a jar. All the ants are of equal size. The sum of those bugs is 10.
Example 2:
There are 9 ants and one spider in a jar. The spider is larger than the ants, so the sum of the bugs is 1. This is because the larger bug, the spider, will consolidate the smaller bugs into its own bug body.
Example 3:
There are 3 ants, 2 spiders, and one big ugly bug with 2 sets of wings and big jointed legs in a jar. Since the largest bug is the big ugly one, and there is only one of them, the sum of those bugs is 1. This is because the spiders will consolidate the ants into their bodies, and the big ugly bug will consolidate the spiders into its body.
The implications of this theorem are far reaching, from space exploration, to medicine, and bug-studies, but mainly bug-studies. If anyone runs a reputable scientific publication and needs some filler, let me know.
Tuesday, August 29, 2006
Fall 2006
I'm on a roll. Two posts in one night. That's because I'm putting off some homework. I work better under pressure anyways. So this is the start of my 6th year in college. Here's what I've got on my plate so far:
Computer Architecture - This is taught by Dr. Rao, who I've had before. Dr. Rao cracks me the hell up. This is a particularly good thing, because I already took the second part of the class, and I think I already know most of what we're going to cover, so he will keep me entertained and things will still be interesting. Rao is a good prof. Anyone who says different, I cut their face. Also good, I have that class with Sheena.
Software Engineering - I guess this is like CSA470j on steroids, and with team work. The professor, Dr. Kiper, seems pretty cool so far, and the work seems interesting. I guess since this is the senior capstone, they expect you to kill yourself working on the projects and whatnot. We'll see. I think the prof will make things fun enough that I don't have to kill anyone, since I sure as hell am not going after myself. Also good, I have that class with Sheena.
Compiler Design - I dreaded this class. Compiler Design is like...I don't know. Something I don't want to do. Like, if I could have any tech job, I think compiler design would be my last freakin pick. Writing in assembly is cool. Writing in higher level languages is cool. If I want to translate between the two, I'll do it in my mind, or just use the right language to begin with. Anyway. It looks like it is actually going to be pretty interesting. Also good, I have that class with Sheena.
Database Systems - To be totally honest, the first day of class, when the professor walked into the room, I was very concerned. The professor was an old dude with a name I couldn't pronounce, and he sat there and just looked over us all while we waited. Turns out, he's pretty cool, and he cracks a funny every now and then that busts everyone up. This is an interesting class because there is a group of business students in the back. Business students = hot chicks. Since I've been working with databases since...well crap...since I was like...12? I'm not too worried about the class, and maybe I'll pick up a tutoring opportunity along the way ;) Probably not though. This class I have with Jon, who is Sheena's ex. He's a smart dude, and he's got a good sense of humor, so I like him. It'll make things fun. Additionally, I sit next to a girl who helps out at an animal shelter down in Cincy, so she's good people. And there's a guy in the front row I say hi to also, his name is either Jim or Tom. I'm going to go with Tom.
Intro to Artificial Intelligence - This class is too god damned big. In a class where you deal with abstract issues like computers thinking, you need small classes for discussion. Whoever put 33 people in this class needs a punch to the head. Also, the professor hands out everything on paper. I do not want to carry around a bunch of paper. I'm a computer science major, not some kind of crap major where you collect shit in folders and lug it around in a backpack and file it in folders and staple things together. The content is interesting though, and the professor seems like a nice guy, so I'm dealing. Also good, I have that class with Sheena.
Probability - Probability is math. What can I say? I like math, but don't exactly like doing homework and taking tests, so it's neutral. The class it a little dry, but like I said, it's math, so I don't know what I expect. Tom is in this class.
So all in all, a good semester ahead, I think! No real complaints. We'll see though. It's still early.
Computer Architecture - This is taught by Dr. Rao, who I've had before. Dr. Rao cracks me the hell up. This is a particularly good thing, because I already took the second part of the class, and I think I already know most of what we're going to cover, so he will keep me entertained and things will still be interesting. Rao is a good prof. Anyone who says different, I cut their face. Also good, I have that class with Sheena.
Software Engineering - I guess this is like CSA470j on steroids, and with team work. The professor, Dr. Kiper, seems pretty cool so far, and the work seems interesting. I guess since this is the senior capstone, they expect you to kill yourself working on the projects and whatnot. We'll see. I think the prof will make things fun enough that I don't have to kill anyone, since I sure as hell am not going after myself. Also good, I have that class with Sheena.
Compiler Design - I dreaded this class. Compiler Design is like...I don't know. Something I don't want to do. Like, if I could have any tech job, I think compiler design would be my last freakin pick. Writing in assembly is cool. Writing in higher level languages is cool. If I want to translate between the two, I'll do it in my mind, or just use the right language to begin with. Anyway. It looks like it is actually going to be pretty interesting. Also good, I have that class with Sheena.
Database Systems - To be totally honest, the first day of class, when the professor walked into the room, I was very concerned. The professor was an old dude with a name I couldn't pronounce, and he sat there and just looked over us all while we waited. Turns out, he's pretty cool, and he cracks a funny every now and then that busts everyone up. This is an interesting class because there is a group of business students in the back. Business students = hot chicks. Since I've been working with databases since...well crap...since I was like...12? I'm not too worried about the class, and maybe I'll pick up a tutoring opportunity along the way ;) Probably not though. This class I have with Jon, who is Sheena's ex. He's a smart dude, and he's got a good sense of humor, so I like him. It'll make things fun. Additionally, I sit next to a girl who helps out at an animal shelter down in Cincy, so she's good people. And there's a guy in the front row I say hi to also, his name is either Jim or Tom. I'm going to go with Tom.
Intro to Artificial Intelligence - This class is too god damned big. In a class where you deal with abstract issues like computers thinking, you need small classes for discussion. Whoever put 33 people in this class needs a punch to the head. Also, the professor hands out everything on paper. I do not want to carry around a bunch of paper. I'm a computer science major, not some kind of crap major where you collect shit in folders and lug it around in a backpack and file it in folders and staple things together. The content is interesting though, and the professor seems like a nice guy, so I'm dealing. Also good, I have that class with Sheena.
Probability - Probability is math. What can I say? I like math, but don't exactly like doing homework and taking tests, so it's neutral. The class it a little dry, but like I said, it's math, so I don't know what I expect. Tom is in this class.
So all in all, a good semester ahead, I think! No real complaints. We'll see though. It's still early.
Stop Bashing Wiki
Okay, out of my 6 classes this semester, I think 3 of my professors mentioned something to the effect of how Wikipedia is not a reliable source for research. I've got a beef.
Granted there's a lot of crap in Wikipedia, between political and business people pushing sides of an issue, 9-year-olds with AOL accounts who just like to mess things up, and people who just don't know what they're talking about, but the Wikipedia community as a whole is fairly on-top of their shit, particularly when it comes to technology-related issues, which happens to be my field. I think the key to using Wikipedia as a resource is knowing how to look at and understand the history of an article, as well as being able to reason and understand what you read.
I'm not working on any papers, and I'd never use Wikipedia as my only resource. I'm just saying. Don't trash it.
Granted there's a lot of crap in Wikipedia, between political and business people pushing sides of an issue, 9-year-olds with AOL accounts who just like to mess things up, and people who just don't know what they're talking about, but the Wikipedia community as a whole is fairly on-top of their shit, particularly when it comes to technology-related issues, which happens to be my field. I think the key to using Wikipedia as a resource is knowing how to look at and understand the history of an article, as well as being able to reason and understand what you read.
I'm not working on any papers, and I'd never use Wikipedia as my only resource. I'm just saying. Don't trash it.
Subscribe to:
Posts (Atom)