This question already has an answer here:
- Best Development Methodology for One Person? 16 answers
I am a chemical engineer, working in an 'old-world' industry (petroleum refinery).
As a computer enthousiast, I have, from the beginning, used code to help me in my daily job. At first, it was VBA macros, increasingly complex.
When I figured it was too complicated to solve some issues in VBA, I switched to VB.NET dlls, then desktop apps. One thing led to an other, colleagues grew fond of my applications, etc.
As a result, I am today 'managing' several applications (Web APIs, desktop apps, VBA macros, etc.), in addition to my 'real' job. I sometime look back at some old code, and realize it is pure garbage, and feel sorry for future me, or the guy that will replace me someday.
I want to take steps to improve on this. I have read about several development methods, but it all really seems overkill for my situation where:
I am the only one developing (therefore, all kinds of code review, scrum meetings, etc. are not really relevant).
I am both the client, and the developer (so I am really client oriented!)
I do this to make my (and my colleagues) 'real' job easier. Therefore, based on the workload, I can have none to a lot of time to spend on this, but I can't really plan sprints, or stuff like this.
Do you know of any development method for this kind of hobby development that would allow me to prepare for the future a bit better than I do today?