ºÝºÝߣshows by User: ruthlesshelp / http://www.slideshare.net/images/logo.gif ºÝºÝߣshows by User: ruthlesshelp / Wed, 18 Mar 2015 08:45:10 GMT ºÝºÝߣShare feed for ºÝºÝߣshows by User: ruthlesshelp Overview of .NET Best Practices /slideshow/overview-of-net-best-practices/45990241 overviewofdotnetbestpractices20150317-150318084510-conversion-gate01
An overview of .NET best practices.]]>

An overview of .NET best practices.]]>
Wed, 18 Mar 2015 08:45:10 GMT /slideshow/overview-of-net-best-practices/45990241 ruthlesshelp@slideshare.net(ruthlesshelp) Overview of .NET Best Practices ruthlesshelp An overview of .NET best practices. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/overviewofdotnetbestpractices20150317-150318084510-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> An overview of .NET best practices.
Overview of .NET Best Practices from Stephen Ritchie
]]>
635 1 https://cdn.slidesharecdn.com/ss_thumbnails/overviewofdotnetbestpractices20150317-150318084510-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Lightweight Documentation /slideshow/lightweight-documentation/45701658 lightweightdocs-20150311-150311065158-conversion-gate01
Lightweight Documentation presentation to the DC Agile User Group meeting 11-Mar-2015]]>

Lightweight Documentation presentation to the DC Agile User Group meeting 11-Mar-2015]]>
Wed, 11 Mar 2015 06:51:58 GMT /slideshow/lightweight-documentation/45701658 ruthlesshelp@slideshare.net(ruthlesshelp) Lightweight Documentation ruthlesshelp Lightweight Documentation presentation to the DC Agile User Group meeting 11-Mar-2015 <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/lightweightdocs-20150311-150311065158-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Lightweight Documentation presentation to the DC Agile User Group meeting 11-Mar-2015
Lightweight Documentation from Stephen Ritchie
]]>
617 1 https://cdn.slidesharecdn.com/ss_thumbnails/lightweightdocs-20150311-150311065158-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Agile Engineering Sparker GLASScon 2015 /slideshow/agile-engineering-sparker-20150128/44005701 agileengineeringbestpractices-20150128-150128122139-conversion-gate02
Government Lean-Agile Software & Systems Conference (GLASScon) 2105 Sparker presentation on Agile Engineering Best Practices.]]>

Government Lean-Agile Software & Systems Conference (GLASScon) 2105 Sparker presentation on Agile Engineering Best Practices.]]>
Wed, 28 Jan 2015 12:21:39 GMT /slideshow/agile-engineering-sparker-20150128/44005701 ruthlesshelp@slideshare.net(ruthlesshelp) Agile Engineering Sparker GLASScon 2015 ruthlesshelp Government Lean-Agile Software & Systems Conference (GLASScon) 2105 Sparker presentation on Agile Engineering Best Practices. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agileengineeringbestpractices-20150128-150128122139-conversion-gate02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Government Lean-Agile Software &amp; Systems Conference (GLASScon) 2105 Sparker presentation on Agile Engineering Best Practices.
Agile Engineering Sparker GLASScon 2015 from Stephen Ritchie
]]>
672 1 https://cdn.slidesharecdn.com/ss_thumbnails/agileengineeringbestpractices-20150128-150128122139-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
DevOps Requires Agility /slideshow/devops-requires-agility/40525880 devopsagility20141021-141021013113-conversion-gate02
DevOps emphasizes communication, collaboration and integration between the developers and the operations folks. Some teams figure out DevOps on their own, but most struggle in their effort to implement DevOps practices, such as, automated builds, automated tests, automated deployments, continuous integration, and continuous delivery. Many consider these practices essential for the success of any software development project, but they require a new way of thinking. In other words: DevOps requires agility.]]>

