I saw something this morning that I found very impressive. I'd never seen anything like it in my four years at USC. In fact, I don't think I'd ever seen anything like it in my life. A kid was sitting on a bench reading a book, without looking up at all. The bench in question was Associate's Park, between Bovard and the PE building. For those not familiar with the geography of USC, this is a location typically used for sitting quietly and reading/studying, unlike, say, Hahn Plaza, which is traditionally where enthusiastic people with clipboards and flyers try to stop you and get you to join their party this weekend/religious organization/service organization/volunteer opportunity.
Anyway, this kid is sitting there, reading a book, not looking up at all. Next to him are two people with some sort of small flyers, talking to this kid about how Jesus loves him and quoting something from Genesis. They're just continuing, on and on and on, seemingly completely unaware of the fact that they're absolutely being ignored. I've never seen anything like it before--I've never seen anyone so intent on getting a stranger to believe what they believe. It was really quite amazing.
Showing posts with label USC. Show all posts
Showing posts with label USC. Show all posts
4.26.2010
1.05.2010
USC Basketball Sanctions
There's been a lot of talk lately about USC's self-imposed sanctions that have been applied to its basketball team in response to the violations of NCAA rules committed two years about by OJ Mayo and Tim Floyd. Some people say USC didn't go far enough, a lot of people say Mike Garrett is sacrificing the basketball team to save the football team.
To me, the whole system seems quite irrational. The NCAA makes it very clear what is and isn't allowed, but as far as I know, there are no official penalties for any of the violations. So when something happens, the school imposes a penalty on itself, hoping the NCAA will think it's harsh enough. If the NCAA accepts it, then maybe we could have gotten away with less, and we punished ourselves unnecessarily. If they impose even harsher sanctions than the ones we came up with, then we look like we're not taking the infractions seriously, simply because we couldn't read the NCAA's mind.
Imagine if the coaches determined their own penalties for fouls during football games. Instead of the officials referring to the rulebook (delay of game = 5 yards, holding = 10 yards, etc.) the coach simply imposes his own penalty and hopes the officials will accept it as "harsh enough." This would be a ridiculous way to run a football game. How hard would it be for the NCAA to create a mapping from violations to specific penalties? If you can find the exact rule that Mayo and Floyd violated, you should also find, on the same page of the NCAA rulebook, a specific description of the penalties that will be imposed on the coach, the school, and players who were involved. Maybe there's a reason the NCAA doesn't work like that. I would love for someone to tell me what that reason is.
But back to the sanctions themselves. My biggest complaint, really my only complaint, is the way the administration is taking our current team (none of whom were involved in the rules violations at all, and most of whom weren't even at USC at the time) out of all postseason play, including the annual Pac-10 Tournament and the NCAA Tournament (which I think we probably would have participated in for the fourth time in a row -- the first time that would have ever happened to USC).
This punishment has absolutely no effect on anyone who is actually responsible, and it keeps a great team, who so far as surpassed all expectations, from showing the country what they can do in "the big dance." So here's what I think we should do instead. Currently, during halftime of USC home games, there are a couple of little challenges, where students come down from the stands and try to make a shot or two in order to win money or plane tickets from Nike or American Airlines. Instead of that, I think we should have OJ Mayo and Tim Floyd come down and stand at midcourt. A student stands at either end of the court and fires a nerf gun at the NCAA rules violators. One student's nerf darts have cardinal paint, and the other's have gold paint, to make it easy to see which one got more hits. The winner receives a free Trojan Fever t-shirt. Mayo and Floyd do not. What do you think?
To me, the whole system seems quite irrational. The NCAA makes it very clear what is and isn't allowed, but as far as I know, there are no official penalties for any of the violations. So when something happens, the school imposes a penalty on itself, hoping the NCAA will think it's harsh enough. If the NCAA accepts it, then maybe we could have gotten away with less, and we punished ourselves unnecessarily. If they impose even harsher sanctions than the ones we came up with, then we look like we're not taking the infractions seriously, simply because we couldn't read the NCAA's mind.
Imagine if the coaches determined their own penalties for fouls during football games. Instead of the officials referring to the rulebook (delay of game = 5 yards, holding = 10 yards, etc.) the coach simply imposes his own penalty and hopes the officials will accept it as "harsh enough." This would be a ridiculous way to run a football game. How hard would it be for the NCAA to create a mapping from violations to specific penalties? If you can find the exact rule that Mayo and Floyd violated, you should also find, on the same page of the NCAA rulebook, a specific description of the penalties that will be imposed on the coach, the school, and players who were involved. Maybe there's a reason the NCAA doesn't work like that. I would love for someone to tell me what that reason is.
But back to the sanctions themselves. My biggest complaint, really my only complaint, is the way the administration is taking our current team (none of whom were involved in the rules violations at all, and most of whom weren't even at USC at the time) out of all postseason play, including the annual Pac-10 Tournament and the NCAA Tournament (which I think we probably would have participated in for the fourth time in a row -- the first time that would have ever happened to USC).
This punishment has absolutely no effect on anyone who is actually responsible, and it keeps a great team, who so far as surpassed all expectations, from showing the country what they can do in "the big dance." So here's what I think we should do instead. Currently, during halftime of USC home games, there are a couple of little challenges, where students come down from the stands and try to make a shot or two in order to win money or plane tickets from Nike or American Airlines. Instead of that, I think we should have OJ Mayo and Tim Floyd come down and stand at midcourt. A student stands at either end of the court and fires a nerf gun at the NCAA rules violators. One student's nerf darts have cardinal paint, and the other's have gold paint, to make it easy to see which one got more hits. The winner receives a free Trojan Fever t-shirt. Mayo and Floyd do not. What do you think?
9.06.2009
Don't look back, don't look forward. Look at where you are.
Yesterday was my last first gameday ever. The last time that I will ever, as a student and as a member of the Trojan Marching Band, experience the thrill of that very first day of USC football. There are more gamedays to come of course, but only a handful of them, and there is nothing like the first game: No substitute for seeing the Coliseum full of cardinal and gold, for the first time since a November or December game that seemed like years ago.
There are going to be a lot of "last" moments this year, and I know that at certain times, it's going to be tough not to get a little disappointed. From my very first band camp, I could already tell how important the band was going to be, and I knew the years would fly past me way too fast. I was right.
I was going to write a whole post about not taking things for granted, because if you do they will be gone before you know it. And I do think that every single day, you should think about all the great things in your life, and how lucky you are to have them. I was going to list all the things that I'm grateful for, from big things like being admitted to USC, to small things like the amusing little running jokes we have in the band, and everything in between.
But I'm beginning to think that won't be an issue for me this year. I'm beginning not to worry that I will take anything for granted. The greater risk for me, I think, is that I will go too far in the opposite direction. That I will spend too much time thinking about how quickly it's all slipping away from me; picturing what it will be like when I march my last step on the field; anticipating how that last finals week in May will feel; picturing commencement and realizing that I may be seeing some people for the last time.
So my goal is to strike the right balance. For every great moment that happens this year, I will mentally detach myself, just for an instant, to realize how lucky I am to be part of it. And then I will try to let the instant pass, clear my mind, and simply live in that moment. It's all about finding the right balance between reflecting on events, and simply living through them.
Fight on, Trojans.
5.12.2008
Writing "code"?
My friend from freshman year, Elliot, has recently started a new blog, Anyone Can Code. I guess he's going to teach some programming courses over the summer, partly because he, like me, doesn't like the way most of the courses he's taken at USC have been taught. And because he believes that, well, anyone can code.
His first post on the Anyone Can Code blog lamented the people who are somewhat interested in computer science, but think they can't code. I've always thought that "people who can't do math" were just people who had terrible math teachers and never took them time to learn any math on their own. There isn't really anything wrong with this, but it's now become relatively socially acceptable to know almost no math. It's also socially acceptable to know literally no coding, since most people never take any computer science classes.
I've digressed a little, but the point I wanted to make here is that perhaps referring to programming as "coding" is not good for making it accessible to the general public. Code, in everyday language, is a message which is unreadable until a person or machine performs some kind of operation on it to decode it, so that humans can read it. Back in the days of punchcards, that may have been somewhat accurate, but now writing computer programs is (or at least should be) almost the opposite. You write down what you want the computer to do, in as clear and straightforward a way as possible. Then the computer compiles or interprets it, which is when it becomes completely unreadable. But the programmer isn't writing "code". They're just writing down a set of instructions, in another language. So maybe instead of "coding," we should look at programming as writing in another language. Because that's all programming languages are--they're just languages, where the rules of grammar must be followed much more strictly than in languages like English or Spanish.
Oh great, you say, so coding is just like learning a language, except with even more emphasis on grammar? Sounds lovely. Well yes, but there's very little emphasis on learning new vocabulary. In fact, most of the important words in most languages are actually words you already know. And the grammar rules are much clearer and completely unambiguous, especially in languages like Ruby and (from what I hear, although I haven't used it myself) Python, which were deliberately intended to be easier to use. I think Elliot is right that anyone can code. It doesn't mean everyone will find it fun. But if we stop thinking of code as "code," perhaps everyone will be able to do it.
His first post on the Anyone Can Code blog lamented the people who are somewhat interested in computer science, but think they can't code. I've always thought that "people who can't do math" were just people who had terrible math teachers and never took them time to learn any math on their own. There isn't really anything wrong with this, but it's now become relatively socially acceptable to know almost no math. It's also socially acceptable to know literally no coding, since most people never take any computer science classes.
I've digressed a little, but the point I wanted to make here is that perhaps referring to programming as "coding" is not good for making it accessible to the general public. Code, in everyday language, is a message which is unreadable until a person or machine performs some kind of operation on it to decode it, so that humans can read it. Back in the days of punchcards, that may have been somewhat accurate, but now writing computer programs is (or at least should be) almost the opposite. You write down what you want the computer to do, in as clear and straightforward a way as possible. Then the computer compiles or interprets it, which is when it becomes completely unreadable. But the programmer isn't writing "code". They're just writing down a set of instructions, in another language. So maybe instead of "coding," we should look at programming as writing in another language. Because that's all programming languages are--they're just languages, where the rules of grammar must be followed much more strictly than in languages like English or Spanish.
Oh great, you say, so coding is just like learning a language, except with even more emphasis on grammar? Sounds lovely. Well yes, but there's very little emphasis on learning new vocabulary. In fact, most of the important words in most languages are actually words you already know. And the grammar rules are much clearer and completely unambiguous, especially in languages like Ruby and (from what I hear, although I haven't used it myself) Python, which were deliberately intended to be easier to use. I think Elliot is right that anyone can code. It doesn't mean everyone will find it fun. But if we stop thinking of code as "code," perhaps everyone will be able to do it.
2.15.2008
Google All-Nighter
There's a contest this Sunday and Monday, taking advantage of the long weekend, called the Google All-Nighter. You have 24 hours to write an application that uses one of Google's APIs in some way, and fits the theme, which will be announced at the start of the competition. It looks like I'll probably team up with this kid Ben I met, and I'll have to leave in the middle of it for the big ucla game, but it should be pretty fun. All this week, Google and USC UPE have been holding workshops on the various Google APIs and other technologies that may be useful in the contest, like Javascript. On Tuesday, we learned how to use the Google Maps API, so I made a little USC trivia game, where a marker appears, pointing at a building on the USC campus, and the user is supposed to guess the name of the building. I'll post a link once I get it working better. Luckily, a lot of the data I need, including a couple of really nice USC map overlays, already exists, but I didn't realize that when I started writing, so when I get some time, I'm going to rewrite my code to deal with that data, and it will be awesome. Perhaps the hardest part will be making it forgiving, so that if the user misspells something, or adds a tiny bit of extra whitespace, the game will still count it as right. I guess I could make it multiple choice instead. What I really want to do is learn the Google Calendar API since I could probably make things that are actually useful, rather than just fun, with that.
In other news, the white-space-phobically named LetMePracticeAtUSC system could be improved so much by a couple of tiny changes, and I have a feeling that, given several hours to understand the code, I could fix it. It appears I would have to learn ASP, and the source code isn't publically available, AFAIK. Which makes it a lot easier to say that kind of thing, I guess.
In other news, the white-space-phobically named LetMePracticeAtUSC system could be improved so much by a couple of tiny changes, and I have a feeling that, given several hours to understand the code, I could fix it. It appears I would have to learn ASP, and the source code isn't publically available, AFAIK. Which makes it a lot easier to say that kind of thing, I guess.
1.20.2008
Spring Semester 2008
There's no better way to celebrate surviving the first week of class than going directly into the first three-day-weekend of the semester. And no better way to spend a Sunday afternoon on such a weekend than to blog about that week. These are my classes for the semester:
MATH 445: This class is going to be all about partial differential equations and such, but so far all we've done is Fourier analysis, which allegedly is an important step towards solving PDEs. My favorite parts of this class are the professor telling us that the required textbook kinda sucks, but we have to buy it anyway, and the fact that we spent almost no time on boring administrative stuff, instead diving right into Fourier series, deriving the formula for it, and then proving it converges, all in three lectures. For the first time in a USC math class, the homework is actually required, but there's none assigned yet.
EE 101: Very low-level digital logic stuff. Binary representations of numbers, and gates, or gates, etc. The "textbook" for this class is a course reader that only cost about $18, and since everything so far is fairly trivial, I've been reading ahead about how to build multiplexers and adders and such. Seems like this is going to be an easy A.
MUEN 308: Men's choir. I did this last spring, but I've never done it in the fall. I guess this is a pattern that could continue to work: Band in the fall, choir in the spring. Anyway, the director is redoing some pieces from last semester, which puts the new people (there are about five of us) a little behind. This was fun last year and it's looking like it will be fun again this year.
PHIL 262: This is my category I GE. The title is something about "Mind and Self." Since this is a philosophy class, I was worried it would be a little like this. And it might be, but I'm very optimistic about it, at this point. The professor told us we can call him Jake. "You do NOT need to call me Professor Ross. My father was Professor Ross. Well, my father wasn't a professor, but if he had been, then he would have been Professor Ross." What's more amazing, he actually listens when students ask questions, instead of assuming he knows what they're going to ask, then going on and on about something unrelated. Again, it's only the first week, and we've already examined five alleged "proofs" for the existence of God. Not an easy A, but it should be interesting.
CSCI 101: I had already heard from my friend Greg, who took this class last semester from the same professor, that the professor wouldn't be all that great, and it's looking like it's going to be a few weeks before we get into anything remotely challenging. Eventually, I might learn something, and it looks like another easy A.
Basketball Band: Another semester of Tony Fox. Joy. This week, we recorded this Foo Fighters song for some youtube contest. Every other week is going to be pretty lame in contrast.
Concert Band: This year's show is all Broadway songs, so I couldn't really pass this up. Still, I feel like the music is way over my head, so I'm going to have to practice a lot. Apparently, I'm allowed to reserve PIC rooms since I'm officially in this class, even though I'm not a music major. This could end up being a really rewarding experience.
Overall, I'm pretty excited about this semester, and I'm fairly confident that my GPA will go up when it's all over.
MATH 445: This class is going to be all about partial differential equations and such, but so far all we've done is Fourier analysis, which allegedly is an important step towards solving PDEs. My favorite parts of this class are the professor telling us that the required textbook kinda sucks, but we have to buy it anyway, and the fact that we spent almost no time on boring administrative stuff, instead diving right into Fourier series, deriving the formula for it, and then proving it converges, all in three lectures. For the first time in a USC math class, the homework is actually required, but there's none assigned yet.
EE 101: Very low-level digital logic stuff. Binary representations of numbers, and gates, or gates, etc. The "textbook" for this class is a course reader that only cost about $18, and since everything so far is fairly trivial, I've been reading ahead about how to build multiplexers and adders and such. Seems like this is going to be an easy A.
MUEN 308: Men's choir. I did this last spring, but I've never done it in the fall. I guess this is a pattern that could continue to work: Band in the fall, choir in the spring. Anyway, the director is redoing some pieces from last semester, which puts the new people (there are about five of us) a little behind. This was fun last year and it's looking like it will be fun again this year.
PHIL 262: This is my category I GE. The title is something about "Mind and Self." Since this is a philosophy class, I was worried it would be a little like this. And it might be, but I'm very optimistic about it, at this point. The professor told us we can call him Jake. "You do NOT need to call me Professor Ross. My father was Professor Ross. Well, my father wasn't a professor, but if he had been, then he would have been Professor Ross." What's more amazing, he actually listens when students ask questions, instead of assuming he knows what they're going to ask, then going on and on about something unrelated. Again, it's only the first week, and we've already examined five alleged "proofs" for the existence of God. Not an easy A, but it should be interesting.
CSCI 101: I had already heard from my friend Greg, who took this class last semester from the same professor, that the professor wouldn't be all that great, and it's looking like it's going to be a few weeks before we get into anything remotely challenging. Eventually, I might learn something, and it looks like another easy A.
Basketball Band: Another semester of Tony Fox. Joy. This week, we recorded this Foo Fighters song for some youtube contest. Every other week is going to be pretty lame in contrast.
Concert Band: This year's show is all Broadway songs, so I couldn't really pass this up. Still, I feel like the music is way over my head, so I'm going to have to practice a lot. Apparently, I'm allowed to reserve PIC rooms since I'm officially in this class, even though I'm not a music major. This could end up being a really rewarding experience.
Overall, I'm pretty excited about this semester, and I'm fairly confident that my GPA will go up when it's all over.
12.19.2007
Entering the blogosphere...
I've recently started using Google Reader and reading a lot of blogs, mostly about science or programming, and I thought I'd try to start my own and see where I can go with it. I hope to post fairly often, and perhaps even establish a base of regular readers.
These first posts are boring, so I'll try to keep it short.
I am Tyler, better known to some as TJ. I'm a sophomore at the University of Southern California, majoring in Physics and Computer Science, unless of course I change my mind at some point down the line. I play alto sax in the Trojan Marching Band. After college, I'm not sure what I'm going to do. Keep reading and you'll find out, I guess.
Please feel free to leave comments, links you think I'd enjoy, or anything else that comes to mind, or to link to posts on this blog.
Fight on!
These first posts are boring, so I'll try to keep it short.
I am Tyler, better known to some as TJ. I'm a sophomore at the University of Southern California, majoring in Physics and Computer Science, unless of course I change my mind at some point down the line. I play alto sax in the Trojan Marching Band. After college, I'm not sure what I'm going to do. Keep reading and you'll find out, I guess.
Please feel free to leave comments, links you think I'd enjoy, or anything else that comes to mind, or to link to posts on this blog.
Fight on!
Subscribe to:
Posts (Atom)