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
HaulLog — Django 5.2 backend for an ELD Trip Planner, powering a React frontend. It securely proxies the TomTom API for geocoding and truck routing, keeping the API key server-side, and runs a stateless, pure-Python FMCSA Hours of Service (HOS) simulation engine that generates a full day-by-day driving/rest/fuel timeline. No database is used — everything is computed per-request. Deployed on Render via Gunicorn, with four core endpoints handling key delivery, geocoding, routing, and trip calculation.
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
Small preview of my free Framer template for weddings 💒👰🏽♀️
Remix for free (and use as you wish!): https://framer.link/OVLj7Ay
That deep wine band framing the hillside shot gives it such an invitation-card feel. Giving this away for free is really kind. Have you seen what people end up doing with it once they remix, or does it mostly disappear into the wild?
Building a 4-role real-time SaaS taught me one uncomfortable lesson: the hard part was never the code.
I've been building RestaurantOS — one platform connecting Owner, Kitchen, Waiter, and Cashier in a single live workflow (Table → Order → Kitchen → Serve → Billing → Reports).
The tech stack was the easy part. The real challenge: keeping 4 different roles in sync in real time without any of them stepping on each other's data — a waiter updating a table while the kitchen marks an item ready while the cashier is mid-billing.
That forced decisions most tutorials never cover:
⚡ How much state should live client-side vs. source-of-truth server-side
⚡ What "real-time" actually needs to mean per role (a kitchen screen needs sub-second updates, a report dashboard doesn't)
⚡ Designing failure states — what happens when the waiter's app loses connection mid-order
Currently redesigning the UI/UX layer too (motion, better visual hierarchy) while keeping this real-time core intact.
If you've built multi-role or real-time systems — curious what broke first for you. And if you're a founder who needs something like this built, my DMs are open.
the role based flow is easy to follow. what part was hardest to keep real time?
Developed a professional corporate website for NGS International, a security infrastructure company providing solutions including CCTV surveillance, access control, fire safety, maritime security, and other integrated security systems for businesses and organisations.
