Matt Stine
RWX / CDX
Fort Lauderdale · December 3 - 6, 2013
I Enable Early-Career Enterprise Software Engineers to Continuously Improve
My passion is taking a metaphysical approach to software engineering: what is the nature of the collaborative game that we continuously play, and are there better, more contextually-aware ways to play that game?
By day I lead a team tasked with taking a first-principles-centric approach to intentionally enabling programming language usage at the largest bank in the United States.
By night I write and teach my way through a masterclass in software engineering and architecture targeting early-career software engineers working in large-scale enterprise technology organizations.
What is the primary goal?
To win the game. More seriously: to get 1% better every day at providing business value through software.
Who am I?
I'm a 22-year veteran of the enterprise software industry. I've played almost every role I can imagine:
- Software Engineer
- Software Architect
- Technical Lead
- Engineering Manager
- Consultant
- Product Manager
- Field CTO
- Developer Advocate
- Conference Speaker
- Author
- Technical Trainer
- Technical Marketer
- Site Reliability Engineer
- Desktop Support Specialist
I've worked at Fortune 500 companies, a tenacious teal cloud startup, and a not-for-profit children's hospital. I've written a book, and I've hosted a podcast. I've learned a lot along the way, including many things I wish I'd known when I first got started. And so now I want to pass those learnings on to you, especially if you've only just begun your career.
Presentations
Cloud Foundry Deep Dive, Part 2: Architecture and Operations
This session will focus on how you can build your very own Cloud Foundry private PaaS running in your own data center or on AWS or even on OpenStack on your own Mac mini. You will learn how the Cloud Foundry BOSH tool constructs a full Cloud Foundry instance from a bare bones virtual machine and continues to coordinate and manage the entire PaaS cloud once it is operational.
Deploy Your Own Cloud Foundry to AWS
In this workshop you'll have the opportunity to deploy your very own instance of Cloud Foundry running on Amazon Web Services, practically applying what you learned in the “Build Your Very Own Private Cloud Foundry” session. You'll walk away with your very own private PaaS.
Deploy Your Own Cloud Foundry to AWS
In this workshop you'll have the opportunity to deploy your very own instance of Cloud Foundry running on Amazon Web Services, practically applying what you learned in the “Build Your Very Own Private Cloud Foundry” session. You'll walk away with your very own private PaaS.
Cloud Application Architecture Patterns
We make many assumptions when we develop our applications. Many of these assumptions no longer hold true when we start to build applications for the cloud. Cloud platforms also introduce architectural possibilities that do not exist in traditional deployment settings. This session will examine five architectural patterns that we can apply to our applications in order to prepare them for the unique characteristics of cloud environments.
Vagrant: Virtualized Development Environments Made Simple
Have you ever wished that your local development sandbox could look exactly like production, but you've got a mismatch between your local OS and your production OS? And what about the age old “it works on my machine” excuse that quite often stems from differences between developer sandboxes? Many have turned to virtualization, creating a machine image that can be passed around the team. But who manages the template? How do you keep things in sync?
In this session, we'll explore Vagrant (http://www.vagrantup.com), an open source tool that allows you to easily create and manage virtual development environments that can be provisioned on demand and “thrown away” when no longer needed.
Deploying Distributed Systems with BOSH
BOSH was originally developed to be the toolchain that installs and manages the Cloud Foundry runtime, which is a large distributed system consisting of multiple components running on multiple virtual machines. In order to deploy and manage such a system, you need elements of:
- configuration management tools, such as Puppet and Chef
- orchestration tools, such as Mcollective and RunDeck
- knowledge of multiple IaaS layers (compute, storage, networking) to support portability
- health management
- monitoring and reporting
- etc.