-
Notifications
You must be signed in to change notification settings - Fork 663
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #143 from WhatsChrisDoing/master
Migrate Toronto 2016 program to new site.
- Loading branch information
Showing
17 changed files
with
427 additions
and
28 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
+++ | ||
City = "Toronto" | ||
Year = "2016" | ||
date = "2016-03-06T21:28:07-06:00" | ||
type = "event" | ||
title = "Jeff Zohrab" | ||
|
||
+++ | ||
|
||
### Agile Databases | ||
|
||
**Abstract:** | ||
|
||
Databases are almost always a pain point for development, especially when it comes to agile. In this talk, I'll discuss what I feel are the main points that need to be considered for successful database development: | ||
|
||
+ each dev should have their own development database, and should create database change scripts | ||
+ changes should be easily integrated | ||
+ baselining | ||
+ the difference between reference and test data | ||
+ handling schema vs code changes | ||
+ testing | ||
+ backwards compatibility checks | ||
+ database refactoring | ||
|
||
For lack of a better tool (at least, at the time!), I wrote a cross-platform database development tool in Python that can/should be able to work with any database for which suitable drivers exist, and implementations are available for MySQL and Postgres. I'll use that as a demo. With this tool (version 0.1 of it, anyway), I had a team of 6 devs destroying and rebuilding their dev databases as needed with a single click, running their dev tests on their dedicated instances, and deploying to multiple QA and integration environments. | ||
|
||
I think that this topic is interesting in general as it highlights the need to pull pain points forward and deal with them. Paraphrasing Jez Humble -- or maybe exactly quoting him per <a href="http://evan.bottch.com/2010/05/26/continuous-integration-if-something-hurts-do-it-more-often/" target="_blank">Continuous Integration – If Something Hurts, Do It More Often</a> -- database things hurt, and so they need to be done as much as possible. Unfortunately, many tools don't address these needs, and advice on the net can end up being problematic (eg the tip "your db change script should check if a column exists before adding it" can end up avoiding one trouble but causing another). | ||
|
||
**Speaker:** | ||
|
||
Jeff Zohrab | ||
|
||
I've been in tech for a few decades now, and was an early adopter with XP designed testing frameworks for VB and C++. I've worked on small, big, and huge projects on the development side as dev, team lead, and architect, and have recently started working with a Japanese company to instill DevOps practices into their culture. |
20 changes: 20 additions & 0 deletions
20
...-toronto/proposals/Are YOU the Change Agent your Organization is Looking For.md
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
+++ | ||
City = "Toronto" | ||
Year = "2016" | ||
date = "2016-03-06T21:28:07-06:00" | ||
type = "event" | ||
title = "Drew Nienaber" | ||
|
||
+++ | ||
|
||
### Are YOU the Change Agent your Organization is Looking For…? | ||
|
||
**Abstract:** | ||
|
||
For most organizations, DevOps means a change, both to your process and your way of thinking. Change is hard and being the one to introduce change into your organization is even more difficult. In this Ignite, I’ll talk about the assumptions we make about change, the universal truths we accept about change, the questions to ask yourself before initiating change and four approaches to bringing it. With the help of the book Change Anything: The New Science of Personal Success, I’ll show how you can be the transformer & revolutionary you’ve always dreamed of being. | ||
|
||
**Speaker:** | ||
|
||
Drew Nienaber, <a href="https://twitter.com/DrewNienaber" target="_blank">@DrewNienaber</a> | ||
|
||
I'm (Drew) a sales guy, but don't hate me for that. I'm also a craft beer aficionado, a dad and a Nawlins boy desperately looking for Zapps chips in Colorado. |
33 changes: 33 additions & 0 deletions
33
...als/Being an introvert and at a conference not as hellish as you think it is.md
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
+++ | ||
City = "Toronto" | ||
Year = "2016" | ||
date = "2016-03-06T21:28:07-06:00" | ||
type = "event" | ||
title = "JJ Asghar" | ||
|
||
+++ | ||
|
||
### Being an introvert and at a conference, not as hellish as you think it is | ||
|
||
**Abstract:** | ||
|
||
I'd like to give some advice on how to deal with conferences as an introvert. | ||
Over the last couple years I've grown and learned to engage with the tech community | ||
in ways that an introvert would find challenging. This talk will hopefully help | ||
the audience avoid some of the landmines that I have stepped on. | ||
|
||
I want to help out my fellow introverts to realize that it's OK to be an introvert | ||
at big conferences. We can enjoy them too. | ||
|
||
**Speaker:** | ||
|
||
JJ Asghar, <a href="https://twitter.com/jjasghar" target="_blank">@jjasghar</a> | ||
|
||
JJ is a Sr. Partner Engineer at Chef, he was also the PTL for the Openstack-Chef | ||
project. He lives in Austin, Texas and has been part of the OpenStack community since Diablo's release. | ||
|
||
He enjoys a good strong stout, hoppy IPA, and some Dwarf Fortress. He's a member | ||
of the Church of Emacs, and usually chooses Ubuntu over CentOS. | ||
|
||
He's a father and husband, if he's not trying to automate his job away he's | ||
trying to convince his daughters to "let the bot's do the work for them." |
28 changes: 28 additions & 0 deletions
28
...roposals/Containers will not fix your broken culture (and other hard truths).md
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
+++ | ||
City = "Toronto" | ||
Year = "2016" | ||
date = "2016-03-06T21:28:07-06:00" | ||
type = "event" | ||
title = "Bridget Kromhout" | ||
|
||
+++ | ||
|
||
### Containers will not fix your broken culture (and other hard truths) | ||
|
||
**Abstract:** | ||
|
||
Containers will not fix your broken culture. Microservices won’t prevent your two-pizza teams from needing to have conversations with one another over that pizza. No amount of industrial-strength job scheduling makes your organization immune to Conway's Law. | ||
|
||
Does this mean that devops has failed? Not in the slightest. It means that while the unscrupulous might try to sell us devops, we can't buy it. We have to live it; change is a choice we make every day, through our actions of listening empathetically and acting compassionately. Iterative improvement starts somewhere for us all; let’s talk about it. | ||
|
||
Tools are essential, but how we implement the tools and grow the culture and practices in our organizations needs even more attention. Whether you’re just starting to implement technical and organizational change, or facing the prospect that you already have legacy microservices, it's worth considering the why and the how of our behaviors, not just the what. | ||
|
||
Making thoughtful decisions about tools and architecture can help. Containers prove to be a useful boundary object, and deconstructing systems to human-scale allows us to comprehend their complexity. We succeed when we share responsibility and have agency, when we move past learned helplessness to active listening. But there is no flowchart, no checklist, no shopping list of ticky boxes that will make everything better. "Anyone who says differently is selling something", as The Princess Bride teaches us. Instead, let’s talk about practical, actionable steps that will help. How do we evaluate our progress? How do we know when to course-correct? How do we react when it seems like there's always something new we should have done last month? | ||
|
||
Part rant, part devops therapy, this talk will explain in the nerdiest of terms why CAP theorem applies to human interactions too, how oral tradition is like never writing state to disk, and what we can do to avoid sadness as a service. | ||
|
||
**Speaker:** | ||
|
||
Bridget Kromhout, <a href="https://twitter.com/bridgetkromhout" target="_blank">@bridgetkromhout</a> | ||
|
||
Bridget Kromhout is a Principal Technologist for Cloud Foundry at Pivotal. Her CS degree emphasis was in theory, but she now deals with the concrete (if 'cloud' can be considered tangible). After years in site reliability operations (most recently at DramaFever), she traded in oncall for more travel. A frequent speaker at tech conferences, she helps organize the AWS and devops meetups at home in Minneapolis, serves on the program committee for Velocity, and acts as a global core organizer for devopsdays. She podcasts at Arrested DevOps, occasionally blogs at <a href="http://bridgetkromhout.com" target="_blank">bridgetkromhout.com</a>, and is active in a Twitterverse near you. |
32 changes: 32 additions & 0 deletions
32
content/events/2016-toronto/proposals/Devops Evolution at Nulogy.md
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
+++ | ||
City = "Toronto" | ||
Year = "2016" | ||
date = "2016-03-06T21:28:07-06:00" | ||
type = "event" | ||
title = "Ian Penney" | ||
|
||
+++ | ||
|
||
### Devops Evolution at Nulogy | ||
|
||
**Abstract:** | ||
|
||
At Nulogy, our operations are supported by our Infrastructure team, colloquially known as the "Computer Friends and Justin" | ||
We are proud to have brought together a team of five veteran hackers with diverse academic and other backgrounds. | ||
|
||
We've recently been through a banner year of growth - having aggressively tackled quick wins to greatly improve the reliability of our flagship SaaS Logistics product to the point where it can be sold to large multinational corporations with a real need for "four nines" of uptime. | ||
|
||
Everyone on the team is a great fit with our well rounded company culture, but none of us started out in life as Devops Experts. We've learned it, and we want to help you learn it, too. | ||
|
||
The company had already been in operation for over ten years by the time we began to embrace DevOps and related practices. How is it possible to beat down technical debt with so many legacy systems, high SLA requirements and entrenched customers practices. | ||
And more to the point: how will this work make your work/life balance better? | ||
|
||
**Speaker:** | ||
|
||
Ian Penney, <a href="https://twitter.com/cr03" target="_blank">@cr03</a> | ||
|
||
Ian Penney has been working as a Systems Administrator and Systems Manager for over 15 years. He's worked at large companies like the Canadian Broadcasting Corporation and other enterprises through an IBM business partner, as well as with over 200 startups, from coast to coast. | ||
|
||
A few years ago, he realized Infrastructure as Code was the future, and so he began focusing on using tools like Chef, Puppet and Ansible. | ||
|
||
Most recently he's celebrated his first happy anniversary at Nulogy as the lead of their Infrastructure Team during a rapid transition towards "moar devops" and less risk. |
Oops, something went wrong.