Last active
August 29, 2015 14:05
-
-
Save spetryjohnson/3c47723f65e16b6ae757 to your computer and use it in GitHub Desktop.
CodeMash submission abstracts - comments welcome!
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
| General bio | |
| ------------------------------------- | |
| Seth has been programming for 25 years, 18 of them professionally. He is a full-stack | |
| developer/architect and enjoys bouncing between the database, .NET and JavaScript with | |
| the occasional foray into devops. He is passionate about bringing order to chaos through | |
| clean architecture, simple designs and testable code. Seth lives in Columbus, OH and is | |
| an active participant in the Midwest developer community. | |
| --------------------------------------------------------------------------- | |
| MVC from the Trenches: Managing Growth and Complexity in Large Systems | |
| --------------------------------------------------------------------------- | |
| It's hard to keep an MVC app clean and testable under the demands of sustained, | |
| long-term development. In this session you'll see a collection of patterns and | |
| techniques working together to keep things simple. You'll learn new ways to organize | |
| your code, how to test using GET/POST models, and how to keep your markup clean and | |
| consistent. Come see how these techniques have kept 1M+ LOC maintainable over five | |
| years of development. | |
| --------------------------------------------------------- | |
| Multi-instance SaaS Deployments Using Octopus | |
| --------------------------------------------------------- | |
| Octopus Deploy is a great tool for automating single application deployments. Managing | |
| multiple instances of an app in a SaaS environment is a bit more difficult. In this session | |
| you'll see a case study of how my team uses Octopus to manage 30+ clients, each with a | |
| different version of the same app. You'll learn why Step Templates are an incomplete solution, | |
| how to structure your build to accommodate change, and how to test build steps in isolation. | |
| You'll also see configuration management patterns and some advanced techniques for supporting | |
| per-client configurations. Prior experience with Octopus is helpful but not required. | |
I would just write it all out, "over one million lines of code". Do we have a measure of "maintainable"? I'm not sure what a good one would be, but it would be help cinch it as well.
You'll also see configuration management patterns and some advanced techniques for supporting
per-client configurations.
Feels like it could be a bit simpler. "configuration management patterns and techniques" might cover it or be a little more explicit in what you're talking about.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider explaining or replacing LOC like: "LOC (Lines of Code)" or just "lines of code".