The Five-Minute Geek Show

Mister Rogers' mom said, when things are going poorly, "Look for the Helpers." I love Mister Rogers, but I have another idea.

I've been creating a lot of content in other places. Here's a quick update on what I've been doing.

Your online presence matters in job applications.

Don't make me throw out your resumé.

Introducing three new not-ready-for-real-time web sites I'm working on: https://onramp.dev/ https://omgphp.com/ https://whyphp.dev/

Figure out the values, then make the choice according to your values

Just break that overwhelming project up

Knowing, and getting, what you want Recent newsletter Sign up for newsletters

I think we have a bit of entrepreneurial survivorship bias Survivorship bias definition

How we picked our insurance provider, and my guiding principle

You can't make everyone happy

How Tighten sets our prices

Per special request, Christmas 2017 with the kiddos

A few simple tricks for editing your blog posts

What's at the top of your brain? And what's the benefit you get from having to wait on something, letting you brain roll over it? Paul Graham - The Top Idea in Your Mind Transcript: Hi, I'm your host Matt Stauffer, and this episode 101 of The Five Minute Geek Show, a weekly show about development and everything around it. It's one topic per episode about front-end, back-end, mobile, project management, design, entrepreneurship, whatever. If it's geeky, it fits. Today, we're going to be talking about your top idea. I've talked about it a little bit in the past, but essentially, at any given moment, there's usually one primary thing that your brain returns to you when it gives a moment to rest. I often have about seven of these, which drives my wife nuts. We've talked often about the fact that I need to have less commitments. Not just because I need to be spending less time doing things, but because I need spaces for my brain to not only rest and have moments where I think about things family life related, not just all these kind of entrepreneurial and work ideas that I'm doing. So, essentially, when you have nothing else to do. When you're stuck in traffic, or when you are using the restroom, or showering, or taking a walk or something like that, your brain kind of rolls on to things. The things that your brain roll onto, often those are kind of like ... People frequently know this, are the things that ... We get some really great thinking done then, right? You've got stuck on something at work, and you go home and you sleep on it, and you come back and you have an answer. Or you go, you take a 15 minute walk. Sometimes you take a 15 minute walk, your brain just needs to re-orient itself. But sometimes ... For example, I'll often have an idea for an application or for a software of service, or for a project or a book or a blog post or a video. I'll have the idea long before I create the thing. I had an idea for a new product ... Not a product but that open-source thing that I want to do, like 11 months ago or something. Every once a while, it pops into my brain. It hasn't been the top of my mind, but it pops into my brain for a little bit. I think about it, and I think about one aspect of it, one nuance. Well, how would I get these people to carry the content here? Or, what would motivate somebody to want to carry the content here versus somewhere else? Or, how would I handle the fact that there's this type of data coming in there, but that type of data coming in there? So, it pops up every once in a while, and I kind of think about it for a little bit, and the thinking that I do there kind of moves into the storehouse of answers that I've come up with for those things. So, every single time I've ever created something of significance size, there's been years or at least many months of thinking about the thing prior to the point where I actually get started. So this thing, I bought a domain name for it three weeks ago, and I told everybody at Titan about it three weeks ago, but I've been thinking about the thing for months. I've been thinking about it even more frequently since then. It's nearly at the top idea of my mind kind of thing where most of my free time, I think, "Well, okay, here's another thing I need to think about it." Then I think through it for a while, while I'm putting my daughter to sleep, or something like that. So it's interesting that there's not just this idea of the top idea in your mind. I've talked often with people about this top idea in your mind thing, Paul Graham's somebody who wrote something about it recently. It's not just the fact that you have one, which of course is an important conversation, because if you've never thought through these things, some of these important things about that are ... Like, if you're trying to split your job responsibility between multiple roles, there may be certain roles that never get to be the top idea in your brain, which means they never get that kind of free time thinking or that free moment thinking or that extra brain power that allows you to power through some things that might not happen during your normal, actual application of the job. Often I've told people who've wanted to do three things, I'm like, none of those three things are going to be done ... Or at least probably two of those three things are actually going to be done to a one-third attention level, because two of them are not going to be the forefront idea. So it's not even the time to spend on the thing, it's the time to spend thinking on the thing. So there's definitely things worth thinking about, just with regard to what is at the forefront of your mind. But what I want to talk about is giving space for yourself to process through the thing over time. It's almost as if ... So, okay, we did a developer battle. I think I'm going to get to my point eventually here. We did developer battle just recently between two of our senior developers. It's their first time doing this thing, where for a very short period of time, you don't know what the task is going to be ahead of you until you actually start, and everybody's watching you. There's all sorts of pressures. There's the pressure of typing while people are watching you, trying to come up with answers in a short amount of time. But one of the things that Keith, who's one of our developers, mentioned was that when he normally codes, he stops and he thinks things through, and he plans them out before he codes. He finds that he really struggled during the battle because he didn't do that. So he didn't have the thinking done prior to doing the coding, so he was trying to think and code at the same time. I think that's part of what it is here. For example, when I created Karani years ago, I'd had the idea in my head, and I actually even started writing some code for it several times. But what it really took was endless running. I hate running, but I do it because I try to stay healthy ... and endless running sessions where I'm seeing the same scenery pass by, and my brain just started wandering. I wandered to various use cases and features for Karani. I'd come back from my run and write some notes down. Or things where you wake up in the morning and you come up with a new idea. I think one of the benefits of Karani is that if I had taken Venture Capital, I didn't even know what it was at the time, and just had to build the whole thing, I really wouldn't have known what to build at first. It was the incremental building process of putting a little out there and then thinking on it. Honestly, not having enough time to work on a thing gives you more brain power. I wonder if there's actually a value to a constraint where you don't get to do the thing yet, and you need to do a little bit of thinking, a little bit of time sitting on it, and allowing yourself those little kind of thinking moments before you do the thing. It reminds me of a trip I took to Mexico City with a guy named Saul [inaudible 00:05:57] and you take two weeks there, and you're spending a whole bunch of time, American, middle-class, college educated kids, working with people in extreme poverty. What you want to do is you want to go in and fix things. That's what those types of trips are usually about. You go in and fix things, you feel better. He won't let you touch a thing for a least a week. First week, all you're allowed to do is learn and listen and get to know people. Only after you've had some time just kind of learning and listening and really hearing people and understanding a greater depth and nuance of their situation than I think would be normal for us to assume when you walk in with a broken roof. One, let me fix that roof. Only after at least a week, at least half your time of really developing relationships with people and hearing them say what they want and seeing their situations, and knowing what other circumstances there are that may influence it, does it even allow you to have any part in actually making a change. It's the same kind of thing. It can be headstrong. I had a thing recently where I felt very, very emotionally and passionately about a thing and wrote a big, long, kind of hairy email. I showed it to my partner Dan, and Dan said, "Okay, cool, why don't you just kind of sit on it a little bit." It's always a good reminder. You know, sit on a bit and see how you feel about in a little bit. With emotional things, it's because you want to get out of the emotion and make sure you're still happy with how you represented yourself. But it's the same kind of thing, this, "Okay, great, that's what you've got, but give your brain space to stretch in different directions. To be in a different mood and look at it, to be at a different frame of thinking and look at it, to allow something to bubble up in response to something else you see. You see a Tweet, and you say, "Oh, you know what? That's one of the people I wanted to moderate the thing, and I just realized, why would they be motivated to use this thing?" I had not actually considered the motivation of the moderators, and so now I need to figure out what changes can I make to my overall structure that makes these moderators want to actually be participating in? Obviously, this is the thing that I've been thinking about over the last year. It's just these various things that pop up in response to other stimuli. But if I had started building it the moment I had the idea, I wouldn't have had that kind of thinking process about the moderators. I just would've built it and would've said, "Okay, moderators, come in", and I never would've had that trigger to say, "Wait a minute, you gotta make sure this is actually valuable for them to be a part of it." So, I know that the thing about the actual tool I'm talking about is super abstract here, but I think the goal ... There's not even a lesson, there's not even a message. It's just think about the value that comes from having to wait. There's value that comes from just letting your brain rest in the thing and stretch around the thing, and approach the thing from different angles, in different perspectives, before you actually get started on the thing. There may be formal ways to implement that, I'm not sure. But I don't know maybe I think that there's just some value for us to seeing value in that waiting in our work and in our processes. So, I don't know. I hope that's good. I hope so. Thanks for listening to The Five Minute Geek Show. We're back at Five Minute Geek Show and Twitter number five. FiveMinuteGeekShow.com, five. Subscribe to us at iTunes or RSS, if you like the show, share it with your friends, rate it in iTunes. Thanks! Till next time, Matt Stauffer, Five Minute Geek Show.

