=== ANCHOR POEM === ═════════════════════════════════════════════════════════════════════════════────── ┌──────────────────────┐ │ CW: SWE~ │ └──────────────────────┘ what if game designers auto-generated a source-code fork with whatever changes the users requested be implemented [software developers too, when working on software for tabular related scrudm based server space] I bet they could if they used AI to pump out bugfixes. The more they worked on it, the more the people demanding they work on that project in particular by proposing a customization request form attached to an itinerary and invoice. the user is free to work on them in whatever order they wish and the developer and the users compete for contracts. "like uber but for source code" click here: ---> ||"meetup.org but for uber but for source code"|| "ah this unit is too punchy, let's buff one of their shields" okay but rocket launchers "oh no my tank is ruined" hey it's okay it's just sugar ... I wonder if anyone's ever inhaled vaporized sugar crystals? the baker's dozen is 13 because bakers are spellbound lucky T.T [for context, it's always nice to have found another one in your bags by the car] ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧══════════════════════════════════════════════════════════════════════─────┘ === SIMILARITY RANKED === --- #1 fediverse/3804 --- ╔════════════════════════════════════════════════════════──────────────────────────┐ ║ @user-570 │ ║ │ ║ well, the idea is that they would handle all the tech debt and merge requests │ ║ and bugfixes and such - the kind of things that aren't very interesting to │ ║ work on. That way, the people who are most dedicated and passionate for the │ ║ project have a way to clear out their backlog and start as if from scratch. │ ║ │ ║ Plus, if they later don't understand how or why something was implemented, │ ║ they could always message the person who implemented it and say "hey why did │ ║ you do it this way I had it this other way before" and then they could reply │ ║ and say "oh yeah because of this-and-this system we implemented for │ ║ these-or-that caching reasons related to integer flow through the syncretic │ ║ binary op-code delimiter" and then actually wait no maybe you're right, I see │ ║ what you mean │ ║ │ ║ well... they don't have to merge everything if they don't want to. They could │ ║ just... ignore the parts that people worked on that they don't want to include │ ║ in the project. I'm thinking it'd be an opt-in thing too, so someone could │ ║ request it! │ ╟─────────┐ ┌───────────┤ ║ similar │ chronological │ different │ ╚═════════╧═════════════════════════════════════════════───────────────┴──────────┘ --- #2 fediverse/364 --- ╔════════════════════════════════════════════──────────────────────────────────────┐ ║ okay here's an idea, waterfall project management where the program is │ ║ developed one tiny piece at a time while being streamed to the entire company. │ ║ Everyone would submit answers which could be upvoted / patched / rewritten as │ ║ the main viewer cycles through each aspect of the project, checking for │ ║ updates to it's design that were suggested by developers or whatever. │ ║ Basically, one person (or one team) gets to write the actual source code, │ ║ while everyone else is just offering suggestions. You could break it up by │ ║ specialty, but the whole point is that everyone gets a complete picture of how │ ║ the program (and organization) is structured. Which should give the employees │ ║ more power to generate value for the company. All around a good deal I think? │ ║ Especially if the main viewer took time to explain each and every part so that │ ║ every viewer had the chance to understand. │ ║ │ ║ the reason why order is important is that our actions ripple through eternity. │ ║ we must set a good example for all the baby aliens, don't you think? │ ╟─────────┐ ┌───────────┤ ║ similar │ chronological │ different │ ╚═════════╧═════════════════════════════════───────────────────────────┴──────────┘ --- #3 fediverse/927 --- ═══════════════════════════════════════════════──────────────────────────────────── @user-638 kinda makes me wish we treated software design more like a science open source by default, working together to create understandings about how to best process information, incorporating the needs and desires of multiple different fields / types of person, creating useful conclusions or programs that people can use for their own enrichment or benefit, and oh wait funded and directed by people who don't care about the technology/science and instead just want results I feel like we'd learn a lot more in our CS degrees if we were tasked with making open source projects. Then maybe professors (or other people doing research) could show us and explain why we're doing things right / wrong. And if we were encouraged to use our peer's tools, then we could work together to design a team. Museums are great because you can meet other people who are also interested in history/biology/ecology/anthropology/science/art/any-other-type-of-civic-good-y ou-can-think-of/ ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘ --- #4 fediverse/5065 --- ═══════════════════════════════════════════════════════════════════──────────────── ┌────────────────────────────────────────────┐ │ CW: strange-ideas-about-software-mentioned │ └────────────────────────────────────────────┘ software should have 3, maybe 4 or 5 maintained releases imo for adding security improvements and whatnot then people wouldn't complain about updates because they wouldn't feel like they were being left behind (after expressing their differences (of opinion and such)) I think that'd uh maintain them as, I guess, userbase optics parallelograms? oh sorry we're on rhomboids this week - right, and no I won't forget the differences in creed, all things are received equally...d. uh-huh yeah no that makes sense. gotcha. okay see you at the location. have fun with your demarketion. what if we played games with swords but like, the peril of steam is that you can't decline to update. meaning if a corporation wants to break an old game and it's collectively hosted servers... all it has to do is push an update that disables them. suddenly nobody has room to do, and the whole -- stack overflow -- ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧════════════════════════════════════════════════════════════───────────────┘ --- #5 fediverse/3802 --- ═════════════════════════════════════════════════════════────────────────────────── what if we got together and adopted a new open source project every month and just collectively worked around the clock to learn and work through the important problems facing it or even like, cleared out the backlog of stupid pointless boring tasks that would allow the developers to work on something better call it the wandering parade of development 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 │ ╘═════════╧╧══════════════════════════════════════════════════─────────────────────────┘ --- #6 notes/emotional-computing --- ═══════════════════════════════════──────────────────────────────────────────────── Okay I gotta go write some w7 but picture this: A computer program that emits emotions during it's computing. Like "oh boy this process is going great!" and sends that into a giant word cloud that represents the entire program. Wait, scratch that, it's slowly filtered up through successive layers that provide detail to different *parts* of a program. Like "Oh the image generation is going great but it looks like the garbage collector is getting bogged down" - this could provide lots of useful information that an AI language model could sift through and filter into a batch of actually useful information. Think of it like this - stuff as much context into the LLM's memory buffer and say "summarize this in the same style. Make emphasis when necessary." the LLM could process all that data and it could be filtered up until there's no unprocessed data and then it could be given to the user in the form of a report or dashboard or something. BOOM AI PRODUCTIVITY. The user will ask the AI to increase certain variables, and it'll filter BACK DOWN THE CHAIN through the same exact process (just backwards) this time) and then individual components will know how to behave. Like imagine if your arms knew you were mad. They'd be much more likely to punch stuff right? Or imagine if your legs knew you were scared. They'd probably try and run as fast as they fucking can. There's an evolutionary reason why this kind of technology would be useful, which means it's likely that it's part of our genetic code. I mean, we have nothing to disprove it, but it's as good an idea as any. ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧════════════════════════════───────────────────────────────────────────────┘ --- #7 fediverse/6107 --- ═══════════════════════════════════════════════════════════════════════════──────── commanding a coding agent to write bash is a lot different than telling it to write a systems analysize. one is "hey can you examine this repository and make a note somewhere on a todo-list or whatever that there needs to be a bugfix in relation to the options setting input translation recommendation algorithm matchbox field because when I click on it the program crashes" and the other is like "okay now put the box over there. great now drag it a little bit closer. okay now take the refluxinator and adjust the bamboozlewhap to account of brass-terminatrix-incorporated and strip out the question-mark-eyes" wait actually neither of them is like that okay the bash one is like: "okay yeah do it. sure. yeah okay. yes, but we should put them at this location: [loc]. ummm it still has this error message. it still says the same error. okay now it says this, I don't think it's gonna work so let's try this other thing." ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧════════════════════════════════════════════════════════════════════───────┘ --- #8 fediverse/2754 --- ══════════════════════════════════════════════════════───────────────────────────── ┌────────────────────────┐ │ CW: is-that-rude??-wha │ └────────────────────────┘ AI engineers only ask users for prompts because they don't have any ideas of their own i'm a programmer, I think of AI like a tool, like a for loop or something. it's trivial to script together a local LLM that can process your stuff 1s slower every time you click the mouse, but like... who cares, right? everybody needs a chatbot... then they plan to script together a computer system that operates just like a corporation and it's like... no way, now there's something that can compete. and they don't know how to implement it. (but they're working on it) like, think about the absolute most automated Microsoft Teams or Discord could be. there's SO MUCH of your text-based information that they could process ANYTHING. well, anything that's been performed before. there'll still be a need for people, who actually apply the things they've learned. and -- stack overflow -- alt text that has a list of attributes that are poster-selected that can be described one-by-one (to paint a picture) ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧═══════════════════════════════════════════════────────────────────────────┘ --- #9 messages/1174 --- ════════════════════════════════════════════════════════════════════════════════─── if you're afraid of the AI bubble popping, one way to avoid it is to pop it ourselves. If we build AI technology that eclipses the entire software development ecosystem, companies might start to be valued based on the value of the employees they've managed to collect. Not fame and fortune, but by those that can build the best applications, on demand[, for free. paid for by nationalized taxes.]. the companies that can hold onto the best engineers, those that know how computers work and can know how they function, can leverage their human capital to achieve great means. essentially, inversing the power dynamic, where workers are favored for their plenty and not for their worth. let the code monkeys tend to their gardens and work their sawmills. We all know they'd rather be teaching kids about plants or playing cards at the grocery. Let the computer nerds, the ones who are really into it, let them make what they feel is worth it for it [the computer]. this will have massive effects on the economy, and none of it will be reflected in new jobs. But we'll all be happier, and we'll all find less stress in our [confines/compromises]. But it's gotta work, first. And it's gotta be locally spendable. If they wanna put a data server in the library, why not let them fund it themselves? They could run powerful statistical models that output useful statistics arranged in human readable and not very statistical ways, and that's a pretty neat infinite information machine to have at your disposal as a library. It could even cite sources (and validate!!) them for students or returning listeners. Plus, if nobody's using it, it could work through the backlog of user requests and act as a "slow" or "unexpected deliver times" style queue for their LLM requests - average wait time less than 1/5th of a minute. for something that can program an entire computer for you, from scratch. If you can describe it, it can make it, so long as you're willing to test out all of it's hacks. I bet we could make one for less than 20,000$. Might need some new chip foundries, might need to forge some new trade deals, let's let both of our wing-arms decide. the value of one currency compared to the other should be a measure of how valuable the goods that country exports are. And yet, it's more often a matter of distribution, as we all visit our local bazaars. What happens when that's all digital? if nobody's a shining city on a hill, then there's no nuclear war. Who would nuke Somalia? Nigeria? Botswana? Idaho? ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧═════════════════════════════════════════════════════════════════════════──┘ --- #10 fediverse/4596 --- ═════════════════════════════════════════════════════════════────────────────────── @user-1707 hey, I'm working on a project. Might need some python, I tend to prefer Lua but it's pretty similar. It uses fediverse software and cheap hardware, think raspberry pi's except risc-v also it might use distributed local LLMs not to generate text, that's garbo and lame and stupid. Instead it uses them to transform text, maybe even translate text, into a more summarized form. Intentionally losing data, like a jpeg compression but for text. Might need some python for that. To glue it all together. The "distributed" part is a whitelist, so we'd need to write that too. Various small little utilities like that for connectivity. oh also there's a one-way ethernet cable that connects two of the boards so we'd need to store some information (easy) and send some UDP packets (hard) anyway it's pretty neat, lmk if you want my contact details and I can tell you about it. I might even be able to pay you. (everything open source, no telemetry, no backdoors, everything private is encrypted, etc etc) ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧══════════════════════════════════════════════════════─────────────────────┘ --- #11 fediverse/4136 --- ╔══════════════════════════════════════════════════════════────────────────────────┐ ║ the kind of old people who post on mastodon because that's the best place to │ ║ do so too │ ║ │ ║ ... er I mean "gee wouldn't it be nice if our grandkids taught us how to host │ ║ our own mastodon server for our weekly poker night?" like how you have discord │ ║ servers for D&D groups, except, less proprietary and more freedom. │ ║ │ ║ I bet someone could make a lot of money by just loading a raspberry pi with │ ║ pre-built software built from an image that automatically hosted a mastodon │ ║ server just based on information about your networking company so they can │ ║ keep tabs on all that you do. │ ║ │ ║ gee sure would be nice if we had a government run computing infrastructure │ ║ project which turned the entire USA into a hive-mind computer. I bet you could │ ║ be paid pretty well to do processing in your own LLM-generated voice. │ ║ │ ║ like... feed it your published works, whether artistic or scientific, │ ║ alongside the breadth of human understanding... then optimize for temperature. │ ║ That which is most different. AKA the user's produced data and habits from IOT. │ ╟─────────┐ ┌───────────┤ ║ similar │ chronological │ different │ ╚═════════╧═══════════════════════════════════════════════─────────────┴──────────┘ --- #12 fediverse/1095 --- ╔═══════════════════════════════════════════════───────────────────────────────────┐ ║ ┌──────────────────────┐ │ ║ │ CW: not-a-profess │ │ ║ └──────────────────────┘ │ ║ │ ║ │ ║ One way to become involved in your passion projects is to contact them and say │ ║ "hey, if you ever want to do [idea about one of their products] let me know │ ║ because I want to be a part of it" │ ║ │ ║ maybe even y'know say it in a public place so people can see what we're all │ ║ interested in │ ║ │ ║ could make like, a forum for it, just like "hey here's my idea" and if enough │ ║ people like it then they can ALL be involved in a project to build it, │ ║ open-source style but funded collectively. │ ║ │ ║ like "hey I'll stick with my day job and maybe do some icons or something" and │ ║ in return their progress is supported. │ ║ │ ║ everyone's gotta pay rent, and if you work in the tech industry you tend to │ ║ have a lot of dollars. Could maybe design some ways to build products │ ║ collectively, ways that financially don't rely on charity. │ ║ │ ║ Idk I'd just like to work on a product that was designed to be as usable as │ ║ possible? Are there any companies out there doing that? │ ║ │ ║ [oh yes all of them silly me how could I forget how wonderful software can be] │ ╟─────────┐ ┌───────────┤ ║ similar │ chronological │ different │ ╚═════════╧════════════════════════════════════────────────────────────┴──────────┘ --- #13 fediverse/281 --- ╔═══════════════════════════════════════════───────────────────────────────────────┐ ║ ┌─────────────────────────────┐ │ ║ │ CW: cursed-game-engine-idea │ │ ║ └─────────────────────────────┘ │ ║ │ ║ │ ║ a game engine which won't let you import custom assets unless you complete a │ ║ few simple tasks using the interface - "build a green capsule collider" "make │ ║ this soldier unit shoot three bullets per shot" or "enable the automatic linux │ ║ support" - using the interface, writing some code, and changing configurations. │ ║ │ ║ why would anyone do this? well it could be useful to increase the difficulty │ ║ of importing external resources. plus it helps the user learn a bit over time, │ ║ and it slows the pace of output such that the user's skills are encouraged as │ ║ the output of the programming and not the program itself. │ ║ │ ║ an inverse curse (an evil one) would be where the requirements to complete │ ║ basic tasks are hidden behind unapplicable skills. like, do you know exactly │ ║ which buttons to press? engage with the skinner box, please. yes yes this is │ ║ what we need - unintuitive software that completely disarms the populace from │ ║ using them! suddenly they're worthless, and can't do anything on any surface. │ ║ it sucks │ ╟─────────┐ ┌───────────┤ ║ similar │ chronological │ different │ ╚═════════╧════════════════════════════════────────────────────────────┴──────────┘ --- #14 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 │ ╚═════════╧════════════════════════════════════════════════════────────┴──────────┘ --- #15 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 │ ╘═════════╧╧═══════════════════════════════════════════════════════════════════────────┘ --- #16 fediverse/4092 --- ═══════════════════════════════════════════════════════════──────────────────────── why not make a unified fediverse identity that can post on whatever instance it wants? ... hmmm could be accomplished with a layer of abstraction. You could use a "fediverse client" software to enter text into an HTML page which would have it's own UI and stuff and would organize your accounts and instances such that you could mark like, 3-7 as places you'd like to put a particular message. Then it would just... do it l m a o spam is gonna get sooooo much worse before it gets better but trust me, we'll figure it out. And it won't be long, either. It's a solvable problem, we just haven't built anything to handle it yet. ... yet... ┌─────────┐ ┌───────────┐ │ similar │ chronological │ different │ ╘═════════╧╧════════════════════════════════════════════════════───────────────────────┘ --- #17 fediverse/2056 --- ╔═════════════════════════════════════════════════════─────────────────────────────┐ ║ sometimes I think about how you can store number values in letters, in │ ║ addition to numbers. Like, ascii values for each word of your grandma's maiden │ ║ name. All you have to do is encode it, and suddenly "44 means something │ ║ different than Q" │ ║ │ ║ if I showed up at your place and used your username as a password to a public │ ║ key I'm showing you in my hand, would you trust me then? Would you trust if we │ ║ ran the simulation on your computer versus mine? Would you trust if I had │ ║ never told you I knew where you lived? │ ║ │ ║ ... probably, tbh, I'm desperate for adventure. Though I got some good things │ ║ going for me, so you'll have to convince me. (not the right attitude in an │ ║ election year, just saying) │ ║ │ ║ why are elections so perilous this is NOT what democracy is designed for │ ║ │ ║ when kids cry in preschool, they're sent to a different room (or put outside) │ ║ until they stop making noise and ruining it for others. That's just natural, │ ║ like "hey baby let's walk around the block while I bounce you on my shoulder │ ║ and hum calming music to │ ╟─────────┐ ┌───────────┤ ║ similar │ chronological │ different │ ╚═════════╧══════════════════════════════════════════──────────────────┴──────────┘ --- #18 fediverse/5911 --- ╔═════════════════════════════════════════════════════════════════════════─────────┐ ║ I was always fascinated by the Linux way of programming. Need to do something? │ ║ write it into a script! You never know when you'll need it again. Then, just │ ║ stay organized, religiously so, and understand that you will forget about │ ║ stuff. But, you'll come across it eventually, ready and willing and able to │ ║ help you. │ ║ │ ║ if you don't want me using AI, then give me ~20 junior developers. Which is │ ║ more efficient, do you think? │ ║ │ ║ "girl you haven't even tested your vibe-coded slop, how do you know if it │ ║ works" │ ║ │ ║ oh I'm sure it doesn't, but it's the thought that counts │ ║ │ ║ ... I guess I'm just saying, please don't burn the data centers. Computers are │ ║ not only bad for the environment when they're burnt, but also we can use them │ ║ for all kinds of neat things. Even if it takes a lot of energy, just... build │ ║ more solar panels and only use the computers for important stuff? │ ║ timeshare-style? │ ║ │ ║ \@/documents/books/man-and-the-computer.pdf │ ║ │ ║ that was my mother's book... I love her. I miss that side of her. She fled │ ║ when the cancer came. │ ╟─────────┐ ┌───────────┤ ║ similar │ chronological │ different │ ╚═════════╧════════════════════════════════════════════════════════════╧═─────────┘ --- #19 fediverse/2947 --- ╔══════════════════════════════════════════════════════────────────────────────────┐ ║ the downside of Proton and Lutris is now the ONLY games that work on Steam are │ ║ either continually updated (untenable) or playable on Lutris or Proton. Same │ ║ thing with Wine, though there's always at least one decent substitute. │ ║ │ ║ kinda makes me want to write a manager-style program which runs programs using │ ║ whichever version of their git repository would work best for their system / │ ║ configuration / purposes. Idk how I would start working on that though. │ ║ │ ║ I bet you could make one that acted like a shop, but where you didn't charge │ ║ any dollars. You could like... "swipe" through UI options, and pick whichever │ ║ felt most useful for your setup. Like, how some people use i3 and some use dwm │ ║ │ ║ with maybe inspectors that are modeled off of video-game style "options" GUIs │ ║ that mainly correspond to flags on the command/terminal line or compilation │ ║ flags │ ║ │ ║ I feel like that kind of abstraction would make it a lot easier for users to │ ║ adjust their system. they're noobs, after all. gotta show them all the choices │ ║ in one place... │ ╟─────────┐ ┌───────────┤ ║ similar │ chronological │ different │ ╚═════════╧═══════════════════════════════════════════─────────────────┴──────────┘ --- #20 fediverse/899 --- ╔══════════════════════════════════════════════────────────────────────────────────┐ ║ frankly I'm just excited to see what humanity does with the endlessly │ ║ calculated and stored blockchains. Like, that's a good set of pseudo-random │ ║ data, I wonder if we could build something off of it that wasn't exclusively │ ║ money? like, a necklace, I dunno. │ ║ │ ║ or like, a numbers station x2, where each message is accompanied with a │ ║ pre-calculated destination somewhere on this endless and │ ║ impossible-to-understand string of data. and that part is what seeds the next │ ║ code. once you start reading, certain numbers would be "flags" while others │ ║ would be "data" and they'd each have the same size on the hardware. that way, │ ║ they're impossible to predict. │ ║ │ ║ ah, but wouldn't it be noticable that certain results seem to appear next to │ ║ one another? well, isn't that just cryptology? Could probably be defeated if │ ║ you had an AI advanced enough, just saying. something that sorted through │ ║ massive mounds of data and gave you results in garbled or broken english. what │ ║ a wonderful tool, that's wonderfully mis-abused, perhaps in the fu │ ╟─────────┐ ┌───────────┤ ║ similar │ chronological │ different │ ╚═════════╧═══════════════════════════════════─────────────────────────┴──────────┘ |