Skip to main content

The Year I Didn't Attend A Conference

Now that the year is mostly through, but we still have enough of it left to talk about, I’m going to make a belated statement and an explanation:

I will not attend a single conference this year.

No PyCon. No Traveling for packed days of community building and education. No lower key conferences in my own home city, even. Not a single conference will list my name as an attendee for the enter year of 2014.

And I feel great about it!

My decision not to attend any conferences this year was an intentional one and has been both uplifting and life saving. The thing is, I absolutely love conferences. I love going to PyCon more than I love most holidays. I’m enormously excited to live in the area that hosts both NCDevCon and All Things Open. Hell, I love conferences so much I organized my own just because I wanted to attend it so badly.

As an enormous supporter of tech conference attendance, I realized that I had no choice but to take a hiatus from attendance. I had something to prove to myself.

I am a skilled developer who grows in my craft through my experience and I am valuable to my teammates, projects, and to myself. I am all of these things through the efforts of my job, which I am very good at. I am all of these things without pouring my energies and emotions into community events and contributions.

What I needed to do was prove to myself that I don’t need to attend conferences. While conferences are incredibly rewarding, enriching, and wonderful I also grew concerned that they were growing into a trap for my self confidence and my self worth. I grew concerned that I was channeling a lot of my valuation of myself through my attendance and participation in these communities.

I went from a self-taught kid messing around with computers in his spare time to a full-time Python consultant supporting his family on what he taught himself to an important member of a growing development team and projects of value to large, important corporations. In a few years time, I became one of the people that I had looked up to when I was learning from the community of programmers I had found online.

When I was younger and teaching myself, I hoped to one day attend PyCon.

When I grew more experienced, I hoped to one day be able to afford PyCon.

At some point, there was a year when PyCon slipped by and rather than look up to and forward to one day going, I spent the time depressed because I was yet to be able to attend. My freelancing made enough money to pay the bills, but not to attending something extra like this. It was a real pain point for me. It hurt. It made me feel inadequate as a developer.

I wondered, more than once, how all these other people attending and loving PyCon were able to be so much more successful than me.

But, it happened. I got better at my job and in turn got better jobs and, eventually, I attended PyCon. I attended three PyCons in a row, and began attending other conferences. I travelled for them as well as attended local conferences, like NCDevCon and All Things Open. I organized PyCarolinas and it was one of the most rewarding experiences of my life. I gave my first talk last year and flew to New York to speak on a live panel about offline applications on the web. I had made it. I was part of the in crowd. I was one of the cool kids.

And none of this is bad. I don’t regret any of this. My choice not to attend conferences this year isn’t any decision that my past attendance was a bad idea, or that it would be a bad idea to attend this year, even. After investing so much self worth in my success with conference going, I just realized that I had to prove to myself that I don’t rely on them. And it was a success, so far. While I haven’t attended any conferences this year, I’ve accomplished things I’m proud of at work, and on my own. I am succeeding in feeling good about myself, and that is an accomplishment in and of itself.

I am not an imposter.

Next year, I’m going to have a great time at a few conferences.

Comments

Popular posts from this blog

On Pruning Your Passions [MOVED]

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…

The Insidiousness of The Slow Solution

In software development, slow solutions can be worse than no progress at all. I'll even say its usually worse and if you find yourself making slow progress on a problem, consider stopping while you're a head.

Its easy to see why fast progress is better: either you solve the problem or you prove a proposed solution wrong and find a better one. Even a total standstill in pushing forward on a task or a bug or a request can force you to seek out new information or a second opinion.

Slow solutions, on the other hand, is kind of sneaky. Its insidious. Slow solution is related the Sunk Cost Fallacy, but maybe worse. Slow solutions have you constantly dripping more of your time, energy, and hope into a path that's still unproven, constantly digging a hole. Slow solutions are deceptive, because they still do offer real progress. It is hard to justify abandoning it or trying another route, because it is "working", technically.

We tend to romanticize the late night hacking…

Finding "One Game A Month"

I was really excited about the One Game A Month challenge as soon as I heard about it.
For about two years I've struggled in fits and starts to make my way into game development. This hasn't been productive in any of the ways I hoped when I started. Its really difficult to be fairly experienced as a developer, which I believe I am in my day job as a web developer, while struggling really hard at an area in which your experience just doesn't exist.
Its like being a pilot who doesn't know how to drive.

But this challenge provided a new breath to this little hobby of mine. It gave me a scaffolding to experiment, to learn, to reflect on finished projects. I had spent far too much time on game projects that stretched on far past their exciting phases, bogged down by bad decisions and regret.
And it has worked.
I have a lot to learn. I have a lot of experience to gain through trial and error and mistake and discovery. I have a lot of fun to be had making more small games t…