TRANSCRIPT: Hi, I'm your host Matt Stauffer and this is Episode 100. One, zero, zero. We've made it! I have not, I was going to say tweeted. I've not podcasted, I've hardly blogged, I thought I was back a couple months ago and then it turns out that babies don't like sleeping. Turns out, who knew? So finally back-ish, it's going to be a slow roll back--I'm not going to promise that I'm 100 percent, but I'm back enough to record Episode 100. Hurray, huzzah, there was much rejoicing. If I wasn't so lazy I'd put sound effects in here. People clapping and cheering. The Five Minute Geek Show! it's a purportedly weekly show about development and everything around it. It's purportedly five minutes long. It's really whenever the heck I can get to it and turns out it's sometimes between five and ten minutes. It's one topic per episode, that's true. About front end, back end, mobile, project management, design, entrepreneurship, whatever. If it's geeky, it fits. I'm glad to be semi back. My son is out of school, and all of a sudden my schedule is rearranged and I'm able to find pockets of time for podcasts and blogs now, so my goal is to get a podcast and a blog out this week. That's what I'm going to try and do. So this week we're going to be talking about community. Capital C community. If you are not a PHP developer this will be a little bit less relevant. If you're not a developer, it will be even less relevant, but it'll touch on some things. There is often a line that is repeated by various people within the PHP community that Laravel, the people in Laravel, the Laravel community, are elitist and that they encourage silos and that what they really needed to do (if they weren't pigeon holing themselves into just being Laravel developers) is be involved in the greater PHP community. People, hoity toity, are proud of the fact that they are just a PHP developer, and they would not be so base as to identify with a particular framework. They say, well, I hope you don't put "Laravel developer" on your whatever. "Why wouldn't you just say PHP developer?" They'll point to the wonderful efforts of people like Cal Evans, and other wonderful human beings whom I love, who do great things to encourage the PHP community to have an identity. Every single time they say these things, I respond in the same ways, and they stop responding when they realize their argument is awful and then somebody else spouts the same crap a month later. So! I'm going to say it out loud here. If you have the temptation to go ham on somebody because they consider themselves a WordPress developer, or a Symfony developer, or a Laravel developer, or whatever else developer because they should be just thinking of themselves as PHP developers... Next time you identify yourself as a PHP developer, I'm going to walk up and I'm going to say, "why are you identifying yourself as a PHP developer? Why aren't you just a web developer?" Then when you go to a web development thing, "why are you are identifying as a web developer, why aren't you just a technologist?" When you go to technologist thing I say, "why are you a technologist, why aren't you just a person?" Why aren't you just a human? Where is the line? You have made up an arbitrary line that you think is the acceptable place for someone to identify, below which is not possible. And we haven't even started talking about geographical location or anything like that. Is it acceptable for someone to identify that they're in the London PHP group? Is that unacceptable because that's a delineation? No, none of this stuff matters. All these groupings are helpful. Now remember, if you've listened to this podcast for any time you understand that a lot of the things I'm talking about come out of faith and religious background. So let me tell you about denominations. In denominations, you have the differences between people of the same faith, similar to sects and stuff like that. Where you have multiple people who ascribe to the same general thing, but are different in certain ways. There's all sorts of horrible things where people have mistreated each other, they've killed each other and all that kind of stuff, with the difference between religions. So, in general, we tend to think of unity as good and division as bad, right? So we often have this naïve concept that if we could just rid ourselves of denominations, and everyone would just be the same faith, the same religion, then all of our problems would be gone. The problem is there are perfectly acceptable, and perfectly normal and often very healthy, differences in opinion, and denominations give you space to find the other people who follow along that line in a different way, and celebrate together with them without having to separate yourselves entirely from the community that you're a part of. Or without fighting all the time. Let's say you have a particular interpretation of how something says whether its Saturday or Sunday. What's the seventh day in the bible--is it Saturday or Sunday? Well, that's going to make a pretty big difference about when your church meets and all this kind of stuff. You could fight about it all day all the time, or you could both do the same stuff on different days of the week, and just split along that line. Split has this negative connotation, but maybe you can just both do great things on different days of the week. Laravel does different things, provides different things, has different priorities and perspectives than Zend. If Zend and Laravel were to mush together into one, you would have a lot of battles because Zend has a very specific set of goals and priorities that are not the same as Laravel's. If they're allowed to co-exist separately, then it's perfectly acceptable for both of these sub groups to be a part of a larger sub group, which is a part of a larger sub group. Why PHP? Why are you in PHP and not Ruby? Well it would be very awkward to have every meet up ever be about PHP and Ruby. Let alone the differences of opinion, how are you ever going to talk about something when everything is completely different? There are healthy things about us finding natural differences in a healthy way accepting and sometimes even celebrating those differences, and also being willing to be a part of the greater community. Now, does me being in one denomination mean I'm now no longer part of the larger faith? No. Does that mean I'm incapable of participating in concepts or meetings, or whatever that relate to the larger faith? No. Similarly, does being a WordPress developer mean you now say I'm not a PHP developer? No. So chill out, take a chill pill, get off your high horse and allow yourself to be in multiples; and guess what, you could be a Laravel developer and a Symfony developer, and a PHP developer, and a Ruby developer, and a JavaScript developer, and an Ember developer, and a React developer all at the same time. It is possible! You can do it. It's like this magical thing where you can be a part of multiple communities and no community police is going to come stop you. It's fine, it doesn't matter. So just enjoy it! Allow yourself to celebrate being a part of whatever communities to get the benefits out of them. Being a part of the WordPress community means you connect with other people who are learning how to make money as a WordPress developer, and that is very different than how to make money as a Laravel developer, right? That's fine. There's nothing wrong with that. Trying to learn how to really up your skills in Symfony and Laravel often looks very similar, but not always. So having differentiation in the community allows space for us to share some resources, and not share the other resources, and that's perfectly fine. Really, this is just me going on a rant. Surprise! That's what this podcast is. Here's the fact that every community has various levels that overlap, and various levels of not overlap, and that is perfectly fine. You can be a part of many communities that are a part of many other communities that are sub groups, of sub groups, of sub groups, and there's no magical line. PHP as a community is not the magical line beneath which everything is an atrocity. Within Laravel, you may find yourself a part of the DDD community, and you may find yourself a part of the Hyper Ruby inspired minimalist Smalltalk community. Those are two communities within the Laravel community and that's okay, because you don't have to do one or the other. It's fine, I'm not actually adding anything new to this conversation at this point, I'm just throwing out random things and saying its fine. Just chill out. Allow people to enjoy being a part of the communities they are. If you want to have a positive impact I think the thing that I hear from these people the most is, well, why don't you participate more in the larger PHP community? They don't say those words, but I think that's what is the inherent. Then say that in a positive, not critical way. Hey WordPress developers, did you know that there's this much larger PHP community that we want to invite you into? Here's ways that we can welcome you. It turns out the best way to welcome people is not by calling them silo'ed whatever heritics. The best way is to be kind, and to enter into their spaces and to learn from them, and to offer what you have to them, and to be nice people. It turns out that's the trick. Be nice. Take care of people. I feel like I'm making voices where I'm mimicking people more than normal, so I hope I don't get too many complaints about how snarky I was in this one. I really do love you all. This is Episode 100, I'm making the heart symbol in front of my chest right now. I also got not a lot of sleep last night, and I'm super caffeinated so that might be part of it now. All right we're almost out of time, I will not go over 10 minutes, thank you. Thank you friends for listening to 100 episodes, those of you who've been here for all 100, and if not, that's okay--thank you for being here for Episode 100 anyway. This is the Five Minute Geek Show, we're at @5minutegeekshow on twitter, fiveminutegeekshow.com. You can subscribe to us on iTunes or RSS if you like the show, and it'd be amazing if you would share it with your friends, rate it in iTunes. Until next time--Matt Stauffer, Five Minute Geek Show. Ready to do it? All right go. "If one more label try to stop me there's gon be some dread head boys in the lobby, UH UH"

