Hey ,
I'm currently working on a project that I eventually want to open source.
The thing is, it’s my first time using both Angular and Go. I feel like I’m constantly refactoring the code and architecture every couple of days just to make it look "clean" and more understandable. I'm worried that if it's not polished, people won’t take it seriously or it’ll be too messy for contributors to get into, even if I don’t expect a lot of contributors, I’d still like the project to be approachable and understandable.
Should I stop worrying about that for now, just focus on finishing the core features, open source it, and then clean things up gradually?
How do you all usually approach this? Is it better to release early, or wait until the codebase is cleaner?Would love to hear your thoughts!
(I hope it is the good channel, sorry if it isn't)
#Should code and architecture be good to make it open source?
opal mauve
vagrant garden
Hello, I'd finish the core first. Going otherwise might lead to never open-sourcing it, as finally getting the feeling it slows you down.
But start documenting your project already, even if it changes, it'll help you for the future.
opal mauve
Ok, thank you. I will do that then. Hope it will help me to get this project set to public quicker :D. Yes, i absolutely need to do the tests and documentation that i keep up do date. Thanks again!