Last active
August 29, 2015 14:17
-
-
Save bradgignac/c624aaa9a8dfefa5eb22 to your computer and use it in GitHub Desktop.
Talk Abstract
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Multiple environments are a staple of software development projects, but do they | |
| actually help us make better software? Do they help us get it into the hands of | |
| customers faster? In this talk, I'll look at the goal of every development team | |
| -- delivering quality software. I'll review how environments have historically | |
| helped achieve this goal as well as the problems they have caused along the way. | |
| Finally, I'll look at alternative techniques that can be used in lieu of | |
| environments. |
@j00k What about the changing:
In this talk, I'll look at the reasons we have environments in the first place - delivering quality software.
To:
In this talk, I'll look at the goal of every software development team - delivery quality software.
LGTM minus the delivery/delivering typo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
the first two questions seem to be doubtful of the value of environments, but the following sentence treats them positively. that's a little confusing to me.
staging environments are a way to improve software quality, but are there better ways to get higher quality software into the hands of customers quicker?