Take care of your people

Take care of yourself

There's a big difference between conversation and snarky quips. Hire More Women In Tech

A chat about indirect vs. direct conflict, what passive aggression is and isn't, and some tips for responding to folks who manipulate others indirectly.

Give credit where credit is due

The tip: Be a grownup. -- Transcript -- Matt Stauffer: Hi. I'm your host Matt Stauffer, and this is episode 94 of the Five-Minute Geek Show, a weekly show about development and everything around it. It's one topic per episode—about frontend, backend, mobile, project management, design, entrepreneurship, whatever. If it's geeky, it fits. Today we're going to be talking about being a freelance web developer, freelance contractor, and what it is that I expect from you as a business owner when you're doing that. I'm also going to turn off the fan so you don't hear the noise in the background. At Tighten we often hit spots where we have too much work, too much stuff on our plate. Sometimes we'll just say no to clients, but sometimes we'll say yes to a project or we'll just need a little bit more, and we'll turn to freelance contractors to help round it out a little bit, because what we don't want to do is, at that point, hire someone then realize that it was just a temporary kind of boost in the amount of work we're getting. Instead, we bring on freelance contractors to help us do work. These are varying from random freelance contractors we found on the internet somewhere to completely famous freelance contractors who are big names in the PHP or frontend space or whatever else it ends up being. The weird thing is, we have had far more negative experiences than we have had positive. Far more people where I say, "What is going on? How do you not know how to manage your business? How do you not know how to be a grown-up? How do you not know how to communicate to me?" Well, what I've discovered is that the number one problem that we have had working with contractors is that they expect to come into our organization as an employee. In some ways that's my fault, because I often say, "Hey, we kind of think of you as an employee while you're here." Because we usually only have them contract basically full time, so I want to know when you're in the office, I want to know when you're out of the office. I want you to do check-ins with me. I want you to feel like you can communicate to me. I want you on our Slack channels, all that kind of stuff. The problem is, they often think that they're employees, in that I'm the one responsible for checking in with them, or I'm the one responsible for setting the list of tasks, or I'm the one responsible for something else. The thing is, the vast majority of contractors we work with are charging anywhere between $100 and $150 bucks an hour (edit: this is not true. A more correct number would be $75 and $125). If I'm paying you far more per hour than I make, then I'm expecting you to do a whole bunch of work for me, right? I'm not expecting to pay you a whole bunch of money for you then to just sit there and wait for me to tell you what to do, or wait for me to check in on you, or babysit what you're doing. That's not acceptable. I think that ... This is not acceptable for me. Maybe that's how it works with other companies. I think that there's a misconception for a lot of folks who are freelance contractors that the process of choosing to be a freelance contractor and charging much higher rates than you would, whatever else, is really just you ... Like we're paying for the value of having somebody to flesh out our team when we didn't have the resources to do it, and that's why the cost is extra or whatever. That's definitely true. You know, if I didn't have somebody to do that, then I would have to do the work, or I'd have to turn down work, or whatever it ends up being, so there's definitely value there. I also think that it is the value of paying someone who's supposed to be a self-sufficient work-doing resource. Self-sufficient in that they handle their own finances, and they handle their own accounting, and they handle their own timeline. The whole concept of ... At least in the US, the difference between a W-2 employee, which is like a full time employee, and a 1099 employee is that you can't really tell the 1099 employee, like legally, ethically, or technically or whatever, you can't tell them exactly when to do it or where to work from or what stuff to do. You really could just tell them, "Here are the things I need done, and here's the timeline in which I need them done. Here are some conditions around it." Some of the conditions are, you can be like, "Well, you need to check in with me every week to show me what you're doing." Or, "I need to know that you're going to use this particular programming technique versus that, because it will affect the final outcome." That's cool, but you can't tell them, "You know, you need to work these hours at this place using this laptop," or something like that. You can't do that. For me, I embrace that. I say, "Look, I'm not telling you that you need to do it a certain way, but I am telling you that I need a certain level of communication. I need a certain output. I need it done in a certain amount of time," and then I want you to handle it from there. Like, you're a contractor. You're 1099, which to me means I'm going to tell you what to do, and you're going to handle it. We just worked with a contractor that is someone we've turned to on a regular basis, and he's just this extremely mature, incredibly effective communicator. I basically kind of pitched to him the original idea of the project, told him what our budget looked like and our timeline, and he said, "Yep, I can do it. That time line. That budget." Asked me a couple of questions along the way, checked in with me probably once or twice a week on Slack, just kind of let me know what was going on, invited me into his project management tool that he uses for everything, and at the end of the project said, "I'm ready to do a delivery. Here's what I have. Here's the documentation I wrote up for your client, and then I have a couple hours left. I'll do the deploys. Everything's good to go." I hardly had to think about this project the entire time he was on it. I'm not making a lot of money off of the project, because he's a contractor. He costs a lot of money, and the amount I'm paying him is close to the amount we're charging the client, but I had to do almost nothing. That's what I'm paying him for, to do fantastic work, to manage himself, to communicate with me, and just kind of to get stuff done. To handle it, right? I've also brought in other contractors where I'm paying them a whole bunch of money, and then I'm spending all my time on it, and it's just like, "If I'm going to do that, then I'll just do the work myself," right? If you're a freelance contractor, if you are ... Especially as a web developer, there's a whole world out there of people who are freelance contractors who are burning bridges left and right. I've talked to a lot, lot, lot of business owners who try to bring in freelance contractors and say, "Nope. Not going to do it. Never going to do this again. It was a total awful experience." Being this one guy that I'm talking about right now, being like him, he will get work from us forever. Like, forever. If somebody else is just in desperate need, I'll give them his name, but I don't want to give too many people his name because then he won't be available when I need him. Yeah, you've got to be a good coder, but like, just being a grown-up and like managing your stuff goes so far. It's crazy that that is the case. It is crazy that that's the case. Just so you know, I'm not just picking on freelancers. I could go on a whole nother rant about employees, people who apply to our jobs, and the weeding out process of people who actually submit applications to be full time. But for right now, I just want to talk about freelancers. It's just like, what I want to know is that bringing you on the project is going to make my life easier. I'm going to do less work. I'm going to think about this less. When you need something, you're going to come to me about it. This is true for my employees as well. You're going to come to me about it, and you're going to ask me questions, and I understand. Like there are other companies that probably do all of that for you, and for freelancers it's probably a lot easier to kind of jump into some massive corporation where you're just a cog, and they just need to add more cogs, and everything is set up for you. I get that being a freelancer for me is probably a lot harder than being a freelancer for somebody else, but I'm not alone. If you really want to set yourself apart as a freelancer, there's certain things you can do, but one would just be communicate, self-manage, basically be like ... Be a company. Like, I don't get to expect my clients to manage my time for me, or to initiate communication for me. I'm on top of that. So as a freelancer, be a company. Manage your time. Communicate well. Manage expectations accordingly. If you do that, you're going to set yourself above 98% of everybody else that's out there. The things aren't that difficult, but they really show, like, your level of attention and care, and that can go a long way. I hope that I'm not making ... Like, if you freelanced with us before, I'm not trying to throw shade on you, whoever you are. I'm sure you were fine. Really, but I just want to pitch to potential freelancers or current freelancers that there's a different way, and if you do that different way, it sets you apart so much that it really will be to your benefit. I hope this helps. If you have any questions about that, reach out to me on Twitter @5MinuteGeekShow. Check out other episodes at FiveMinuteGeekShow.com. Subscribe, iTunes, RSS, all that kind of stuff. If you like the show, and you're a freelance contactor, go be that 2% of amazing freelance contractors. If you like the show and you're not a freelance contractor, I don't know. Rate it, iTunes and all that kind of stuff. Thanks. Until next time, Matt Stauffer, Five-Minute Geek Show. Son: Five-Minute Geek Show? Matt: Yeah. When you're singing it. Can you do that? Son: Say "Five-Minute Geek Show?" Matt: Yeah, but sing it with that song. Son: (Singing) “I am iron man….” Five-Minute Geek Show. Matt Stauffer: Perfect. My man.

