๐ง๐ต๐ฒ ๐ฃ๐ฎ๐ฟ๐ฐ๐ฒ๐น ๐ง๐ต๐ฎ๐ ๐ง๐ฎ๐๐ด๐ต๐ ๐ ๐ฒ ๐๐๐ฒ๐ฟ๐๐๐ต๐ถ๐ป๐ด
My manager asked for parcel delivery. I said yes. I did not know where to start. The app already handled food orders. I had to build a new system on the same platform.
Week one was hard. I built the order form. The first version failed. Autocomplete broke. Cost estimates were wrong. I deleted the code. I stopped trying to be perfect. I wrote working code.
Week three was the map. Riders needed to see pickup and drop-off points. I fought with a simple line for three days. I almost gave up. It worked on Sunday at 2 a.m.
Week five was real-time tracking. I solved for slow networks. I solved for GPS loss. I used colors for status:
- Green for delivered
- Red for cancelled
- Blue for in transit
- Orange for pending
I spent two months building:
- 11 pages
- 3 user roles
- 3 API services
- An interactive map
A real user finally used the app. The tracking worked from start to finish.
The lesson is simple. You do not need to know how to build it before you start. Write bad code first. Learn from it. Rewrite it better. Persistence is the secret.
Source: https://dev.to/ogeobubu/the-parcel-that-taught-me-everything-4kgf