=== ANCHOR POEM === ══════════════════════════════════════════════════───────────────────────────────── The difference between front-end and back-end programming is whether or not you want to design abstractions or use them. Backend is all about creating abstract things that are networked together, while front end is about putting them together in a way that suits the user. Front end is collage, back end is pencil drawing. ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧═══════════════════════════════════════════────────────────────────────────┘ === SIMILARITY RANKED === --- #1 fediverse/5247 --- ════════════════════════════════════════════════════════════════════─────────────── the hardest problem in computer science is figuring out why users do what they do. ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧═════════════════════════════════════════════════════════════──────────────┘ --- #2 fediverse/617 --- ═════════════════════════════════════════════────────────────────────────────────── So much of computing is just... handling the quirks of hardware and presenting it to the user (programmer) in a way that is sane and makes sense, instead of the arcane and [nebulous/confabulous/incomprehensible] way that physical nature demands our absurdly potentialized computational endeavors be. ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘ --- #3 fediverse/6015 --- ══════════════════════════════════════════════════════════════════════════───────── ┌──────────────────────┐ │ CW: AI-mentioned │ └──────────────────────┘ In 2025, if you want to create a piece of software your options are to either: devote your life to it, or use AI to build a semi-working prototype that you can use to pitch your idea to a bunch of people who have devoted their lives to learning how to use your idea as documentation while they build it from scratch, throwing out most of the code but keeping all the checklists and progress-trackers you built along the way, perhaps even utilizing some of your tooling that you used while constructing the scaffolding of this monstrous application that you won't be using most of the source-code for. ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧═══════════════════════════════════════════════════════════════════────────┘ --- #4 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 │ ╘═════════╧╧════════════════════════════════════════════════───────────────────────────┘ --- #5 messages/1159 --- ════════════════════════════════════════════════════════════════════════════════─── claude-code can make whatever kind of front-end you want. all you have to do is leverage scale and give everyone a moment to do what they want. then, the computer becomes scientifically self-aware. (do you expect anything less from a machine?) cultural bias damage (we all gotta work through our origin stories, here's one we crafted for you) ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧═════════════════════════════════════════════════════════════════════════──┘ --- #6 fediverse/633 --- ═════════════════════════════════════════════────────────────────────────────────── @user-192 the neat thing about BASH is that it's the glue that holds all your other code together. Write libraries in C and call them with BASH - accomplish broader tasks that are easier to co-create. That's why I like it - it's not the most important, but it's quite beneficial I think _^ ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘ --- #7 messages/127 --- ═════════════════════════════════════════════────────────────────────────────────── All I want for my mobile computing is the ability to use the interface of android to access resources and perform tasks that are relevant to my primary computer. Like, a mainframe with the phone as a terminal. Except instead of text, it's buttons and sliders and all the things that mobile UI experts have spent so much time carefully crafting. ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘ --- #8 fediverse/5442 --- ══════════════════════════════════════════════════════════════════════───────────── @user-1839 the trick is to just make it and point people toward it as if it's supposed to be there. ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧═══════════════════════════════════════════════════════════════────────────┘ --- #9 fediverse_boost/4174 --- ◀─╔═══════════════════════[BOOST]═════════════════════════───────────────────────╗ ║ ┌────────────────────────────────────────────────────────────────────────────┐ ║ ║ │ the belief that the world consists of discrete 'objects', rather than regarding it as an undifferentiated field of matter to which we can attach various framings, is a widespread mental limitation │ ║ ║ └────────────────────────────────────────────────────────────────────────────┘ ║ ╠─────────┐ ┌───────────╣ ║ similar │ chronological │ different ║ ╚═════════╧═════════════════════════════════════════════───────────────┴───────╝─▶ --- #10 fediverse/4527 --- ════════════════════════════════════════════════════════════─────────────────────── @user-1600 Yes! The ease of use for GPU programming is lovely. Like I said all I need is a use-case, I've downloaded as much reference material as I think I'd need to be able to hack together something fairly quickly if I needed it. That's all I have the mind-space to focus on lately haha ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧═════════════════════════════════════════════════════──────────────────────┘ --- #11 fediverse/4118 --- ═══════════════════════════════════════════════════════════──────────────────────── all modern software should be written in a multithreaded way, change my mind ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧════════════════════════════════════════════════════───────────────────────┘ --- #12 fediverse/1168 --- ═══════════════════════════════════════════════──────────────────────────────────── shitty AI products are a classic case of the engineers designing something really cool with specific use-cases and then the "higher ups" getting dollar signs for their eyes and deciding that every hammer is suddenly a nail and that we should pull out all the screws that held the building together and replace them with hammer shaped nails no I will not elaborate I think I made myself clear : ) ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘ --- #13 fediverse/1810 --- ═════════════════════════════════════════════════════────────────────────────────── some people hear words like "datastructures" and "object-oriented programming" and think they're made up terms that don't mean anything important. ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧══════════════════════════════════════════════─────────────────────────────┘ --- #14 messages/1230 --- ═════════════════════════════════════════════════════════════════════════════════── The machine cult is just when everyone's job is building and maintaining the computer. ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧══════════════════════════════════════════════════════════════════════════─┘ --- #15 messages/527 --- ═════════════════════════════════════════════════════════────────────────────────── could give us some experience organizing small, short-term projects to accomplish specific goals and tasks in an ad-hoc way that relied less upon procedure and more on "I think so-and-so knows something about that, they were looking into those files and posted a breakdown of how they work yesterday" ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧══════════════════════════════════════════════════─────────────────────────┘ --- #16 messages/110 --- ═════════════════════════════════════════════────────────────────────────────────── The best way to program computers is to organize them according to their relations. Like, when x increases by 4 then y increases by 2 - basically, a math equation that you can continuously solve by calculating more and more comprehensively and deeply. ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘ --- #17 fediverse/5212 --- ════════════════════════════════════════════════════════════════════─────────────── the reason you start with a game engine is because then you'll have tools to make however-many games you want. Tools that you know intimately enough that you can debug and improve them without breaking your creative flow by learning something new halfway through a project the whole point of individualized projects instead of viewing each computer as a complete and total whole (why do we need servers again?) is that you can paint a picture of where the design of the program is intended to go, such that all the considerations are in place and whatever issues or struggles you might face along the way are adequately addresssed, -- stack overflow -- [because I mistyped addressed] -- -- if you know what "stack overflow" means you have intimate knowledge of the technology, and can probably guess what it means in context when I say it. "nuts I lost that train of thoguht" -- stackl ov ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧═════════════════════════════════════════════════════════════──────────────┘ --- #18 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 │ ╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘ --- #19 fediverse/2475 --- ══════════════════════════════════════════════════════───────────────────────────── If you want to design a society, first learn how to build a decentralized scalable multiprocessor computer program. It could literally flip bits, the point is to practice architecture not accomplish a goal. ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧═══════════════════════════════════════════════────────────────────────────┘ --- #20 fediverse/2423 --- ══════════════════════════════════════════════════════───────────────────────────── does anyone know of any fedi software that lets you link to a particular post and read forward on a person's timeline from there? Or back I guess, but chronological viewing specifically. ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧═══════════════════════════════════════════════────────────────────────────┘ |