Understanding the end goals--the motivation--of your clients, or yourself, allow you to make the small decisions in ways that serve the goal, rather than potentially fighting it.

Spoiling yourself to avoid burnout

Small, measurable, manageable commitments help people like me move toward their goals. Transcript: Hi, I'm your host, Matt Stauffer, and this is Episode 91 of The Five Minute Geek Show, a weekly show about development and everything around it. It's one topic per episode about front end, back end, mobile project management, design, entrepreneurship, whatever. If it's geeky it fits. Today we're going to be talking about goals and commitments. I know a lot of people who really value the idea of setting goals and measuring your, long goals. I have a lot of friends who really care about analyzing others. The word that they use for it I forget but basically having metrics about everything you do, how often I eat that, how often I do that. I do some of those things. I've been tracking my food and calories through either ... I think the old one was called Calorie Counter and the new one's called My Fitness Pal for years. It really helps me have a good understanding of what my health is like and everything so I'm very thankful for those things. One of the things that I've noticed is a lot of those folks who think deeply about journaling and planning, executing, all that kind of stuff, they all talk about setting goals. If you haven't had some teacher or parent or someone at some point in your life tell you you need to set goals I'd be extremely surprised. Why is it that people like me have so much ... Okay. I have a lot of trouble setting and focusing on goals. I set them and they're really great and a nice idea but some of the things I run into are first, it's really hard to predict what my goals should be. It's like how much should I increase sales by? Well, I guess 10%. Is that realistic? Is that good? Is that bad? How do I really know, I've just kind of made up things. It's good to focus on those made up things but often it's just hard for me to really use them as motivation. Additionally, the hardest part for me is that they're not present. Unless you do a really good job of keeping them at the forefront of your mind or checking in on them regularly or whatever else which I don't do you set the goal and then you feel guilty when you had forgot about it for three months. That's not to say that goals are bad but if you're like me you might find that there's something a little bit better which is small, measurable commitments. Instead of saying, "I'm going to set a goal to lose a certain amount of weight." Instead make a commitment, "I'm going to make a commitment that I'm going to cap my food at 1800 calories a day." "The source of my calories is going to be 40% protein." "I'm going to make a commitment that I'm going to make 10,000 steps everyday." What that ends up meaning is when I have that doughnut in the morning that means in the end of the day I'm scrambling a little bit to figure out how am I going to get my protein in or the next day when I feel really bad about that it's going to motivate me to be less likely to have that doughnut. When it's the end of the day and I've only hit 7,000 steps and I want to go to sleep I say, "Hey, I made a commitment." My wife knows that I made that commitment and so she's okay when I, like a crazy person, go walk around in circles in my neighborhood for 45 minutes to get my steps. Those commitments are easy to make because I say, "I committed to do this thing, therefore I'm going to do it." It's easy to justify the decisions in response to it because it's very hard both to myself and to other people to say, "Well, I need to lose weight. Therefore, I'm going to go walk." That's definitely, it's a true thing but it's vague, it's very distant, and it's very easy to justify away. "Well, I can just skip walking this time, I can just whatever. How much is it really going to matter? I'm already making progress, blah, blah, blah"... but... "I committed to walking 10,000 steps everyday." You don't justify that away. If you don't make 10,000 steps that day it's because you're breaking your commitment. That's not like you should feel guilty or whatever but it's much closer to the wire thing to fulfill. "I committed to 10,000 steps today, I'm going to do 10,000 steps today, that's it." My hope is that I make commitments that are in line with my values. My value isn't actually losing weight, it's just being healthy. I just want to give examples of things that are maybe small, measurable, and very clear when you broke them in the moment, in the immediate space. Commitments might be a good way to reach goals. By doing that I now have to worry less about being able to predict what my goals should be in the future. I have to more just say what are healthy decisions to make that are in the same direction as that goal. With my physical health it's very easy because I know what things are healthy. With things that are a little more abstract sometimes it's a little bit tougher. What are the things ... What are the immediate commitments that you can make right now to get you to the place that you want to be in your career or in your business' growth? Well, let's say you want to become a better developer. Well, it might mean saying, "I commit that every single day I will work through my lunch break and I will watch one Laracasts video and I will read at least 10 pages of this book. Regardless of anything else I will do that or every night I'm going to work through this thing or I will spend one hour on this site app every single day so I have a portfolio piece," or whatever else it ends up being. Maybe if you're a business owner it will be, "Every single day I will put at least 30 minutes into one of 10 business development tasks. I will either blog or make phone calls or follow-up with these people or whatever. I will spend at least 30 minutes doing that every single day regardless." You didn't say, "I'm going to increase my sales," or, "I'm going to be the best developer ever." You said, "Every single day I'm going to do X amount of things to get myself ... Or every week or whatever to get myself moving in the direction I want to go." I think the primary goal of this one is just saying that if you're like me you may find that goals are nice but often just induce guilt when you forget about them. Small, measurable commitments that will move you in the right direction are a lot easier to keep fresh because you just get in the pattern of them. It's a lot harder to break them and it's a lot easier to justify doing things that might seem a little weird for the sake of them. It's a lot harder to justify not doing them when they're small. It's not as if you're like, "Well, I'm going to lose 50 lbs." Well, it's very easy to feel vaguely non-committal to that when time comes and it's family doughnut time. It's a lot easier to say, "I'm going to walk 10,000 steps today," and you're a little tired and say, "You know, it's only 2,000 more steps and I committed, I'm going to do it." I hope this helps someone. Thanks for listening to The Five Minute Geek Show. We're at Five Minute Geek Show on Twitter number five. Fiveminutegeekshow.com. You can subscribe to us on iTunes via RSS. If you like the show share it with your friends right on iTunes. Thanks. Until next time, Matt Stauffer, Five Minute Geek Show.

