Notes
Notes on work we actually do, written for the people who buy it. Each one covers a decision or a fault we meet often enough to have a settled answer, and says what we would do about it.
There are few of them on purpose. A note goes up when it would save a client a conversation, not to fill a page.

Articles
The notes so far
Running what you have
- Upgrading Laravel one major version at a timeWhy skipping releases makes the jump harder, and the order we follow
- Five ways a payments product loses money without crashingFaults that pass every demo, and the design that prevents each one
Before you build
- Store app or responsive web app: how to decideThe questions that settle it, and the order that keeps both options open
- Why app stores reject apps, and the checks that avoid itThe usual reasons, and the checklist we run before the first submission
Pages that read like notes
How we work
- Custom softwareDiscovery first, working software every two weeks
- Hire a developerA named person by the month, rates on request
Question
Something you want us to write about?
Ask it here. If the answer is useful to others, it becomes the next note. We reply within one business day.
