Jumpstart Lab

Technically Awesome

2012-09-27T11:24:15-04:00

Something Technical and Awesome

Jeff Casimir gives a talk on Internationalization & Localization.

Talk presented at Steel City Ruby 2012.

Madison Ruby 2012 Panel: Teaching Rails

2012-09-27T11:24:37-04:00

Madison Ruby 2012 Panel Discussion including Chad Pytel, Jeff Casimir, Jeff Cohen, and Stephen Anderson.

Anti-Oppression 101

2012-10-03T13:40:58-04:00

Everyone acknowledges that the software field has an issue with gender balance, but there are many of arguments about what to do about it. Recent events have caused the community to scrutinize how they treat the issues of race and gender. The social justice community uses the term 'anti-oppression' to describe techniques for being more inclusive to people of a wide variety of backgrounds, ethnicities, sexualities, and genders. Software developers generally lack exposure to these terms and techniques. In this talk, Lindsey and Steve will introduce basic anti-oppression concepts, and provide specific examples of situations where we as software developers can use these tools to engender a more inclusive community.

Presented at the 2012 Madison Ruby Conference

Hungry Academy: Full of Lessons

2012-10-03T13:39:02-04:00

Building Developers: Lessons Learned from Hungry Academy

Here's the quick story of what's worked, what hasn't, and the lessons learned as we try to solve the developer shortage.

Presented at Goruco 2012

Designing Hypermedia APIs

2012-10-03T13:45:41-04:00

Rails did a lot to bring REST to developers, but its conception leaves the REST devotee feeling a bit empty. "Where's the hypermedia?" she says. "REST isn't RPC," he may cry. "WTF??!?!" you may think. "I have it right there! resources :posts ! What more is there? RPC? Huh?"

In this talk, Steve will explain how to design your APIs so that they truly embrace the web and HTTP. Just as there's an impedance mismatch between our databases, our ORMs, and our models, there's an equal mismatch between our applications, our APIs, and our clients. Pros and cons of this approach will be discussed, as well as why we aren't building things this way yet.

Presented at RailsConf 2012

"Ruby can't scale." O RLY?

2012-10-03T13:51:09-04:00

Metrics-Driven Ruby/Rails Performance

"Ruby can't scale." Tell that to LivingSocial, Groupon, Gowalla, Sony, and the rest of our community pushing millions of requests per day. Scaling an application isn't about piling up hardware and dropping in the newest database fad, it's the combination of design and refinement. In this session, we'll look at refining Ruby code using tools to:

Find CPU-intensive hotspots
Measure memory and object allocation
Monitor query count and duration
Isolate data-store bottlenecks

This is not about info-porn. It's about finding the 1% of your code that, through optimization, can dramatically improve performance.

Presented at the 2012 LA Ruby Conference

WAMU's Kojo Nnamdi "Tech Tuesday"

2012-01-16T15:40:28-05:00

Tuesday 1/17 at noon I’ll join friends Roz Lemioux from Fission Strategy and Ryan Seashore from CodeNow to talk about “learning to program” on WAMU’s Kojo Nnamdi show. You can listen live at http://thekojonnamdishow.org/shows/2012-01-17/training-where-tech-jobs-are-coding

After the show I’ll update this post with takeaways and notes from the conversation.

The World is Full of Real People

2012-01-13T07:42:21-05:00

Yesterday at CodeMash 2012 in Sandusky, Ohio, I gave a five minute lightning talk about something that’s been in my mind: the developer’s life of priviledge. Here’s the text of my talk:

The World is Full of Real People

You are in a spot of exceptional privilege. You’re well paid to move your fingers around a keyboard. Your greatest danger is probably carpal-tunnel syndrome.

In a time when almost thirty percent of our country is unemployed or underemployed, you make jokes about how annoying recruiters are wanting to offer you job after job. There’s nothing here that’s your fault. You didn’t do anything wrong. This isn’t about blame and I’m not saying you should be ashamed of anything.

But you do need to recognize you lead a life of privilege.

We need to do more.

It is easy to write software for other developers. You understand what it’s like to be a developer, so you know exactly how they think and operate. If you want to make quick money, build tools that make developers lives easier.

We can all then form a big circle and pat each other on the back.

Meanwhile, your new testing framework didn’t make any jobs. It didn’t bring significant joy to anyone’s life. In the big scheme of things, you’ve taken your gifts and used them to pleasure yourself.

Let’s take a step back.

Real people don’t use technology, at least not the technology you build. Unless you work at Facebook, the chance of anyone at this hotel having ever heard of your company, much less your product, is slim. Why is that? Why do we build so many things for ourselves?

Because it’s easy.

Solving real problems is hard. Changing real lives is hard. Making real people happy is hard. When we do write things for the public, we find out that those users are “such idiots” – they can never do things properly. “It’s not worth it!”

You wield the power to make amazing change in the world. You can fix problems with a speed and scale that no other industry can match. Your work, once created, can be replicated at almost zero cost. Your power breaks economics, terrifies governments, and endangers the status quo.

Instead of measuring ourselves by the size of our Series A or our average profit per employee, let’s measure in lives changed.