It turns out, it's perfectly OK to specialize in a certain tech. Who knew! Tighten

Whether it's getting a new job, launching a product, or finding new business, the things you'll need in the future require you to plan now.

Notes: Equality vs Equity Graphic The New Jim Crow Carlos Doesn't Remember - The Revisionist History Podcast Transcription: Hi. I'm your host Matt Stauffer, and this is episode 88 of The Five Minute Geek Show, a weekly show about development and everything around it. It's one topic per episode about front end, back end, mobile, project management, design, entrepreneurship, whatever. If it's geeky, it fits. Today, we're going to be talking about diversity in hiring. So what I mean by that is: I own a business, I co-own a web development business, and I also care deeply about equality, equity, diversity, and opportunities being given to people who don't have so many opportunities. I'm highly aware of the fact that as a white American male--Christian, straight--I have basically the best gig there is. It's very difficult for someone to have it better than me. By this I don't mean, like, "My life is great, and your life is bad." I mean: I have privilege, and I have power, and I have all sorts of things going for me. I've talked a lot about this before a lot. I was on a call with some friends the other day who are also business owners, and in our conversation I found words for something for the first time, and wanted to share it. It's really helpful for me to think it through. We were talking about diversity in hiring, talking about this question: "How do you hire either employees or contractors in a way that works towards bringing about a more equitable world?" I think the first step we tend to take is saying, "How do we do more diverse hiring? How do I make my company not just a whole bunch of white dudes?" This is okay. This is a good start. Diversity for the sake of diversity is a good thing, but I think it's a too-basic understanding of it; "I have all white dudes. That's not the way it's supposed to be, therefore I will change it." Let's talk about moving past just that. One of the more important things to do next is to ask yourselves questions along the lines of, "What is the reason that I want diversity, and what is the reason I don't have diversity right now the people I work with?" You'll start getting into interesting questions--talking about how common it is to hire people we already know, seeing what people's pre-existing friend networks do for them. One thing you'll often notice is that people who have a lot of power, and privilege, and networks, tend to get internships or first jobs based on relationships with friends. Maybe your dad's college buddy has an agency, so you intern with him, and that's an opportunity that other people don't have. You get to go to college, and your parents pay for your college, and so you can go to college for 4 years without having to work, and so you get opportunities while you're there. Whatever it ends up being. Heck, just the entire concept of the unpaid internship is very limited to people with a lot of money or ability in the first place. There's all these things that come into that kind of conversation. Let's also notice that we have primarily white male business owners. People in general, not just White people, have networks that generally reflect their ethnicity. White people in the US are more guilty of having networks that only reflect their ethnicity than anybody else, but everybody's guilty of it. And maybe it's not even "guilty." It's just life. And with that being the case, if you're hiring the people you know, or you're hiring the people you run into more often, or a little more subconsciously, nefariously, if you're hiring the people who are more like you and make you more comfortable, then that's going to have a lot of influence on who you have working with you. We've got to have the conversation about this. I hope we will choose to say, first, "I want my company to be more diverse"... but hopefully also, second, "That is the case not just because I feel some external pressure, but because I recognize that having people that are different than me on my company is good for my company, and I recognize that there's people in my country who have less opportunities, and I want to be a part of bringing about equity. I want to bring about justice." This is good. If you've never heard of the term "equity", and you wonder why I'm using it instead of "equality", I'll link a graphic in the show notes that explains it really well. Basically, the difference between equity and equality is, equality means treating everybody the same. A lot of people come out of, let's say, 500 years of racist United States history, and say, "Okay, that was bad. Now everybody should be treated the same." That's equality. The problem with equality is it's assuming that everybody has an equal playing field. All you have to do to be equal, to treat people well, is to give everybody the same thing. Equity says, "Whoa. 500 years of difference makes 500 years of difference. We don't get to just now, all of a sudden, make everything exactly the same." Equity means, for example, recognizing that white families have had that many years to build up wealth. We keep wealth in a lot of different ways. We keep wealth in houses that we own, or in savings, or in tables that get passed down when you get married or whatever. There are so many things that we keep wealth in. The wealth that we have gathered, we have had the ability to gather in a way that other people have not had the ability to gather. If everybody has an "equal" starting point, just wealth alone would put us in this much different place, not even talking about all of the differences that have to do with education, and opportunity, and jail rates. If you want to think about that, go read the book The New Jim Crow. All those things are striated along racial lines in the US. There's just so many pieces where things are different and have been different for so long that you can't just come today and just say, "Okay, treat everybody the same. Now you're done." It doesn't work. Equity says, "You treat each person uniquely based on who they are, and the experiences they have, and the opportunities they have, such that the goal is for everyone to be able to end up in the same place." I'm not talking about socialism, you know, some crazy thing that will turn you all of. I'm socialist-ish, maybe, but I'm not talking about something crazy in terms of, like, "Well, nobody should be able to work harder or work less, or lazy people should get the same as everyone else ..." No, no, no. You should put extra work in to give people the opportunity to have the same chance for their hard work to get them a good thing. It's going to take more work to help someone who has a historic lack of opportunities, and lack of wealth, and lack of education, and lack of whatever else. It's going to take more work to help that person have an equal amount of opportunity than it is to give someone who has privilege and power and all that kind of stuff historically to get the same amount of opportunity. In the end, they should have to do the work, and they will do the work. It's not about giving something a freebie, but it's about recognizing that someone has to do the work to overcome those disparities, so that everyone has an equal opportunity. You could say, "Oh, well, pull yourself up by your bootstraps. Take a look at this one guy who escaped poverty; why aren't you all like him?" If you want to think about that, Malcolm Gladwell has a podcast, and he has a couple of episodes recently that I'll link to talking about this exact same thing. Talking about what happens when big schools like Stanford and Yale have programs to basically give free rides to really bright students from really difficult neighborhoods, and the episodes talk all about that. I'll link that in the show notes. In general, it's just not that easy. Yes, a few exceptional people escaped, but the difference is, with white folks, white males especially, we don't have to be exceptional to graduate college. We don't have to be exceptional to get a good job. We just have to do okay. We have to be in the top 50% of our class or something like that. With people of color, with women, with people of historically oppressed groups, they have to be in the top, like, 1%, and overcome like 10 million other things. Again, we want the final amount of opportunity and freedom to be equal, and therefore we must be equitable. All of that set up, when we're talking in the hiring context, ends up with me having said a thing that I wanted to share here, which is: "Somebody, somewhere, somehow is going to have to do the work to make that difference." One of the great examples of it I love, often, that we use in helping students understand this, it's basically this game where everybody starts in a line, and you say, "Your goal is to get to the other wall." Then, we start asking questions about your privilege. "Have you ever had this? Have you ever had that?" Everybody who answers yes to any question has to take a step forward--before the race even begins. Basically, people with privilege and power, where your parents had this kind of money, or your parents had this kind of education, or your schooling had this kind of thing, whatever, it ends up being you take a step forward, and another, and another, and by the end, before the race even starts, you recognize that the primarily white males end up basically a foot away from the wall. The people of color, and the women, and everyone else, end up basically against the back wall. What we're recognizing here is, if we all have a starting point that is different, what we want is not to carry somebody over the finish line. We want to do the work to get everybody at the same starting line. Somebody's going to have to do that work. A lot of programs, and a lot of democratic type stuff says, "Well, the government should be responsible for that." I think that the government should help! Then a lot of, especially religious right, conservative people say, "The government shouldn't do it. The church should do it. Individuals should do it." Okay, cool, great. Church should do it. Individuals should do it. Great. Awesome. What I'm just saying is everyone should do it. I want the government to do it. I want the individuals to do it. I want religious organizations to do it. But for me, as a business owner, hiring is a place in which I don't want to carry somebody over the finish line of working for me. I don't want to give someone a job just because they're a woman or a person of color or whatever else. However, there's an opportunity in hiring for me to make things fair and for me to act with equity. What that ends up looking like is, sometimes, I need to put more work into bridging those gaps. I can talk at another time about what that more work looks like in my specific context. I'm way out of time. This is going to be the longest Five Minute Geek Show ever, but that foundational concept is really weird to say out loud, but if we are saying we want to make a difference, we want to see diversity reflected, we want to see people all have equal opportunities, it's not just as simple as saying, "Okay, now where are the qualified women and people of color who want to come work for me?" You know what I mean? I'm not saying anybody in particular I know says that, but that's kind of maybe my first response. When I say, "Okay, I want to hire diversely." "Okay, well where are they?" That's, like, common refrain kind of thing, right? The thing is, it's not just as simple as, "Where are they?" It is, "Am I willing to put in the work?" Somebody's got to put in the work to change the starting line so everybody has the same starting line, in your hiring process, right? Are you willing to put in that work? Are you willing to make a commitment to putting forth effort and money to changing the starting line of getting a job with you, or getting a job in your industry, or whatever else? Yeah, I'd love to talk more about this. Maybe I'll do another Geek Show about this later, but I hope this helped someone think through these things. I'd love for you to contact me if you have any questions. I'm @StaufferMatt on Twitter. You can also hit me up at @5MinuteGeekShow on Twitter, or we're at FiveMinuteGeekShow.com. That's it. Thanks for listening!

