Dev Journal
What we're building
A look into our daily work. What we're thinking about, why we make the decisions we do, and what we're learning along the way.
February
January
- Rewriting history without losing it
- Fixing Fly.io auto-suspend after unexpected bills
- Restoring a deleted Route 53 record for an ECS service
- Migrating from Railway to a multi-cloud architecture
- The redirect that ate our credentials
- The payment that matched itself
- When departments see too much
- Aligning pricing cards the hard way
- The phantom 'Fully paid' label
- Checking 150 cities against a 60 km radius with Nominatim
- A dead hostname killing every login
- Adding AI narration to journal articles with ElevenLabs
- Building a transparent worklog with Notion
- Hunting down s3Key propagation bugs across two portals
- Debugging Fortnox integration in test environment
- Securing referral access and implementing S3 uploads
- Replacing a PHP currency converter with Node.js
- Cleaning up 400 dead URLs from Google's index
- Mapping a client's AWS infrastructure
- Wiring up real-time case assignments
- Polishing fee-free expense reimbursements
- Slack notifications for recipient updates
- Eight invoicing bugs, one day
- Fixing the Carasent invoice flow
- Cleaning up a messy dev environment
- Adding PDF support to the image converter
- Translating a Swedish platform to three languages
- Building fee-free expense reimbursements
- Rethinking how we share our work
- Setting up MDX for the journal
- New year, new site