To obtain a position as an asp.NET developer that allows me to pursue the latest technological innovations and challenges me with unique problems to solve.
Special Knowledge
Programming
C#, ASP.NET 1.1, 2.0, 3.5, MVC, ASP, VBScript, VB.NET
AJAX, CSS2, HTML, JavaScript
TSQL, Relational Database Normalization
Software
Visual Studio 2003, 2005, 2008 & 2010
Microsoft SQL Server 2000, 2005 & 2008
Biztalk Server 2006
Ubuntu Linux
IIS
Work Experience
University of Cincinnati IT - Custom Solutions
Nov 2006 - Present: Full time Applications Analyst
May 2006 - Oct 2006: Contractor Web Developer
Sept 2004 - Apr 2006: Co-Op Student Worker
Lead developer on eCurriculum
Web application that facilitated the UC's conversion from quarters to semesters and restructuring of courses and programs
Took part in the whole application development lifecycle from gathering requirements, development, testing, and maintenance
Modules included course and program creation (including approval)
Wrote the HTML & logic for the Central Login Service web page (which is used by students/faculty/staff to log in
to any web application) in ASP.NET, ASP, and Cold Fusion
Helped set development and deployment standards for the group in a way that allows anyone to pick up code, begin working, and deploy to production
One of the first in the department to learn and use .NET
Worked on many highly visible projects such as Web Registration, UC Main Page
(www.uc.edu), & New Student Orientation
Helped create a department-wide shared library that made many common functions more simple (such as error handling &
sending emails)
Secured legacy applications by switching them to trusted connections and implementing SQL Injection Prevention
Became the go-to guy for .NET questions
Created BizTalk project to transfer placement test scores from an uploaded flat file to a SQL database and Universis
(UC's student information system)
Maintained IIS 5.1 (XP Pro) and 7.5 (Windows 7) on local workstations when doing local development
Became very familiar with ways to secure web applications because Cenzic HailStorm was run on all high risk applications and any discovered vulnerabilities would need to be fixed or be proved to be a false positive