Development's Ability: Ruby


Description

You develop expertise in our server-side stack in the Ruby ecosystem and whatever comes next.

Milestone 1

(adds 1 mile to your journey)

I believe and have seen evidence that [I’ve | <insert person name> has] shown a consistent, comfortable, continuous, and clear positive impact to my team when wielding this ability, and with only a small amount of guidance


  • You understand Ruby syntax
  • You write code according to our Ruby Style Guide.
  • You write basic unit tests with RSpec.
  • You fix isolated bugs by making improvements to our Ruby code.

Milestone 2

(adds 3 miles to your journey)

I believe and have seen evidence that [I’ve | <insert person name> has] shown a consistent, comfortable, continuous, and clear positive impact to my team when wielding this ability, and [is/am] a trusted active or passive mentor to others


  • You make use of and, when called for, creates new abstractions to eliminate inconsistencies and duplication.
  • You assess the correctness and utility of existing code and avoid uncritical copy-pasting.
  • You ask questions to identify (and make explicit) the unspoken requirements of application functionality (such as tracking, logging, and edge cases).
  • You ensure data is kept private and secure when writing code.
  • You create jobs to perform an asynchronous service

Milestone 3

(adds 6 miles to your journey)

I believe and have seen evidence that [I’ve | <insert person name> has] shown a consistent, comfortable, continuous, and clear positive impact to multiple teams when wielding this ability, and [is/am] considered an expert within this discipline


  • You identify needs for new patterns (such as policy objects) and successfully usher their adoption, adding clarity and consistency around common approaches.
  • You act as a caretaker for our Ruby codebase, e.g. by contributing to our linter configuration and Style Guide.
  • You identify and spearhead high-leverage optimizations (such as switching from JSON to Oj for faster JSON serialization)
  • You identify, guide, and help ensure the team is utilizing the most performant Ruby methods.

Milestone 4

(adds 12 miles to your journey)

I believe and have seen evidence that [I’ve | <insert person name> has] shown a consistent, comfortable, continuous, and clear positive impact to all teams when wielding this ability, and [I/they] (help) set the tone for this at the company level


  • You usher the adoption of new technologies that change in fundamental ways how Lessonly works for both users and engineers.
  • You pioneer architectural changes that empower all server-side engineers to be more productive.

Milestone 5

(adds 20 miles to your journey)

I believe and have seen evidence that [I’ve | <insert person name> has] shown a consistent, comfortable, continuous, and clear positive impact to not just internal teams but the community/industry in general when wielding this ability


  • You implement new Ruby techniques and frameworks to meet the needs of the wider community.
  • You define and promote a long-term vision for our server-side architecture and coordinates across the team to ensure projects are in service of it.

Configuration Health

  • ✅ Associated with 11 roles
  • ✅ Has been referenced in 1 piece of public recognition
  • ℹ️ No one has achieved a milestone on this ability
  • ⛔️ Last updated: about 5 years ago
  • ℹ️ Last conversed about: about 6 years ago

Role & Position Requirements

Examples / Observations

  Observation created almost 6 years ago

In last week's Learn Squad weekly huddle, the topic of a bug (dubbed "a hole in the spacetime continuum") came up. This bug came to life as a result of a story I had recently done in the Accessibility epic, but Tom had taken the initiative to fix it shortly after it was noted as an issue in Slack. I greatly appreciated him taking this on, but found myself feeling even more appreciative in Monday's meeting during the conversation around what happened/why the bug occurred. He explained that he guided me down the wrong path when I consulted him on some Ruby syntax while working on the ticket, and explained the fix. Prior to this, I had never seen someone take so much ownership over an issue that occurred from assisting another engineer. In my past work, the responsibility would've fallen all on me, so this experience left me in awe. I am very thankful to work alongside someone like Tom, who a) understands we're all human, and b) takes ownership of his work (whether that's in the codebase, or offering help to others)!

Conversations about Ruby

This section is for Lessonly folks only. Sign your team up to find your Gruuv!

Embed code

<iframe src="http://ourgruuv.com/our/powers/5?embed=true&name=ruby&organization=lessonly"></iframe>