=== ANCHOR POEM ===
═════════════════════════════════════════════════──────────────────────────────────
functions should be forced to describe the context of why they were being
called. I think it would help debug a lot if we supplied a reasoning for each
and every request [function call] that we made. We might even be able to parse
them into semantic pyramids which we could sorta use to estimate [tree-like
scanning] how and why the program did do wrong.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧══════════════════════════════════════─────────────────────┴───────────┘
=== SIMILARITY RANKED ===
--- #1 fediverse/1983 ---
═════════════════════════════════════════════════──────────────────────────────────
@user-1037
I guess I'm saying that for non-standard functions (most of them) they should
need to make a ticket every time they want to run a function call. Perhaps
only in debug mode...
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧══════════════════════════════════════─────────────────────┴───────────┘
--- #2 fediverse/5979 ---
═════════════════════════════════════════════════════════════════════──────────────
whenever you call a function, just pass along the arguments that you don't
know what to do with yet. they'll surely be useful sometime. and, luckily, you
can always search for them from the past, and just insert a "store this value
in this random spot of memory and mark it as needed" then pass it along. used
something? think it's still useful? pass it along (suddenly, formulaic
stateless development, where everything is used until it's no longer needed,
then generated again in a cyclical time-loop cycle which echoes and
reverberates groundhog day but mostly a game-loop, which nobody will
understand unless you're a game dev. but now since I said game dev, anyone can
look it up, so like... not that one, but others like it.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧══════════════════════════════════════════════════════════─┴───────────┘
--- #3 fediverse/3544 ---
════════════════════════════════════════════════════───────────────────────────────
┌───────────────────────────┐
│ CW: programming-mentioned │
└───────────────────────────┘
"I wish there was a language that was as simple as C but had [insert complex
language feature here]"
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧═════════════════════════════════════════──────────────────┴───────────┘
--- #4 messages/264 ---
═════════════════════════════════════════════──────────────────────────────────────
Don't write self documenting code! Force people to read the documentation so
they know how to use it
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧══════════════════════════════════─────────────────────────┴───────────┘
--- #5 fediverse/2859 ---
══════════════════════════════════════════════════─────────────────────────────────
┌───────────────────────┐
│ CW: cursing-mentioned │
└───────────────────────┘
large corporations will often error check *constantly* which slows down their
software to an immense degree.
every time data passes from one function to another, there's like... 15
different tests to check if it's this type or that, or in the right random seed
and it's like... wow can you not, like. design your software intelligently and
then you won't need a bunch of slow-ass if checks every time you want to
update a string???
software should be writable without fucking getters and setters. If it isn't,
then your functions aren't complete.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧═══════════════════════════════════════────────────────────┴───────────┘
--- #6 fediverse/5189 ---
══════════════════════════════════════════════════════════════─────────────────────
computer programming essentially boils down to putting the right values into
the right datastructures at the right time and in the right order.
If you count a function call as a datastructure, which I do, because I have
opinions.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧═══════════════════════════════════════════════════────────┴───────────┘
--- #7 fediverse/1691 ---
════════════════════════════════════════════════───────────────────────────────────
"I don't know what I was doing with this line of code so I'm going to delete
it and fix it later"
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧═════════════════════════════════════──────────────────────┴───────────┘
--- #8 fediverse/3274 ---
═══════════════════════════════════════════════════────────────────────────────────
"I can't remember that function, it does too few things"
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧════════════════════════════════════════───────────────────┴───────────┘
--- #9 fediverse/4846 ---
╔══════════════════════════════════════════════════════════────────────────────────┐
║ programmers already spend a ton of time as downtime. │
║ │
║ what if instead of interviewing someone they just... watched them program for │
║ like, 3 hours or so │
║ │
║ while they were thinking about a problem │
║ │
║ and like, if the person is cool, working on their own projects or whatever, │
║ then yeah hire them │
║ │
║ -- stack overflow -- │
║ │
║ I also │
║ │
║ ========================= stack overflow │
║ =============================================================================== │
║ ======================== │
║ │
║ a person thinks out loud the thoughts that their foes know. it's how you know │
║ it's not secret anymore, and it's better to keep it among allies │
║ │
║ [something like that? seems a little off] │
║ │
║ (are you really searching for edits) │
║ │
║ [that sounds pretty cool, sure why not we got a millenia] │
║ │
║ (beep boop one partial millenia later) │
║ │
║ [ah that was not a long rest. let's see, where were we when we were working on │
║ this test? oh dear, seems the biology's gone rogue, that's pretty interesting │
║ to attest. │
║ │
║ neato │
║ │
║ anyway let's wait until they figure out how water works │
╠═════════╗ ┌───────────┤
║ similar ║ chronological │ different │
╚═════════╩═══════════════════════════════════════════════─────────────┴───────────┘
--- #10 fediverse/282 ---
════════════════════════════════════════───────────────────────────────────────────
@user-209
I think you're right. Every letter in the variable name is another byte the OS
has to keep track of, which was a bigger problem in the past than it is today
(when it's been made irrelevant)
it's interesting how habits persist though the conditions that caused them
have faded. like a personal reflection of the environment you learned in.
"A a = new a();" is much more concise and (crucially) you can fit more words
to the right.
"a + b = c; c -= 2; f_z.write(c); f_z.close();" could conceivably be written
on a single line if you have short variable names. and when you only have so
many lines...
glad we're not constrained by those things anymore. the skeletal code that we
look at daily is much clearer - scope is more important, and so it makes sense
to encourage a coding style that illustrates it. however I can't help but
think block formatting like this could be useful in some situations, such as
when you'd normally be compelled to write a function for an operation that
runs once or more.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧═════════════════════════════──────────────────────────────┴───────────┘
--- #11 fediverse/6437 ---
════════════════════════════════════════════════════════════════════════───────────
if I was writing a programming language, I'd name it C just to fuck with people
(great, now others can decide how it's known)
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧═══════════════════════════════════════════════════════════╧═──────────┘
--- #12 fediverse/1871 ---
═════════════════════════════════════════════════──────────────────────────────────
I think all software should have config files
or accept as many command line arguments as necessary to achieve all the
functionality of a config file without requiring a standardized setup
or accept a config file as a command line argument, to allow for multiple
different implementations
or whatever you can throw together in your spare time because software is
either open source or it hates you.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧══════════════════════════════════════─────────────────────┴───────────┘
--- #13 fediverse/5229 ---
╔══════════════════════════════════════════════════════════════────────────────────┐
║ what if programs just checked the current state of the program against their │
║ past memory of it every time their looping functions got to the end of a new │
║ kind of while loop which checked the previous state of all the variables in │
║ the system as compared to the arguments of the function that is called by the │
║ new kind of while loop which look exactly the same as the last memory of the │
║ program. Okay. Let's write it to RAM and then start working on the next one. │
║ Once we run out of space or the operating system needs more, we can relinquish │
║ the oldest ones. The idea is to store state after all which could be │
║ programmatically checked to make sure it didn't change underneath our feet. │
║ Then you pretty much wouldn't need to worry about buffer overflows or │
║ cybersecurity incidents at all... │
║ │
║ after all, it's only read only. what's the harm in reading our tax │
║ documentation? │
║ │
║ anyway, something about functional programming languages like lisp passing the │
║ entire state of the program to each recursion...if you use that kind... │
╠═════════╗ ┌───────────┤
║ similar ║ chronological │ different │
╚═════════╩═══════════════════════════════════════════════════─────────┴───────────┘
--- #14 messages/488 ---
═══════════════════════════════════════════════════────────────────────────────────
Look at the unique patterns in a programming language, and you will find
within them a usecase.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧════════════════════════════════════════───────────────────┴───────────┘
--- #15 fediverse/5248 ---
═══════════════════════════════════════════════════════════════────────────────────
programming is something that everyone should learn at 14 to be used for
calculating large sums of data, visualizing something they're trying to
explain, or connect two systems that aren't normally connected.
It should not be used as an eternal debug producing machine, nor as a way to
collect and store user information to be sold as the real product, nor to be
collecting and targeting -- stack overflow -- wow, talk about death of the
author, amiright? -- -- endless data hoarding monger machines to point and to
ponder the eternal ramifications of the brutal and violent prompts and their
baggage implied when submitted for each semi-random thought that from the
users mind was displaced.
... "they can sell this" and or "this is mrs selvig" who is this mister and
why is the ms's his-es
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧════════════════════════════════════════════════════───────┴───────────┘
--- #16 fediverse/5658 ---
══════════════════════════════════════════════════════════════════─────────────────
do you think the "main menu" in video games is named after the main() function?
┌─────────┐ ┌───────────┐
│ 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/3680 ---
════════════════════════════════════════════════════───────────────────────────────
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 │
╘═════════╧═════════════════════════════════════════──────────────────┴───────────┘
--- #19 fediverse/6166 ---
══════════════════════════════════════════════════════════════════════─────────────
Computer programming has always been the practice of applied abstraction. At
what level do you wish to apply your reasoning, and what level do you wish to
trust others? I have no idea how the Linux kernel works.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧═══════════════════════════════════════════════════════════┴───────────┘
--- #20 messages/455 ---
═════════════════════════════════════════════════──────────────────────────────────
I don't understand why modern software isn't error correcting. We shouldn't
have any bugs in this day and age.
For example, if you're missing a dependency then why doesn't your program try
to, I dunno, download that dependency to the program's installation directory
and use it there? Seriously there are very few problems that are unsolvable!
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧══════════════════════════════════════─────────────────────┴───────────┘
--- #21 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 │
╘═════════╧════════════════════════════════───────────────────────────┴───────────┘
--- #22 fediverse_boost/150 ---
◀═╦════════════════════[BOOST]══════════════════════─────────────────────────────┐
║ ┌──────────────────────────────────────────────────────────────────────────┐ │
║ │ i think my complaints about rust really boil down to “i know what im │ │
║ │ doing and this language is designed for people who don’t” │ │
║ └──────────────────────────────────────────────────────────────────────────┘ │
╠─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧═══════════════════════════════════════─────────────────┴───────────┴─▶
--- #23 fediverse/3543 ---
════════════════════════════════════════════════════───────────────────────────────
@user-777
my favorite thing about specialization is that not everyone has to do
everything
(translate *that* into C lmao)
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧═════════════════════════════════════════──────────────────┴───────────┘
--- #24 fediverse/1960 ---
═════════════════════════════════════════════════──────────────────────────────────
Source code is like, the worst way to view code, but I can't think of anything
better, so whatever
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧══════════════════════════════════════─────────────────────┴───────────┘
--- #25 fediverse/5684 ---
image.png
══════════════════════════════════════════════════════════════════─────────────────
"stack overflow" just means "oops I ran out of ram"
ram is just how much you can keep in your working memory at one time.
like, multitasking, where you have to keep track of juggling several balls or
plates.
if things are too easy, it's normal to get bored.
if things are too hard, collapse at your leisure.
"stack overflow" is just when the things that I'm building correlations and
implication charts of in my mind are too large and require too much affection
to explain for my regular human sized brain and I drop one of the balls and go
grab and fix it, or drop one of the plates and feel sorrow forevermore. yep,
right in the trash bin. along with everything else.
damn... there was hundreds of thousands of jewels of hoard there. if only I
could displace that bit of space... I bet she'd find it once more.
*cursed artifacts be like*
"stack was large enough to contain the flow" is just when the provided space
was just enough space. which is rare, because most thoughts reverse all over
the place.
"*easy*"
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧═══════════════════════════════════════════════════════────┴───────────┘
--- #26 fediverse/3396 ---
╔═══════════════════════════════════════════════════───────────────────────────────┐
║ you should only use variables for things that are user-configurable. │
║ │
║ everything else should be hard-coded, with a clear and coherent reasoning │
║ stored in the documentation, with git-style revisions included and easily │
║ browsable. │
║ │
║ (what if you want to tweak a value somewhere? you'd have to update it on every │
║ single page!) │
║ │
║ true. maybe we could set aside a section of memory to store a value and then │
║ just point to it using a label. That way we could always keep our values │
║ hardcoded, but also be able to find them easier. │
║ │
║ [tweak them, not find them] │
║ │
║ ... yah okay fine both would technically work │
║ │
║ [yes but one of them is not a good timeline to lead the world down.] │
║ │
║ ?..?...?....?..... -.- ...... /shrug ....... ...? │
║ │
║ "bruh why is she reinventing variables" │
║ │
║ she's learning give her time │
║ │
║ ... did you hear a doctor diagnosed her finally │
║ │
║ "whaaat what'd they give her" │
║ │
║ they said it was "schizotypal" │
║ │
║ "... did she forget a symptom or three?" │
║ │
║ no dude thats one of the bad ones │
║ │
║ "oh right. I heard typical" │
║ │
║ yeah so anyway │
╠═════════╗ ┌───────────┤
║ similar ║ chronological │ different │
╚═════════╩════════════════════════════════════════────────────────────┴───────────┘
--- #27 fediverse/6169 ---
══════════════════════════════════════════════════════════════════════─────────────
┌──────────────────────┐
│ CW: AI-mentioned │
└──────────────────────┘
AI programming be like:
"hmmm, it seems that there is an error. Let me try disabling the error and
seeing if that fixed it. Perfect! The program runs without crashing. Here's a
summary of what I accomplished:"
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧═══════════════════════════════════════════════════════════┴───────────┘
--- #28 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 │
╘═════════╧═════════════════════════════════════════──────────────────┴───────────┘
--- #29 messages/365 ---
════════════════════════════════════════════════───────────────────────────────────
Programmers should treat LLMs more like a different type of "if" statement
rather than a UI element
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧═════════════════════════════════════──────────────────────┴───────────┘
--- #30 fediverse/5839 ---
════════════════════════════════════════════════════════════════════───────────────
@user-1074
good code isn't always easily read. sometimes the architecture is more
important.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧═════════════════════════════════════════════════════════──┴───────────┘
--- #31 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 │
╘═════════╧═══════════════════════════════════════════────────────────┴───────────┘
--- #32 fediverse/3800 ---
════════════════════════════════════════════════════───────────────────────────────
@user-1352
You're absolutely right, the compiler knows better than me! Certainly the
compiler doesn't know *best*, but certainly the compiler knows *better than
me*.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧═════════════════════════════════════════──────────────────┴───────────┘
--- #33 fediverse/5783 ---
╔══════════════════════════════════════════════════════════════════────────────────┐
║ I think our industry should work on one project at a time │
║ │
║ "do one thing and do it well" │
║ │
║ linux users code. │
║ │
║ everyone backends ffmpeg. │
║ │
║ everyone online uses chrome. │
║ │
║ what if we just rewrote every single program and... left it without updates in │
║ a "permanently forbidden" zone │
║ │
║ ... I mean what if we wrote non-proprietary alternatives to every proprietary │
║ source of computational knowledge and then we could only patch security │
║ vulnerabilities and compatibility change-bounties [oh no now you're allowing │
║ for endless levels of abstraction [meaning, operating system package │
║ installation bloat] and distasteractions.] │
║ │
║ the futures where all is not well nearly outnumber the well. but the inverse │
║ is also true, for they are divided roughly equal fifty. balance, in all │
║ things, is the only temperate state. when balance is │
║ [changed/something/uplifted], balance is inevitable to be search-shifted. │
║ │
║ why must you die for an audience? │
║ why │
║ │
║ ... I don't really want to, but what happens happens. we'll see if it's a for │
║ sure dealing. │
╠═════════╗ ┌───────────┤
║ similar ║ chronological │ different │
╚═════════╩═══════════════════════════════════════════════════════─────┴───────────┘
|