🆙
Lightward
  • 👉Start here
  • Context
  • Priorities: Recursive health
  • Product: Playing the game
    • 1. Load the game
    • 2. Play the game
      • How to play
      • When to stop
      • The customer's health is not your job
      • Don't sign up for custom work
    • 3. Save your game
      • 3a. Record what's new
      • 3b. Push the update
      • 3c. Prepare for next time
  • Publishing: Erring public
  • Glossary
    • Concepts
    • Applications
  • Technical
    • README
    • Screenshots
    • Cronitor
      • SSL certificate expiration warnings
    • Fly
      • Overview
      • Restarting apps
      • Fly ATC
      • Counting all org machines
      • Autoscaling
      • Environment variables
      • Deploys
        • Recovering from deploy failures
      • Rough edges
      • SSH
      • Unusual consoles
    • GitHub
      • Dependabot
    • Migrations
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. Product: Playing the game
  2. 2. Play the game

Don't sign up for custom work

Seriously, don't do it!

PreviousThe customer's health is not your jobNext3. Save your game

Last updated 2 months ago

Was this helpful?

If you discover that something is doable, but only by building something not already on our List Of Well-Formed Things We Own And Operate As A Natural Part Of Maintaining Our (tm), you've found CUSTOM WORK.

Simpler definition: if you discover something that is doable by building a new product, instead of by , you've found custom work.

We don't do custom work here! You can do custom work independently if you want (seriously, go for it!), but we only work on products that are our own. That's how we help the world: by working on the products and relationships we can hold.

The only thing we make for customers (whether at their behest or in the course of supporting them) is improvement to our own products. Documentation is a product too, and may well be updated more often than the products themselves. Strictly speaking, maybe our relationship with the customer is a product as well? Maybe?

Redirect the energy

If you've discovered a thing that feels like it wants to be done but isn't in scope for us, there are two ways this can go:

  1. We add to our product list, and commit to its ongoing health.

    • Possible, but rare.

    • Examples of this happening: Mechanic, Lightward AI, Guncle Abe

  2. We write a quick sketch of the potential thing to be done, save it in the docs (so that this never has to be written again), and send doc link to the customer.

    • This may happen often. That's okay.

    • Remember: .

    • Since we're not the ones who are gonna build this, point the customer toward a path that may be helpful to them for that journey.

      • Mechanic:

      • Locksmith: todo

Health
evolving our existing products
documentation-free email
https://learn.mechanic.dev/custom