Jan K. Labanowski, Ph.D, Cover Letter
Jan K. Labanowski
2715 Westmont Blvd
Columbus, OH 43221
tel. 614-487-8373(h)
Email: ,
Cover Letter
In 2005 I decided to work as a software developer rather than to continue on the academic development path. I realized that I like working with computers more than manage others who do the actual programming and have all the fun. Simply, to restrict myself to the expert knowledge of Power Point and MS Word was not an acceptable option for me. Since that time I worked with organizations that use extensive, distributed and complicated informational infrastructure. But I also run a small project from my basement ( as a hobby (though it pays for itself with ads) out of sentiment to my academic years. It is a discussion forum and a Web based informational resource for computationally savvy chemists, my former colleagues from all over the world.
I have a very broad computer background, and everything I did since my college years, be it research or contracts, involved a significant computer processing element. This actually makes a task of writing my resume quite hard, since it always looks like a random list of disparate assignments. I cannot escape the fact that I always tried to use the latest tools or technologies in my work. I also have an important advantage compared to my younger colleagues, since in most cases I did something similar before. I know both the legacy stuff and the latest stuff, and in fact, they are usually not that different after you worked for over 15 years in the leading supercomputer center. The new stuff is just an old stuff that became a cheap commodity.
Most recently I was working mainly with large perl projects using large databases and Web (front and back end). A a few years ago my focus was Java for XML and document processing. Some of this work was for banking/insurance, credit card payment industry and employee management where attention to transaction security and reliability is paramount. Before that I worked with one of the largest publishers of scientific literature where the emphasis is on accuracy and timely processing. So I am slightly biased and if I err, it is on the side of quality and reliability rather than speed of delivering poor quality software to beat the project deadlines.
You can find details and scope of my work in the long version of my CV. I am a quick learner and even quicker to refresh my memory on things that I once did. I work well with a team and alone, and value the quality of the work that I do. I also may over-comment and over-document my work. But it may not be that bad, since I am rarely asked to remove my comments when my code is reviewed. It is never a game of job security by obscurity for me, but a satisfaction of the job well done.
Thank you for your interest.
Jan Labanowski