DevOps emphasizes communication, collaboration and integration between the developers and the operations folks. Some teams figure out DevOps on their own, but most struggle in their effort to implement DevOps practices, such as, automated builds, automated tests, automated deployments, continuous integration, and continuous delivery. Many consider these practices essential for the success of any software development project, but they require a new way of thinking. In other words: DevOps requires agility.]]>
Tue, 21 Oct 2014 01:31:13 GMT /slideshow/devops-requires-agility/40525880 ruthlesshelp@slideshare.net(ruthlesshelp) DevOps Requires Agility ruthlesshelp DevOps emphasizes communication, collaboration and integration between the developers and the operations folks. Some teams figure out DevOps on their own, but most struggle in their effort to implement DevOps practices, such as, automated builds, automated tests, automated deployments, continuous integration, and continuous delivery. Many consider these practices essential for the success of any software development project, but they require a new way of thinking. In other words: DevOps requires agility. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/devopsagility20141021-141021013113-conversion-gate02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> DevOps emphasizes communication, collaboration and integration between the developers and the operations folks. Some teams figure out DevOps on their own, but most struggle in their effort to implement DevOps practices, such as, automated builds, automated tests, automated deployments, continuous integration, and continuous delivery. Many consider these practices essential for the success of any software development project, but they require a new way of thinking. In other words: DevOps requires agility.
DevOps Requires Agility from Stephen Ritchie
]]>
1017 1 https://cdn.slidesharecdn.com/ss_thumbnails/devopsagility20141021-141021013113-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Continuous Integration - NoVA CodeCamp 2014-10-11 /slideshow/nova-codecamp-cintegration20141011/40232287 continuousintegration20141011-141014002919-conversion-gate01
]]>

]]>
Tue, 14 Oct 2014 00:29:19 GMT /slideshow/nova-codecamp-cintegration20141011/40232287 ruthlesshelp@slideshare.net(ruthlesshelp) Continuous Integration - NoVA CodeCamp 2014-10-11 ruthlesshelp <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/continuousintegration20141011-141014002919-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
Continuous Integration - NoVA CodeCamp 2014-10-11 from Stephen Ritchie
]]>
421 1 https://cdn.slidesharecdn.com/ss_thumbnails/continuousintegration20141011-141014002919-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Lightweight Documentation: An Agile Approach /slideshow/lightweight-docs-20140818/38137790 lightweightdocs-20140818-140819104719-phpapp02
One of the values of the Agile manifesto is working software over comprehensive documentation. However many agile teams think that now we are Agile we don’t need to document. Come to this session to learn about lightweight documentation and how to strike a sensible balance between working software and documentation. Learn which documents are necessary and which documents you can do without as well. Learn about JIT lightweight alternatives to our tradition documentation set. Leave with specific techniques to evaluate the value of each document along with recommended alternatives.]]>

One of the values of the Agile manifesto is working software over comprehensive documentation. However many agile teams think that now we are Agile we don’t need to document. Come to this session to learn about lightweight documentation and how to strike a sensible balance between working software and documentation. Learn which documents are necessary and which documents you can do without as well. Learn about JIT lightweight alternatives to our tradition documentation set. Leave with specific techniques to evaluate the value of each document along with recommended alternatives.]]>
Tue, 19 Aug 2014 10:47:19 GMT /slideshow/lightweight-docs-20140818/38137790 ruthlesshelp@slideshare.net(ruthlesshelp) Lightweight Documentation: An Agile Approach ruthlesshelp One of the values of the Agile manifesto is working software over comprehensive documentation. However many agile teams think that now we are Agile we don’t need to document. Come to this session to learn about lightweight documentation and how to strike a sensible balance between working software and documentation. Learn which documents are necessary and which documents you can do without as well. Learn about JIT lightweight alternatives to our tradition documentation set. Leave with specific techniques to evaluate the value of each document along with recommended alternatives. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/lightweightdocs-20140818-140819104719-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> One of the values of the Agile manifesto is working software over comprehensive documentation. However many agile teams think that now we are Agile we don’t need to document. Come to this session to learn about lightweight documentation and how to strike a sensible balance between working software and documentation. Learn which documents are necessary and which documents you can do without as well. Learn about JIT lightweight alternatives to our tradition documentation set. Leave with specific techniques to evaluate the value of each document along with recommended alternatives.
Lightweight Documentation: An Agile Approach from Stephen Ritchie
]]>
3073 5 https://cdn.slidesharecdn.com/ss_thumbnails/lightweightdocs-20140818-140819104719-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Continuous Integration: Blueprint, Toolbox, Master Craft /slideshow/continuous-integration-blueprint/28178801 continuousintegration20131113-131112190610-phpapp02
Continuous Integration: Blueprint, Toolbox, Master Craft]]>

