 |
|||||||||||||
 |
|
 |
|||||||||||
 |
 |
||||||||||||
Well, hey every one! I graduated (again) in May. Now I am a Master of Computer Science. That took way to much time. I really enjoyed the work, but I feel like it drained away some aspect of my energy. This may be why I haven't updated this blog in quite sometime. I doubt any one even reads it any more. So, what have I been up to? Well, immediately after graduating, I took about two weeks off to play video games pretty much constantly (Resident Evil 4: Wii Edition-- why is it so much more fun to blow up zombies by pointing at them?). That was my version of a vacation. Meanwhile, I've continued to work on my Master's Project, even though I'm technically graduated. For those of you who are unaware, it is a little tool that analyses the heap structure of a program to try to learn invariants, and flags violations of those invariants as possible bugs. Well, I achieved a basic proof of concept, but there is always more to do. So I've spent a lot of my time sitting at my little graduate student desk, even though in some technical sense I am no longer a graduate student. No one seems to want to kick me out. Eventually, I'm going to need some one to pay me though. I've been slowly looking for work. Lots of recruiters call me. I go on interviews. For the most part, the jobs are totally boring. Perhaps I am spoiled. But maybe I just know myself. If I take a boring job, I'll probably just stop showing up in about six months and then starve to death. I feel like I may as well get the starving to death out of the way upfront. Any one know about any interesting computer programming jobs? Perhaps something a little mathy? Maybe something that will let me learn more about compilers? Or some one who will pay me to learn Haskell? Actually, while I am on the topic, here is a not necessarily inclusive list of things I am interested in: Parallel Computing: Doing things in parallel makes easy problems hard, and hard problems insane. Every one gripes about this, but no one has any good ideas what to do about it. How do effectively program massively parallel machines with out making the programmer go mad? (or how do we make the programmer not mind being mad...) Computational Geometry: I studied computational geometry quite a bit. There are a number of interesting problems here, but the academic side seems to mostly focus on reducing the asymptotic complexity, ignoring the practicality of actually programming the algorithms. I'd love to design and/or implement some algorithms in the field. Programming Languages: The ways a program can be expressed in a variety of mostly equivalent languages is pretty amazing. Even more amazing is how much _better_ expressed some things are in some languages. I'd love to work on problems involving programming languages. Making high level languages more efficient, for example. Or improving correctness. Or making parallel computing easier :) Programming Tools: There is more to programming than just the language. The whole tool set has an enormous effect. For example, can we use more machine learning to improve debugging? Can we instrument a binaries to send useful feed back to the developer with out slowing down the program (much)? Hmm... now how to actually do some of these things and not starve. Does any one else find having to eat to be incredibly annoying? Maybe I should go back to graduate school. Post a comment in response: |
| © 2002-2008. Blurty Journal. All rights reserved. |