work.html

---
title: Ryan Bigg is not currently looking for work
layout: default
---

<article>
  {% include work/not_looking_for_work.html %}

  <div class="history">
    <h1 class="text-center my-8">Work History</h1>

    <section class="my-12">
      <h3 class="text-center border-b-4 border-green-300 pb-2">Aug '21 -> Ongoing &mdash; Fat Zebra - Lead Front-End Developer for the Platform Team (Full-time)</h3>

      <p class="text-xl">
        Providing an expert eye across Fat Zebra's payment tech stack.
      </p>

      <strong>Team & Culture</strong>

      <ul>
        <li>
          ✅ Led interview and hiring process for new developers.
        </li>
        <li>
          ✅ Providing support to other developers through pair programming and code review, focussing on their career progression by providing dedicated 1-on-1 slots and general advice.
        </li>
        <li>
          ✅ Focussed on blameless post-mortem retros when things did go wrong and helped everyone learn and grow from their mistakes.
        </li>
        <li>
          ✅ Discussed and developed a series of logging, metrics, alerting and dashboards to improve oversight into our applications.
        </li>
        <li>
          ✅ Assisted in the development of an on call rostering system with generous time-off-in-lieu policy, and ensured developers were supported adequately while on call. And ensured they took their time off in lieu!
        </li>
      </ul>

      <strong>Zeal Design System</strong>

      <ul>
        <li>
          ✅ Led the design and implementation of the Zeal Design System, a React-based design system that is used across five distinct applications.
        </li>
        <li>
          ✅ Planned and delivered documentation for the design system in collaboration with the wider team.
        </li>
        <li>
          ✅ Provided cross-team advice on how other developers could use this system by working with developers and managers on those teams.
        </li>
        <li>
          ✅ Revamped JavaScript build pipelines on all frontend projects to use ESBuild, SCSS and Tailwind.
        </li>
      </ul>

      <strong>Merchant Dashboard</strong>

      <ul>
        <li>
          ✅ Led the redesign of the Merchant Dashboard to use the Zeal Design System to prove out that project.
        </li>
        <li>
          ✅ Introduced bug triaging processes into the team to ensure that the right bugs were being fixed.
        </li>
        <li>
          ✅ Introduced cooldown sprints into the team to ensure that the team had time to work on technical debt and other improvements.
        </li>
        <li>
          ✅ Worked with the project manager and lead designer to prioritise the backlog and new feature introductions within the team.
        </li>
      </ul>

      <strong>PayNow</strong>

      <ul>
        <li>
          ✅ Took ownership over our payment processing application, PayNow, which processes millions of payments a month.
        </li>
        <li>
          ✅ Led the redesign of the PayNow application to use the Zeal Design System.
        </li>
        <li>
          ✅ Delivered the MasterCard Click to Pay project in collaboration with MasterCard developer support.
        </li>
      </ul>

      <strong>JS SDK</strong>

      <ul>
        <li>
          ✅ Took ownership of the JavaScript SDK, which allows merchants to embed PayNow into their websites.
        </li>
        <li>
          ✅ Made improvements to the SDK to make it more reliable when integrating with the 3rd party 3DS2 Cardinal Commerce integration.
        </li>
        <li>
          ✅ Collected requirements with the PM and merchants for a React version of the SDK and the team delivered the project on time.
        </li>
      </ul>
    </section>

    <section class="my-12">
      <h3 class="text-center border-b-4 border-green-300 pb-2">Feb '21 -> Aug '21 &mdash; Freelance contractor</h3>

      <p class="text-xl">
        Working as a part-time "mercenary for hire" across a variety of tech stacks, but primarily focussing on
        Typescript-based React with Ruby on Rails backends.
      </p>

      <ul>
        <li>✅ 4-days-a-week as a TypeScript / React / Ruby developer, working in a team of around 4 people. </li>
        <li>✅ 3-days-a-week as a TypeScript / React / Ruby developer at a small company, primarily focussed on improving
          their frontend code, upgrading jQuery componentry to TypeScript-powered React.
          <ul>
            <li>In addition to that: I research and implemented platform stability measures by working with other
              developers to add additional Ruby tests, a CI system, and monitoring through logging and AppSignal.</li>
          </ul>
        </li>
        <li> ✅ 2-days-a-week upgrading a Ruby on Rails application from Rails 5.0 to 6.1, and tidying up other deprecation
          messages / warnings in the build logs. </li>
      </ul>
    </section>

    <section class="my-12">
      <h3 class="text-center border-b-4 border-green-300 pb-2">December '08 &rarr; Current &mdash; Tech Book Author</h3>

      <p class="text-xl">
        I have contributed extensively to documentation for Ruby and Rails. I started
        writing documentation for Rails in December 2008. The two guides I am best
        known for are the
        <a href="http://guides.rubyonrails.org/getting_started.html">Getting Started guide</a>
        and
        <a href="http://guides.rubyonrails.org/active_record_querying.html">Active Record Querying guide</a>. I also wrote
        the
        <a href="http://guides.rubyonrails.org/engines.html">Engines guide</a> and the
        <a href="http://guides.rubyonrails.org/asset_pipeline.html">Asset Pipeline guide</a>.
      </p>

      <p class="text-xl">
        During 2010, I was contacted by <a href="https://manning.com">Manning</a> to
        write a book for them called
        <a href="manning.com/books/rails-3-in-action">Rails 3 in Action</a>. This
        subsequently went on to produce a second edition, called
        <a href="https://manning.com/books/rails-4-in-action">Rails 4 in Action</a>.
      </p>

      <p class="text-xl">
        After the success of
        <a href="http://manning.com/books/rails-4-in-action">Rails 3 and Rails 4 in Action</a>
        I decided to strike out on my own and become a self-published author. I do
        this through <a href="https://leanpub.com">Leanpub</a> and have published <strong>seven</strong>
        books:

      <ul>
        <li><a href='https://leanpub.com/rails'>Active Rails</a></li>
        <li><a href="https://leanpub.com/multi-tenancy-rails-2">Multitenancy with Rails</a></li>
        <li><a href="https://leanpub.com/toyrobot">Toy Robot walkthrough, in Ruby</a> and another one in <a
            href="https://leanpub.com/elixir-toyrobot">Elixir</a></li>
        <li><a href='https://leanpub.com/maintain-rails'>Maintainable Rails</a></li>
        <li><a href='https://joyofelixir.com'>Joy of Elixir</a></li>
        <li><a href='https://leanpub.com/apollo-handbook'>The Apollo Handbook</a></li>
      </ul>
      </p>

      <p>
        You can read more about these books over on
        <a href="/books">my books page</a>.
      </p>

      <p>
        To support writing these books, I wrote my own book review tool, called <a
          href='https://github.com/radar/twist-v2'>Twist</a>.
      </p>
    </section>

    <section class="my-12">
      <h3 class="text-center border-b-4 border-green-300 pb-2">December '20 -> Feb '21 &mdash; Seachange + beach holiday</h3>

      <p class="text-xl">Largely an operational role: moving an entire household from Melbourne to Warrnambool. Spent a lot
        of time on the beach. It was good.</p>
    </section>

    <section class="my-12">
      <h3 class="text-center border-b-4 border-green-300 pb-2">
        May '20 &rarr; December '20 &mdash;
        <a href="https://covidence.org">Covidence</a> - Lead Developer
      </h3>

      <p class="text-xl">Covidence provides workflow tooling that assists researchers with their systematic reviews.</p>

      <p class="text-xl">
        My role at Covidence was as a senior full-stack developer, leading efforts across the codebase ranging from
        compiling
        a design system in React, CSS & TypeScript to standardise the different components across our application.
      </p>

      <p>
        I worked on a re-work of one of Covidence's major features called "Extraction", and was part of the team that
        launched (and maintained) Extraction 2.0.
      </p>
    </section>

    <section class="my-12">
      <h3 class="text-center border-b-4 border-green-300 pb-2">
        December '19 &rarr; April '20 &mdash;
        <a href="http://coderacademy.edu.au">Coder Academy</a> - Lead Educator
      </h3>

      <p class="text-xl">
        <a href="http://coderacademy.edu.au">Coder Academy</a> runs bootcamps for first-time developers, with the aim of
        getting them into their first ever developer job.
      </p>

      <p class="text-xl">
        At Coder Academy I was the Lead Educator for the Code Like a Girl cohort. I was training a group of 14
        junior-junior
        developers in Ruby on Rails. I was then made redundant in this role due to the impact of COVID.
      </p>

      <p>
        Alongside this work, I was also working in a small team to improve the curriculum for Coder Academy across all of
        their campuses and bootcamps, focussing primarily on Computer Science Fundamentals, Ruby on Rails and JavaScript
        curriculum.
      </p>
    </section>

    <section class="my-12">
      <h3 class="text-center border-b-4 border-green-300 pb-2">
        August '16 &rarr; November '19 &mdash;
        <a href="http://cultureamp.com">Culture Amp</a> - Junior Engineering Program Lead
      </h3>

      <p class="text-xl">
        <a href="http://cultureamp.com">Culture Amp</a> aims to improve the culture of
        companies around the world.
      </p>

      <p class="text-xl">
        From August 2017 until November 2019, I was the Junior Engineering Program Lead at Culture Amp.
        This job involved recruiting and mentoring junior engineers in Ruby and
        JavaScript (and lots more!) with the goal of training them up to be the next
        great engineers at Culture Amp and in the wider developer community.
      </p>

      <p class="text-xl">
        My work at Culture Amp prior to being the JEP Lead, involved working as a
        Senior Developer with a small (~5-8 people) team of developers to maintain our
        large Rails monolith and to write event-sourced microservices in Elixir, along
        with frontends in React, and associated tech.
      </p>

      <p>
        The role of Junior Engineering Program lead was made redundant at the end of 2019 and I chose to take a redundancy
        payout rather than continue in a different role.
      </p>

      <p>
        I loved working at Culture Amp because I got to do what I love: mentor and grow
        junior developers. I also get lots of opportunities to help out other
        developers by working with them on difficult issues.
      </p>
    </section>

    <section class="my-12">
      <h3 class="text-center border-b-4 border-green-300 pb-2">2005 &rarr; 2016 &mdash; Various</h3>

      <p class="text-xl">
        My formative years. Spent this time working for various companies and
        freelancing, doing whatever PHP or Ruby on Rails work came my way.
      </p>
    </section>
  </div>
</article>