My first thought is "How much of this can I get to work in a day or two using mostly shell scripts, existing programs, and text files?" My first drafts of web

My first thought is "How much of this can I get to work in a day or two using mostly shell scripts, existing programs, and text files?" My first drafts of web apps always look exactly like this: <!doctype html> <title>Foo <link rel=stylesheet href=index.css> <div id=app /> <script src=index.js></script> I've also embraced a kind of chaotic method, analogous to "write drunk, edit sober." Getting something to work with purposefully bad code is a productivity hack for me. Refactoring it later is enjoyable and often necessary, but the separation of mindsets is crucial. It's like what the XP guys called spike solutions. Make sure that you can plausibly get from A to B without caring at first about performance and elegance. This gives you information and confidence. In my experience, developing cannot be a clean and controlled process unless you're doing something you've already done before.