I have a private repo on GitHub that is private for this reason. I made it in a weekend for fun, and it’s honestly so bad. I have spent way longer fixing dumb mistakes that I spent developing the main features in the first place. But I learned a lot while doing it (and fixing it), and my current project that I’m working on is much, MUCH better. I do have it in a public repo.
I like your code. I’m a senior developer who is fastidious about code form and will comment on bad form on any PR put in front of me because readability is the second most important characteristic of code for maintainability. Still, I’ve written uglier code. Take this comment and print it out if you want to, it’s a writ of permission to write ugly code just as long as you eventually plan on cleaning it up.
I have a private repo on GitHub that is private for this reason. I made it in a weekend for fun, and it’s honestly so bad. I have spent way longer fixing dumb mistakes that I spent developing the main features in the first place. But I learned a lot while doing it (and fixing it), and my current project that I’m working on is much, MUCH better. I do have it in a public repo.
Nobody that isn’t an asshole is going to shame you over dirty code - and if you make it public maybe someone will help you clean it up.
Oh I’m sure. But knowing that doesn’t make me any less self conscious about it.
I like your code. I’m a senior developer who is fastidious about code form and will comment on bad form on any PR put in front of me because readability is the second most important characteristic of code for maintainability. Still, I’ve written uglier code. Take this comment and print it out if you want to, it’s a writ of permission to write ugly code just as long as you eventually plan on cleaning it up.
Sometimes stackoverflow is leaking