Posted
by
Peter Baumgartner
on
June 12, 2013.
Filed under
trailmapping
Trailmapping.com was a fun experiment with rapid development in Django I released almost 5 years ago now(!). I spoke about it at the first DjangoCon (also my first “real” talk in front of an audience). I didn’t give it much attention after the initial release, however, and the last meaningful commits are almost 4 years old now. Despite the lack of attention, over 2000 trips were posted and nearly 1500 people registered for the site.
Today, there are much better places to post and share GPS data and it’s long past the time to put this project to bed. We’ll be shutting down the server on July 20, 2013 (its 5 year anniversary). If you have any questions feel free to post a comment or chat with us in #lincolnloop on the Freenode IRC network.
Posted
September 18, 2008.
Filed under
django,
presentation,
trailmapping
DjangoCon was an amazing conference all around. I met some great people and learned a lot. I also had the opportunity to get up on stage and present some of the things I’ve been working on here. I was really nervous and after seeing how well prepared the presenters before me were, I had doubts about my plan to go on stage and wing it. I spoke about Trailmapping and Gondola the CMS I’ve been working on.
Afterwards, I was blown away by the number of compliments I received. A few people told me they thought my talk was the best of the bunch which was really encouraging. To everyone that reached out, all I can say is thanks; it meant a lot. I’m inspired to carve out some more time to blog about the things I’m working on, specifically Django admin customization and jQuery.
Well ...
Posted
July 20, 2008.
Filed under
django,
trailmapping
All the recent hub bub about 1 week and 1 day application development, motivated me to see how quickly I could launch a website for myself. I, like many developers, struggle with building and releasing personal sites. Ask a web developer and they’re likely to tell you about a couple of sites they started and never finished. Time is always an issue, but the bigger problems are striving for perfection prior to launch and always holding out for that one “killer” feature. As time goes on, interest in the project wanes until it finally gets shelved.
The Plan
Prior to development, I set a few goals for myself:
- Launching quickly was priority number one. I set a goal of 3 days.
- Use as much existing code as possible. Even if it wasn’t a perfect fit, if it was functional, use it.
- Optimize later.
- Stop scope/feature creep at ...
