The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
FastAPI booking backend: correct failures and repeatable tests
Independent portfolio demo built with Python, FastAPI, and SQLite. The API exposes six documented routes and tests booking, cancellation, invalid inputs, missing records, and conflicting reservations. A conditional SQL update prevents claiming an already-booked slot; cancellation is idempotent. Source-derived OpenAPI documentation and an isolated test database make the project easy to inspect and run. The supplied validation record contains 26 passing tests. This is an offline demo using synthetic references, not a deployed clinic system.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
THREADLINE ATELIER
A premium booking experience for a custom fashion studio in Lagos.
I wanted to solve a simple problem: when someone asks, “Can I book with you?”, the designer shouldn't have to spend the next hour going back and forth about availability, measurements, event dates, and scheduling.
Threadline Atelier turns that into one smooth flow:
Inquiry → Design Brief → Availability → Booking → Deposit → Confirmation
Customers can choose what they're making, share their occasion and event date, upload inspiration, select a real available consultation time, pay the consultation deposit, and get booked.
For the designer, it reduces manual coordination, follow-ups, and scheduling headaches.
Visually, I wanted it to feel like a luxury fashion house with a digital experience editorial typography, contemporary African fashion, cinematic motion, and subtle thread-inspired interactions.
The signature moment:
“YOU'RE BOOKED.”
This is a well structured website but the booking experience is what I looks good.
I built Aurora, a booking experience for Studio Aurora Beauty, a fictional solo beauty studio in Belo Horizonte, Brazil.
The problem was simple: the owner was spending too much time answering availability questions, confirming appointments, sending reminders and handling rescheduling through WhatsApp and Instagram.
Aurora turns that manual back-and-forth into a seamless booking flow.
Customers can choose a service, check real-time availability, book an appointment, receive instant confirmation, and reschedule or cancel without contacting the owner.
On the business side, the owner gets a dashboard with upcoming appointments, booking statuses, pending confirmations and automated reminders.
The goal was not to build another calendar. It was to reduce the manual work around booking.
From “Can I book with you?” to “You’re booked.”
Another late night. Building a quant trading system an agentic model where different AI agents handle research, testing and risk, and none of them is allowed to place a trade on its own.
The hardest part so far? Being honest when the results say "not yet." Most strategies I've tested failed once real costs were included. That's exactly what testing is for.
Keeping The Psychology of Money and The Diary of a CEO close while I figure it out. What are you reading these days?
Curious how you’ve separated the agents from execution. When you say none can place a trade on its own, is that enforced through a separate execution service with fixed risk checks, human approval or both? I’d love to understand where the agent's decision-making ends and the hard rules take over.