Continuous Integration: Blueprint, Toolbox, Master Craft]]>
Tue, 12 Nov 2013 19:06:09 GMT /slideshow/continuous-integration-blueprint/28178801 ruthlesshelp@slideshare.net(ruthlesshelp) Continuous Integration: Blueprint, Toolbox, Master Craft ruthlesshelp Continuous Integration: Blueprint, Toolbox, Master Craft <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/continuousintegration20131113-131112190610-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Continuous Integration: Blueprint, Toolbox, Master Craft
Continuous Integration: Blueprint, Toolbox, Master Craft from Stephen Ritchie
]]>
952 3 https://cdn.slidesharecdn.com/ss_thumbnails/continuousintegration20131113-131112190610-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Dc scrum agile_eng_20130923 /slideshow/dc-scrum-agileeng20130923/26498288 dcscrumagileeng20130923-130924091212-phpapp01
Scrum and Agile Engineering Practices - What every ScrumMaster needs to know Some Agile teams fail to figure out or implement technical practices that are necessary for long term success. Practices like automated builds, automated tests, automated deployments, continuous integration, and continuous delivery are now considered essential for the success of any software development project. Join us for a tour of software engineering best practices. We'll discuss what these practices are and their impact on scope, schedule, cost, resources and quality. We'll also share some ideas on how to start adopting these practices and how to incrementally introduce them and gradually improve your team's software development process. ]]>

