A small bug with big impact. On a UK-based platform, workers were submitting timesheets before th...A small bug with big impact. On a UK-based platform, workers were submitting timesheets before th...
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
Muhammad's avatar
Muhammad Asad
pro
• Sep 23
A small bug with big impact.
On a UK-based platform, workers were submitting timesheets before their shift even started. It looked like a system issue, but the root cause was timezone mismatch, the system was using local time instead of UK time.
Since development/testing was happening from Pakistan, the system incorrectly allowed submissions early.
Fix: Instead of changing stored data, I introduced timezone-aware validation. The system now converts current time into UK timezone and validates shift start conditions against that.
Key decision: Keep stored timestamps untouched. Only use timezone conversion for validation logic.
Why it matters: This avoids data corruption and ensures reporting consistency while still enforcing correct business rules globally.
Now the system correctly follows UK shift timing regardless of where the request comes from.
If you’re building or scaling a SaaS/product that deals with multi-region users or complex business logic like this, I help solve backend problems like this in production systems.
Let’s connect: asadraza.digital
Backend DevelopmentNode.jsproblemsolving
Back to feed
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