WEBVTT NOTE This file was generated by Descript 00:00:03.165 --> 00:00:07.545 I recently read a book that talked about vision and mission, and I 00:00:07.545 --> 00:00:12.435 realized that we really need to put something out into the world to explain 00:00:12.435 --> 00:00:14.805 what our vision and mission are. 00:00:16.005 --> 00:00:18.315 What our mission and vision though. 00:00:18.705 --> 00:00:22.035 I think vision is the world that we want to create. 00:00:22.575 --> 00:00:25.725 The one that we want to see at the end of this journey. 00:00:26.505 --> 00:00:28.665 Mission is how we get there. 00:00:28.695 --> 00:00:33.405 The path we choose and construct to make our vision a reality. 00:00:34.785 --> 00:00:36.885 Let's talk about vision first. 00:00:37.365 --> 00:00:41.715 We see a world right now, where there are loads of people who could 00:00:41.715 --> 00:00:46.305 build amazing tech platforms that could help millions of other people. 00:00:47.265 --> 00:00:51.825 But they don't build those platforms either because they don't have 00:00:51.825 --> 00:00:56.235 access to the technology or the education or the current ecosystem 00:00:56.235 --> 00:00:58.155 just doesn't support them. 00:00:59.505 --> 00:01:03.585 What we envision with the Chewy Stack is a world where nobody hits 00:01:03.585 --> 00:01:07.575 those barriers to access where people can build the platforms they've 00:01:07.575 --> 00:01:10.425 imagined to serve their communities. 00:01:11.685 --> 00:01:13.995 Okay, now let's talk about mission. 00:01:14.625 --> 00:01:16.185 This is going to be a lot longer. 00:01:16.995 --> 00:01:17.955 At first. 00:01:18.405 --> 00:01:23.085 We thought we should start a bootcamp or an accelerator to help people learn how 00:01:23.085 --> 00:01:25.245 to build digital products and launch them. 00:01:25.815 --> 00:01:31.395 But we realized that we were particularly focused on helping people build. 00:01:32.175 --> 00:01:36.435 So we decided we needed to come up with a curriculum that came from 00:01:36.435 --> 00:01:40.335 our experience, building web and mobile apps for small organizations. 00:01:41.115 --> 00:01:45.375 When I say we, I mean Éphémère Creative, which is the small digital 00:01:45.375 --> 00:01:48.255 product studio behind all of this. 00:01:48.828 --> 00:01:53.328 The thing is if we were going to build a curriculum based off 00:01:53.328 --> 00:01:55.788 of our process and experience. 00:01:56.268 --> 00:02:02.448 Well, we use a process and a stack that's really efficient to build products 00:02:02.478 --> 00:02:07.608 quickly in a variety of contexts, but it's pretty complicated to set up 00:02:07.608 --> 00:02:10.728 initially and can be hard to manage. 00:02:11.538 --> 00:02:17.058 So we decided we should build some tooling to automate a bunch of the 00:02:17.058 --> 00:02:22.398 configuration and management for this stack, which we want to put out into 00:02:22.398 --> 00:02:24.528 the world to help achieve our vision. 00:02:26.568 --> 00:02:29.598 Essentially that's what the Chewy Stack is. 00:02:30.108 --> 00:02:34.488 It's a collection of open source tools that make up a really nice way 00:02:34.488 --> 00:02:38.808 to build complex web and mobile apps that we've glued together with some 00:02:38.808 --> 00:02:43.008 custom tooling that make them a lot easier to manage and deploy, which 00:02:43.008 --> 00:02:47.268 should make the whole process way more accessible to way more people. 00:02:49.128 --> 00:02:53.658 In the end, the best way to define the chewy stack. 00:02:54.048 --> 00:02:59.088 Is probably to say that it's a framework kind of, it's a way to organize 00:02:59.088 --> 00:03:00.678 your code for front end and back. 00:03:00.678 --> 00:03:03.588 End features built on top of a few different services. 00:03:03.858 --> 00:03:07.668 But unlike most frameworks, the infrastructure is actually 00:03:07.668 --> 00:03:09.408 defined in the framework. 00:03:09.708 --> 00:03:15.498 So the idea is that if you're using the Chewy Stack, you can use AWS without 00:03:15.498 --> 00:03:20.148 being an AWS expert, or you can deploy to a DigitalOcean droplet without 00:03:20.148 --> 00:03:22.488 having to learn how to do that properly. 00:03:23.448 --> 00:03:28.278 So many tools and frameworks promise to get out of your way and let you 00:03:28.278 --> 00:03:32.928 write application code, but there's so much variability in how to manage 00:03:32.928 --> 00:03:37.638 infrastructure and environments, even with platforms as a service like 00:03:37.668 --> 00:03:43.218 Heroku, that if you're a small or working solo you inevitably have to 00:03:43.218 --> 00:03:47.838 deal with something going wrong at some point or another, as you try to 00:03:47.868 --> 00:03:52.068 move from development to production and it just doesn't work quite right. 00:03:53.088 --> 00:03:57.948 That's the promise of the Chewy Stack: you can build complex applications 00:03:57.948 --> 00:04:02.808 and move from dev to staging, to prod across infrastructures and only ever 00:04:02.808 --> 00:04:04.878 have to think about application code. 00:04:05.085 --> 00:04:09.825 It's a set of open source services that make it easy to build web and mobile 00:04:09.825 --> 00:04:13.695 apps quickly that are connected and managed by some more code to make things 00:04:13.695 --> 00:04:19.215 nice and easy so that more people can build better products more easily.