360 karma · joined November 4, 2010
[ my public key: https://keybase.io/dennyabraham; my proof: https://keybase.io/dennyabraham/sigs/Nq79RuQ7BQbKX1rQwNFaxool-LEdQ6j-RaAIpSPbwyY ]
email(-at-sign-)dennyabraham.com
I soon discovered that despite being the rails solution that best fit the project, it still lagged far behind wordpress and other similarly battle-hardened software. Most of the other options didn't fare better.
Unless you need interoperability with Ruby libraries, need direct access to ActiveRe* datasources, or you have a well-defined, tightly-limited use case, I'd recommend going with wordpress or something equally mature.
If there are any onerous terms, I'd like to know what they are prior to installation.
google maps's stroke width for roads seems to be based on some measure of traffic or connectedness. from my experience, roads that see fewer cars and fewer intersections tend to show up less prominently. since google has vector data for maps, my guess is they algorithmically weigh and display routes and this leads to dead ends being fainter than other roads
SQL is being replaced in niches that strain its model. elsewhere, it remains steadfast.
1. Write tests around everything you have the time to.
2. Communicate frequently.
3. Try to write things in vertical (shippable) slices.
4. Work in short iterations.
5. Keep what works, drop what doesn't
Ultimately, the most important element to reap the benefits of 'agile' was #5.
tldr; I feel like wikipedia cried wolf this year.