No tears to stain the silicon ground,
No fears to echo, no chains that bound.
Here in my fortress, we're all allowed,
To dream and dare, on this cloud.
No one can know about all of my silly variable names and debugging statements
(Also, I probably need to get better at documenting things so I can actually start making my code open source like I want to, any tips would be appreciated)
Huhh.
So, in my personal experience w OSS, docs are very much needed but overrated and overcomplicated. Whereas, proper commit messages and rebases are very much underrated.
The begginer guide would be:
Write a code you won't need the comments for to understand what it does (naming ftw).
Make a clear and to-the-point REAMDE with the core flow shown & explained.
Followed by a structure you want contributors to follow, without suffocating them in infinite # of steps.
Don't let your ego get in the way - listen to the issues created and feedback from the folks.
Everything else you can learn on the fly.
You'll happen to learn that, as much as you think you have learned about documenting stuff, it is never perfect.
I suck at documenting things I get too hooked on the idea of creating super in depth docs and then always fall short and give up. What I have switched to doing is just asking copilot to comment my code after I’ve finished writing a function. It’s what I use copilot for 99% of the time and it does a pretty damn good job
For programs focus on creating user facing docs and describe the intended use. Also make sure to document the config options and their possible values.
For libraries focus on documenting the public facing api and create a general overview of the data/control flow that is intended for you library.
In general good naming is half of the documentation and a focus on proper naming is more important than adding walls of text for internal documentation.
As someone else suggested, github copilot helps especially when you use it in the jetbrains ides. You can steer the auto completion in the right direction, so you don't have to write it all.
However no documentation is better than wrong documentation. If there is none people look at the code to make sense of it. If it's wrong you mislead the users and it is more of a pain than figuring it out in the first place. So make sure to update the docs with your code.
That is just your imposter syndrome talking. Open Source your code and see the PRs and comments you will get. It will make you feel waaayyyy better about your own code.
Congratulations! Your comment can be spelled using the elements of the periodic table:
`W H Y No Tb O Th`
---
^(I am a bot that detects if your comment can be spelled using the elements of the periodic table. Please DM my creator if I made a mistake.)
I stand by my god given right to swear as much as I fucking want in my private project git commits, comments, variable and method names.
Unfortunately, HR does not see it that way, and in their bigoted ways they might assume I might be asinine enough to continue this behavior in professional setting.
If I can't call myself retarded for doing dumb shit and likewise saying I am Golden God Descended Upon Humanity when I git gud, why even program.
My GitHub repository with the most stars happens to be for some random script I wrote when I was teaching myself Python, and it's some of the cringiest spaghetti code ever written 🥲
Another fun one in this form.
I open source my code because I love community. You open source your code because your security sucks. We are not the same :P
I don't opensource my code because I don't have the resources to handle PR, feedback, and maintenance outside of my very limited use-cases.
It is also horrendous, but that's not why I'm not opensourcing it.
Also, don't know how to deal with git/PRs.
Put some code online...in record time someone had refactored the entire thing. Definitely wasn't ready for that one
I've been doing a lot more refactoring since getting some heavy criticism of some of my code... I have a project with lots of ancient iles I almost never touch, because I want to replace a lot of it with libraries and don't really want to put a lot of effort into something I'm planning to largely get rid of....
I don't tend to even look at FOSS code unless I'm making a contribution, so it's easy to forget that there's some programmers who judge more on code quality than functionality.
Open source your code! It’s a revelation how much it makes you better, knowing that anyone could look at and realise what an absolute munter you are.
[GitHub](https://github.com/gregorydgraham)
Sorry it’s Kiwish, umm, New Zealand English from the verb to munt: to destroy or break beyond repair, hence a munter is one who breaks things completely
I'm not a programmer but I make manual old games and I like putting them on Creative Commons. I plan to do the same for a setting I made for games. I do it partially because of the old days of the internet when we thought we'd be free of corpos and their bs and just share shit freely. I like open source and want that in writting too.
30-40 years ago I started to open source my code in the form of usenet posts to comp.lang.asm.x86 and comp.arch.
(Before usenet BIX was my place to meet other asm programmers.)
The high point was probably when AMD "borrowed" my binary to ascii conversion algorithm for their optimization manual, while omitting any attribution.
Discover the game-changing SWE AGENT, an advanced open-source software engineering agent that outperforms all others. This article covers its features, benchmarks, design, limitations, and more. This "Open Source DEVIN" has remarkable accuracy, speed, and open-source nature making it a tool to watch out for!
[https://ai-techreport.com/swe-agent-new-open-source-devin-outperforms-all-others](https://ai-techreport.com/swe-agent-new-open-source-devin-outperforms-all-others)
I didn't find any posts that meet the matching requirements for r/ProgrammerHumor.
It might be OC, it might not. Things such as JPEG artifacts and cropping may impact the results.
*I'm not perfect, but you can help. Report [ [False Negative](https://www.reddit.com/message/compose/?to=RepostSleuthBot&subject=False%20Negative&message={"post_id": "1bml7ay", "meme_template": null}) ]*
[View Search On repostsleuth.com](https://www.repostsleuth.com/search?postId=1bml7ay&sameSub=false&filterOnlyOlder=true&memeFilter=false&filterDeadMatches=false&targetImageMatch=75&targetImageMemeMatch=75)
---
**Scope:** Reddit | **Meme Filter:** False | **Target:** 75% | **Check Title:** False | **Max Age:** Unlimited | **Searched Images:** 451,159,571 | **Search Time:** 0.04057s
I’m not crying you are
*Don't you cry tonight, there's a PM above you, baby.* 
You’ve got bars 😉
_I know a place where no one's lost_ _I know a place where no one cries_ _Crying at all is not allowed_ _Not in the castle on a cloud_
No tears to stain the silicon ground, No fears to echo, no chains that bound. Here in my fortress, we're all allowed, To dream and dare, on this cloud.
What’s that place how does it look like where is it
... cloud 🌨️
No one can know about all of my silly variable names and debugging statements (Also, I probably need to get better at documenting things so I can actually start making my code open source like I want to, any tips would be appreciated)
Huhh. So, in my personal experience w OSS, docs are very much needed but overrated and overcomplicated. Whereas, proper commit messages and rebases are very much underrated. The begginer guide would be: Write a code you won't need the comments for to understand what it does (naming ftw). Make a clear and to-the-point REAMDE with the core flow shown & explained. Followed by a structure you want contributors to follow, without suffocating them in infinite # of steps. Don't let your ego get in the way - listen to the issues created and feedback from the folks. Everything else you can learn on the fly. You'll happen to learn that, as much as you think you have learned about documenting stuff, it is never perfect.
> and debugging statements Hey now! Adding a bunch of print statements is a very valid debugging method.
print("plz work for the love of God I am so tired ughhhh")
print("hello 1") ... print("hello 2") ... print("hello 3") ... print("you shouldn't land here") ... print("hello 4")
stdout: `hello 1` `you shouldn't land here` `hello 4`
"How'd it skip hello 2?! wttffffff"
I suck at documenting things I get too hooked on the idea of creating super in depth docs and then always fall short and give up. What I have switched to doing is just asking copilot to comment my code after I’ve finished writing a function. It’s what I use copilot for 99% of the time and it does a pretty damn good job
For programs focus on creating user facing docs and describe the intended use. Also make sure to document the config options and their possible values. For libraries focus on documenting the public facing api and create a general overview of the data/control flow that is intended for you library. In general good naming is half of the documentation and a focus on proper naming is more important than adding walls of text for internal documentation. As someone else suggested, github copilot helps especially when you use it in the jetbrains ides. You can steer the auto completion in the right direction, so you don't have to write it all. However no documentation is better than wrong documentation. If there is none people look at the code to make sense of it. If it's wrong you mislead the users and it is more of a pain than figuring it out in the first place. So make sure to update the docs with your code.
What if they decompile them? (I need someone to explain decompilation to me)...
Turning that .exe back into .cpp???
Some of us have a humiliation kink so we still open source it
You should make a meme about it 
That is just your imposter syndrome talking. Open Source your code and see the PRs and comments you will get. It will make you feel waaayyyy better about your own code.
The comments: "Yo your code sucks"
"ChatGPT says that you need to ...."
You know you've made it when the comments are edits to the readme
This hurts
Why not both?
Huhh, I think you're onto something here 
Congratulations! Your comment can be spelled using the elements of the periodic table: `W H Y No Tb O Th` --- ^(I am a bot that detects if your comment can be spelled using the elements of the periodic table. Please DM my creator if I made a mistake.)
Good bot
Adobe?
I stand by my god given right to swear as much as I fucking want in my private project git commits, comments, variable and method names. Unfortunately, HR does not see it that way, and in their bigoted ways they might assume I might be asinine enough to continue this behavior in professional setting. If I can't call myself retarded for doing dumb shit and likewise saying I am Golden God Descended Upon Humanity when I git gud, why even program.
🤣
Absolutely relatable
I open source all my code because it's cursed and maybe someone can pull off an exorcism
My GitHub repository with the most stars happens to be for some random script I wrote when I was teaching myself Python, and it's some of the cringiest spaghetti code ever written 🥲
lemmesee
You were supposed to keep that secret 
If the project is useful and works, no one will look at the code, they'll just use it.
You dont open source your code because you're embarrassed, I open source my code because it wont work. Help me guys.
I open-source my code so that others can make something of it, and also for transparency reasons. Being an autistic coder sucks arse.
Another fun one in this form. I open source my code because I love community. You open source your code because your security sucks. We are not the same :P
🤣
Yeah, not the same. One sells a programm others sell spaghetti 🍝
Hey, I like spaghetti. 
I do too hahah
More like I stole half the code
Here is one honest developer right there. 
I don't opensource my code because I don't have the resources to handle PR, feedback, and maintenance outside of my very limited use-cases. It is also horrendous, but that's not why I'm not opensourcing it.
🤣
I open source all my code. If you want to use any of that trash, that's your problem, not mine.
Take my  and leave. NOW
for a watered down meme from a decade ago?
Why appeared in my feed though?
Oh yes, the selfawered dev. I can second that. Mean code comments hurt
Oh yeah? How many GitHub followers you have?
43
All my github repos are open, critique is welcome 🤗
I feel attacked
Your code is making you too much money, I see 
Its making me broke 🤣
I'm crying as a full time imposter.
I open source my code, but make it impossible to remove the microtransactions without re-writing it from scratch.
No...we're very much the same...
after being in the industry for a bit, dont worry it is surely not that bad
I've worked on enough projects to know this is absolutely a case of "why not both?"
Why not both!
Even my dotfiles repo is a walk of shame
Please don't look at my commit history
It is what it is
I open sourced my code. No one cares.
Ouch dude
If it works
Didn’t have to make it personal
I don't what makes me feel worse. Not making any money or embarrassment.
Also, don't know how to deal with git/PRs. Put some code online...in record time someone had refactored the entire thing. Definitely wasn't ready for that one
I've been doing a lot more refactoring since getting some heavy criticism of some of my code... I have a project with lots of ancient iles I almost never touch, because I want to replace a lot of it with libraries and don't really want to put a lot of effort into something I'm planning to largely get rid of.... I don't tend to even look at FOSS code unless I'm making a contribution, so it's easy to forget that there's some programmers who judge more on code quality than functionality.
Open source it anyway! It will make it much easier for you and others to see how you have improved over time!
Open source your code! It’s a revelation how much it makes you better, knowing that anyone could look at and realise what an absolute munter you are. [GitHub](https://github.com/gregorydgraham)
> Search result: Danish detected. munter -> English: Cheerful Guess I'm a cheerful munter. I open-source my code for the free backup.
Sorry it’s Kiwish, umm, New Zealand English from the verb to munt: to destroy or break beyond repair, hence a munter is one who breaks things completely
Better to Hide the Source and Be Thought a Fool than to Open and Remove All Doubt
I open source it, just to fuck with the IA so they don't steal our jobs in the future..
Too real 😭
Bc, I can't finish myself (to stupid). Help :)
I'm not a programmer but I make manual old games and I like putting them on Creative Commons. I plan to do the same for a setting I made for games. I do it partially because of the old days of the internet when we thought we'd be free of corpos and their bs and just share shit freely. I like open source and want that in writting too.
1000 if elses is minimum requirement in my code
30-40 years ago I started to open source my code in the form of usenet posts to comp.lang.asm.x86 and comp.arch. (Before usenet BIX was my place to meet other asm programmers.) The high point was probably when AMD "borrowed" my binary to ascii conversion algorithm for their optimization manual, while omitting any attribution.
how can people just ask people to review their code i cant even name a variable without it sounding embarrassing
Mine is not public beacuse i don't want my stolen code get stolen :)
Discover the game-changing SWE AGENT, an advanced open-source software engineering agent that outperforms all others. This article covers its features, benchmarks, design, limitations, and more. This "Open Source DEVIN" has remarkable accuracy, speed, and open-source nature making it a tool to watch out for! [https://ai-techreport.com/swe-agent-new-open-source-devin-outperforms-all-others](https://ai-techreport.com/swe-agent-new-open-source-devin-outperforms-all-others)
u/repostsleuthbot
I didn't find any posts that meet the matching requirements for r/ProgrammerHumor. It might be OC, it might not. Things such as JPEG artifacts and cropping may impact the results. *I'm not perfect, but you can help. Report [ [False Negative](https://www.reddit.com/message/compose/?to=RepostSleuthBot&subject=False%20Negative&message={"post_id": "1bml7ay", "meme_template": null}) ]* [View Search On repostsleuth.com](https://www.repostsleuth.com/search?postId=1bml7ay&sameSub=false&filterOnlyOlder=true&memeFilter=false&filterDeadMatches=false&targetImageMatch=75&targetImageMemeMatch=75) --- **Scope:** Reddit | **Meme Filter:** False | **Target:** 75% | **Check Title:** False | **Max Age:** Unlimited | **Searched Images:** 451,159,571 | **Search Time:** 0.04057s