drogus's apache-upload-progress-module at master - GitHub
Filed under //
development
"...elephantine adventures in pursuit of the obvious."
I'm Eric Farkas, currently a mechanical draftsman, as well as a web developer, doing mainly Ruby on Rails. I am also the CTO of TalentSoup, as well as one of the founding members of Sensus Divinitatis Publishing. I have a number of side projects, including SD News, Perplexed Labs, Inc. and GenXCommune. In a past life I was a founding member of HoverSpot.
I worship at the OPC of Franklin Square with my family, where I serve as a deacon.
You can check me out on various social sites:
del.icio.us
Facebook
Flickr
Goodreads
last.fm
LinkedIn
Twitter
I like to read books. I keep an Amazon Wishlist and a Reading List.
I also keep a Training Log of workouts.
This blog is my attempt to catalog what I read and see, as well as offer my thoughts on theology, philosophy, technology, and culture.
I hate coffee.
Email me: speric at gmail dot com
Filed under
development
The best bug tracking system. Don’t raise bugs, write an automated test!
When anyone finds a bug, he/she immediately writes an automated test that fails based on the bug just discovered. This mechanism have the following advantages.
- Gets rid of versioning problems, everyone works on the head.
- Guarantees that the bug is never gonna reappear undetected.
- Eliminates uncertainty on what the bug exactly is.
- Eliminates bureaucracy
- Consolidates the development activities in one place, the code.
Interesting approach.
Filed under //
development
Comments [0]
Google Geo Developers Blog: Introducing the new Google Geocoding Web Service
Geocoding - finding the geographical location of a given address - is one of the most popular features of the Google Maps API. Both the JavaScript Maps APIs and the Maps API for Flash include classes that enable applications to perform geocoding, and there is also a RESTful web service that offers the option of making geocoding requests from server side applications with output in both XML and JSON.
Filed under //
development
Comments [0]
19 Rails Tricks Most Rails Coders Don’t Know
Sick of writing things like post.collect { |p| p.title } or post.select { |p| p.activated? }.collect{ |p| p.title} ? A little Ruby hackery that allows you to convert symbols into proc references makes it easy. You can write post.collect(&:title) or post.select(&:activated?).collect(&:title) instead!
via rubyinside.com
Some good ones here.
Filed under //
development
Ruby on Rails
Comments [0]
A New Way of Working: A Two-Month Recap - (37signals)
For two week iterations, true scope should be nailed down no later than half-way through. We found ourselves up against the wall a few times because we didn’t cut scope early enough. So we decided that on Monday of the second week we’ll review the work done during the previous week and the work remaining to complete the iteration. Since humans are notoriously bad estimators, we’ll be extra conservative with scope. We’ll bring out the hammer and beat down the scope. And then we’ll do it again on Wednesday, two days before the end of the iteration. We want to throw work overboard, not our sanity or our sleep. Late nights are a sign of scope failure. Hero mode is a sign of scope failure. You can’t compartmentalize burnout. Yes, we start new iterations every two weeks, but burnout carries over. The scope hammer helps eliminate burnout.
via 37signals.com
I love the Scope Hammer.
Filed under //
development
Comments [0]
ReinH — A Git Workflow for Agile Teams
Wherein our hero describes a workflow for using git productively and painlessly in an Agile environment.
via reinh.com
Filed under //
development
git
Comments [0]
Comments [0]