I assume you're being facetious (because of the smiley) but:

1. With the current code sitting on your laptop you'll only ever have one developer (this is the same as Nokia doing lots of stuff internally and throwing it over the wall when "finished". Other developers could follow your commits and learn, or provide useful comment if development was done in the open).
2. "This is the fastest and most flexible way to do development" until you're hit by a bus. And then Mauku dies too.
3. "This is the fastest and most flexible way to do development" until you accidentally rm -rf the wrong folder.
4. "This is the fastest and most flexible way to do development" as long as you're sure you never want to refactor or experiment and know exactly what code is going to be written. Once committed you've got a safe place to go back to if your refactors/experiments don't work out.

In short (and with respect), you're wrong - you just might not know it yet ;-)