Scrum and Agile Engineering Practices - What every ScrumMaster needs to know Some Agile teams fail to figure out or implement technical practices that are necessary for long term success. Practices like automated builds, automated tests, automated deployments, continuous integration, and continuous delivery are now considered essential for the success of any software development project. Join us for a tour of software engineering best practices. We'll discuss what these practices are and their impact on scope, schedule, cost, resources and quality. We'll also share some ideas on how to start adopting these practices and how to incrementally introduce them and gradually improve your team's software development process. ]]>
Tue, 24 Sep 2013 09:12:12 GMT /slideshow/dc-scrum-agileeng20130923/26498288 ruthlesshelp@slideshare.net(ruthlesshelp) Dc scrum agile_eng_20130923 ruthlesshelp Scrum and Agile Engineering Practices - What every ScrumMaster needs to know Some Agile teams fail to figure out or implement technical practices that are necessary for long term success. Practices like automated builds, automated tests, automated deployments, continuous integration, and continuous delivery are now considered essential for the success of any software development project. Join us for a tour of software engineering best practices. We'll discuss what these practices are and their impact on scope, schedule, cost, resources and quality. We'll also share some ideas on how to start adopting these practices and how to incrementally introduce them and gradually improve your team's software development process. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/dcscrumagileeng20130923-130924091212-phpapp01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Scrum and Agile Engineering Practices - What every ScrumMaster needs to know Some Agile teams fail to figure out or implement technical practices that are necessary for long term success. Practices like automated builds, automated tests, automated deployments, continuous integration, and continuous delivery are now considered essential for the success of any software development project. Join us for a tour of software engineering best practices. We&#39;ll discuss what these practices are and their impact on scope, schedule, cost, resources and quality. We&#39;ll also share some ideas on how to start adopting these practices and how to incrementally introduce them and gradually improve your team&#39;s software development process.
Dc scrum agile_eng_20130923 from Stephen Ritchie
]]>
1055 2 https://cdn.slidesharecdn.com/ss_thumbnails/dcscrumagileeng20130923-130924091212-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Test Driven Development: Blueprint, Toolbox, and Master Craft /slideshow/test-driven-development-blueprint-toolbox-and-master-craft/17859780 tddblueprinttoolboxmastercraft20130401-130329090748-phpapp01
Many say that the practice of test driven development (TDD) has the ability to transform software engineering. Let’s break it down from a skeptical pragmatist’s viewpoint. This presentation focuses on three key ideas; the blueprint, the toolbox, and the master craft. Let’s look at TDD as a blueprint for writing code and discuss the implications and benefit. Let’s go beyond the theoretical application of TDD and focus on the toolbox, with examples of what developers need to know to get going. Finally, TDD is a master craft of Agile engineering. To be effective with TDD, let’s look at the progression of skills needed to achieve the promised results of TDD and to maximize its value. Stephen is the organizer of DC Alt.Net (http://bit.ly/ZRDxUj). He frequent speaker and trainer on many .NET topics, including automated testing, continuous integration, code analysis, and .NET best practices.Stephen is the author of the book "Pro .NET Best Practices" (http://amzn.to/v8TD8E).]]>

Many say that the practice of test driven development (TDD) has the ability to transform software engineering. Let’s break it down from a skeptical pragmatist’s viewpoint. This presentation focuses on three key ideas; the blueprint, the toolbox, and the master craft. Let’s look at TDD as a blueprint for writing code and discuss the implications and benefit. Let’s go beyond the theoretical application of TDD and focus on the toolbox, with examples of what developers need to know to get going. Finally, TDD is a master craft of Agile engineering. To be effective with TDD, let’s look at the progression of skills needed to achieve the promised results of TDD and to maximize its value. Stephen is the organizer of DC Alt.Net (http://bit.ly/ZRDxUj). He frequent speaker and trainer on many .NET topics, including automated testing, continuous integration, code analysis, and .NET best practices.Stephen is the author of the book "Pro .NET Best Practices" (http://amzn.to/v8TD8E).]]>
Fri, 29 Mar 2013 09:07:48 GMT /slideshow/test-driven-development-blueprint-toolbox-and-master-craft/17859780 ruthlesshelp@slideshare.net(ruthlesshelp) Test Driven Development: Blueprint, Toolbox, and Master Craft ruthlesshelp Many say that the practice of test driven development (TDD) has the ability to transform software engineering. Let’s break it down from a skeptical pragmatist’s viewpoint. This presentation focuses on three key ideas; the blueprint, the toolbox, and the master craft. Let’s look at TDD as a blueprint for writing code and discuss the implications and benefit. Let’s go beyond the theoretical application of TDD and focus on the toolbox, with examples of what developers need to know to get going. Finally, TDD is a master craft of Agile engineering. To be effective with TDD, let’s look at the progression of skills needed to achieve the promised results of TDD and to maximize its value. Stephen is the organizer of DC Alt.Net (http://bit.ly/ZRDxUj). He frequent speaker and trainer on many .NET topics, including automated testing, continuous integration, code analysis, and .NET best practices.Stephen is the author of the book "Pro .NET Best Practices" (http://amzn.to/v8TD8E). <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/tddblueprinttoolboxmastercraft20130401-130329090748-phpapp01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Many say that the practice of test driven development (TDD) has the ability to transform software engineering. Let’s break it down from a skeptical pragmatist’s viewpoint. This presentation focuses on three key ideas; the blueprint, the toolbox, and the master craft. Let’s look at TDD as a blueprint for writing code and discuss the implications and benefit. Let’s go beyond the theoretical application of TDD and focus on the toolbox, with examples of what developers need to know to get going. Finally, TDD is a master craft of Agile engineering. To be effective with TDD, let’s look at the progression of skills needed to achieve the promised results of TDD and to maximize its value. Stephen is the organizer of DC Alt.Net (http://bit.ly/ZRDxUj). He frequent speaker and trainer on many .NET topics, including automated testing, continuous integration, code analysis, and .NET best practices.Stephen is the author of the book &quot;Pro .NET Best Practices&quot; (http://amzn.to/v8TD8E).
Test Driven Development: Blueprint, Toolbox, and Master Craft from Stephen Ritchie
]]>
1137 8 https://cdn.slidesharecdn.com/ss_thumbnails/tddblueprinttoolboxmastercraft20130401-130329090748-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Agile Testing Best Practices /slideshow/agile-testing-best-practices/17382861 agiletestingbestpractices20130319-130319172546-phpapp02
Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses the current date and time? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away Agile testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.]]>

Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses the current date and time? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away Agile testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.]]>
Tue, 19 Mar 2013 17:25:46 GMT /slideshow/agile-testing-best-practices/17382861 ruthlesshelp@slideshare.net(ruthlesshelp) Agile Testing Best Practices ruthlesshelp Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses the current date and time? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away Agile testing obstacles, avoiding common pitfalls, and staying away from dangerous practices. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agiletestingbestpractices20130319-130319172546-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses the current date and time? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away Agile testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.
Agile Testing Best Practices from Stephen Ritchie
]]>
7247 7 https://cdn.slidesharecdn.com/ss_thumbnails/agiletestingbestpractices20130319-130319172546-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Continuous Integration: Blueprint, Toolbox, Master Craft /slideshow/continuous-integration-blueprint-toolbox-master-craft-16627385/16627385 continuousintegration20130219-130219110339-phpapp01
The practice of continuous integration (CI) has the ability to transform software development from a set of manual processes to a logical series of reproducible, automated processes. There are three concepts that are key to continuous integration; the blueprint, the toolbox, and the master craft. This session presents the CI lifecycle as a blueprint. You will see and understand the series of development processes that establish an effective, automated progression from source code to a packaged deliverable. You will learn about the CI server, which is the fundamental tool that initiates, performs, coordinates, and reports throughout the CI phases. The toolbox includes both the CI server and the combination of technologies that support CI. Continuous integration is a master craft of Agile engineering. To help you be effective with continuous integration, this talk demonstrates both the knowledge and skills needed to achieve the desired results of CI and to maximize its value.]]>

