I joined Comcast Central Division App Dev team for the great opportunity to work and gain experience with many great technologies. I create, develop, maintain, and deploy a variety of SSIS projects. Extensive SSIS script module experience automating emails, calling web api's, staging and manipulating data for applications from many types of sources. Visual Studio SSIS is very powerful. I create, develop, and deploy and maintain many web api projects. Utilizing Microsoft new web api architecture and newtonsoft json, it's possible to create very scalable and extremely easy to read and maintain web services. I have gained an incredible amount of IIS experience here at Comcast by deploying and maintaining many web applications and web services to multiple IIS farms using load balancing and strategies to test single machines in each farm along with VIP / Load Balancer. This knowledge includes extensive debugging and knowledge of IIS logs and failed trace logging and analysis. I've had the opportunity to create many MVC web applications that use Entity Framework for the data layer. I'm still not 100% sold on EF, but it's pretty powerful once you learn all of it's quirks and bugs :) MVC of course is a great architecture for building robust applications. I'm recently working a project that utilizes jqGrid and a single page style application. I've learned a lot about jqGrid and am seeing it's potential when used correctly. This single page style application utilizes OData for it's data requirements. This was a technology I had to pick up quickly. Sharepoint is another area I've gained much experience here at Comcast. I discuss site requirements with internal clients and build their Sharepoint sites. I've also had the opportunity to create application pages / web parts and learned how to deploy WSPs to sharepoint farms and push out upgrades to Sharepoint sites and farms. Every day is an opportunity to learn something new and I'm having a great time :)

A main responsibility for me has been the evaluation, architecture, development, and testing of third party interfaces into our product. This involves maintaining relationships with third party vendors, analyzing their documentation and services, discussing workflow and integration points from customer systems, estimates on development and testing, and finally developing the interface. I work with a great team of folks that are dedicated to streamlining interface development and architecture, and ensuring a painless integration and go live for customers wanting to interface with third party vendors. It can be a very painful process when having 3 or 4 stakeholders in a project. By using agile development principals and ensuring all parties understand and assume their responsibilities, painless and successful go lives of major interface additions are a reality, I promise :)Another area of responsibility and development during this time frame was statistical reporting for Insurance carriers. Developed processes and methodologies for reporting to the 3 main stat bureaus. This included code to create stat files to be sent to each bureau, real time analysis of data during processing to give details on errors or incorrect data combinations, and guaranteed QUICK processes to ensure all losses and premiums being reported are accurate per customers system data. All of this PRIOR to running data through stat bureaus own supplied edit packages to find data errors. Working statistical reporting with the 3 main bureaus and folks in house has given me a much broader understanding of the various reporting buckets of claims / losses / and premiums that need to be reported each year. This work involved meetings and relationships with all bureaus so they could help me interpret their wordings and rules. If you ever tried to read a stat bureau's documents and manuals, you know what a fun time that can be :)

Responsibilities changed as progressing to a team lead title. The working of larger scale product enhancements for customers continued to be a main responsibility alongside new management responsibilities. Responsibilities in this time period involved managing the architecture, development, communication with customers for larger groups of developers and business analysts on various projects. A main focus for me was having a deep understanding of the strengths of all developers and develop processes to take advantage of everyone's strengths on the various teams. Another main responsibility I took on was to ensure communication was very positive and existed between all stake holders. Building good team work and a team environment on each team was a big reason for the successes we had. This is building internal teams across testers and developers and business analysts. This also ensured the team work and communication with the customers was very positive and team spirit minded. To do this, I would sit in the weekly team meetings with the customer and development and help facilitate the meeting and act as a bridge between the technical folks and the customers. If you look at the agile processes of today and how they are explained and documented, 85% of the standard explanations and processes is how I handled the various teams and communication across stakeholders. I am a huge believer in most of the agile methodologies, while adding in some processes of my own that have proven very successful.

As a senior developer, responsibilities changed and grew rapidly again. Working larger scale product enhancements for customers was a main responsibility that existed along side all others. This involved discussing requirements with customer, ensuring workflow and architecture was understood by all parties involved ( especially customer and development and internal testing were in sync ). My main responsibilities in this area would then change to coding the project, testing and ensuring all parties understood and tested correctly, work with customer on changes being requested after initial testing. This would involve estimates on changes and assisting customer with decisions to expand scope or keep current scope based on analyzing the cost / estimates / value / risk of adding more to the current scope. Looking back now, I realize I was using many agile development principles. This was before there were books and fancy names around some great practices :)

Started my professional career at this great company. Responsibilities changed and grew very rapidly in my first 2 year period with the company. Here is a good breakout trying to maintain some correct order: defect work, worked reports with customers and business analyst, perform full rate changes for customers including all rating code and validations and workflow changes, created processes and became point of escalation for developer assistance, worked database special projects to assist customers with data corrections, started to sit with customers to talk through rate filing requirements to ensure all gaps were covered from a development perspective to ensure quality and on-time system deliveries.