DZone
Agile Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Agile Zone > The Four Year Typo

The Four Year Typo

Read one programmer's perspective on how a fresh pair of eyes can make all the difference, and even beginners can have something to teach experts.

Richard Schneeman user avatar by
Richard Schneeman
·
Apr. 20, 17 · Agile Zone · Opinion
Like (5)
Save
Tweet
4.38K Views

Join the DZone community and get the full member experience.

Join For Free

I’m a horrible speller. I often joke that I got into programming because it doesn’t matter how you spell your variables, as long as you spell them consistently. Even so, I spend a good portion of my days writing: writing docs, writing emails, writing commit messages, writing issue comments, and, of course, writing blogs. Before I publish an article, I run my work by an editor, which makes this typo even more exceptional.

I got a note about a typo on a Devcenter article on Rails 5.x that I maintain. This article published over a year ago has had 4 different editors/contributors and 19 revisions. I can’t give out numbers but this article has had A LOT of page views. It is the number one article I maintain by a huge margin, it was pretty surprising when I opened this note and it mentioned I had a typo.

and if you app depends on a gem from one of these groups to run, you should move it out of the group

Did you catch it? I didn’t. Here it is spelled out:

and if you[r] app depends on a gem from one of these groups to run, you should move it out of the group

I checked and sure enough, that typo has been there from the original version of the doc. You might ask, “but Rails 5 has only been out for a year, how was this typo alive for 4?” I copied the 5.x guide from the 4.x guide and sure enough, the typo in the Rails 4.x guide has the typo going back for 4 years. The 4.x document had an additional 7 contributors who didn’t notice.

I messaged the reporter to thank them for the find and explained how the typo had gone unnoticed for so long, and this was their response:

You’re welcome! I’m learning to create a rails server so I had to be extra thorough 

Epic. I love this. I’ve read through these docs probably hundreds of times. I wrote an automated build system to compile and test these docs. I’ve spent a good chunk of time refining and tweaking these articles. But I didn’t stop and look close enough for FOUR FREAKING YEARS to see what was right in front of me. There is always value in a fresh perspective. There is value in every contributor regardless of skill level. I’ve been at this Ruby programming thing for 10+ years, and someone just beginning Rails development can still reach out and help. You can make an impact on whatever you like, just get involved.

I aspire to live each day through the eyes of a beginner, to catch the moment that might otherwise go unnoticed. I want to challenge myself not just to get to the destinations, but to appreciate the journeys along the way. I think we all need a fresh perspective, I’m just hoping my next one won’t take 4 more years.

Doc (computing) app code style GEM (desktop environment) Fresh (IDE) Moment Testing

Published at DZone with permission of Richard Schneeman, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • How To Evaluate Software Quality Assurance Success: KPIs, SLAs, Release Cycles, and Costs
  • SQL GROUP BY and Functional Dependencies: a Very Useful Feature
  • Major PostgreSQL Features You Should Know About
  • Java’s Encapsulation - When the Getter and Setter Became Your Enemy

Comments

Agile Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo