Stephen of Bell's in Winchester, VA on Brand Image
Hello, welcome to import this a podcast for humans. I'm here today with Stephen, Shanda. He is my favorite stylist and my personal stylist. And he is here at bells in Winchester, Virginia. And he's not a software engineer, like the other people that I interview. But I think that there's something that we can learn from him because he has absolutely excellent taste.
Ernest W. Durbin III on the PSF's Migration to DigitalOcean
hello everyone welcome to import this a podcaster humans My name is Kenneth Reitz and today I am joined by the wonderful. Ew Durban the third, which is a wonderful name of the Python Software Foundation fame. And also hailing from Cleveland, Ohio, I believe. At the moment I'm in Pensacola, Florida, but I do reside in Cleveland, Ohio. Most of your mailing addresses right. That's correct. That's what your legal addresses that was a joke. Oh, well, yeah. I mean, that is where my Google dresses though. There's no joke. How you doing? I'm doing very well. I'm sort of currently on a little bit of a road trip. But I'm static in Pensacola and have a nice, relaxing place to be for a little bit for head the pie, Texas next week. I'm going to be there. I'll be there. Oh, excellent. I will see you there. Awesome. I'm going to try to hallway track which is difficult at a single tracks. conference. Maybe we can grab coffee or something. That would be great. I would love that. coffees on me. Even better, even better. Yeah. Okay, so yeah, so we thought we get to get together and talk a little bit. I heard that the Python Software Foundation just made this really cool migration to this really cool tech stack on this really cool infrastructure provider. I thought you could tell us a little bit about it. I'm sure. So a quick intro for myself. I'm Ernest. I'm the director of infrastructure for the Python Software Foundation. So a lot of people don't quite know exactly what the Python Software Foundation is what we do. But we're a nonprofit. And we sort of pulled the legal rights and and manage the legal parts effectively around the Python programming language, protecting the trademarks and the intellectual property. Exactly. And also we manage, you know, the contribute, contribute contributor license agreements and such to make sure that everything's aboveboard, so that Python can remember You know, fully open source. And you know, we're a nonprofit. And so our mission is that, but outside of that, we also do a lot of community work. We put on the Python us conference every year. And we send grants out to, you know, people who are using are teaching Python all around the world. I think a big part of that, too, that when you say infrastructure, it's not always just software. I mean, it's not always just like hardware infrastructure is also because there's like pipe di, you know, the Python package index, obviously, is a huge piece of infrastructure. But there's also things like voting, that's a piece of infrastructure that needs to be thought of thought through and maintained and decided upon by volunteers, but at the same time, it also needs to be executed by a group that's trusted and the CSF is that trusted group? Certainly. So yeah, I mean, you bring up a great point. We also provide infrastructure for effectively, you know, software infrastructure, if you will.
Erin X. O'Connell on PyCon 2019 and PyColorado!
Follow Erin on Twitter: https://twitter.com/erinxocon Sign-up for DigitalOcean ($100 credit!): https://do.co/42 Hello everyone and welcome to import this a podcast for humans. This is episode I'm not actually sure we're not keeping track anymore. But today I am joined by my wonderful friend Aaron x O'Connell, who have been really good friends with since 2007. Actually, we went to college together. Yeah. George Mason University. Right, Aaron? Yeah, it's true. We went to college together and drop down together. Well, actually, yeah, around the same time. And we're both successful now. So doesn't matter. E Erin X. O'Connell 0:30 Well, success can be measured in adult, various number of ways. I was talking to someone about that the other day, actually. And they told me that success is it wasn't happiness, it was a fulfillment. They had a really good way of putting it I have to remember. 0:47 Also think about that one actually. There's many ways to measure success and I think that's something that that is worth dwelling on. 0:57 Yeah, but But anyway, 1:00 Aaron is known for many things, including helping organize pi Colorado at the moment. She's also working for occipital, which is an excellent company, which I'm sure she can tell us a little bit about. 1:15 Yeah, definitely. So 1:18 yeah, I am working with PI Colorado right now. We're trying to organize our conferences in September. I'm currently I am working on Code of Conduct stuff, response stuff, and also swag. So I'm trying to get some cool, cool stuff there. We have a lot of cool companies in Colorado that are local to Boulder 2:00 Remember the exact wording but was basically treat others with respectfulness and professionalism. And if anyone does otherwise contact us immediately. 2:11 Basically, the code of conduct, 2:14 conduct 2:16 is intended to provide a safe space and make people feel comfortable. And that's why it's there. It's not there to police people, it's there to enable people who would otherwise not feel comfortable coming to feel comfortable coming. Is that a correct understanding? 2:33 Well, the Code of Conduct is a little more than that. It is a set of rules. You know, we don't want to be policing people. But we do need to do that, to an extent. The Code of Conduct is also a response guideline. So it's a set of, yes, it's a set of incident response that we have to take. So you know, if you make a code of conduct violation, then I'm also on the team that responds to that. 3:00 Those types of things and so, you know, the Code of Conduct violation does based I mean if you boil it down it does basically say, you know, be nice to each other and and you know, be respectful and things like that. But the whole the whole other part documents the whole process right and that's the important part is that there's transparency and the process. Yeah, so the process you know, 3:21 we do say what we're going to do the PSS actually put us through a training to do this. So we went through a training where we you know, were paired off and we actually were incident responders and incident reporters and we went through the whole process and you know, documented it and you know, made sure that we felt comfortable doing that so itself, Natalie was one of the SF it's wonderful that the PSS provides that that's not a cheap training, I'm sure. No, I don't think so. And it was actually it was really cool. We got to meet a lot of people from other conferences. People from 4:00 pie a new or pie Australia where there and pie cascades pie Colorado. Me to chris chris number? 4:13 I don't know. I'm not sure I'll have to get her on the show these people from each thing could do it. He's the traditional organizer in my mind of Python a I've been there twice and Keynote at once or maybe twice author on it wasn't it was
The Western Zen of Python
CC BY-NC-SA 3.0, DigitalOcean. Sign-up for DigitalOcean ($100 credit!): do.co/42 Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch. Now is better than never. Although never is often better than *right* now. If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea -- let's do more of those!