3 ms·
Heavily refactor the code and files constantly. Split a huge file into different files, put them into "src" or "app", etc. You should be doing this fairly freq
by franciscop 9y ago
Heavily refactor the code and files constantly. Split a huge file into different files, put them into "src" or "app", etc. You should be doing this fairly frequently if there was little planning or the project is quite experimental.
When you have everything clear from the beginning try to anticipate and plan the structure beforehand. But still refactor as needed.
As the final version is near, start improving/making the documentation. Too early and you'll have to change many things, too late and it'll seem like a huge different optional task (which it is normally not). BTW, I am the creator of https://documentation.agency/ https://documentation.agency/ if you need some help there.
- _eht 9y agoDocumentation as a service sounds really valuable to me as an engineer. I personally love solving a problem and building a solution framework, but never feel I do enough justice to help whomever comes after me.
- franciscop 9y agoThe target is not so big as I initially though. Individual developers would (I think) not normally pay for that, and mid-big companies have their own team. So this is either for developers who can spare some money for great docs or for small companies doing OSS. Question, what is stopping you from contacting through the form? Maybe I can also learn how to improve it.