It seems to me like it has been good advice to first try to just get an app working. Build all the features --- or at least most of them --- without fretting ab

It seems to me like it has been good advice to first try to just get an app working. Build all the features --- or at least most of them --- without fretting about elegance. Then refactor it. If I try to plan it all out in my head before writing anything, or if I am constantly refactoring as I go, then I just write in circles. Anyway, my premature optimizations often are revised out later or get in the way of other features. It's not that I don't like elegant code. This way yields more elegant code, and I finish faster. --- I also liked the part where he warns against database abstraction: "Either you completely dumb down your data layer (and struggle with delivering functionality), or acknowledge the database as part of your solution (e.g. postgres geo/json features) and throw away configurability guilt. Your stack is as much part of your solution as your code."