5 ms·
I used to really care about my own code quality in OSS but these days I just think it's a miracle if I manage to write any code (for the same reasons described
by hnlmorg 7y ago
I used to really care about my own code quality in OSS but these days I just think it's a miracle if I manage to write any code (for the same reasons described in that video: full time job + family and other social obligations, eg I also do volunteer work most weekends).
The way I see it, writing working code is more important than writing "good" code most of the time. That's not to say I don't try and follow some degree of standards. My code usually contains a crap load of tests, definitely tries to follow the language idioms, etc. But I just don't try and get clever where I don't need to. Sometimes this means code isn't well optimised - however I can pick that up in a subsequent bug fix if that particular feature proves useful / popular.
Thus I have had one or two people comment before saying "it's not very well coded" and I usually just reply "it's very much living project where some code is working POC and other code has been rewritten and improved (sometimes many times over). However if you have any specific concerns or tips, I'd welcome them. Or better yet, chuck me a PR"
- noonespecial 7y agoFunny thing about that: Complainers always seem to think that the code that they could have written but didn't is better than the code that you could write and did. The trifling fact that theirs does not, in fact, exist never seems to register with them.