#batman#superman#bruce wayne#clark kent#dc fanart#superbat#superman 2025
#ao3#writeblr#ao3 fanfic#archive of our own#writing community
seen from Maldives
seen from Netherlands
seen from Malaysia
seen from Germany
seen from Netherlands
seen from China
seen from Maldives
seen from Lithuania
seen from Argentina
seen from Maldives
seen from Netherlands
seen from Canada
seen from Germany
seen from Netherlands
seen from China
seen from South Korea
seen from Malaysia
seen from China
seen from Netherlands
seen from Netherlands
gonna model the rest of my cog ocs and jades too … i just finished patty and started ralph + bruster
"I need AI to help me brainstorm!" Actually, you need a rubber duck.
Can’t remember if I showed y’all this little guy.
I was in San Diego visiting family and we went to the county fair, and I bought this from a local alpaca farm. Made of 100% baby alpaca wool (SO soft)
His name is Albert.
I’ve been learning to code and he’s now my “rubber duck.”
What do you prefer to use for rubber duck debugging?
An actual rubber duck
A specific figurine
A good friend
An AI (ChatGPT, Gemini, etc)
The voices in your head
Something else
I don’t code / show results
Another Tylvinian Tales update
I want you guys to meet the assistant lead programmer for this visual novel project:
His name is Perfect Cell and he listens to me bitch about errors until I realize what I did wrong.
There’s this thing in software engineering called Rubber Duck Debugging that basically involves trying to troubleshoot code by explaining the code line-by-line to anyone, but I guess in the book in which the term originated, the programmer would carry around a rubber duck to explain their code to.
Anyway, the whole deal is that sometimes, just by saying out loud what you’re trying to do, you’ll suddenly see the problem staring you in the face without anyone else contributing to the conversation. And this totally works for coding.
It also works for writing.
Like, I usually bounce stuff off of a select couple of people, but maybe I should start explaining things to a rubber duck.
(I kind of just want to explain things to a rubber duck tbh.)
One of my computer science teachers (I have two) promised to buy us rubber ducks at the end of our A Level and if he breaks that promise I will be pissed
(btw it's because there's this thing called rubber duck debugging where you explain any problems you're having with your code to a rubber duck. It's because verbalising your problems can help you find solutions to them.)
Imagine asking Karl Heisenberg to explain his plan to you like you're a rubber duck.
