Ask HN: What horrible things do you do in your own code when no one is watching?
It's your code, no one else will ever see it or maintain it. What worst practices and cheap shortcuts do you use when you really are going "quick and dirty?"
I never hide data. All structs with all public members. Even if I write an API around that, I can still just access everything directly if I want to.
When I use raw pointers, I usually don't check for nullptr.
I abuse unions and their initial members and don't bother checking tags even if I tag them.
Does it compile? Good. Does it run? Good. If I leave it running does it eat all my RAM? No? it's probably fine then.
I tend not to push changes for weeks or sometimes months, and my commit message is basically that I forgot everything I actually changed. Also, my commit messages are terrible.
I keep one big text file full of notes, comments and old code pasted in. My source code itself tends not to be commented well as a result.
Cause it's fun.
process.argv.forEach((arg, i, argv) => {
switch (arg) {
case "--foo":
foo = argv[i + 1]
break
case "--bar":
bar = argv[i + 1]
break
}
})or a huge block of comments at the head of my main file, with all the TODOs...
Also, not using version control, and only switching to it when the project is already a considerable size...
See g string ^^
The more useless social media BS Github piles onto its site the more it becomes the new Linkedin... no thanks.
Somebody off me.
String str;