I don't think we mean the same thing when we say "remote"

Why source diving is an undersung skill

Planning makes better (meetings, podcasts, bizdev, interviews)

I don't think you have $10,000 to waste on that AWS token -- don't commit your credentials to GitHub! phpdotenv dotenv 10,000 AWS secret access keys carelessly left in code uploaded to GitHub

You have more power than you realize. Really. With Great Power Comes Great Responsibility Brandon Sanderson's Steelheart series The Great Tighten Experiment Andy Crouch: Culture Making, Playing God

In what ways, other than money, are we paid for our free (open source, teaching, etc.) work? My latest blog post: Why I Published My Book With O'Reilly Bootstrapped.fm with Jane Portman CreatorLove

42 Lines article "Some principles of web development" including good talk about when you're sick

Vision and goals for every thing you do allow you to make good decisions in the face of conflict Refactoring To Collections

Quick thoughts on my new iPad Pro and Apple Pencil

Inbox Zero, Getting Things Done, and freeing your brain Inbox Zero Trusted Trio Getting Things Done My six-year-old write up of GTD

I don't just care about tech: I'm also deeply passionate around issues of race, ethnicity, and justice. Three-Minute Geek Show My old race/ethnicity/justice blog Pulled Over

Write code that you will love to write and return to, not for speed or computer optimization or whatever else. Pay money to stop wasting time "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." - Martin Fowler Writing Tests You Can't Automate - Three-Minute Geek Show Episode 45 ActiveRecord and the School of Zonda - Laravel Podcast "The sabbath was made for man" quote in Mark 2

