Clint Howarth
a Fine Software Developer in Boston's South Shore
Skills
- Project Leadership
- I've led multiple concurrent and successful small-team projects, with team members who don't overlap. I like to keep meetings short, and morale high. I like teaching quickly and getting people productive. I like shipping product.
- Software Practice
- I'm a big fan of developer responsibility, shipping features, and killing bugs. I like working with customers to get them what they need, not what they ask for. I like to write software that is functional, reliable, easy to understand, and used.
- Languages
- I prefer Python, but I'm pretty good with Java and Jython; and alright in Javascript and Perl. I play with lots of languages.
- Data Storage
- I've worked a great deal with Oracle and JSON, administered PostgreSQL, and lived with XML and file-based solutions, including many horrible biology file formats.
- Environments
- Linux. I'm a fine power user. I can work in Eclipse (or other IDEs) when required to. I've trained on AWS.
- Visualization
- Web development using Flask, and assorted relevant modern web technologies. I've done maintenance work on a large java visualization app and some wxWidgets work.
- Technical Review
- I've reviewed technical books for O'Reilly and Manning, on programming languages such as Jython and Python, development tools such as JUnit and Ant, broad subjects like Collective Intelligence, Natural Language Processing, and application platforms such as Google App Engine.
Employment History
2005 - present
Principal Software Engineer in Analysis and Annotation Engineering in the Genome Sequencing and Analysis Program
Software
Worked on a production pipeline that facilitated both manual and high-throughput, automated genome annotation. This involved intricate applications with rapidly changing heuristic analyses, reading and writing arcane bioinformatics file formats, web design, automating the software whose execution case takes five pages to explain, database tuning — all using a big server farm. When I started, our department annotated and published four genomes per year. Now, we have the ability to do the same for over five thousand a year, with better quality and consistency. My work directly helped make that transition possible. I've designed, implemented, and maintained critical components, and more.
The Broad Institute isn't a software company, so working here is like working for a very small software company with an unusually steady client. I work closely with geneticists to try to help them sort, understand, annotate, and publish their technical data. In a small company, each team member must be flexible and able to do many things at the same time, handle turnover, maintain a low cost, and an ability to deliver regularly; this is the kind of environment that I thrive in.
Part of working as a small team means working closely with our customers, in this case geneticists. It means friendly, productive relationships with people from vastly diverse backgrounds, each of whom is very, very smart and know where they want to be — but not how to get there. My job is not just listening to what they say they want, but learning the nature of the goal and understanding what they need. This is one of my favorite parts of this job.
Wrote GenePidgin, an open-source suite of Python tools related to gene naming. I've presented this work at a Cold Spring Harbor Labs bioinformatics conference.
Biology
The Broad Institute is a hotshot research lab, which means in part it's hard to nail down things like departments. Teams, initiatives, and organizations are fluid. It's easier to describe the work I've been involved in:
- Genomic Sequencing Center for Infectious Diseases.
- Fungal Genome Initiative
- Human Microbiome Project
- Sequencing and annotation effort in response to the recent European E. coli outbreak
My software has assisted in annotating many horrible infectious diseases, including tuberculosis, malaria, influenza, the dengue virus, tuberculosis, Staphylococcus Aureus (of staph infection fame), HIV, and many more. Of course, I'm just working on their source code, but the compiled executables are troublesome.
From my work in annotation (and naming), I've been published as a contributing author in a few journals, most notably in Science magazine ("A Catalog of Reference Genomes from the Human Microbiome"), related to the Human Microbiome Project. A few other papers as well. For better or worse, I'm also listed as part-author on more than one million genes.
The automated classification and tagging of coding DNA is cool.
1998 - 2002
Software Engineer
Software Group Leader
I worked in the tools and test group, eventually becoming a technical lead. The project's goal was to cause the company's shipping products to fail locally rather than during the on-site company installs. My proudest point in this group was to lead the development of the large, multiple-developer, readable Perl application which was used and extended by software testers who were not software engineers.
Our group was distributed across two major locations, and we had frequent collaborations with developers and testers around the world. I learned how to work and lead remotely.
I went on to serve as project lead for a group who reverse engineered the undocumented communication protocol at the center of our company's core product; document it, write a system that would help us isolate, test, and deliver those components as independent software units. It sounded like a good idea at the time.
Independent Contractor
2002 - 2005
Chief Software Pack Mule
I was a self-employed contractor who played backup infield for a few software projects. Every contract I worked on was: "This is behind schedule and we need to get something done." This wasn't the most interesting work I've ever done, but the lack of steady income was exciting.
1996 - 1998
Parts Engineer
Software Engineer
Began as a mechanical engineer, where I made sure that the given parts in radar and missile systems wouldn't corrode each other in surprising ways. I transitioned to being a software engineer, where I worked on a document repository system.
Education
May of 2001: I received my MS in Computer Science from Worcester Polytechnic Institute. I enjoyed language design and parsing most of all. I went to school at night while I worked, and it took just short of five years.
May of 1996: I received my BS in Mechanical Engineering with a specialization in Material Science from Worcester Polytechnic Institute. I've largely forgotten the technical details, but I very clearly remember the beauty of particle flow, and how the materials discovery process for every human implant seems to end in either a titanium alloy or polymethylmethacrylate.
Links
- Personal website, with contact information.
- GenePidgin, a gene naming suite I wrote.
Interests
My kids and family, books, software, games of all kinds, and fiction writing (not on this resume).
References
Available by request.