Verified Ruby-Doc.org author
Ruby developer, writer, and creator of Ruby-Doc.org
James Britt created Ruby-Doc.org in 2002 as a central home for Ruby documentation and learning resources. After serving as its long-term maintainer, he now writes practical Ruby tutorials and code examples for Ruby-Doc Learn.
About James Britt
James is an artist, writer, musician, technologist and Ruby developer based in Scottsdale, Arizona. He operates Neurogami, which he founded in 2001 for software, art and interactive technology projects.
His Ruby work spans documentation, teaching, JRuby desktop development and open-source projects. For Ruby-Doc Learn, his focus is useful, runnable examples that explain not only what a piece of Ruby does, but when a developer would use it.
- Ruby programming
- Ruby documentation
- JRuby development
- Developer education
Ruby community work
James's public Ruby record extends beyond maintaining Ruby-Doc.org. Independent sources document his technical writing, conference talks, JRuby open-source work and published Ruby packages.
Technical writing
Ruby-lang.org highlighted his 2004 Linux Journal article on manipulating OpenOffice.org documents with Ruby.
Conference speaking
RubyEvents records his MountainWest RubyConf talks “Black-boxing with Ruby” (2007) and “Hubris: The Ruby/Haskell Bridge” (2010).
JRuby and open source
InfoQ interviewed James about Monkeybars, a JRuby MVC framework, and the Rawr packaging tool.
Published Ruby packages
RubyGems lists James as an author of qft and Neurogami-wiiremotejruby.
These sources support James's documented work in Ruby publishing, conference speaking and open-source development. They do not identify him as a Ruby core committer.
Why this profile is verified
Ruby-Doc.org has verified James's identity and current author role. The site's history and his professional background are independently supported by:
- James Britt's original Ruby-Talk announcement of Ruby-Doc.org on 10 November 2002.
- O'Reilly's James Britt author biography, which records his Ruby community, writing and Ruby-Doc.org work.
- James Britt's official personal profile and Neurogami profile.
Identity and role verified by Ruby-Doc.org. Last verified 2 September 2026.
Articles by James Britt
UI Design Agencies for Modernizing Legacy Ruby on Rails Apps
Eight UI design agencies to consider for an established Ruby on Rails application, with practical questions about Ruby experience, workflow preservation, testing, and implementation.
Using Rust with Ruby: Integration Options and How to Choose a Development Partner
A Ruby application can work well for years before one job starts taking too long. A nightly import may spend hours parsing files. A calculation may hold up requests even though the rest of the Rails application has little to do. That is a useful point to investigate Rust. Ruby can handle application behaviour, database […]
Download Instagram Highlights: A Sixteen-Year Changelog for Ruby Developers
A Ruby developer’s guide to Instagram Highlights: the history of old gems, current API limits, manual download options and authorised Story archiving.
Building a Reliable Ruby Development Environment
A Rails test works for your colleague but fails on your laptop. Before changing the application, check Ruby versions, installed gems and database configurations. A difference in the setup can send you looking for a bug that has little to do with the code you were editing. A useful Ruby development environment makes it easy […]
Build a Digital Wardrobe in Ruby
A wardrobe tracker makes a useful Ruby project because its rules are easy to inspect. An item belongs to someone, has a category and may be available to wear. An outfit combines several items. A wear log records what actually happened. The interesting work starts when those records disagree. A saved outfit contains shoes that […]
Ruby on Rails Cloud Migration in 2026: What CIOs Should Check Before Moving
The Rails application boots on its new cloud host. The home page loads, staff can sign in, and the migration looks finished. Then someone downloads an old attachment and gets an error. A scheduled export runs twice. The database reaches its connection limit while the web servers still have spare capacity. Those are useful problems […]