Welcome,

My name is Philip Reames and you've reached my personal website. There isn't a lot of content on this website currently; most of what's available is my blog.

I'm currently a graduate student at UC Berkeley where I work on tools - particularly programming languages - for writing reliable systems software. Before returning to school, I spent four years at FactSet Research Systems as a software developer and manager of their Portfolio Publisher suite of products. I graduated from UIUC with a BS in Computer Science. I do consulting on the side for fun and profit.

Research Interests

I'm a graduate student at UC Berkeley. My research focuses on development and maintenance of large scale systems software. I'm a programming languages guy, so some of that is going to be developing language features to make such systems easier. While language design is certainly fun, it's nearly impossible to get a new language adopted in practice. As such, any work I do on that front will have interoperability and migration as core foci.

Given the practical limitations around designing new languages, the majority of my work is going to be focused on tools for existing languages and code bases. I'm interesting in techniques for incrementally improving reliability, maintainability, and/or performance in existing code.

To me a large system is one with millions of lines of code. Any tool which does not scale to at least that scope is not practical. I am targeting languages such as C, C++, and Fortran for my work due to the number of existing systems in those languages.

I plan on discussing my ongoing work on my blog. If you're curious about what I'm working on, give it a read.

I'm just starting my graduate studies, but if you're curious about my previous publications and talks, you can check this list.

Consulting

Information on my contract programming and consulting work has been moved to its own page.

Contact Info

If you want to reach me, send me an email at: public [at] this domain. I am not always the best at responding to email, so if you want to ensure a quicker response, give me a call. (You'll have to ask me in person for my number though.) You can also reach me on LinkedIn. Don't expect quick responses on the latter though.