The practice of continuous integration (CI) has the ability to transform software development from a set of manual processes to a logical series of reproducible, automated processes. There are three concepts that are key to continuous integration; the blueprint, the toolbox, and the master craft. This session presents the CI lifecycle as a blueprint. You will see and understand the series of development processes that establish an effective, automated progression from source code to a packaged deliverable. You will learn about the CI server, which is the fundamental tool that initiates, performs, coordinates, and reports throughout the CI phases. The toolbox includes both the CI server and the combination of technologies that support CI. Continuous integration is a master craft of Agile engineering. To help you be effective with continuous integration, this talk demonstrates both the knowledge and skills needed to achieve the desired results of CI and to maximize its value.]]>
Tue, 19 Feb 2013 11:03:39 GMT /slideshow/continuous-integration-blueprint-toolbox-master-craft-16627385/16627385 ruthlesshelp@slideshare.net(ruthlesshelp) Continuous Integration: Blueprint, Toolbox, Master Craft ruthlesshelp The practice of continuous integration (CI) has the ability to transform software development from a set of manual processes to a logical series of reproducible, automated processes. There are three concepts that are key to continuous integration; the blueprint, the toolbox, and the master craft. This session presents the CI lifecycle as a blueprint. You will see and understand the series of development processes that establish an effective, automated progression from source code to a packaged deliverable. You will learn about the CI server, which is the fundamental tool that initiates, performs, coordinates, and reports throughout the CI phases. The toolbox includes both the CI server and the combination of technologies that support CI. Continuous integration is a master craft of Agile engineering. To help you be effective with continuous integration, this talk demonstrates both the knowledge and skills needed to achieve the desired results of CI and to maximize its value. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/continuousintegration20130219-130219110339-phpapp01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> The practice of continuous integration (CI) has the ability to transform software development from a set of manual processes to a logical series of reproducible, automated processes. There are three concepts that are key to continuous integration; the blueprint, the toolbox, and the master craft. This session presents the CI lifecycle as a blueprint. You will see and understand the series of development processes that establish an effective, automated progression from source code to a packaged deliverable. You will learn about the CI server, which is the fundamental tool that initiates, performs, coordinates, and reports throughout the CI phases. The toolbox includes both the CI server and the combination of technologies that support CI. Continuous integration is a master craft of Agile engineering. To help you be effective with continuous integration, this talk demonstrates both the knowledge and skills needed to achieve the desired results of CI and to maximize its value.
Continuous Integration: Blueprint, Toolbox, Master Craft from Stephen Ritchie
]]>
7931 4 https://cdn.slidesharecdn.com/ss_thumbnails/continuousintegration20130219-130219110339-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Continuous Integration DCAEC12 /ruthlesshelp/continuous-integration-dcaec12 continuousintegration20121207-121207092554-phpapp02
DC Agile Engineering Conference 2012 -- Continuous Integration presentation.]]>

