3 ms·
This is a pretty broad question. In general, hobby projects should be as simple as possible since the goal is mostly learning one thing. = No UML, scaffolding
by NicoJuicy 5y ago
This is a pretty broad question.
In general, hobby projects should be as simple as possible since the goal is mostly learning one thing.
= No UML, scaffolding, don't care about performance tuning, all in one app ( identity management, configuration, ... )
A couple of hobby projects were "promoted" and are being sold to customers. So I've got an ecosystem of apps ( status page, sts, spa with gateway and a monolith DDD app), auto client informing of updates, adr if someone would be helping, ... So i wouldn't consider that a hobby application anymore.
Eg. I had an application to learn Microservices. As soon as I implemented all functionality I wanted, i abandoned it and didn't finish it: https://github.com/NicoJuicy/poc-micro-service https://github.com/NicoJuicy/poc-micro-service
The learnings from that project are implemented in other places.
- Karsteski 5y agoSo you're saying you just go with the flow instead of planning out things then?
- NicoJuicy 5y agoSure. What's the goal of your hobby project and how many do you have/start per year? As a comparison, i have like 40-60 hobby projects ( currently only 3 in progress and 1 big one for customers + 1 site). A lot of them are probably lost on previous computers, that's okay. I would say most of them were 1 weekend of work. The ones that I actually wanted to use were promoted and/or redone from scratch ( = at least integrated with my STS ) For when it's appropriate, I actually try hard to keep them as simple as possible. To be honest, I'd say i start one within a month of thinking about it and reading more about it. But I have most of the project planned before in my head before i even start. I normally keep my hobby projects small and disposable. Eg. You're currently on V1 of the engine. How much of the code would you want to start over, now that you know more about it? In general, business make the same errors. Iterate and improve.