An interview with Steven Wade, the creator of Upstate PHP Upstate PHP @stevenwadejr PHP.Net page on User Groups Gainesville PHP Greenville, SC Wikipedia

I can't feel my hands (when I'm overwhelmed with stress/anxiety) Greg Baugues - Devs & Depression Ed Finkler - Open Sourcing Mental Illness Adam Culp - Developer Anxiety, We're Not Alone Adam Culp - Delayed Anxiety, Never Forgotten (not mentioned in the podcast, discovered later) Fred LeBlanc - Surviving Digital Overwhelm & Burnout

Talking about the new service, briefs.fm, and my new diary/micropodcast, the Three-Minute Geekshow Briefs.fm Ben Orenstein Chris Hunt Three-Minute Geek Show Three-Minute Geek Show on Twitter Vim tips with Ben podcast Codecation updates podcast

Statamic - note that everything I say on this episode is about the Statamic v2 beta Craft Soon-coming Tighten blog

How we use Pull Requests at Tighten Tighten Five Minute Geek Show Episode 23: 3 Ways to Give Back to Open Source & How to Write Good Pull Requests LICECap

Giant Robots Smashing Into Other Giant Robots Fortune writeup on Seth Priebatsch

Convention over Configuration, Convenience over Complication

A live-streamed episode about live-streaming. How meta. My Twitch channel AssertChris' tutorial on how to stream on Twitch OBS

Full Stack Radio - Woody Zuill #NoEstimates Agile Manifesto

Don't be a jerk Gator Linux User Group event

Ottomatik Nitpick Forge Dead Man's Snitch