DC Agile Engineering Conference 2012 -- Continuous Integration presentation.]]>
Fri, 07 Dec 2012 09:25:54 GMT /ruthlesshelp/continuous-integration-dcaec12 ruthlesshelp@slideshare.net(ruthlesshelp) Continuous Integration DCAEC12 ruthlesshelp DC Agile Engineering Conference 2012 -- Continuous Integration presentation. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/continuousintegration20121207-121207092554-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> DC Agile Engineering Conference 2012 -- Continuous Integration presentation.
Continuous Integration DCAEC12 from Stephen Ritchie
]]>
293 2 https://cdn.slidesharecdn.com/ss_thumbnails/continuousintegration20121207-121207092554-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
An Overview of .NET Best Practices /slideshow/an-overview-of-net-best-practices-15197448/15197448 overviewofdotnetbestpractices20121115-121115153947-phpapp02
This presentation is a practical overview of many of the best practices that you can apply to your .NET projects today. We will cover a broad range of practices and principles with an emphasis on tools and technologies in four key areas: build automation, continuous integration, automated testing, and code analysis. Since complex problems often require iterative solutions, this presentation looks at an iterative approach to adopting new and better practices. Through a stepwise process we’ll examine key areas to improve, how to get started and continue to grow implementation, and what might motivate folks to stick with .NET best practices.]]>

This presentation is a practical overview of many of the best practices that you can apply to your .NET projects today. We will cover a broad range of practices and principles with an emphasis on tools and technologies in four key areas: build automation, continuous integration, automated testing, and code analysis. Since complex problems often require iterative solutions, this presentation looks at an iterative approach to adopting new and better practices. Through a stepwise process we’ll examine key areas to improve, how to get started and continue to grow implementation, and what might motivate folks to stick with .NET best practices.]]>
Thu, 15 Nov 2012 15:39:45 GMT /slideshow/an-overview-of-net-best-practices-15197448/15197448 ruthlesshelp@slideshare.net(ruthlesshelp) An Overview of .NET Best Practices ruthlesshelp This presentation is a practical overview of many of the best practices that you can apply to your .NET projects today. We will cover a broad range of practices and principles with an emphasis on tools and technologies in four key areas: build automation, continuous integration, automated testing, and code analysis. Since complex problems often require iterative solutions, this presentation looks at an iterative approach to adopting new and better practices. Through a stepwise process we’ll examine key areas to improve, how to get started and continue to grow implementation, and what might motivate folks to stick with .NET best practices. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/overviewofdotnetbestpractices20121115-121115153947-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> This presentation is a practical overview of many of the best practices that you can apply to your .NET projects today. We will cover a broad range of practices and principles with an emphasis on tools and technologies in four key areas: build automation, continuous integration, automated testing, and code analysis. Since complex problems often require iterative solutions, this presentation looks at an iterative approach to adopting new and better practices. Through a stepwise process we’ll examine key areas to improve, how to get started and continue to grow implementation, and what might motivate folks to stick with .NET best practices.
An Overview of .NET Best Practices from Stephen Ritchie
]]>
1035 3 https://cdn.slidesharecdn.com/ss_thumbnails/overviewofdotnetbestpractices20121115-121115153947-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Advanced Code Analysis with .NET /slideshow/advanced-code-analysis-with-net/15179987 advcodeanalysisnet20121114-121114152924-phpapp01
This presentation covers three basic ideas: static code analysis, dynamic code analysis, and the analyze-improve-monitor cycle. This session demonstrates many pragmatic tools and technologies that you can apply today within your .NET projects in order to perform effective code analysis.]]>

