31–40 of 100 posts
Truth: no-one really cares about your code We publish code so others can see it , the lazy and the productive. Lazy people do not prosper, so don't waste your energy thinking about them. Why do you want to publish yours, just as a portfolio? Then make a portfolio.
If someone else steals your work, you should be proud. They found it to be valuable. If they managed to sell it or build something with it, they’ve demonstrated that you can do the same. Use it as a learning experience. Keep in mind that you are in control of what people are allowed to do with your software. By default, your code is unlicensed even if it is public, which means no one else can distribute it or change…
Thank you.
As someone how has spent several years in therapy in part related to anxiety, the answer to "how do you get over the fear of X" is "do things that incrementally approach X". https://en.wikipedia.org/wiki/Exposure_therapy There's really no other successful approach I've seen for curing anxiety. You have to just steel yourself and do the thing you're afraid of. It gets easier every time.
If you know who you are, what you're capable of, you won't let other people's opinions hurt you.
It comes with age and experience. I don't mean programming experience either, life experience.
One can also focus on the end goal and drop that foolish pride. The goal is to have a working product, all help is welcome.
I’ve had several people steal my open-source code for different projects before. I’m talking copying (not cloning) the whole thing, changing the credit to their name, making no other modifications, and then republishing on their account. Fortunately they never gained much traction. The ones I know about I blocked on GitHub with a note. No idea if they ever found out or if they tried workarounds, but I figured there’s…
What license did you use? Most licenses require that forks change the name, few require credit except for original copyright headers, and no licenses require modification
I was under the impression that the opposite was the case; that requiring a name change was extremely rare, but some historically important free software packages had it (one such being LaTeX, IIRC), so it was, somewhat grudgingly, considered acceptable. But no normal licenses (like BSD, GPL, Apache, etc.) requires name changes today, AFAIK.
Once you're out of the class, there's no reason to keep it private in my humble opinion. The answers to everything every instructor gives in school is out there somewhere. And AI can solve most of them.
Fundamentally most code goes no where, no one shows much interest unless you release a hit project. It can however be really impactful in interviews and recruitment, if your code is readable and well tested and such then it can be quite a positive for the right types of organisations. So at some point you may very well want to make it public for this purpose.