Ok. I am going to let you in on a secret about how to make programming projects.
You know how people write really good code? Easy to read, easy to work with, easy to understand and very efficient?
By refactoring.
The idea that you write glorious nice code straight is an insane myth that comes from thinking tutorials is how people actually code.
That is because programming is just writing. Nothing more. Same as all other writing.
The hobbit is ~95000 words.
Do you think Tolkien created the Hobbit by writing 95 thousand words?
Of course not! He wrote many many times that. Storylines that ended up scrapped or integrated in other ways, sections that got rewritten, dialog written again and again as the rest of the story happened. Background details filled in after the story had settled down
Writing. Is. Rewriting.
Coding. Is. Refactoring.
Step 1 in programming is proof of concept. Start with the most dangerous part of your project ( danger = how little experience you have with it * how critical it is for your project to work )
Get it to do... anything.
Make proof of concept code for all the most dangerous parts of the project. Ideally there is only 1 of these. If there is more than 3 then your project is too big. ( yes, this means your projects needs to be TINY )
Then write and refactor code to get a minimum viable pruduct. It should do JUUUUUST the most important critical things.
Now you have a proper codebase. Now everytime you need to expand or fix things, also refactor the code you touch in order to do this. Make it a little bit nicer and better. Write unit tests for it. The works.
After a while, the code that works perfectly and never needs to be touched is hard to read. Which does not matter because you will never read it
And the code that you need to change often is the nicest code in the codebase.
TRYING TO GUESS AHEAD OF TIME WHAT PARTS OF THE CODE WILL BE CHANGED OFTEN IS A FOOLS ERRAND.
( also, use git. Dear god use git and commit no more than 10 lines at once and write telling descriptions for each. GIT shows WHAT you did. YOU write WHY you did it )
Is this how to make your hobby project?
Yes. And also how all good software everywhere is made.
Let's write a C++ program together. I'll start us off.
int main() {
i fucking hate writing java dude what do you mean list.stream().forEach(list2::add)??!
syntax written by clowns
You all disappoint me. Not one (1) drawing of a personified tumblr mourning the lifeless corpse of 4chan? Not ome? They were our rivals you sick fucks. Nary a whiff of 1 (one) fix-it AU? Im going to hibernate now..youve pirssed me off
coding got me saying shit like “target the child” “assign its class” “override its inheritance” like the third wife of a dying oil baron discovering his of-age son born out of wedlock
i post from here. if you even care.
I distinctly remember ranting on tumblr about a problem in my code like half a year ago and I was frustrated with arrays of strings in c++ and I REMEMBER a furry adding a comment that just said “you could try parsing the string uwu” and I did it and it WORKED and I was so relieved because I had been fighting with it for like a week.
The only problem is I can’t find that post and I think I dreamt it up. I think God came to me in a dream as a furry responding to my tumblr post to help me fix my code. I am going insane why did my brain do this.
Computers be like "omg bestie so true" and it's just the number 1
I don't expect porn games to have top-notch gameplay, but I do at least expect them to engage with the mechanical conventions of the genres they're pornifying. "RPG where you have sex with the monster when you lose a fight" bullshit – I want to see porn versions of those tedious filler puzzles every indie RPG is apparently contractually required to have. Let's see an erotic version of the Towers of Hanoi.