Evanalyze

My first major software project–that is, the first one that’s been intended for other people to use–has been unecessarily difficult because I skipped the common sense step when deciding what to do next.  I originally thought that I should avoid building anything that had a dependency on a system I hadn’t build yet.  For example, I shouldn’t build a login system until I figure out how to do password recovery and things like that.

It sort of makes sense, since no one wants to use an application that depends on things that don’t exist.  But what I’ve learned is that no one actually uses something that’s not finished yet, they test it.  Any if people are willing to test a half-baked idea they don’t care if you need to manually reset their password in the database or if they need to use some dummy login credentials until you have a real signup system.

Thinking really gets in the way sometimes.