Life

A change in pace and style

Historically I have tried to maintain a very specific tone and format for blog posts.

I have since decided it’s more important to me to get things written down and out there than to triple check and make sure everything is perfect.

If I’m going to advocate for others to be active in the community, I need to put up or shut up. So why not make my blog more closely mirror me: big, loud, opinionated, and weird.

Oh yeah, extra helpings of weird.

I’ve long said I’m ok being loud and crazy at conferences because if nothing else it gives the two most awkward people there (when one of them doesn’t happen to be me!) someone to point and laugh at together.

So, there you have it.

LONG LIVE THE WEIRD.

If you’re not worried yet, then you definitely have a lot more faith in my ability to be normal than I do.

Looking back: Sunshine PHP 2013

Warning: there is some name dropping. Okay, a lot of it. The only goal of it is to try and convey the extreem importance of attending smaller conferences like Sunshine PHP. Close knit communities in tight quarters breed very interesting opportunities to talk to people you normally might not have a chance to. Take advantage of it every chance you get.

First, show up early

If at all possible, come in the day before the event. Not only will you wake up rested for the conference, but you can take part in pre-conference festivities. The night before the conference, a rather large group of us all went out to dinner together. In no particular order (and please forgive me if I have left anyone out, or added anyone, it has been quite a few days): Jim Ruga, John Kary, Brian Fenton, Jeff Carouth, Sebastian Bergmann, Anthony Ferarra, Matt Davis, Damon Jones, Matt Frost, Beth Tucker-Long (and her family), and Lonnie Brown.

Now even if you’re not super community savvy, a few of those names should stick out like a very sore thumb.

Second, don’t forget the hallway track

I know, I know. You’re excited to go see all the speakers give their talks. By all means, if there are talks that look like they absolutely cannot be missed, then go watch them! However, don’t forget that you will likely be missing a rare opportunity to sit down and have a (near) one-on-one conversation with someone you normally may not run into. I lost count of the number of times I saw Cal Evans and Paul M. Jones talking at a table with a couple empty chairs, or Anthony Ferarra, or any number of people. If there’s someone you want to be able to have a prolonged conversation with, look out for them between talks and talk to them.

Third, be actively involved

The more you participate in the conference, the more you will get out of it. Join the hackathon, play jeopardy, or just Drink With Friends(tm) (seriously, how is that NOT a game yet??). Introduce yourself. Break out of your shell. As out of place as you feel, others feel the same and are just hoping someone comes and talks to them. If you talk first, then you don’t have to wait so long! Want to meet someone but not feeling up to introducing yourself? Come find me (or, if I’m not there, ping me on twitter and I’ll try to find someone to help you!) and I will go do the “hard awkward part” of the initial introduction.

Seriously. The PHP community is an amazing group of people. If you love the community, it will love you back. I’m not just talking about the publicly visible members, I’m talking about everyone. Each and every one of us contributes to the community in our own way, and it needs all of us to thrive. Coming to events like Sunshine PHP helps to foster the community feeling, because people stop being these faceless nicknames. It makes it easier to communicate with people online, and helps you feel like less of an “impostor” at future events, as instead of simply going to a conference, you get to go see your friends again!

2012 Recap

So I wanted to take a little time and document what happened in 2012 for myself.

I think the biggest things I want t take away from 2012 are a few key lessons:

Don’t Be Afraid of What Other’s Think

If you spend your life mired in worries about what others will think of what you are doing, you will never get anything done.

Just do.

Too much of our lives (collectively) are spent wondering about what others will think about what we are doing? So what. Who CARES if you are wrong. People are wrong ALL OF THE TIME. What matters is that you are not so attached to your wrong opinion that you don’t change it when presented a valid argument otherwise.

It’s said the most ‘thought to to be smart’ people aren’t smart because they’re right but because they are quick to change their minds.

I, of course, have the luxury of never particularly caring what others have thought of what I say or do. It’s lead to some pretty awful predicaments — but some pretty awesome ones too. Who, among my close friends, would have pictured me as being one of the ones to immediately volunteer for Symfony Jeopardy at Symfony Live? Especially when I am culturally dumb and (at time time) was quite technically deficient. That didn’t stop me from answering the only then-to unanswered question though!

Just do.

Go up in front of everyone, be a goof ball, have fun, laugh, be silly. Anyone who actually cares in a bad way isn’t anyone you want to associate with anyway.

Just do.

Don’t be afraid of what others will think. Seriously. Most commonly, what most other people will be saying is “Gee, I wish I could do that!” And you know why they can’t? BECAUSE THEY ARE AFRAID! 99% of the people who would say anything negative would never have the nerve to do anything like what you are doing. It’s 100000x easier to criticize than to produce. Be sure to check the background of those who give you negative feedback and take their input with the appropriate level of expertise it warrants.

Just do.

Get out in the community

The PHP Community in general is AMAZING. It’s full of brilliantly smart people you can talk to, and gives you external input to your internal processes. If your local community isn’t as as deep into the things you are? Learn to teach them! Learn about how to talk to other developers, how to share your skills and techniques. You’d be surprised what you’re capable of.

If you haven’t spoken to groups before, consider giving a few talks to a local user group. Most likely they’re running their regular speaker lineup through the wringer, week after week, and offering to talk about something (anything!) that you know even passingly well enough to talk about (I once essentially winged a talk about design patterns — shhhh!).

The other thing being in the community will do is give you a feel for the pulse of where things are heading. There are currents and drafts in the community which you don’t catch unless you’re paying attention. See what’s on the horizon, and pay attention. You’ll never know what you’ll miss if you’re not paying attention.

