Open Source

Decoupling your Composer from GitHub and Packagist made easy

, , , 2 Comments

One of the things I learned very early on about working with a large team, is if you don't make tasks as frictionless as possible, they have a tendency to not get done.

When we bought into using Behat as our functional testing framework of choice, it came with a mandate that when we install Behat, it cannot come from public sources. GitHub goes down. Repositories get updated. There have been instances of repos being compromised. We had to insulate ourselves from all of that risk. Fortunately, Composer has a GREAT tool for this, called Satis.

Satis provides you a way to create your own Packagist repository, complete with distributable tarballs of supported libraries. The one problem that I ran into (and this may have since been fixed? I'm not sure!) is that I couldn't get it to download the dependencies of my dependencies. For example, your composer.json requires Package A which requires Package B. When I tried this, Satis would only build a repository with Package A. Knowing this would cause trouble down the line, I decided there had to be a way to make this simpler.

Out of that, Satis Repository Builder was born.

It will generate a Satis repository and upload it to S3 all with a single command. It's still got some cleanup, but I realized that if I hadn't done it in the last 4 months I wasn't likely to do it in the next 4, and perhaps some feedback (or pull requests!) will spur some new life into my interest in it.

Once you have uploaded your repo, you can simply use the following setup in your composer.json to enforce pulling from your Satis repository:

That's it! I'm sure there's tons that can be done to the repo builder, and I look forward to seeing issues and pull requests!

One last piece of advice from the trenches

When you're using a tool like this to decouple yourself from the risk of third party updates, be sure you are as specific as possible. List all of your dependencies and your dependencies dependencies, so when you do need to go back and upgrade a version of something, you control the scope of the update, not composer. The more specific you are in your composer.json about versions, the less variation you will see between builds of your satis repository.

Virtualizing your stack with Vagrant and Puppet (Redux)

, , , No Comments

I had the great fortune to be invited into the Columbus tech community and present my Virtualizing your stack with Vagrant and Puppet talk at the 2013 Columbus Code Camp. I had a blast, and if you're reading this from Columbus, thank you for having such an awesome community.

This talk has been almost completely revamped since the last time I gave it. We walked through what Vagrant is, and how it relates to various virtual machine systems and cloud providers, and then forked from there to talk about how to use Puppet to create meaningful configuration of your servers.

Finally, and I think most importantly, we talked about how to sell the time investment to your superiors, and discussed the fact that if your development environment is not as close of a carbon copy of your production environment as possible, there is no clear way to verify that the code you have in your development environment will work at all once released to production.

https://speakerdeck.com/jmather/virtualize-your-stack-with-vagrant-and-puppet-columbus-code-camp-2013-edition

(if the slides are not showing up, they may not have finished processing just yet)

Additional resources:

p.s. The video was reconstructed by manually taking the audio and combining them with the images in iMovie. If there's something wrong, please let me know and I will work to correct it.

p.p.s. There is (somehow) a complete section on Hiera missing! I don't know if I opened the wrong slide deck or what. The up side is there apparently wasn't time to cover the material anyway, but the next time I give this talk it will be there.

Code Evolution: Contact Form (part 2) – A2LAMP

, , , , No Comments

On Saturday, February 16th, 2013, I talked my way through setting up the same sort of contact form we set up in Code Evolution: Contact Form (part 1) using Silex instead of creating our own framework. There was a lot of invaluable discussion around the room about the value frameworks bring to the table as well.

For code reference, you can see where we started from, and what the code looked like when we were finished.

Related links:

Looking back: Sunshine PHP 2013

, , , 2 Comments

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

, , , , , 1 Comment

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!

1 2 3 4›»