3 ms·
When prototyping something to see if a concept works, or building something for your own private use, you really shouldn't waste time trying to make the code pe
by noduerme 2y ago
When prototyping something to see if a concept works, or building something for your own private use, you really shouldn't waste time trying to make the code perfect for public consumption. If later you find you want to open source something you wrote, there will inevitably be some clean-up involved, but thinking of writing the cleanest and most readable code on a blue sky project just hampers your ability to create something new and test it quickly.
- fragmede 2y agobut that's the reality of writing software. the problem is that no matter how sincere the promise of "I'll clean it up and release the code" is, it rings very hollow because few people realistically actually ever get there. if a developer is so afraid of judgement that they can't release the code to something they want to release, we have a cultural problem (which we do), but the way forwards from that is to normalize that sharing code that is more functional than it is pretty is better than future promises of code. as the saying goes, one public repo up on GitHub is worth two in the private gitlab instance
- __MatrixMan__ 2y agoLeave it broken, that's fine, just don't leave it misleading. And leave hints for how a passer by might improve it in the future. Probably you'll be that passer by in the future, and you'll thank yourself. Or you won't, and someone will thank you.