Joy finder && software developer.
Accessibility, videogames, webdev, cloud, amateur but appreciative gardener.
he/him 🏳🌈🌎
Working at Rare on #SeaOfThieves and beyond~
| blog | https://topher.io |
| threads | https://www.threads.net/@winwardo |
Joy finder && software developer.
Accessibility, videogames, webdev, cloud, amateur but appreciative gardener.
he/him 🏳🌈🌎
Working at Rare on #SeaOfThieves and beyond~
| blog | https://topher.io |
| threads | https://www.threads.net/@winwardo |
Okay but what if I made a crunchy found footage style horror game in Unreal? 👀
Beeen playing around with this on my lunch breaks and I think I nailed the 90s style crappy camcorder vibes.
"i use linux as my operating system," i state proudly to the unkempt, bearded man. he swivels around in his desk chair with a devilish gleam in his eyes, ready to mansplain with extreme precision.
"actually," he says with a grin, "linux is just the kernel. you use GNU+linux."
i don't miss a beat and reply with a smirk, "i use alpine, a distro that doesn't include the GNU coreutils, or any other GNU code. it's linux, but it's not GNU+linux."
the smile quickly drops from the man's face. his body begins convulsing and he foams at the mouth as he drop to the floor with a sickly thud. as he writhes around he screams "I-IT WAS COMPILED WITH GCC! THAT MEANS IT'S STILL GNU!"
coolly, i reply "if windows was compiled with gcc, would that make it GNU?" i interrupt his response with "and work is being made on the kernel to make it more compiler-agnostic. even if you were correct, you won't be for long."
with a sickly wheeze, the last of the man's life is ejected from his body. he lies on the floor, cold and limp. i've womansplained him to death.
I sometimes also hear the response of "Bad documentation is worse than none!" and I completely disagree!
Bad docs are usually written with good intent and the best knowledge of the time, even if it is now no longer valid.
Fear of writing bad docs sometimes stop some people writing in the first place, even if what they write would have been helpful
There are two fairly reliable steps to writing great #software documentation:
a) Write down *something* that you know about the topic at hand
b) Edit it into something worth reading
Many people feel they're no good at b), and in turn avoid a) entirely!
*Some* docs are better than none.