This presentation covers three basic ideas: static code analysis, dynamic code analysis, and the analyze-improve-monitor cycle. This session demonstrates many pragmatic tools and technologies that you can apply today within your .NET projects in order to perform effective code analysis.]]>
Wed, 14 Nov 2012 15:29:22 GMT /slideshow/advanced-code-analysis-with-net/15179987 ruthlesshelp@slideshare.net(ruthlesshelp) Advanced Code Analysis with .NET ruthlesshelp This presentation covers three basic ideas: static code analysis, dynamic code analysis, and the analyze-improve-monitor cycle. This session demonstrates many pragmatic tools and technologies that you can apply today within your .NET projects in order to perform effective code analysis. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/advcodeanalysisnet20121114-121114152924-phpapp01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> This presentation covers three basic ideas: static code analysis, dynamic code analysis, and the analyze-improve-monitor cycle. This session demonstrates many pragmatic tools and technologies that you can apply today within your .NET projects in order to perform effective code analysis.
Advanced Code Analysis with .NET from Stephen Ritchie
]]>
1840 5 https://cdn.slidesharecdn.com/ss_thumbnails/advcodeanalysisnet20121114-121114152924-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Overcoming the Obstacles, Pitfalls, and Dangers of Unit Testing /slideshow/overcoming-the-obstacles-pitfalls-and-dangers-of-unit-testing/15160827 automatedtestingobstaclespitfallsdangers20121113-121113142201-phpapp01
Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses DateTime.Now? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away automated testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.]]>

Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses DateTime.Now? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away automated testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.]]>
Tue, 13 Nov 2012 14:22:00 GMT /slideshow/overcoming-the-obstacles-pitfalls-and-dangers-of-unit-testing/15160827 ruthlesshelp@slideshare.net(ruthlesshelp) Overcoming the Obstacles, Pitfalls, and Dangers of Unit Testing ruthlesshelp Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses DateTime.Now? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away automated testing obstacles, avoiding common pitfalls, and staying away from dangerous practices. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/automatedtestingobstaclespitfallsdangers20121113-121113142201-phpapp01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses DateTime.Now? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away automated testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.
Overcoming the Obstacles, Pitfalls, and Dangers of Unit Testing from Stephen Ritchie
]]>
1848 6 https://cdn.slidesharecdn.com/ss_thumbnails/automatedtestingobstaclespitfallsdangers20121113-121113142201-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
An Overview of .NET Best Practices /slideshow/an-overview-of-net-best-practices/15139581 overviewofdotnetbestpractices20121112-121112102705-phpapp01
This presentation is a practical overview of many of the best practices that you can apply to your .NET projects today. We will cover a broad range of practices and principles with an emphasis on tools and technologies in four key areas: build automation, continuous integration, automated testing, and code analysis. Since complex problems often require iterative solutions, this presentation looks at an iterative approach to adopting new and better practices. Through a stepwise process we’ll examine key areas to improve, how to get started and continue to grow implementation, and what might motivate folks to stick with .NET best practices.]]>

This presentation is a practical overview of many of the best practices that you can apply to your .NET projects today. We will cover a broad range of practices and principles with an emphasis on tools and technologies in four key areas: build automation, continuous integration, automated testing, and code analysis. Since complex problems often require iterative solutions, this presentation looks at an iterative approach to adopting new and better practices. Through a stepwise process we’ll examine key areas to improve, how to get started and continue to grow implementation, and what might motivate folks to stick with .NET best practices.]]>
Mon, 12 Nov 2012 10:27:03 GMT /slideshow/an-overview-of-net-best-practices/15139581 ruthlesshelp@slideshare.net(ruthlesshelp) An Overview of .NET Best Practices ruthlesshelp This presentation is a practical overview of many of the best practices that you can apply to your .NET projects today. We will cover a broad range of practices and principles with an emphasis on tools and technologies in four key areas: build automation, continuous integration, automated testing, and code analysis. Since complex problems often require iterative solutions, this presentation looks at an iterative approach to adopting new and better practices. Through a stepwise process we’ll examine key areas to improve, how to get started and continue to grow implementation, and what might motivate folks to stick with .NET best practices. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/overviewofdotnetbestpractices20121112-121112102705-phpapp01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> This presentation is a practical overview of many of the best practices that you can apply to your .NET projects today. We will cover a broad range of practices and principles with an emphasis on tools and technologies in four key areas: build automation, continuous integration, automated testing, and code analysis. Since complex problems often require iterative solutions, this presentation looks at an iterative approach to adopting new and better practices. Through a stepwise process we’ll examine key areas to improve, how to get started and continue to grow implementation, and what might motivate folks to stick with .NET best practices.
An Overview of .NET Best Practices from Stephen Ritchie
]]>
866 3 https://cdn.slidesharecdn.com/ss_thumbnails/overviewofdotnetbestpractices20121112-121112102705-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
DCDNUG 10/16/2012 Automated testing obstacles pitfalls dangers /ruthlesshelp/dcdnug-10162012-automated-testing-obstacles-pitfalls-dangers automatedtestingobstaclespitfallsdangers-121017203318-phpapp02
]]>

]]>
Wed, 17 Oct 2012 20:33:15 GMT /ruthlesshelp/dcdnug-10162012-automated-testing-obstacles-pitfalls-dangers ruthlesshelp@slideshare.net(ruthlesshelp) DCDNUG 10/16/2012 Automated testing obstacles pitfalls dangers ruthlesshelp <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/automatedtestingobstaclespitfallsdangers-121017203318-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
DCDNUG 10/16/2012 Automated testing obstacles pitfalls dangers from Stephen Ritchie
]]>
388 2 https://cdn.slidesharecdn.com/ss_thumbnails/automatedtestingobstaclespitfallsdangers-121017203318-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Automated Testing: Obstacles, Pitfalls, and Dangers /ruthlesshelp/automated-testing-obstacles-pitfalls-and-dangers automatedtestingobstaclespitfallsdangers-120906074446-phpapp01
]]>

]]>
Thu, 06 Sep 2012 07:44:43 GMT /ruthlesshelp/automated-testing-obstacles-pitfalls-and-dangers ruthlesshelp@slideshare.net(ruthlesshelp) Automated Testing: Obstacles, Pitfalls, and Dangers ruthlesshelp <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/automatedtestingobstaclespitfallsdangers-120906074446-phpapp01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
Automated Testing: Obstacles, Pitfalls, and Dangers from Stephen Ritchie
]]>
5614 5 https://cdn.slidesharecdn.com/ss_thumbnails/automatedtestingobstaclespitfallsdangers-120906074446-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Advanced Code Analysis In .NET /slideshow/advanced-code-analysis-in-net/13577030 advancedcodeanalysisnet-120708135323-phpapp02
The code samples from the session are on GitHub: https://github.com/ruthlesshelp/Presentations ]]>

