Method
expertly executed development.
in the making.
here’s why that matters.
You’ll be pleasantly
surprised.
We’re all “full-stack”
We don’t have frontend or backend devs. We just have programmers, and damn good ones.
We don’t estimate
We’re great at programming, but we’re not great at guessing how long it will take—nobody is. So we don’t.
Our engagements are
time-and-materials
Stacking up features and selling them for a fee doesn’t work. We block out time and give you our absolute best work. Which is all we have to give.
Each of us works on
one project at a time
Context switching kills productivity, so each of our programmers immerses in one project at a time, normally in teams of two.
Fridays are for Twenty Percent Time
We dedicate a day of the week to honing our skills and giving back to our community via open-source and pro-bono projects.
We don’t work overtime
🤷 That’s it.
We’re agile, with a
lowercase “a”
We love the Agile Manifesto, but we don’t always love what Agile has become. We’ll pass on Story Points and Velocity, and stay focused on our work.
We avoid meetings
Meetings are costly, disruptive, tend to beget more meetings, and can often be averted with a thoughtful email or chat message.
We’re remote, but
intentionally synchronous
Our team has been geographically distributed since the beginning, but we show up regularly at the (virtual) office just like an in-person team.
Our contracts are easily breakable
Sometimes a relationship has run its course, so let’s be grownups about it. Our MSA allows for mutual termination, with or without cause.
We love helping onboard
your new hires
Chances are, we won’t be your dev team forever, so right from the start we are thinking about how to transition our work to its next owner.
essential partnership roles.
let’s talk.