Jim was an amazing guy, and I wish I had spent more time talking with him.<p>There was a time several years ago when the Ruby community was very vibrant and energetic, and in all that energy, just a little hostile to newcomers. There was a lot of hype about the best new testing methods with RSpec and this new thing called Cucumber, 100% paired programming all the time, 100% TDD, and 110% test coverage, fat-model, skinny-controller, decorators and service-based architectures, and on and on. These were all good things on the path to quality software as a community goal, but to a newcomer, it was overwhelming. It was the fanatical attitude and the all-too-common phrase, "you're doing it wrong."<p>I had already been doing Ruby for a couple years when all of this hype came to a peak. I remember pushing back over dinner table discussions with various speakers at conferences that this attitude was hurting the community. It was erecting a barrier to beginners. We were telling people they couldn't just build something that did something. They had to do it this way, using all these tools and methodologies. Unless you know and fully understand the purpose and constraints and context for what someone is building, how can you tell them they're doing it wrong? Where was the support for learning progressively? What happened to the joy of just building something? After all, this is where Ruby, as a language, shines!<p>I bring all this up, because I met Jim at one of the first Ruby conferences I had ever gone to around this time. Though I had been doing Ruby for a couple years, I was relatively new to the conference-going community, and so not part of the "in-crowd". I remember the highlight of that conference for me was talking with Jim.<p>He seemed not to care for the existence of any sort of clique while simultaneously being its unknowing leader. He was very approachable and friendly. But more importantly, he was a great listener and thinker. I remember talking with him about my views on TDD and pair-programming (at the time, the view that "it depends" was controversial), and how the hype was hurting the community. He was one of the few who gave it considerable thought, and after discussing it, even encouraged me to give a talk. As someone new to the conference and public developer community, and outside the speaker in-crowd, this was very encouraging.<p>I had been asking what happened to the joy of just building something in the community at that time, but I can honestly say, Jim never lost it.<p>Jim, you'll be missed.