3 min read
Aaron ReismanAaron Reisman

Starting Seriously Serious LLC

I started a small software and games company. It makes its own products, and it takes on client work: from a first prototype to a product in production. Here is what it does and how to work with me.

Last updated

I started a company. It’s called Seriously Serious LLC, and it’s a small software and games company. The name is a joke. The work isn’t.

It does two things. It makes its own products, and it builds software for other teams. This post is about both, but mostly about the second one, because that’s the part where I might be able to help you.

What it makes

Three products so far:

  • Infinite Threads is live. Describe a graphic, pick your favorite of up to four designs, and wear it on a T-shirt, hooded sweatshirt or tank top. Shirts start at $24.99.
  • Deep Line is a 1-bit fishing game for Playdate. You turn the crank to reel in nine species from 375 meters down. It’s free.
  • Void Runners is a co-op twin-stick roguelike for one to four pilots, announced on Steam. Beams link your ships and cut through everything between you.

Building your own products keeps you honest. Infinite Threads covers the whole path a real business needs: generate a design, place it on a garment, take payment, and hand the order to a print partner who makes and ships it. Nobody else picks up the pieces when something breaks. That’s the same job I do for clients, just with my own name on the invoice.

What I do for clients

I’ve been shipping software since 2007, mostly with React, TypeScript, Phoenix and Elixir. Along the way I’ve shipped with teams at Amgen, Genentech, Johnson & Johnson, McCormick, Nike and Novartis, and with growth-stage startups. The work is mostly the same problem at different scales.

Through Seriously Serious, I take on work for teams of any size, from the first prototype to a product in production. The kind of work I’m good at:

  • Product engineering. Taking a feature from an idea to something real users rely on, including the boring parts: error states, empty states, loading, and the words on the screen.
  • Component systems. Building UI components that a team can actually reuse, and that don’t fall apart the second time someone needs a variant. I wrote down how I think about this in the component manifesto and how MasonryKit is built.
  • Refactors and the hard parts of an existing codebase. The code everyone is scared to touch, the flow that breaks in production, the migration that keeps getting pushed to next quarter.
  • The parts users only notice when they go wrong. Sign-in and account recovery (auth that doesn’t trap your users) and error handling (in Phoenix LiveView with Ash).

If you read one of those posts and thought “we have that problem,” that’s the best kind of starting point.

How to work with me

Send a note to [email protected]. You don’t need a spec. A few sentences are enough:

  1. What you’re building, and who uses it.
  2. Where it hurts right now: what’s slow, broken, or stuck.
  3. When you need it to be better.

I’ll write back, and if it looks like a fit, we’ll set up a call and figure out the smallest piece of work that proves it. If it’s not a fit, I’ll tell you that too, and point you somewhere better if I can.

About the author

Aaron Reisman

Aaron Reisman

Aaron Reisman is a software engineer who writes about React, Elixir, and the parts of products that decide how they actually feel.