The code samples from the session are on GitHub: https://github.com/ruthlesshelp/Presentations ]]>
Sun, 08 Jul 2012 13:53:22 GMT /slideshow/advanced-code-analysis-in-net/13577030 ruthlesshelp@slideshare.net(ruthlesshelp) Advanced Code Analysis In .NET ruthlesshelp The code samples from the session are on GitHub: https://github.com/ruthlesshelp/Presentations <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/advancedcodeanalysisnet-120708135323-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> The code samples from the session are on GitHub: https://github.com/ruthlesshelp/Presentations
Advanced Code Analysis In .NET from Stephen Ritchie
]]>
5860 10 https://cdn.slidesharecdn.com/ss_thumbnails/advancedcodeanalysisnet-120708135323-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
Automated Testing with Databases /slideshow/automated-testing-with-databases/12895021 automatedtestingwithdatabases-120511091312-phpapp02
]]>

]]>
Fri, 11 May 2012 09:13:09 GMT /slideshow/automated-testing-with-databases/12895021 ruthlesshelp@slideshare.net(ruthlesshelp) Automated Testing with Databases ruthlesshelp <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/automatedtestingwithdatabases-120511091312-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
Automated Testing with Databases from Stephen Ritchie
]]>
5992 8 https://cdn.slidesharecdn.com/ss_thumbnails/automatedtestingwithdatabases-120511091312-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0
https://cdn.slidesharecdn.com/profile-photo-ruthlesshelp-48x48.jpg?cb=1706986161 Stephen Ritchie is the author of Pro .NET Best Practices. Software (http://www.amazon.com/gp/product/1430240237). He is a software developer with more than 20 years of experience designing and developing software solutions. Stephen specializes in Microsoft .NET web-based development, including: .NET Framework development in C#, ASP.NET MVC, NHibernate, LINQ, SQL Server, and several more. ruthlesslyhelpful.net https://cdn.slidesharecdn.com/ss_thumbnails/overviewofdotnetbestpractices20150317-150318084510-conversion-gate01-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/overview-of-net-best-practices/45990241 Overview of .NET Best ... https://cdn.slidesharecdn.com/ss_thumbnails/lightweightdocs-20150311-150311065158-conversion-gate01-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/lightweight-documentation/45701658 Lightweight Documentation https://cdn.slidesharecdn.com/ss_thumbnails/agileengineeringbestpractices-20150128-150128122139-conversion-gate02-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/agile-engineering-sparker-20150128/44005701 Agile Engineering Spar...