<?xml version="1.0" encoding="UTF-8"?>
<speaker>
  <biography></biography>
  <company></company>
  <company-website></company-website>
  <id type="integer">2791</id>
  <linkedin-url>http://www.linkedin.com/in/jasonharris</linkedin-url>
  <location>Brighton, MI</location>
  <name>Jay Harris</name>
  <personal-website>http://www.cptloadtest.com</personal-website>
  <title>Software Consultant</title>
  <twitter-username nil="true"></twitter-username>
  <average-rating type="decimal">4.55</average-rating>
  <avatar-url>/avatars/2791/thumb/stream.12856.0</avatar-url>
  <talks type="array">
    <talk>
      <created-at type="datetime">2009-12-10T16:33:31+00:00</created-at>
      <event-id type="integer" nil="true"></event-id>
      <id type="integer">1887</id>
      <info>Does your team spend days integrating code at the end of a project? Does your team spend more time fixing bugs than writing code? Does it seem like something breaks every time you download the latest code? Continuous Integration can help. Using Continuous Integration will eliminate that end-of-project integration stress, and at the same time will make your development process easier, simpler, and with fewer surprises. But Continuous Integration is more than just a tool like CruiseControl.Net; it is a full development process designed to reduce bugs, increase visibility of project status throughout your team, and to streamline code deployments to QA or to your client. Find out what Continuous Integration is all about, and what it can do for you.</info>
      <location>History, Arts, &amp; Libraries Building, 702 W. Kalamazoo St, Lansing, Michigan 48915</location>
      <series-id type="integer" nil="true"></series-id>
      <slides-url>http://www.slideshare.net/jayharris/continuous-integration-more-than-just-a-toolset</slides-url>
      <slideshare-key>continuous-integration-more-than-just-a-toolset-090630074039-phpapp01</slideshare-key>
      <talk-url></talk-url>
      <title>Continuous Integration: More than just a toolset</title>
      <updated-at type="datetime">2009-12-10T16:33:31+00:00</updated-at>
      <when type="datetime">2009-12-10T14:00:00+00:00</when>
      <average-rating nil="true"></average-rating>
    </talk>
    <talk>
      <created-at type="datetime">2009-11-19T00:23:20+00:00</created-at>
      <event-id type="integer" nil="true"></event-id>
      <id type="integer">1847</id>
      <info>Does your team spend days integrating code at the end of a project? Does your team spend more time fixing bugs than writing code? Does it seem like something breaks every time you download the latest code? Continuous Integration can help. Using Continuous Integration will eliminate that end-of-project integration stress, and at the same time will make your development process easier, simpler, and with fewer surprises. But Continuous Integration is more than just a tool like CruiseControl.Net; it is a full development process designed to reduce bugs, increase visibility of project status throughout your team, and to streamline code deployments to QA or to your client. Find out what Continuous Integration is all about, and what it can do for you.</info>
      <location>Michigan State University, 1235 Anthony Hall, East Lansing, MI</location>
      <series-id type="integer" nil="true"></series-id>
      <slides-url>http://www.slideshare.net/jayharris/continuous-integration-more-than-just-a-toolset</slides-url>
      <slideshare-key>continuous-integration-more-than-just-a-toolset-090630074039-phpapp01</slideshare-key>
      <talk-url></talk-url>
      <title>Continuous Integration: More than just a toolset</title>
      <updated-at type="datetime">2009-11-19T00:23:20+00:00</updated-at>
      <when type="datetime">2009-11-19T18:00:00+00:00</when>
      <average-rating nil="true"></average-rating>
    </talk>
    <talk>
      <created-at type="datetime">2009-09-10T21:53:56+00:00</created-at>
      <event-id type="integer" nil="true"></event-id>
      <id type="integer">1454</id>
      <info>When a request occurs for a ASP.Net page, the response is processed through a series of events before being sent to the client browser. These events, known as the Page LifeCycle, are a complicated headache when used improperly, manifesting as odd exceptions, incorrect data, performance issues, and general confusion. It seems simple when reading yet-another-book-on-ASP.NET, but never when applied in the real world. In this session, we decompose this mess, and turn the LifeCycle into an effective and productive tool. No ASP.NET MVC, no Dynamic Data, no MoroRail, no technologies of tomorrow, just the basics of ASP.NET , using the tools we have available in the office, today.</info>
      <location>New Horizons, 4488 W Bristol Rd, Flint, MI?</location>
      <series-id type="integer">52</series-id>
      <slides-url>http://www.slideshare.net/jayharris/dev-basics-the-aspnet-page-life-cycle</slides-url>
      <slideshare-key nil="true"></slideshare-key>
      <talk-url>http://www.cptloadtest.com/Speaking.aspx</talk-url>
      <title>Dev Basics: The ASP.NET Page Life Cycle</title>
      <updated-at type="datetime">2009-09-10T21:53:56+00:00</updated-at>
      <when type="datetime">2009-09-10T18:00:00+00:00</when>
      <average-rating type="decimal">4.3</average-rating>
    </talk>
    <talk>
      <created-at type="datetime">2009-07-08T18:29:35+00:00</created-at>
      <event-id type="integer">139</event-id>
      <id type="integer">1248</id>
      <info>When a request occurs for a ASP.Net page, the response is processed through a series of events before being sent to the client browser. These events, known as the Page LifeCycle, are a complicated headache when used improperly, manifesting as odd exceptions, incorrect data, performance issues, and general confusion. It seems simple when reading yet-another-book-on-ASP.NET, but never when applied in the real world. In this session, we decompose this mess, and turn the LifeCycle into an effective and productive tool. No ASP.NET MVC, no Dynamic Data, no MoroRail, no technologies of tomorrow, just the basics of ASP.NET , using the tools we have available in the office, today.</info>
      <location nil="true"></location>
      <series-id type="integer" nil="true"></series-id>
      <slides-url></slides-url>
      <slideshare-key nil="true"></slideshare-key>
      <talk-url></talk-url>
      <title>Dev Basics: The ASP.NET Page Life Cycle</title>
      <updated-at type="datetime">2009-07-08T18:29:35+00:00</updated-at>
      <when type="datetime">2009-08-01T09:00:00+00:00</when>
      <average-rating nil="true"></average-rating>
    </talk>
    <talk>
      <created-at type="datetime">2009-06-14T02:14:05+00:00</created-at>
      <event-id type="integer">131</event-id>
      <id type="integer">1191</id>
      <info>When a request occurs for a ASP.Net page, the response is processed through a series of events before being sent to the client browser. These events, known as the Page LifeCycle, are a complicated headache when used improperly, manifesting as odd exceptions, incorrect data, performance issues, and general confusion. It seems simple when reading yet-another-book-on-ASP.NET, but never when applied in the real world. In this session, we decompose this mess, and turn the LifeCycle into an effective and productive tool. No ASP.NET MVC, no Dynamic Data, no MoroRail, no technologies of tomorrow, just the basics of ASP.NET, using the tools we have available in the office, today.</info>
      <location></location>
      <series-id type="integer" nil="true"></series-id>
      <slides-url>http://www.cptloadtest.com/content/binary/Dev-Basics-ASP-NET-Page-Life-Cycle.pptx</slides-url>
      <slideshare-key nil="true"></slideshare-key>
      <talk-url></talk-url>
      <title>Dev Basics: The ASP.NET Page Life Cycle</title>
      <updated-at type="datetime">2009-06-30T03:20:08+00:00</updated-at>
      <when type="datetime">2009-06-26T13:00:01+00:00</when>
      <average-rating type="decimal">4.61</average-rating>
    </talk>
    <talk>
      <created-at type="datetime">2009-06-14T02:20:19+00:00</created-at>
      <event-id type="integer" nil="true"></event-id>
      <id type="integer">1192</id>
      <info>Does your team spend days integrating code at the end of a project? Continuous Integration can help. Using Continuous Integration will eliminate that end-of-project integration stress, and at the same time will make your development process easier. But Continuous Integration is more than just a tool like CruiseControl.Net; it is a full development process designed to bring you closer to your mainline, increase visibility of project status throughout your team, and to streamline deployments to QA or to your client. Find out what Continuous Integration is all about, and what it can do for you.</info>
      <location>Microsoft Offices, 1000 Town Center Dr., Suite 1930, Southfield, MI 48075</location>
      <series-id type="integer">49</series-id>
      <slides-url></slides-url>
      <slideshare-key nil="true"></slideshare-key>
      <talk-url></talk-url>
      <title>Continuous Integration: More than just a toolset</title>
      <updated-at type="datetime">2009-06-14T02:20:19+00:00</updated-at>
      <when type="datetime">2009-01-21T18:30:01+00:00</when>
      <average-rating nil="true"></average-rating>
    </talk>
    <talk>
      <created-at type="datetime">2009-06-15T12:32:53+00:00</created-at>
      <event-id type="integer">133</event-id>
      <id type="integer">1193</id>
      <info>oes your team spend days integrating code at the end of a project? Continuous Integration can help. Using Continuous Integration will eliminate that end-of-project integration stress, and at the same time will make your development process easier. But Continuous Integration is more than just a tool like CruiseControl.Net; it is a full development process designed to bring you closer to your mainline, increase visibility of project status throughout your team, and to streamline deployments to QA or to your client. Find out what Continuous Integration is all about, and what it can do for you.</info>
      <location nil="true"></location>
      <series-id type="integer" nil="true"></series-id>
      <slides-url></slides-url>
      <slideshare-key nil="true"></slideshare-key>
      <talk-url></talk-url>
      <title>Continuous Integration: More than just a toolset</title>
      <updated-at type="datetime">2009-06-15T12:32:53+00:00</updated-at>
      <when type="datetime">2009-01-08T16:50:01+00:00</when>
      <average-rating nil="true"></average-rating>
    </talk>
  </talks>
</speaker>