I want to look back and say “I worked harder than I had to. I gave up time with my kids, with my friends, to do what needed to be done. To give back to the rest of the world, to enable them to live just a little bit happier, a little bit better.”

The problems of our world can’t be fixed with software, that’s naive. But they can be fixed by people, and great software helps people do what needs to be done.

As a developer you can only do so much. You don’t understand all the problems, the nuances, the challenges of the world. That’s ok. The people who do understand those challenges are desperate for your help – they’ll tell you everything you need to know. Just ask.

I’m not saying you need to change a thousand lives. But if you could say that you really changed ten, what would that feel like?

You might not ever have a Wikipedia page, but you’d live on in those ten memories – in the lineage of families they start, the kids that grow up happier because their parent is employed, less stressed, or otherwise improved. When you think about generations upon generations, the compound interest on the investment you make in others pays off in the biggest way.

Your software will be forgotten, but true impact never will.

What’s your mark on the earth? Is it big enough, is it deep enough, is it good enough?

Get to work. Thank you.

Hungry Academy is Open Education

2012-01-05T10:46:17-05:00

The developer shortage is a serious problem. Hungry Academy is training developers for LivingSocial, but we’re doing much more than that.

If you want to learn what we’re learning, do what we’re doing – you’re invited.

We’ve always made our tutorials public under Creative Commons licenses, and Hungry Academy will maintain that trend. We’re publishing:

Our classroom tutorials
Our project assignments
Our model programs
The best of our participant’s projects

Cool? It keeps going. As part of the program, the participants will be creating weekly presentations on small topics, in the style of RailsCasts. Those presentations will be live streamed. The best of them will be posted weekly in video form. They’ll also have dedicated time for contributing to the open source, as is standard in the community.

All those things will be open in whatever form appropriate, up on Github, and we’d love your feedback, corrections, and additions. The only limitation on their use is “please don’t start a technical training company using our stuff” - MIT license for code, a CC-attribution-non-commercial license for text.

We’ll be using Ryan Bigg’s Forem for group discussion of projects and general problems/solutions. Most of that will be public, plus we’ll have a dedicated forum for anyone following along with us. You can support each other, and we’ll do our best to pitch in too.

We’re supporting the local DC community, and will host and teach CodeNow classes to expose high school students to the world of programming.

If you’re already a Ruby/Rails developer, we’d love to have you involved with supporting the public community. We’re coordinating one-on-one mentorships internally, and if there’s interest we could likely use the same tools/techniques to match external mentors and learners.

In the end, this is a social agenda. We want to grow the programming community. Join us. If you want to learn, we will make sure you have no excuse.

Of course, applications are still open for the Hungry Academy program itself. They close Monday, January 9th, so don’t delay.

Understanding Our Culture, Part 1

2011-12-30T19:17:19-05:00

As part of the Hungry Academy planning I’m building several reading lists. The one I’m most excited about I named “Culture & Self for Developers.” The Ruby community is special because of the people and their understanding of the world, these are books that explain that ethos.

I’ve joked during conference talks that I’m better at buying books than reading them – and it’s completely true. First up are the ones I’ve actually read:

The Pragmatic Programmer is so classic. It is essential reading for any developer. This was the first programming-related book that I felt a real “connection” to; it shaped the way I think about the profession. Even though it’s twelve years old, the ideas are still current and important. Concepts so heavily emphasized in the Ruby community, like “Don’t Repeat Yourself” and the “Single Responsibility Principle” come out of this book. It’s a text that I’ve wanted to re-read and I can’t wait to discuss it with the program attendees.

The Passionate Programmer is very much a follow-up to The Pragmatic Programmer. I love how Chad Fowler divides the content into short segments that get right to the point. This is the kind of book that you finish and say “that was interesting…but it all felt like common sense.” The ideas aren’t ones that will blow your mind with their complexity or cleverness, they’re just simple and great. They should just be common, but they’re often overlooked.

One of the most exciting parts of Hungry Academy is that both I and the attendees get to spend many days with Chad, trying to make these concepts a part of our daily practice.

Can nine women, together, create a baby in one month? The absurdity of that question is the core of The Mythical Man Month. In software, bigger is not better and it definitely isn’t faster. This book does an excellent job of explaining why scaling programming labor is so difficult. One of the aspects I’m most nervous about with the Hungry Academy class is how to avoid these issues – how to make our team of twenty-four feel like a team of five, then how to integrate the twenty-four into the big engineering team at LivingSocial.

I was in high school when open source software started becoming mainstream in the developer world. As someone enamored with both coding and economics, I devoured books like The Cathedral and the Bazaar. It does an amazing job of explaining why we should care about open versus closed source. The economic and social arguments in this book are eye-opening for people accustomed to economies based on scarcity. When electronic reproduction eliminates the marginal cost of goods, the standard rules go out the window.

The Thank-You Economy, the second book from Gary Vaynerchuk, has stuck with me. The idea I continue to think about is this: in the olden days there were neighborhood businesses. If you give great service to the neighborhood, you’ll build a great reputation. Give crap service to just a few people and you’re reputation disappears, then you’re out of business.