Prove you can ship

I can’t reiterate this enough. The value of someone who can actually ship a product is waaaaay above someone who can only point to minor contributions in a larger project. If you’re one of those nameless cogs in a giant organization, it’s time to join an open source project or build your own thing on the side. Seriously. Nothing shows your value more than being able to to actually ship something. In the world of business, ideas are cheap, and execution is everything. Show people you can execute, and you will open doors.

Know your stuff

Read up on the important things core to being a high quality software developer: Patterns, Anti-Pattens, and Code Smells, among other things. These will teach you the do’s and don’ts of our industry, our trade. They will show you what to do, and often more importantly, what not to do. It’s the same as new inductees into Martial Arts learn Kata’s, new developers need to learn these patterns, anti-patterns, and code smells. It gives you the tools to reflexively approach similar problems in the future, and tools to expand on when you need to create something out of thin air.

Don’t be afraid to be wrong

Look at my blog, or the advice I give out in #symfony — I’m “wrong” all of the time. There’s usually a much more efficient way to do something than I recommend — but I don’t know it! I help people get stuff done. The academic stuff can be left for those Ivory Tower folk. I’m much more interested in what gets stuff done in the trenches. Getting something done is more often much more important than doing it in the best possible way. Working implementations refactor much quicker than potential implementations grow while wandering in the sea of WTF I HAVE NO IDEA WHAT I AM DOING?!. Being wrong is not a bad thing. It means both that you were strong enough in your opinion that you could voice it, and that when presented with solid contrary evidence, you changed your wrong opinion into a right one. How awesome is that?!

Enjoy what you do

We’re in this because we have a passion for either building better code, or building things people love to use, or hell, even just building things. But if you’re not enjoying your work — seriously the door is right over there. Life is FAR TOO SHORT to spend your days doing things you loathe. If you’re going to do something for your career, make sure it’s something you enjoy. I avoided doing development as an actual full career for many many many many many many many many years, because I was afraid that if I took what I loved and made it a job, it would never be the same. Interestingly, I was right — it was never the same. Now I love going to “work” almost every single day. Seriously, it’s that simple. Do what you love and you never work a day in your life. Honest.

Now with that out of the way

You may be asking yourself “But this is a recap — what do YOU do during this year?” Well, let’s see:

  1. I went to Symfony Live.
  2. I started blogging more regularly.
  3. I was more active in #symfony, #silex, #phpmentoring, #protalk, and #symfony-dev (yikes, right?).
  4. I contributed to the Symfony Documentation.
  5. I started attending User Groups regularly (in Lansing, and Ann Arbor).
  6. I gave a talk in front of 100+ people.
  7. I gave a talk over 30+ minutes.
  8. I have at least one person using one of my open source bundles for Symfony2
  9. I have given three people technical feedback on their technical products which have (I feel) reasonably improved the quality of their product (I think I have a knack for this — have sent an email to php|arch to be a technical reviewer — look for this in 2013’s recap!).
  10. I convinced my 4 best business friends to all be business friends together.
  11. I started mentoring officially (Uzo, Luis, and Yitzchok — you guys are the best folks a mentor could ask for, really!).

What do I want to do, going forward?

I’ll tell you what’s on my list.

  1. I want to launch a product (in the works)
  2. I want to give a mainstream talk at a conference (not an unconf talk)
  3. I want to be more involved in the community (you guys are awesome, seriously!)
  4. I want to help more people hate their jobs less (hey, it’s what I do…)
  5. I want to blog more (is this cliché?)

Anyway — 2012 was great, let’s make 2013 even better!

On taking our jobs seriously

So, Myles Recny wrote a little conversation about why you should be nice to programmers.

There’s so much about programming that is incredibly satisfying and empowering. But it doesn’t change the fact that, for me, programming builds an acutely negative mindset over time. I’m always asking the question “what’s wrong with this?” Positive people are always focusing on “what’s good about this?”

As soon as I saw it, I immediately sent the following back to him:

We can’t spend our lives mired in depression by seeing everything we do as imperfect. Nothing is perfect. Especially with our “programmer’s eyes” for technical detail, we will almost never achieve a level of quality that we would consider perfect. In fact, I would be worried if we did achieve perfection with any regularity.

Instead, if you start to feel the same way as Myles did, take a step back, and a deep breath. Stop looking at your code base, and start looking at your usage metrics. Look at all of the people using your code. Deriving value from your code. Improving their lives because of your code. If you don’t have access to that information, ask for it! Validate that your “bug-riddled mess” is actually helping people do something they want (or need) to do. Seeing this will help fuel your creativity, and drive you to provide ever better solutions.

Take some time to connect to your users. They are your best defense against the negative subtext that we operate in. View your work through their eyes, and see how they derive value from it. It’s a powerful thing, knowing you are improving someone else’s life — and we get to do it every single day. How lucky are we?

On continuing education – Podcasts

I wanted to write a quick note about one of the ways that I stay up to date with things: podcasts.

They’re great for anyone who commutes, and the rest of you can surely find some time to fit them in somewhere. Even if you can only track one or two.

A lot of the podcasts I listen to aren’t specifically web development or even PHP related, but that is on purpose. I have Twitter and RSS feeds, as well as IRC for keeping up with more directly related topics. I’ll detail those later.

For Development

For Education

  • The Critical Path — A podcast by Horace Dediu about the theory and practice of disruption, and jobs to be done theory. It has an Apple centric overture, but it uses Apple as an example to build a lesson from.
  • Freakonomics — Always interesting(ish) topics, to keep the brain going.

For Humor

twitter