I have been working on this Google Maps Radar project for more than two years.
I consider I have finished it only tonight… If you take a look at it, it doesn’t seem very complicated. It’s not. But why did it take more than two years?
Lessons learned:
- Do not start a stupid project like this for fun if you don’t intend to finish it in the week.
- Don’t lose your original plan while moving. Scan the paper, host the picture somewhere on the web. Or use softwares. (But I prefer paper ^^)
- Stick to your naming conventions. Lazyness + lack of rigor in writing (+ influence of multiple teams conventions on other projects?) -> bad code -> awful to read + stupid bugs -> don’t want to finish.
- Thinking about sharing is motivating. Thanks GitHub!
- Javascript using prototyping classes is awesome. Frameworks such as jQuery are nice but sometimes coming back to the roots can be also instructive and fun.
Voila, see you for the next project in less than two years!
Solutions Architect at Fearless Dinosaur
Solutions Architect, I build great workflows for the news, media and broadcast industries. I play with data too.
Latest posts by Fab (see all)
- La Commune : review - 30 March 2024
- Fearless Dinosaur - 12 March 2024
- Au Printemps des Monstres : review - 25 November 2023