building a fish farm management platform for commercial operations
ui's done. architecture's done.
now the real work wiring it up to fastapi
sharing the wins and the "why is this breaking" moments as they happen
Spent time modeling a restaurant operations system before writing code.
The tricky parts weren’t the tables themselves. They were the rules: when stock should change, how to handle partial deliveries, what happens when a ticket is voided, and how to preserve order history after menu prices or recipes change.
Getting the model right first should make the build a lot less messy.
A message queue doesn’t guarantee that your business operation executes exactly once.
A consumer can commit a database transaction and crash before acknowledging the message.
The broker redelivers it.
Your handler must recognize that the business operation already happened
A restaurant system is more than CRUD operations
It’s a combination of access control, state transitions, data consistency, tenant isolation, and interconnected business workflows
I wrote about the architecture and engineering decisions behind the multi-role system I’ve been building
👇
https://t.co/pLSLKBeaLJ
A successful HTTP response isn’t proof that money moved correctly.
A robust financial system needs transaction state tracking, unique references, idempotency, reconciliation, and a clear distinction between initiated, pending, successful, and failed operations.
Money movement requires stronger guarantees than a 200 OK
Application-level validation is useful.
Database constraints are essential.
If two services write to the same database, relying entirely on one service’s validation logic creates inconsistent guarantees.
Use constraints to enforce invariants that must remain true regardless of the caller
Increasing your database connection pool doesn't automatically increase throughput.
At some point, additional connections introduce contention, memory pressure, and context-switching overhead.
A saturated database with 500 connections isn't necessarily faster than one with 50.
Measure before increasing limits.
Introducing Claude Meetings: add Claude to your team’s video call and it builds docs, whiteboards, and other artifacts with you while you’re still talking.
Starting to roll out in beta on Team and Enterprise plans.
Frontend developers: The button isn’t working.
Backend developers: The API is returning 200.
DevOps: Everything is green.
Users: We can’t log in.
Beautiful industry.
One thing I’m learning about application security:
security headers are useful, but they’re not a substitute for secure application logic.
CSP can reduce the impact of certain injection attacks.
CORS controls which browser origins can read cross-origin responses.
Neither fixes broken authorization or insecure business logic
I’ve started enjoying technical documentation more than tutorials.
Tutorials teach you a path.
Documentation helps you understand the boundaries of the tool itself