=== ANCHOR POEM ===
╔════════════════════════════════════════════════════════──────────────────────────┐
║ @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 │
╚═════════╧═════════════════════════════════════════════───────────────┴──────────┘
=== SIMILARITY RANKED ===
--- #1 fediverse/3805 ---
═════════════════════════════════════════════════════════──────────────────────────
neat
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════════════════─────────────────────────┘
--- #2 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 │
╚═════════╧════════════════════════════════════────────────────────────┴──────────┘
--- #3 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 │
╘═════════╧╧══════════════════════════════════════════════════─────────────────────────┘
--- #4 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 │
╘═════════╧╧═════════════════════════════════════════════════════════════──────────────┘
--- #5 fediverse/6317 ---
═════════════════════════════════════════════════════════════════════════════──────
┌──────────────────────┐
│ 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 │
╘═════════╧╧══════════════════════════════════════════════════════════════════════─────┘
--- #6 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 │
╘═════════╧╧════════════════════════════════════════════════════════════───────────────┘
--- #7 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 │
╚═════════╧═════════════════════════════════───────────────────────────┴──────────┘
--- #8 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 │
╚═════════╧════════════════════════════════════════════════════────────┴──────────┘
--- #9 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 │
╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘
--- #10 fediverse/707 ---
══════════════════════════════════════════════─────────────────────────────────────
@user-524
Sometimes when I feel overwhelmed with all the boilerplate I just start coding
and making stuff. Doesn't matter if it works, doesn't matter if it says /*
FIXME */ all over the place, doesn't matter if it includes header files that
don't exist yet, as long as you're hacking out the mechanics of whatever
operations you need to perform then you can figure the rest of that stuff out
later. The creative urge doesn't last forever, which is why projects get
abandoned, but with discipline you can keep bringing yourself back to fix all
the /* FIXME */'s and the compiler errors.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════────────────────────────────────────┘
--- #11 fediverse/1204 ---
╔═══════════════════════════════════════════════───────────────────────────────────┐
║ @user-883 │
║ │
║ the future is what we make for ourselves. │
║ │
║ there are endless problems to solve, yet hardly anyone around to fix them. │
║ │
║ If only we had a small group of people who could organize and say "hey. I need │
║ someone to solve this particular problem" to a large group of people with │
║ nothing to do and no bills to pay, I feel like we could get a lot done. │
║ │
║ alas, the problems that need solving are too specific and complex. Almost by │
║ design, they've stripped us our capabilities to address the difficulties they │
║ hoisted upon us. Alas! That we should be so morassed. But time and again our │
║ ingenuity compels us. │
║ │
║ I dream of a world where people like you and I have a purpose, something we │
║ can apply ourselves to and eventually overcome. I subscribe to "grand │
║ narratives", but frankly they're only of my own design. Does that make them │
║ any less grand? I think not. │
║ │
║ If I knew enough people perhaps I could be like that. I could direct and │
║ organize and administer and manage and apply our guys. But alas I am just a │
║ noob sigh. │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧════════════════════════════════════────────────────────────┴──────────┘
--- #12 fediverse/1526 ---
═════════════════════════════════════════════════──────────────────────────────────
"employee of the month" but like, not per month. per project. "here is our
foremost, help them as much as you can" like, a hero. or champion. or tech
lead.
they don't have to be expertly competent, their job is to learn and apply
themselves as best they can.
Then, after this project, they can go into a pool with all the other tech lead
hero champions, and then they can work on something more powerful. The process
repeats, until you have a CEO or three.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════════─────────────────────────────────┘
--- #13 fediverse/5478 ---
╔═════════════════════════════════════════════════════════════════════─────────────┐
║ you won't get far with a "community" of dedicated people │
║ │
║ what you need are teams. who can trust each other. you build them through │
║ brotherhood, and you trust them from their results. │
║ │
║ for example if you wanted to organize a grouping or get-together, you'd put a │
║ bunch of people in a room or seven and let them while they're there work on a │
║ plan or a decision. │
║ │
║ who needs tabling? who needs the chance to speak? just let them socialize and │
║ say "hey guys here's where you'll plan" │
║ │
║ [uh no officer we were just playing board games] │
║ │
║ plans are hard without material so make sure you always prepare a pricetag on │
║ each plan you produce. │
║ │
║ keep it for reference. make sure you note all the requirements. the location │
║ is often the least important part. │
║ │
║ "what the hell man you can't just say stuff like that as if it'd work" │
║ │
║ yep, I, uh, am a passenger in life just the same as you. And I only write down │
║ what I want to. │
║ │
║ you could show me anything on the internet and I'd believe it. Facts aren't │
║ important to me because I "forget" │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧══════════════════════════════════════════════════════════──┴──────────┘
--- #14 notes/open-source-flaws ---
═════════──────────────────────────────────────────────────────────────────────────
the flaw with open source software is also it's greatest strength.
it is open, so it can be observed by practically unlimited perspectives.
however, it lacks follow-through. a larger, more concerted effort, can often
bring greater and more efficient results.
the trick is in the balancing, and ideally you'll never falter -
but it's best when you all get along.
new ideas, new frames of mind, and more of us kept together.
if one splinters off, the rest are at fault,
and you don't want to lose your finger
so why fight at all? why not focus on our own times? and then together we are
one
in sight of our homes, is when we're most alarmed, because houses are not for
your homeless
yet together they might
have strength for the fight
that ever bears down on our shoulders
x x x x x x x x x x x x x x x x x x x
x x x x x x x x x x x x x x x x x x x
x x x x x x x x x x x x x x x x x x x
x x x x x x x x x x x x x x x x x x x
x x x x x x x x x x x x x x x x x x x
There was something else, but I can't remember. Something about open source
software that was important enough to get me to write this note. Somewhere
along the first line I lost it, or rather felt I needed more context, and
then when the context was finished the original intent was lost. It's hard
because when I go for the conclusion first and justify it with context,
then the conclusion doesn't make sense and the context meanders. I'll try
harder next time. These notes are my life's work.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘════════─┴╧══─────────────────────────────────────────────────────────────────────────┘
--- #15 fediverse/434 ---
═════════════════════════════════════════════──────────────────────────────────────
@user-324 @user-325 @user-326
thus enters the promise of technology: that we might solve the problems of
bureaucracy once and for all by ever more effiency-aligning mechanical
processes that produce effects which we desire - such as efficient allocation
of medical resources such that all of humanity is protected from the ravages
of pain and the incongruencies of our nature.
Alas, that we should only conceive of success through the lens of profit.
Perhaps another design is in order?
(oh yeah also people who are in control are worried that we, like all other
examples of natural entities, might immediately proceed to breed beyond the
capability to cater to the needs of said entity (such as "to feed" and medical
resources) and therefore might overburden (and therefore destroy) said system
which allows for their sustenance and initial creation. To this I say... Yeah
probs, what should we do about it?)
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘
--- #16 fediverse/5001 ---
══════════════════════════════════════════════════════════════════─────────────────
┌───────────────────────┐
│ CW: systems-mentioned │
└───────────────────────┘
"we'll figure out how it works after we push to prod"
yeah okay point taken.
How about this:
for every large decision, write a little essay about why you made the choice
that you did.
Observe, Orient, Decide, Act, Explain. OODAX : )
Make sure you connect your goal to one or more of these three colors:
red : people
green : places
blue : things
and then explain which numbers you're going to gather to determine whether or
not it worked.
If someone has a problem with your choice, show them the essay, and let them
write an essay of their own.
If they still have a problem, then let someone you both respect decide which
one to use.
It's not perfect, but it's not meant to be. Make something better and easier,
I dare ya.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════────────────────┘
--- #17 fediverse/2293 ---
══════════════════════════════════════════════════════─────────────────────────────
┌────────────────────────────┐
│ CW: re: politics-mentioned │
└────────────────────────────┘
@user-1218
true, which is why such an idea should be more than a formality, more than a
technicality, and closer to a schedule or event-driven system.
"Well, the duration on this-or-that project elapsed, and the team assigned to
study it has produced these scientific results. Look on page 7 there's a
pretty cool graph! What should we try next, to compare with what we just
tried?"
repeat until we all decide that one of the methods we tried was the best, then
re-implement that one if necessary and mark it as "long-term"
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════────────────────────────────┘
--- #18 fediverse/4147 ---
═══════════════════════════════════════════════════════════────────────────────────
a messaging app where you only had a limited amount of X/Y space to pin sticky
notes so you had to delete stuff bit by bit.
trick is... you can only delete things that your conversation partner picks.
and you have to share the space, so... if one person is overwhelmed or working
on other stuff, eventually there comes a ceiling where you can't work together
on a project anymore.
A tool like this would essentially alert them to this, because you would run
out of places to put your produced [work-value but pronounced as "harms/worms"
for some reason]
plus that way you can say "yep I got that covered" as in, I'll be the next one
to post about this. Hence I'm grabbing this post-it and putting it on my
board. work work work work okay here's that post-it back, but I added a little
more specs to it. Ah but you're out of room, only got 333 characters
remaining, here I'll keep it on my board until you're through with whatever it
is that you do
oh? you want to prioritize me and my productions? okay I'm listening..
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════════───────────────────────┘
--- #19 fediverse/2118 ---
═════════════════════════════════════════════════════──────────────────────────────
listen, judges are useful character moralities, but they don't have to be the
only ones to decide things.
I mean, if they disagree, then let the one who cares the most about it have
the decision-making power.
if you do this equally for everything, then everyone will get what they want.
so, like, if you care about something, then believe in it.
if it's truly good, then more people will come to it, and it'll naturally
extinguish (with care and love) the least favored approach, which... honestly
now that I think of it is not such a good approach either.
the reason I say that is because it's good to be multi-faceted, and to have
general flows and rough surfaces.
These are places people can hold onto you, the times when you're trying your
mostest.
y'know, your tough patches. the things that are difficult in your life.
the stuff you're working on can push you forward,
if you only had someone to play catch with.
or like, send letters to.
or shared encryption keys.
I don't know anyone. Well, maybe o
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════════════─────────────────────────────┘
--- #20 fediverse/4020 ---
╔══════════════════════════════════════════════════════════────────────────────────┐
║ if computers were sane, IT technicians would act like secretaries who wandered │
║ around in a company and improved their QoL and access to new features │
║ according to their needs, skillset, and personal way of working. │
║ │
║ for example... │
║ │
║ do they like typing, or would they rather use a mouse, │
║ │
║ are they more visual with graphs or textual like a piece of math │
║ │
║ what needs do they have, what here could be automated │
║ │
║ do they like the cupboards and drapes, we can switch out the profile and the │
║ theme... oh, no, yeah I guess you're right it doesn't matter. [changes it │
║ every week] [then a long time down the line when she finally leaves the │
║ company, a few people begin to wonder - didn't the colors in outlook change │
║ every week or so?] │
║ │
║ but alas, computers are not sane, meaning we're more like firemen rushing from │
║ scene to scene. │
║ │
║ "can you put that in the ticket?" │
║ "I heard you can help with this-or-that thing" │
║ "did you hear back from corporate?" │
║ "oh that's good to hear! So, next Tuesday? │
║ "Hold on, I heard it was such-and-such" │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧═══════════════════════════════════════════════─────────────┴──────────┘
|