61–70 of 72 posts
Personally, I wouldn't care at all. If it works it isn't embarrassing. If you're worried about it reflecting poorly on you, make a new github account (asylum-open-source or whatever) and publish under that?
I firmly believe that a finished, running project - no matter how embarrassing the code will not make the person who developed it look bad. Human endeavors are difficult and nothing incredible was made by one person. Additionally, when we make things in groups it isn't one person who's perfect and everyone else is being shaped by that one person. We all learn and grow and help each other learn and grow. I suggest pos…
We all talked shit about how bad that code was (like we were some experts or something...). People who want to talk shit will talk shit. People who don't know what they don't know will talk shit. Do what you want to do.
There IS such a thing as asshats in our industry who will find any excuse to bully others.
Most people like to pretend they understand Software Engineering and all their code is designed well but that is far from the truth. Real world products are always messy in the first version. It is only when you start rewriting it that it starts getting better (relatively speaking). What counts primarily is that you finished a product/project to requirements and shipped it; everything else comes later.
This is how all learning and development has been done throughout Human history.
Old code isn't embarassing, it's an unlocked achievement at a given state of progress.
If you feel embarassed by your code you'll never face the harsh reality that time is a limited contigent, and therefore limits the quality of code. Everyone has a trade-off equilibrium when the time spent on a project doesn't justify its workload complexity (or reduction thereof) anymore.
At my current place of work, we did a stroll through my github at the interview, I just flat out told "these are terrible, I learnt a lot" and he said "yeah, I saw, but it worked, what would you like to talk about?" and I found one of the more recent projects (still crummy, but you're allowed to write crummy code on your own time!)
I'm about to relaunch a 2D MMO title I made in 1999-2001 with new graphics. It's all in Java and uses MySQL. Should be fine! :D Don't know if I would publish the source though, unless it's successful and people want to mod it.
This sounds exciting! Where will this become available to play when you put it online? :) Also, have a look at Canvas Legacy if you want some inspiration.
It will be more action than CL.
I'm about to relaunch a 2D MMO title I made in 1999-2001 with new graphics. It's all in Java and uses MySQL. Should be fine! :D Don't know if I would publish the source though, unless it's successful and people want to mod it.
Why not publish the source, though?
Still torn about open-source, I believe more in source-available + license fee.
The way it works now no single dev. code can be commercially viable except closed source.