| > How do I stop being obsessed with software architecture and actually focus on getting shit done? Write the documentation of the current and besides it write documentation of the new version. Refactoring is important and it helps further to have the documentation of the new before you've rewritten the old. Unless it's a brand new application; it's going to be the same right? Articulate your current application so you have a visual proof of that it is doing what it should be doing. how is it's functioning and ensuring you can rebuild said app from scratch from documentation alone. With that documentation you then start to unbundle the knots you've created in your mind and code. You see the faults, lags and notice where improvements and new features can all the rest. The newly documented pseudo-code then presents the foundation plan of your next version and enables the ability of implementation of feature sets, the fixes required that would be a struggle to retrofit. It's tedious, boring, a great effort and hard discipline but when you've got it down on paper you've then got true focus to the software architecture. It opens your mind. Documentation plays a big part in all code and your app/program will always feel not-it without it. I'm currently writing mine and it's a chore. I would love to implement my new discovery feature or to create an editor to document my own code but the deeper I go without documentation the more thicker dark mist I encounter. |