In the 80s and 90s, mass-marketing replaced “word of mouth.” As people moved to the suburbs they stopped talking. Reputations grew through commercials, not genuine experience. All of a sudden, thanks to the Internet, we’re back to being a small, global neighborhood. If you give great service 99 times and crap service once, bet that one person is going to post a review on Yelp and chase your customers away. Genuine feedback once again rules over marketing.

If you ever get the chance to see Gary speak live, take it. This video from RailsConf is only a mediocre substitute.

Last but not least, Daniel Pink’s Drive is so insightful I can’t do it justice. Through my years as a classroom teacher I have significant hands-on experience trying to figure out motivation. Getting a high school freshman to care about their homework more than phone calls with their friends is a significant challenge. Everything I learned over those years aligned perfectly with Pink’s thoughts and research in this book. I especially love how he works in a thread about open source software and what it means for the future.

That’s it for now! The rest of the list is still in my “To Read” stack, but I plan to have them done before the start of Hungry Academy in March. Expect a follow up post with thoughts and highlights, but you can also see the full list on Amazon.

NOTE: Amazon links in this article contain referral keys. This has no effect on the pricing you see, but Jumpstart Lab will earn a small payment from Amazon if you purchase books using the links above. Thanks for your support!

Hungry Academy: JumpstartLab + LivingSocial

2011-12-24T10:30:47-05:00

A few months ago, my friend Chad Fowler, VP of Engineering at LivingSocial, asked “If you could design a program to turn 24 people into excellent developers, what would you do?”

Then I had a long flight, which consisted of furious notes, numbers, projections, schedules, brainstorms – and that would become Hungry Academy.

Our mission is to create a program that’s “better than college.” With five months, two instructors, and the support of an awesome company, we can do it. We’ll be learning full time in a mix of classroom-style tutorials, team projects, individual research/writing/presentation, and giving back to the community.

You can learn more about it on the Hungry Academy website, but don’t slouch – the applications are due in just three weeks! There are many more pieces to this project which will be revealed over the coming months.

Technical Training Wants to Be Free

2011-12-21T13:15:10-05:00

jQuery Air: First Flight, our introduction to jQuery on CodeSchool is now free! Did you know that our text tutorials have always been free under a Creative Commons license?

Technical training resources naturally have a short lifespan, so it only makes sense for them to eventually enter some form of the public domain. The price paid for any knowledge, whether it’s an online course like this or a traditional book, goes to pay for the time invested in creating it, offset some of the time/cost of the author developing the expertise in the first place, and provide seed capital for further material.

Courses like jQuery Air: First Flight cost tens of thousands of dollars to create. But once that cost is paid then keeping materials behind a pay-wall limits their effect while the content is decaying.

Here at JumpstartLab, we believe in “Learning Out Loud” – we want to promote the spread of these skills, regardless of your ability to pay for our classes. To that end, we publish all our tutorials under Creative Commons licenses, allowing individuals to build their own skills for free.

Over the past years we’ve had the tutorials locked up in our CMS, which didn’t make any sense. Now we’re migrating them to Github, using a specialized version of Octopress, and opening up the source to the public. We hope that this setup will allow the community to pitch in and improve the tutorials.

And with our new program, announced in the coming days, expect to see lots of new content hitting the site in 2012.

Blow Up Your Views

2011-12-20T16:28:21-05:00

Rails views have, more or less, stayed exactly the same since 2005. The only thing we’ve changed is the file extension (formerly .rhtml, now .erb). I believe simplifying and improving the view layer is one of the next areas of emphasis for the community.

This past summer I gave a talk entitled “Blow Up Your Views” at several regional Rails conferences including Madison Ruby, Frozen Rails, and NYC.rb / GoRuCo.

You can check out the latest slides on SpeakerDeck or a video from my GoRuCo session below. A later version of the talk from MadisonRuby should be available soon.

There Are No Tests

2012-09-26T11:21:59-04:00

The Ruby community is obsessed with testing, supposedly. In my experience, about four out of five applications have either zero or completely ineffective test coverage.

Have the courage to change it. Whether your own projects or recovering someone else’s mess, let’s talk strategy:

Starting with metrics
Refactoring for understanding
Comment-driven development
The unit testing foundation
Bug reports are your best integration tests
Focusing on value

Rescue projects are popping up everywhere, and a strategic testing approach can save the day.

The Return of Shoes!

2012-09-25T15:27:55-04:00

If you haven’t heard of Shoes, it’s a GUI toolkit for Ruby. Most of these are simply bindings to toolkits written in other languages, like QT or Tk. Shoes is native to Ruby, so it uses Ruby-only features heavily, such as blocks. Shoes also includes packaging functionality that allows you to distribute your apps on Linux, OSX, and Windows. In this talk, Steve Klabnik covers the basics of building applications with Shoes, the challenges of maintaining a large polyglot project with an absent inventor, and what’s in store for the future of Shoes.

Steve Klabnik presented The Return of Shoes at the 2011 Ruby Conference in New Orleans, LA.