| HN Mirror

Web is its own beast -- even movie making software has to be learned, certainly true of new software domains. I'd recommend researching your tools thoroughly before diving in, and finally when you choose a few candidate tools try and build small prototypes in each that would become modular chunks of your main app. In this way you can evaluate which tools you'd like to use from some low-risk investment of time and effort, and walk away with clear tool commitment. Once you commit to a toolset, you can dive into development as much as your toolset accommodates expression and feedback. I'd recommend using something that has a REPL (Clojure/script with Selmer and even Python with Django have this) which is a way to get immediate feedback from changes in your code. The feedback loop in traditional web development is way too long to make responsive apps in a reasonable amount of time.

Definitely find forums for the tools you are using and ask questions in the beginners channels. No need to be embarrassed, if you've never held a cup it's not a big deal, it just takes time to learn how to hold one. Then time to walk to the river, then time to scoop some water into the cup. But eventually, piece by piece, you'll get a delicious drink that satiates, and you'll know how to fashion a cup even more cleanly for the next time(s) you need a new cup. Aha, at this point one can start seeing code reusability, state management via atomic actions through swaps, and functional approaches as fundamental to achieving incremental progress. Laying the foundation hardly looks like progress, but actual progress is impossible without an excellent foundation.