I mostly work on the human aspects of code editors. My process is: observe actual developers to understand their problems -> design and build a tool to overcome

I mostly work on the human aspects of code editors. My process is: observe actual developers to understand their problems -> design and build a tool to overcome a problem -> evaluate the tool with real users. For example, we observed devs spending a lot managing tabs in Eclipse/VS and scrolling through files. I built a code editor that does away with tabs and instead has a novel interface for navigating code. Brief summaries of my projects and all of my publications can be found on my website: http://austinhenley.com/ http://austinhenley.com/. I'm interested in many different areas of SE and would be happy to let a motivated student explore their interests.