What's wrong with AI-generated docs https://buff.ly/xAp81oX
let me tell you what’s wrong with docs and docs sets entirely generated by LLMs.

What's wrong with AI-generated docs https://buff.ly/xAp81oX
let me tell you what’s wrong with docs and docs sets entirely generated by LLMs.
Yeah so once I connected a camera module to the #RaspberryPiZero and streamed video to my desktop through #UDP and watched it with #VLC. Good thing I documented absolutely NOTHING about that setup and now have to start from scratch even though I am tired and irritable.
Fuck!
Write shit down, folks. I highly recommend it!
L' #intelligenceartificielle est plus que jamais dans l'actualité, elle méritait bien un #VendrediLecture !
Des arts au marketing, de la philosophie aux sciences de l'éducation, nous vous proposons une sélection documentaire pour explorer le sujet.
#discord IS LITERALLY THE PROBLEM!
It's worse than any #IRC, #Mumble or even the old #TeamSpeak & #Skype for that matter.
It combines the disadvantages of #Forum, #paywalled #documentation, #chat and #voicechat with 0 redeeming qualities (unlike #Zulip & Mumble & #XMPP+#OMEMO) it's just an #InformationBlackhole!
I'm shure fecking #dread has better moderation and I'd rather use #MicrosoftTeams + #Slack cuz those at least have proper #moderation tools.
Case in point: I'd rather #SelfHost all my comms infrastructure than to ever use something like Discord or any other #GDPR-violating SaaS that is just enshittification.
I'd rather recommend people to instead choose a tool that does everything but horrible to go with multiple smaller & good tools
Check @alternativeto and @european_alternatives for options.
#BlueSpice 5.0 is here! Reach a new level in managing your #company #knowledge. Discover new #features like the automated #DeepL #translation or the editor for #BPMN #process diagrams.
Test BlueSpice 5.0 now in our online #demo:
https://en.demo.bluespice.com/wiki/
Overview of all new features at:
https://bluespice.com/bluespice-5-0-has-arrived/
Over the past couple of months, I've been spending more time reviewing my tech notes from the last five years.
Partially out of a new interest in posting publicly & also trying to improve my writing.
Despite my placing numerous reference links & quotes in these notes, I feel that I'm really blurring the line between plagiarism, absorbing concepts & re-writing them in my own words.
These notes continue to be useful. Just can't quite place the source. A new imposter syndrome.
Everytime I have to write "Yeah, about this button. it doesn't do anything. Don't click it. The developers didn't finish that feature in time but were too lazy to hide it before we shipped" I die a little bit inside. #TechnicalWriting #documentation
A lack of code documentation is killing new libraries.
Addendum: I was wrong!
Original Post:
@dalias @servo already the #documentation seems to be #AI #hallucinated garbage.
And yes, undocumented, buggy and inefficient code will be the result, even if we don't think IP would be an issue...
@ptrc if one can't be assed to #code and #document themselves, why should I use their #software or trust their #documentation???
Documentation complaints.
The Curse of Knowledge is real in documentation, even for some big and pricey ecosystems.
Two examples I ran into this morning:
1. GitHub's CODEOWNERS documentation does not explicitly mention where to create the file.
2. NPM's docs do not explain allowed characters in package names.
We have updated our Python Basics tutorial to describe the guidelines for docstrings in more detail:
https://python-basics-tutorial.readthedocs.io/en/latest/document/sphinx/docstrings.html#guidelines
#Python #Documentation #DX
new & final status update on 'moving image zines rdam':
The complete archive (355 videos) from 2005-2025 has been uploaded & is available on archive.org: https://archive.org/details/moving-image-zines-rdam?sort=-date
All videos are downloadable as high-quality files [mp4/h264 codec, 32 Mbit/s] and reusable under the Creative Commons Attribution-ShareAlike 4.0 International license.
This morning, I finally checked in the code for turning a few lines of text like:
Today, Sat Apr 05, 2025
1000-1600 Cactus Sale
1100-1400 March at the Roundhouse
into text displayed on the eInk screen from WaveShare. As always, it took longer than expected, but it's mostly working. #coding #documentation #EverythingTakesLonger #YakShaving #WoodWorking… (1/3)
#OffShore fianance created Cloud #money before we have #Cloud Computing ...
grandiose #documentation
deep inside the shadowy world of offshore finance and corporate tax avoidance, revealing how the world's largest corporations are reshaping the global economy at the expense of ordinary citizen
All developers I've met in my career in IT, who insisted code is self-documenting were exceptionally bad in documenting anything
While their code usually ran just fine, they could hardly ever explain how it worked or why it was structured that way to someone else, especially junior developers.
Comments and annotations exists for a reason.
Good #Coding practices question for #Documentation:
Are there some general guidelines on what info to put in the comment at the top of each code file? Like date, author, basic description of what the code does? Maybe something about dependencies? Are there templates for this somewhere (e.g. for #Matlab or #Python if that matters)?
so the e-bike brake handle had an OH137 hall effect sensor in its case and a magnet. Let's hope I can fix that lel
Focus on what you CAN do, not what you CAN’T
In these past few weeks it seems that there were so many horrible things happening that just making a list of them feels overwhelming and exhausting. Some of the decisions of the current U.S. government have an impact on the global level, others hit people personally, some of whom are close friends. And then, there are those who seem to target the very core of our profession, like the shutting down of the Institute of Museum and Library Services (IMLS) and the termination of grants already awarded by the National Endowment of the Humanities (NEH).
It is hard not to lose all hope in this climate. And yet, aren’t we, as museum professionals, used to things not really looking pretty? Haven’t we battled budget and staff cuts before? Haven’t we brought uncomfortable truths in front of the eyes of our visitors and politicians before? Maybe the current crisis is not comparable to what we were confronted with before. But just as well, we are well trained in going against adversarial circumstances.
We have always done so with resilience, creativity, and, most of all, a sense of community. We might be spread out across the world and we might have spread ourselves thin by taking on too many responsibilities, but we are not alone. I have reached out to my network over the past few days to check in on some people, see how they are coping, and getting ideas of what can be done, because, in the end, focusing on what can’t be done never made anything better.
Turns out that John E. Simmons had already started collecting what can be done to prepare for what is coming at us in something we registrars love: A list.
I contributed a few of my thoughts to it and we also asked some more colleagues to add to it. What I am posting here today is by no means a comprehensive and finalized list of what to think about and what to do, but it is a start. Feel free to add more ideas in the comments section, just like we enhance it going forward.
What Can We Do?
1. Apply the lessons that museums learned from Covid
2. Prepare the collections for long-term, low maintenance storage by preparing the most sustainable and passive storage environment possible:
3. Protect the databases
4. Update the institutional emergency preparedness plan to include procedures for coping with sudden, prolonged shutdowns of the building.
5. Stock up on critical supplies
6. Download anything needed from federal websites (such as the NPS Museum Handbook and Conserve O Grams or IMLS reports) immediately, while the information is still available. Store this data in a safe place that is only accessible to authorized personnel and make deleting those resources as hard as possible.
7. Keep in mind that most serious problem going forward will probably not be the cuts in federal funding to the NIH, NEA, NSF, IMLS, etc., because most of this money goes to projects which can be postponed or funded by other sources (such as donations). The most serious problem will be the lack of funds resulting from damage done to the economy due to a combination of the rising deficit, increasing unemployment (e.g., the mass reductions in the federal workforce and corresponding loss of jobs in sectors that serve the federal workforce), and decreased tax revenues due to tax cuts for the wealthy, tariffs on imports, and cuts to social services. In other words, the predicted problems with the US economy are far more likely to be a bigger problem for museums than the loss of federal grant funds.
Words of Cheer:
Best Advice:
If your institution does not have a plan for long-term survival during a financial crisis, the next pandemic, or climate change, get busy now to correct this deficit.
Helpful Information
Some more notes
Share this resource freely with anyone you think needs to see this, no need to ask for permission. Add what applies to your special case. Let us know what we should add. Download, save, print, circulate.
Registrar Trek is hosted on a server in Germany and following EU laws. I am currently looking through all the plug-ins I use to make sure none of them collects and shares any personal data with the U.S. Or, in fact, anybody. I always was mindful not to collect any personal information but will double-check again if everything is safe.
Hang on in there, you are not alone!