@noelle can we do the opposite of this plan i think that would really help with inflation
@aescling time to pivot to ruby
« Protests were traditionally just one tool in activist campaigns to pressure governments, alongside back-room negotiations with political leaders or alliance-building with powerful actors. The use of social media, by channeling popular energy away from such organizing, means that mass protest is now often the only tool, and typically ineffective on its own. »
@noelle although the most severe concerns of https://youtu.be/hqwP6uuYOWo aren't applicable to non-fan creators, i agree generally with the take that the list of reasons to talk about a thing prematurely look something like
1. you need help finishing the thing
2. there is no reason 2
(actually there are some other reasons, like you want to teach people HOW you are doing the thing so they can follow in your footsteps, you want to give friends insight into your life, etc, but these are all decidedly non-promotional)
@noelle i think ideally you should never talk about it
as a creator, both (a) the time spent talking about the thing and (b) the positive feedback you receive about the thing sap your strength to actually finish the thing (both in terms of cost of engagement and because you inevitably start to derive fulfilment from “talking about the thing” instead of “doing the thing”, which is not a position which lends itself well to the thing getting done)
the ideal situation for someone making a thing is for OTHER PEOPLE to share it and talk about it without you having to say a word, so you can focus on your job, which is actually making the dang thing. in my opinion they will do that if:
- they can make cool things with your thing
- your thing enables them to better connect with others
- your thing enables them to complete important tasks
- your thing is impressive to them in some way
- your thing makes them feel emotions
- they are a fan of you or your previous work
unfortunately all of these cases except the last one require already having made a thing
i would much rather somebody take my code and extend it and then let me know, so that i could review the extensions and make my own determination on whether or how to incorporate them into the original codebase, than someone send me an MR
share recipes, share patches, write code you can use today and then use it
« With the implementation of the Belt and Road strategy, especially the launch of Chinese Language Resources Protection Project by the Ministry of Education and the State Language Commission in 2015, a strong impetus is given to the rescue and protection of minority languages. The Jinping dialect of the Dai languages was included in the 2015 language preservation project and the project was completed. This is the first time that this dialect has been approved as a special research project. In May 2019, with the support of the Jinping County Party Committee and the county government, the Jinping County Cultural Centre hosted the first Jinping Dai writing system standardization seminar, discussing the normalization, standardization and informatization of the Jinping Dai writing system. Experts from the Office of the Steering Committee for Ethnic Minority Languages in Yunnan Province, Yunnan Minzu University and other Dai experts and scholars from Honghe Prefecture reached a consensus on how to solve the problems of irregularities in Jinping Dai writing system and inconsistencies between the written and spoken languages, and initial results were achieved in the standardization process. »
not sure this will get accepted in its current state but i like it https://www.unicode.org/L2/L2022/22209-wuyue-zhenxing-tu-fu.pdf
and this all really comes down to good initial design and the longevity guarantees baked into javascript. maintenance costs are virtually nonexistent because of lightweight modular design and good OPP/duck typing practices, and a programming language with a rigid standardization process that never breaks old code
it's not even like a lot of code necessarily but even ignoring the vast size of my github archives the things i am actively piecing together over on gitlab are an awful lot of power for a system which has one user who is mostly coding things for her personal websites
the status.kibi.exposed version has a link https://status.kibi.exposed/topics/KibiSoftwareRelease/01838769-bea2-77f5-888a-733b993c7cf7
Administrator / Public Relations for GlitchCat. Not actually glitchy, nor a cat. I wrote the rules for this instance.
“Constitutionally incapable of not going hard” — @aescling
“Fedi Cassandra” – @Satsuma
I HAVE EXPERIENCE IN THINGS. YOU CAN JUST @ ME.
I work for a library but I post about Zelda fanfiction.