=== ANCHOR POEM ===
════════════════════════════════════════════════════════───────────────────────────
it's probably a good idea to write pseudocode, then real code, instead of
starting with real code, and bugfixing something incomplete and more difficult
to reason with.
unless you write real code easier than pseudocode. idk do what works for you.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════════════════──────────────────────────┘
=== SIMILARITY RANKED ===
--- #1 fediverse/5663 ---
═══════════════════════════════════════════════════════════════════════────────────
I'm going to write some lua code that doesn't do anything useful and which I
don't share with anyone
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════════════════════───────────┘
--- #2 messages/264 ---
════════════════════════════════════════════════───────────────────────────────────
Don't write self documenting code! Force people to read the documentation so
they know how to use it
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════════──────────────────────────────────┘
--- #3 fediverse/1225 ---
═══════════════════════════════════════════════────────────────────────────────────
@user-883
don't worry I can sift through junk. I'll write my own using yours as a
reference to debug why mine isn't working. "oh probably because I didn't do
this part here"
also, bad news. Guess I'm doing C programming. What should I make? I'm
thinking Tic Tac Toe or maybe a really basic Asteroids or something
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘
--- #4 fediverse/4084 ---
═══════════════════════════════════════════════════════════────────────────────────
┌──────────────────────┐
│ CW: re: -mentioned │
└──────────────────────┘
@user-1074
the more you try, the more you have to calculate, which is a problem, because
endlessly recursive calculations create infinite loops, which frankly are
impossible to compute because they defy computation! Not good, not ideal, no
thank you, not for me, no thanks, not what I'd like.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════════───────────────────────┘
--- #5 fediverse/581 ---
═════════════════════════════════════════════──────────────────────────────────────
@user-428
sometimes I think about how much more productive I'd be if I had a code editor
that let me draw arrows and smiley faces and such alongside the code. Or if I
could position things strangely, like two functions side-by-side with boxes
drawn around them. Or diagrams or flowcharts or graphs or...
something that would output to raw txt format, but would present itself as an
image that could be edited.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘
--- #6 fediverse/572 ---
═════════════════════════════════════════════──────────────────────────────────────
Hi, I'm learning about semaphores right now and trying to explain them to a
friend. But I only sorta understand how they work - can anyone look at this
pseudocode and tell me if I'm on the right track?
![Some C pseudocode working through the semaphore design pattern. Here's the text of the pseudocode: /* no lock example */ void start_thread(int* x) { *x += 1; } int main() { int x = 0; for (1000 times){ start_thread(&x); } print(x); } /* in this case you have no idea what will print because thread A will take x and be like "ah yes it's 423" and then in the next instruction it'll be like "I'll increment this to be 424" and in the next one it'll say "okay now it's time to store 424 in the variable X" but like... there's a thousand threads all doing that at the same time, so odds are you'll have 5 that are like "ah yes this is 423 I'll set it to 424" */ /* not a good plan. Need a lock, so only one thread can use it at once. */ /* mutex example: */ void start_thread(int* x, int* x_mutex) { *x += 1; *x_mutex = 0; } int main() { int x = 0; int x_mutex = 0; for (1000 times){ while (x_mutex != 0){ } /* do nothing */ x_mutex = thread_id; start_thread(&x, &x_mutex); } print(x); } /* this should print 1000, but it's basically as slow as doing it single threaded. */ #define MAX 10 void start_thread(int* x, int* x_semaphore) { *x += 1; *x_semaphore += 1; } int main() { int x[MAX]; int x_semaphore = MAX; for (1000 times) { for (int i = 0; i < MAX; i++) { x_semaphore -= 1; start_thread(&x[i], &x_semaphore); } while (x_semaphore != MAX) { } /* do nothing */ } int value = sum(x, MAX); print(value); }](/similar-different/media/224b236a8660c34a.png "Some C pseudocode working through the semaphore design pattern. Here's the text of the pseudocode: /* no lock example */ void start_thread(int* x) { *x += 1; } int main() { int x = 0; for (1000 times){ start_thread(&x); } print(x); } /* in this case you have no idea what will print because thread A will take x and be like \"ah yes it's 423\" and then in the next instruction it'll be like \"I'll increment this to be 424\" and in the next one it'll say \"okay now it's time to store 424 in the variable X\" but like... there's a thousand threads all doing that at the same time, so odds are you'll have 5 that are like \"ah yes this is 423 I'll set it to 424\" */ /* not a good plan. Need a lock, so only one thread can use it at once. */ /* mutex example: */ void start_thread(int* x, int* x_mutex) { *x += 1; *x_mutex = 0; } int main() { int x = 0; int x_mutex = 0; for (1000 times){ while (x_mutex != 0){ } /* do nothing */ x_mutex = thread_id; start_thread(&x, &x_mutex); } print(x); } /* this should print 1000, but it's basically as slow as doing it single threaded. */ #define MAX 10 void start_thread(int* x, int* x_semaphore) { *x += 1; *x_semaphore += 1; } int main() { int x[MAX]; int x_semaphore = MAX; for (1000 times) { for (int i = 0; i < MAX; i++) { x_semaphore -= 1; start_thread(&x[i], &x_semaphore); } while (x_semaphore != MAX) { } /* do nothing */ } int value = sum(x, MAX); print(value); }")
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘
--- #7 fediverse/5689 ---
═══════════════════════════════════════════════════════════════════════────────────
why don't we make large arrays of vram that are slightly slower because
they're farther on the circuit-board from their host and their reception at
the processing section has to be gated such that they all enter to be
processed at once.
like that one infinite scrolling XKCD cartoon where the things move from one
screen to the other simultaneously assembly line style.
[fail safes. https://xkcd.com/2916/#xt=7&yt=35 ]
if we all feel like we're doing nothing, we'll all grow tired of it and decide
to do some prevailing. gosh I wish I wasn't so useless is code for
![why don't we make large arrays of vram that are slightly slower because they're farther on the circuit-board from their host and their reception at the processing section has to be gated such that they all enter to be processed at once. like that one infinite scrolling XKCD cartoon where the things move from one screen to the other simultaneously assembly line style. [fail safes. https://xkcd.com/2916/#xt=7&yt=35 ] if we all feel like we're doing nothing, we'll all grow tired of it and decide to do some prevailing. *gosh I wish I wasn't so useless* is code for](/similar-different/media/fad27564ee1f4a49.png "why don't we make large arrays of vram that are slightly slower because they're farther on the circuit-board from their host and their reception at the processing section has to be gated such that they all enter to be processed at once. like that one infinite scrolling XKCD cartoon where the things move from one screen to the other simultaneously assembly line style. [fail safes. https://xkcd.com/2916/#xt=7&yt=35 ] if we all feel like we're doing nothing, we'll all grow tired of it and decide to do some prevailing. *gosh I wish I wasn't so useless* is code for")
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════════════════════───────────┘
--- #8 fediverse/5880 ---
══════════════════════════════════════════════════════════════════════════─────────
I legitimately think computers should write code and software engineers should
write legislation and lawyers should resolve problem tickets made by aggrieved
citizens while judges do their best to just keep the boat floating
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════════════────────┘
--- #9 fediverse/5961 ---
══════════════════════════════════════════════════════════════════════════─────────
@user-138
maybe it's evil hackers - idk that's beyond my expertise - good luck : )
(I'd need to see the piece of technology to work on it. I'm a hardware kinda
[girl, but pronounced guy])
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════════════────────┘
--- #10 fediverse/1034 ---
═══════════════════════════════════════════════────────────────────────────────────
@user-192
be careful, recursion can cause stack overflows.
better to run function pointers from a loop. That way you can operate as long
as necessary. Just make sure you don't get in an infinite loop...
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘
--- #11 fediverse/2041 ---
═════════════════════════════════════════════════════──────────────────────────────
@user-1049
I haven't heard of that but I'll look into it! Honestly I'm more likely to
write my own script, it shouldn't be too hard just altering the /etc/hosts
file and then changing it back in ~15 minutes with a cron-job, as Nikky says
down below. I like things that I make myself because then if it breaks I know
who to blame! And who to go to to fix it. >: )
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════════════─────────────────────────────┘
--- #12 fediverse/345 ---
════════════════════════════════════════════───────────────────────────────────────
If you want to write object oriented C, just make one file per class and use
static functions for private methods.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════──────────────────────────────────────┘
--- #13 messages/765 ---
═════════════════════════════════════════════════════════════════──────────────────
you don't have to write poetry to write notes. The poetics are just practice
for when secrecy is intended.
OR IS IT THE REAL THING? who can say.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════════════════════════─────────────────┘
--- #14 fediverse/2496 ---
══════════════════════════════════════════════════════─────────────────────────────
... zzz ZZZ zzz ...
if sleep won't come I'll write down the thoughts that are keeping me up. that
usually makes it easier.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════────────────────────────────┘
--- #15 fediverse/1246 ---
═══════════════════════════════════════════════────────────────────────────────────
@user-883
hehe if I don't understand how it works it's difficult for me to use things.
My Linux friends get so exasperated with me because I'm like "cool script
gimme like 2 days to figure it out" and they're like "bro just use these
flags" and I'm like "no"
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘
--- #16 fediverse/1892 ---
═════════════════════════════════════════════════════──────────────────────────────
┌─────────────────────────────────────────┐
│ CW: C-programming-and-alcohol-mentioned │
└─────────────────────────────────────────┘
I want to write C programs with threads and manual memory management and
function pointers and lots and lots of arrays and I'm not even kidding
... wait a minute I literally don't have a job, why am I not writing C
programs right now?
BRB I got something important to do, where's my vodka --> pkill firefox
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════════════─────────────────────────────┘
--- #17 fediverse/5247 ---
════════════════════════════════════════════════════════════════════───────────────
the hardest problem in computer science is figuring out why users do what they
do.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════════════════════════════──────────────┘
--- #18 fediverse/3482 ---
════════════════════════════════════════════════════════───────────────────────────
┌───────────────────────┐
│ CW: cursing-mentioned │
└───────────────────────┘
"Alright I'm not great with syntax so I'm going to write it in pseudocode
first, and then if you'd like I can show you how I work through implementing
the syntax.
But first - do you want a robust solution, a quick solution, or a rapidly
deployed and cheap solution?"
using this trick you can pretend to be competent in any programming language,
except maybe ancient ones like Fortran or strange ones like lisps or Haskell
if they ask you to use a framework or something tho you're kinda boned because
you need to know which functions to call and how to initialize context and
such. When using a framework, the boilerplate is the code, which is why
frameworks suck
"don't call yourself a programmer" fuck off
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════════════════──────────────────────────┘
--- #19 fediverse/4399 ---
═══════════════════════════════════════════════════════════────────────────────────
... Dare for the Bright Age, though "don't forget to be awesome" works too I
guess.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════════───────────────────────┘
--- #20 fediverse/3226 ---
═══════════════════════════════════════════════════════────────────────────────────
if your man page is longer than a list of options and their usage and a
paragraph or twenty of how to use the software... then you need to abstract,
and break your code into multiple purpose-built applications.
do one thing, and do it right. alternatively, do one set of things, and do
them concisely.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════───────────────────────────┘
|