Dollhouse at the NSA
Over the previous summer, I rediscovered Angel and Buffy the Vampire Slayer and watched some old episodes at hulu. (And let me just say, think you hulu for throwing my resume aside so nonchalantly after you read the second line. Electrical engineering major I may be, but I know RoR, SQL, Unix C, and just as much crap as any other CS guy out there.) Anyhoo, some of you Joss Wheedon fans may have heard that Wheedon has a whole new series out by the name of Dollhouse, not nearly as popular as some of his other shows, but still pretty cool. Or at least it started out cool, lately, its just been getting a little kinky and weirdish.
But I digress, I'm not here to discuss the merits of Dollhouse (I'll save that for another time) but rather to point out a few odd little facts about episode 9 (A Spy in the House of Love). Theres a part in episode 9 where Sierra knocks out some Japanese chick on a train, steals her identity, and walks into some big NSA facility. Now as I was watching Sierra traipse through the sparse halls of the NSA, I had a strange feeling of deja vue. But it wasn't until the part where she checks in with a security guard to access some giant government database, that I realized what I was seeing: the building that they used for the NSA in episode 9 was none other then UCLA's infamous Boelter Hall, (aka my third home (the first being my real home, and the second being my dorm room)) and the room that Sierra and the security guard were in was none other then Boelter 6426. I know Boelter quite well, having spent far too much of my time there (or rather, here, since I'm in Boelter right now), and I know the building's appearance right dsown to the ugly water fountains, square black digital clocks, distinctive green flecked staircases, and blocky gold door numbers.
There are of course people that still doubt me, I know. So go to hulu and watch the section from episode 9 again, and then look at these pictures that I took at 7:30 on Monday morning.
Request for a Change
Hauling out my change of major request essay...
Prior to UCLA my knowledge of anything vaguely associated to the field of electrical engineering was essentially nil, so it should come as no surprise when I say that I cannot for the life of me begin to remember why I chose electrical engineering as a major. And now, the more electrical courses I take, the more tiresome I find the subject matter to be. So the question I should be answering isn't "why do I want to change majors," but rather, "why did I wait till now to change?"
Over the last two years, I have trudged my way through the required introductory math and physics courses, never particularly excited by the material but always telling myself that it was going to get better when I reached the EE courses and that then, everything would be worth it. So it came as somewhat of a surprise to me, that I found the electromagnetics in EE 1 to be as unexciting as the materials in all the prerequisite courses. But after having spent the better part of two quarters convincing myself that "it was going to get better," I continued to drag myself through another uninteresting class, and during my second year, I proceeded to take EE 2, 16, 116L, 10, and 102, continually hoping that things would get better. Happily, they did.
It was during second quarter of this year while I was doing EE homework one night, that I realized that the only EE classes that I have ever actually enjoyed were the multi-departmental classes (16, and 116L) shared by the EE and CS departments, and that CS 35L (informally called “intro to Linux) was without a doubt my most enjoyable class ever. Shocked by my newfound epiphany, I stood up from my desk and declared to my roommates that I did not like electrical engineering and that instead, computer science was the field for me. My roommates were unsurprised by my sudden realization, saying that they had always noticed that I liked computers more than electrical engineering, and that the energetic mannerisms that I adopted when talking about Linux or computer architecture deeply contrasted the dull and tiresome attitude I exhibited when I approached my EE homework. Indeed, during my past two years at UCLA, I have probably spent as much time tinkering with Linux and reading essays like Neal Stephenson’s In the Beginning was the Command Line, and Fred Brooks’ The Mythical Man-Month: Essays on Software Engineering, as I have dedicated to my EE classes.
I am, however, not choosing to switch into computer science, but rather computer science and engineering since my enthusiasm for all things computer related extends below (so to speak) the software level. Now lately, numerous people have pointed out to me the similarities between electrical engineering with the computer engineering option, and computer science and engineering, and asked why I simply do not stay with EE CE. A question to which I can only respond to by saying that the differences between the two majors is quantitatively quite small (That is to say, the difference in course requirements between the two is almost negligible.), but that the content of the almost negligible difference is quite significant to me; I would much rather take a compiler class rather than another electromagnetics course.
Having now realized what subjects I enjoy the most, I am loath to continue in a major I find no pleasure in. Though perhaps over-dramatic, it would not be inaccurate to say that this change of major could have the potential to dictate my future happiness.
Three Weeks of Biking
Because I've had these numbers on a post-it-note for almost a month now...
Distance Traveled: 16.529 miles
Elapsed Time: 1 hour and 17 minutes
Average Speed: 12.9 MPH
Max Speed: 30.4 MPH
Distance Traveled: 10.18 miles
Elapsed Time: 44 minutes and 39 seconds
Average Speed: 13.7 MPH
Max Speed: 29 MPH
Distance Traveled: 10.692 miles
Elapsed Time: 49 minutes and 51 seconds
Average Speed: 13.2 MPH
Max Speed: 29.7 MPH
Daily Biking
Numbers from last week...
Elapsed time: 44 minutes and 20 seconds
Distance traveled: 9.542 miles
Average Speed: 12.9 MPH
Max Speed: 28.5 MPH
I guess alot of high schools have been on break the past week, and as a result we've had a lot of tour groups roaming campus and a lot more cars driving around. Last week, I got pretty fed up with Asian high schoolers and their parents that drive at insanely slow speeds, so I started passing cars on my way to class. Probably not the smartest thing to do since the streets around the campus are single lanes.
Weekly Biking
Numbers from my bike computer for this past week of riding to class.
Distance Traveled: 9.313 miles
Average Speed: 13.5 MPH
Max Speed: 31.5 MPH
Time Traveled: 41 minutes and 22 seconds
So pretty average stats.
I want a real road bike. I'm not saying my bike is bad (beause its not, I like my antique KHS), I just want a bike that doesn't weigh 32 pounds and have a knocking headset. Sometimes when I have some extra time between classes I like to check out the bikes locked up at a nearby bike rack. Generally, the only bikes I see are antique Schwinn road bikes, shiny Huffy mountain bikes with crap-tastic components, and a few home-made fixies (some of them quite nice) that seem to be all the rage these days. But every now and then I'll see a good road bike thats worth admiring: a Trek 1000 or 1.2, Giant OCR3, Jamis Ventura Sport, or a Fuji Newest 2.0. On a few occasions, I might see something really expensive, like a full carbon fiber Fuji, or a fancy Scattante racing bike. And seeing a nice road bike just makes me want to get a road bike even more. Unfortunately, I'm not winning to fork over the several hundreds of dollars that I would need to make such a purchase. Still, I like to dream.
Anyways, back to studying. At least my head doesn't feel like its going to explode, like it did last night.
Run Run Run
This past quarter, I've been trying to go to the track at least a few times a week and run at least two miles. Up until last week, I didn't bother to time myself, figuring that I was running "fast enough." I was surprised to find out after a two mile run on the track, that I was averaging almost eight minutes a mile. Not good. Not good at all.
So the next night that I went running, I pushed myself a little harder and managed to average about seven minutes and thirty seconds per mile (for three miles) which is significantly better, but still not as good as I would have liked; I could manage six minutes and fifteen seconds fairly regularly when I was in high school.
Now today (the day of my two killer finals) I wasn't planning on doing any running, and was hoping instead that after my two finals over, I could just grab something quick to eat and then be able to go to sleep early. And after my last final of the day got out, this seemed like a great idea, as my head was pounding and I was having trouble focusing and keeping my eyes open. But the line for food was ridiculously long and my lack of recent physical activities was starting to make me feel like a fatty, so I dropped my notes in my room and ran to the track, where I proceeded to run a mile at high speed (or at least my highest speed) and then do twenty minutes or so of stairs. My mile time for today was six minutes and forty seconds, significantly faster then last weeks, but still on the slow side. Lets hope it gets better.
Muxing the Clock
My final lab project for my digital design class is basically a free-for-all, design your own project. The project that my lab partner and I have chosen includes displaying a countdown timer on four seven-segment displays. We wanted to have the displayed value decrementing once every second, and we also wanted to make it so that the user could pause the counter and change the displayed value with push-buttons. The only problem with this scenario is that since the counters are connected to a 1Hz clock, the speed at which a user can set the displayed values is also 1Hz. This is bad, as we quickly found out, because it is unbearably slow, especially when you want to set a value of 100. So I came up with what I thought was a great idea: mux the clock input on the counters and then use the "set" button as the mux selector. If one of the mux inputs was then a 1Hz signal and the other a 4Hz clock, we'd be able to switch back and forth between the clock signals at will. Like most things I come up with, I thought it was a brilliant idea. And like most of my ideas, it died in the implementation phase.
The results of muxing the clock signal resulted in a buggy counter that would often spaz out whenever the "set" button was pressed. The clock would settle back into a regular pattern after one or two cycles, but the damage would have already been done: nobody wants to have a clock timer that explodes in a mad counting rush every time you press a button. I believe the reason for the bugginess is due to the fact that the rising and falling edges of the 1Hz and 4Hz clock do not coincide in time perfectly, and so when the mux switches clocks the counters see a clock signal that fluctuates at a weird rate for a brief interval.
And one more thing that I've learned in digital design lab: Xilinx software is total crap. Project files get regularly corrupted, the program crashes at odd times, compiling takes so long that I could probably wire the design by hand faster, and the auto-wirer was designed by a disgruntled employee on crack. The quiet murmuring that fills the digital design lab room is frequently broken by loud exclaimations of "I hate this software," "I will find the engineer that designed this auto-wirer and kill him," "#$(@*$&(@!***#&!!" and other such phrases (generally not by me). I could maybe understand the total crappiness if Xilinx's ISE was a beta version and avaliable for free, but its not. We're running version 9.2 (somewhere around there) and the school paid buttloads for Xilinx's POS software. Please don't even bother with Xilinx.