I'm streaming KDE docs:
Be sure to join and ask any questions related to KDE and I'll try my best to answer them. The stream will last several hours.
Every single stream I do is an Ask Me Anything KDE Edition ™️
I'll continue working on improving KConfig documentation as before.
#KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Twitch
Reminder for the technical writers on the Fediverse to share their anti-LLM sentiment in the #TechnicalWriting, #WriteTheDocs and #Documentation hashtags too thanks :neofox_3c_256:
😮One of the coolest technical artists is back on the fediverse!!
I really recommend following @heytibo, he makes such wonderful things, often #Godot related!!
You will adore him if you like any of these things:
🎮 #GodotEngine, #GameDev
🌸 #WebDev, #FOSS
🎨#Design, #Art, #UI, #Blender
🌻#TechnicalWriting, #TechArt
🪐#Space, #Indie, #VideoGame
Boosts are welcome, he deserves them!!
#FediFollow #FollowFriday
I'm streaming KDE docs:
Be sure to join and ask any questions related to KDE and I'll try my best to answer them.
Every single stream I do is an Ask Me Anything KDE Edition ™️
Today I'll see about improving KConfig (which @me was curious about :P) and maybe play a bit of beginner Super Mario World kaizo romhacks in the end.
#KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Twitch
Tech writers using AI: what’s the most “confident but wrong” thing you’ve seen it produce in docs?
My take: the key skill isn’t “Can AI write?”
It’s Can we tell when it’s wrong?
https://aitransformer.online/why-can-ai-do-this-is-the-wrong-question-for-technical-writers/
We have significantly expanded our German-language documentation guide on the technical writing of top-level domains, IP addresses and telephone numbers: https://www.cusy.design/writing/wordlist.html
#TechnicalWriting #RFC
I'm streaming KDE docs:
Be sure to join and ask any questions related to KDE and I'll try my best to answer them.
Every single stream I do is an Ask Me Anything KDE Edition ™️
Today I'll see about finishing polishing the "Preparing your software for release" page. Otherwise, I might start porting another library to QDoc. I may also play with RPM packaging.
#KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Twitch
Does the Enterprise's computer have a user manual? #startrek #technicalwriting
Several "good-to-remember" questions - both for software developers and technical writers focused on API documentation:
"REST APIs power most of the internet's integrations. Whether you are applying for a backend role, a full stack position, or a software engineering job, you will likely face questions about REST API design, HTTP methods, and authentication patterns.
In this guide, I will walk you through the questions interviewers actually ask. I have organized them by difficulty level and role type, so you can focus on what matters most for your target position. Each answer includes practical examples and, where relevant, code snippets you can adapt.
One thing to keep in mind: interviewers test fundamentals far more often than advanced topics. If you nail the basics (HTTP methods, status codes, statelessness), you will handle most REST API interviews confidently. The fancy architectural patterns come later."
https://www.datacamp.com/blog/rest-api-interview-questions
#APIs #REST #RESTAPI #RESTAPIs #Programming #API #SoftwareDevelopment #TechnicalWriting
I'm streaming KDE docs:
Be sure to join and ask any questions related to KDE and I'll try my best to answer them.
Every single stream I do is an Ask Me Anything KDE Edition ™️
#KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Twitch
"Fabrizio: I think automation engineering is is like an expression… one of the many expressions of systems thinking. Which I believe we brought up in previous podcasts as well. And I think systems thinking is one of the top skills I would probably seek in anybody in the future working with AI. Because it’s really about orchestrating and seeing the big picture and relating systems between each other. Which is something that I don’t expect AI ever to be able to do.
And automation… well you can also… there’s always this thing about the automatons building themselves and I think AI can help you build parts of that automation system. But in the end how you connect the pieces together is entirely up to you. Because that’s that’s ultimately the system you build is an expression is of… and I’m getting philosophical here… of volition. Of something you want to do.
And wanting to do something is purely organic human. Like you want to achieve something that you care about. So yes I think definitely automation as a part of that system thinking definitely. The other I think is communication, you know in all forms. So and I think I was having this conversation with a developer the other day on BlueSky. He writes Python tutorials. And we were agreeing that anybody who has both the technical knowledge and the communication skills is like in the best position going forward in the tech world. Because you will need both. You will need like an understanding of what the tech does but at the same time like a certain command of words.
And I would argue that 60 or 70 percent going forward."
https://idratherbewriting.com/blog/predictions-2026-tech-comm-podcast
#TechnicalWriting #TechnicalCommunications #Automation #AutomationEngineering #AI #GenerativeAI #SoftwareDevelopment
I'm streaming KDE docs:
Be sure to join and ask any questions related to KDE and I'll try my best to answer them.
Every single stream I do is an Ask Me Anything KDE Edition ™️
#KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Twitch
"In this scenario, it doesn't make a lot of sense to target your API documentation exclusively at developers. It's definitely time to write it in a way that your non-technical stakeholders understand. So, how can you document your API capabilities?
Identifying capabilities is an exercise that begins with understanding the benefits your API offers to consumers. Benefits are the things that consumers obtain after they use your API, not what your API has to offer. You need to understand how consumers use your API and what their daily habits are. A good framework is studying your consumers' jobs-to-be-done (JTBD). Each JTBD represents something one or more consumers are trying to accomplish by using your API. After you group JTBDs by categories according to their similarity, you'll notice that clusters of benefits begin to emerge. If you then order those clusters by degree of criticality, you end up with a list of the most important benefits your API offers to potential consumers. I think you can already see where this is leading. With the list of benefits, you can get to a list of API capabilities by translating each one. While the benefit is what consumers achieve, the capability is what helps them get there. Let's look at an example to make things easier."
https://apichangelog.substack.com/p/documenting-your-api-around-its-capabilities
#API #APIs #APIDocumentation #TransactionEnrichment #TechnicalWriting #SoftwareDocumentation #SoftwareDevelopment
I'll be a bit late :neofox_laugh_sweat_256:
I'll be streaming KDE docs:
Be sure to join and ask any questions related to KDE and I'll try my best to answer them.
Every single stream I do is an Ask Me Anything KDE Edition ™️
Today initially I'm going to merge what I worked on last stream and do some housecleaning, and then we'll see what I'll tackle today.
#KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Twitch
I'll be streaming KDE docs today in one hour from now:
Be sure to join and ask any questions related to KDE and I'll try my best to answer them.
Every single stream I do is an Ask Me Anything KDE Edition ™️
Today I'll finish and merge our new "Understanding the software lifecycle" tutorial page and improve the existing Incubation and KDE Review pages.
@kde #KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Twitch
It’s my #birthday (yes, and I'll cry if I want to, lol) and the start of #365to50. I’m moving my 30 years of editorial experience from #underground #fanzines and #webpublishing into the technical sphere.
I immensely enjoy #FOSS and #fediverse ideas and philosophy, and while I am still a very #linux #newbie , I'd like to start giving back to the community. I’m looking for #FOSS projects that need high-quality Slovak or Czech localization ( #L10n ).
If your documentation or UI needs an editor’s touch to feel truly native, let’s talk!
#Introduction #Linux #OpenSource #Translation #TechnicalWriting #Slovakia #Czech
Today's stream lasted 4 hours and 30 minutes and was extremely productive! Thanks to sitter showing up to assist with my doubts about our release software tooling.
It consisted of explaining to a new developer what the KDE software lifecycle is supposed to look like, what you should do to publish your software, and in what order. I even made diagrams!
I'm streaming work on KDE documentation:
Be sure to join and ask any questions related to KDE and I'll try my best to answer them.
Every single stream I do is an Ask Me Anything KDE Edition ™️
Today I think I'll get started on the documentation for making projects part of KDE / releasing KDE software.
@kde #KDE #Linux #Documentation #TechnicalWriting #FurryStreamer #FurryVTuber #VTuber #Twitch
Tell me you haven't talked to a real live tech writer on a time scale of decades without telling me.
https://kibbler.dev/blog/turn-your-codebase-into-a-knowledge-base
#TechnicalWriting #docs #documentation #writeTheDocs #techWriter
Technical writers aren’t a luxury. They are the people who translate what you’ve built into something others can use. Without them, you’re shipping a product that can’t speak for itself, or that lies. Your product needs to speak. AI can generate noise effectively and infinitely, but only a technical writer can create the signal.
To those who fired or didn't hire tech writers because of AI
