Mastodon 🐘

Miguel Afonso Caetano"Tech comms can be a business, but thinking is not selling: it requires intellectual freedom and courage. Leaving these conversations to engineers risks turning technical communication into a caricature of itself, a four-quadrant fantasy devised to lure developers into thinking that documentation is a simple pastime, yet another Jira task.Only independent thought can help us progress and navigate uncertainty, including our future in a world where AI is injected into every domain that deals with words. Technical writers must own their problems and the conversations around them, or they will slowly fade into irrelevance, their problems absorbed by other disciplines that have more pressing problems to focus on. And if you’re reading that we should lobby more, you’re not wrong: defending knowledge requires power.”<a href="https://tldr.nettime.org/tags/TechnicalWriting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalWriting</a> <a href="https://tldr.nettime.org/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a> <a href="https://tldr.nettime.org/tags/SoftwareDocumentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareDocumentation</a> <a href="https://tldr.nettime.org/tags/CriticalThinking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CriticalThinking</a> <a href="https://passo.uno/tech-writing-depth-issue/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://passo.uno/tech-writing-depth-issue/</a>

Miguel Afonso Caetano“Don’t cover all the details of the product and the technologies it relies on because no one reads the documentation anyway, right?”WRONG! If you’re writing for the Web, you can never be sure of the level of computer literacy of the person who has to read your docs. Moreover, you can never know if that person is looking for detailed instructions on how to use a particular feature or API endpoint. Who knows? It might just be something that you or the rest of the team overlooked as secondary.When it comes to online content, every page is page one. If you want the user to trust you and use your product with confidence, you should strive to provide as much context as possible. For example, if the user is expected to know how to use Node.js and Docker before getting started with a particular CLI-based application, you should explicitly say so at the beginning of the application's tutorial. Ideally, you should not only provide resources for the user to familiarize themselves with these tools, but also explain elsewhere the benefits of using these tools for this application rather than another tech stack. A documentation site is a highway with no predefined entrances and exits. Any user can start reading it from any point. It's up to you, the content designer, to determine where it logically starts and ends in terms of information architecture, and to make sure there are enough accessible connections to other learning resources along the way. The learning experience provided to the end user should be analogous to a great technical book like The Unix and Linux System Administration Handbook (1500 pages), which is not only a classic reference, but also a comprehensive resource with a detailed table of contents and index. Although it's regularly updated with new technical advances that have been introduced since the last edition, it still contains the same core. <a href="https://books.google.pt/books?id=f7M1DwAAQBAJ" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://books.google.pt/books?id=f7M1DwAAQBAJ</a><a href="https://tldr.nettime.org/tags/TechnicalWriting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalWriting</a> <a href="https://tldr.nettime.org/tags/SoftwareDocumentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareDocumentation</a> <a href="https://tldr.nettime.org/tags/Documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Documentation</a> <a href="https://tldr.nettime.org/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a>

Miguel Afonso Caetano"[T]o build effective docs you not only need tools and content types, but also a model of needs that documentation must satisfy as a product, or of actions users need to accomplish through docs. This model should be fairly independent from the type of software product you’re documenting, in the same way conceptual models of product design and satisfaction abstract away the specifics. Aiming for a general model is necessary because it helps professionals learn and communicate together. What follows is my own descriptive model of user needs for documentation, one I’m following to build and arrange documentation today. The approach I’m proposing here is a model of what user actions the docs are meant to satisfy. The model aims at connecting both UX research and documentation frameworks with a conceptual and functional layer that focuses on two aspects: docs as a product and what users are meant to accomplish through them. It’s an attempt at describing what technical documentation should do. It’s treating docs as a product that someone is going to use to achieve actual goals. As I said, the core of the model is actions. I’ve identified seven that I think cover a decent amount of goals that a consumer of docs may want to accomplish when using documentation. They represent common patterns in how users interact with documentation across different products and domains. They’re the following, each bearing an alternative term in parentheses: Appraise (Discern), Understand (Learn), Explore (Discover), Practice (Train), Remember (Recall), Develop (Integrate), and Troubleshoot (Solve)."<a href="https://passo.uno/seven-action-model/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://passo.uno/seven-action-model/</a><a href="https://tldr.nettime.org/tags/TechnicalWriting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalWriting</a> <a href="https://tldr.nettime.org/tags/Documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Documentation</a> <a href="https://tldr.nettime.org/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a> <a href="https://tldr.nettime.org/tags/UX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UX</a> <a href="https://tldr.nettime.org/tags/DocumentationFrameworks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DocumentationFrameworks</a> <a href="https://tldr.nettime.org/tags/UXResearch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UXResearch</a> <a href="https://tldr.nettime.org/tags/DocsAsProduct" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DocsAsProduct</a>

Miguel Afonso Caetano"Similar to Wood’s conviction that AI’s transformative potential doesn’t come from simple tasks like writing emails, tech writers will likely find conviction when they go beyond fixing simple grammar errors to using AI for developing conceptual articles, generating release notes, or understanding connections across disparate API products.One of my colleagues compared using AI like learning to play an instrument—it’s one thing to have an intellectual understanding about the instrument and notes, but knowing how to play an instrument well is entirely different. It takes practice, experimentation, learning, diligence, and time. Maybe too many tech writers feel that AI should provide a push-button solution to creating documentation effortlessly (a misguided perception based on too much AI hype). When pushing that button doesn’t magically produce great docs, perhaps they become cynical and dismissive?"<a href="https://idratherbewriting.com/blog/trends-predictions-2025-tech-comm" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://idratherbewriting.com/blog/trends-predictions-2025-tech-comm</a><a href="https://tldr.nettime.org/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> <a href="https://tldr.nettime.org/tags/GenerativeAI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GenerativeAI</a> <a href="https://tldr.nettime.org/tags/TechnicalWriting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalWriting</a> <a href="https://tldr.nettime.org/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a> <a href="https://tldr.nettime.org/tags/APIs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#APIs</a> <a href="https://tldr.nettime.org/tags/APIDocumentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#APIDocumentation</a> <a href="https://tldr.nettime.org/tags/PromptEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PromptEngineering</a> <a href="https://tldr.nettime.org/tags/TechComm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechComm</a>

Kari J. Lundgren, PhD 🏳️‍🌈My open-access peer-reviewed article on medical <a href="https://med-mastodon.com/tags/charting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#charting</a> as technical communication came out last week, and I hope others may find it valuable and useful! I argue that looking at actual chart notes can help us to develop and implement curriculum for teaching rhetorical reading and writing principles to providers, thereby positively impacting both <a href="https://med-mastodon.com/tags/patientcare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#patientcare</a> and administrative efficiency.<a href="https://doi.org/10.17077/2151-2957.33754" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://doi.org/10.17077/2151-2957.33754</a><a href="https://med-mastodon.com/tags/EHR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EHR</a> <a href="https://med-mastodon.com/tags/rhetoric" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rhetoric</a> <a href="https://med-mastodon.com/tags/RHM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RHM</a> <a href="https://med-mastodon.com/tags/primarycare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#primarycare</a> <a href="https://med-mastodon.com/tags/technicalcommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#technicalcommunication</a> <a href="https://med-mastodon.com/tags/research" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#research</a> <a href="https://med-mastodon.com/tags/academia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#academia</a>

LeanpubTechnical Writing And Professional Communication: Revived by Henrik Lynge <a href="https://leanpub.com/technicalwritingandprofessionalcommunication-revived" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://leanpub.com/technicalwritingandprofessionalcommunication-revived</a> by Henrik Lynge is the featured book on the Leanpub homepage! <a href="https://leanpub.com" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://leanpub.com</a> <a href="https://mastodon.social/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a>

LeanpubThe Frontend Dogma Super Bundle 10 <a href="https://leanpub.com/b/frontend-dogma-10" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://leanpub.com/b/frontend-dogma-10</a> by Jens Oliver Meiert is the featured bundle on the Leanpub homepage! <a href="https://leanpub.com" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://leanpub.com</a> <a href="https://mastodon.social/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDevelopment</a> <a href="https://mastodon.social/tags/CSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSS</a> <a href="https://mastodon.social/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a> <a href="https://mastodon.social/tags/Reference" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Reference</a> <a href="https://mastodon.social/tags/SoftwareEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareEngineering</a> <a href="https://mastodon.social/tags/Javascript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Javascript</a> <a href="https://mastodon.social/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a>

LeanpubThe Frontend Dogma Super Bundle 10 <a href="https://leanpub.com/b/frontend-dogma-10" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://leanpub.com/b/frontend-dogma-10</a> by Jens Oliver Meiert is the featured bundle on the Leanpub homepage! <a href="https://leanpub.com" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://leanpub.com</a> j9t@mas.to <a href="https://mastodon.social/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDevelopment</a> <a href="https://mastodon.social/tags/CSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSS</a> <a href="https://mastodon.social/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a> <a href="https://mastodon.social/tags/Reference" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Reference</a> <a href="https://mastodon.social/tags/SoftwareEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareEngineering</a> <a href="https://mastodon.social/tags/Javascript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Javascript</a> <a href="https://mastodon.social/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a>

Larry SwansonHis LavaCon <a href="https://mastodon.social/tags/ContentStrategy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ContentStrategy</a> conference and <a href="https://mastodon.social/tags/TechnicalComm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalComm</a> staffing agency give Jack Molisani a high-level view of the world of technical content, including the impacts of <a href="https://mastodon.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> on the field. Fun conversation - hope you enjoy it, too.<a href="https://contentandai.com/jack-molisani/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://contentandai.com/jack-molisani/</a><a href="https://mastodon.social/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a> <a href="https://mastodon.social/tags/ContentStrategy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ContentStrategy</a> <a href="https://mastodon.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a>

Miguel Afonso Caetano<a href="https://tldr.nettime.org/tags/TechnicalWriting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalWriting</a> <a href="https://tldr.nettime.org/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a> <a href="https://tldr.nettime.org/tags/Docs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Docs</a> <a href="https://tldr.nettime.org/tags/SoftwareDocumentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareDocumentation</a>: “We know that the decision to make a purchase or maybe to buy more of your product is heavily reliant on the kind of technical content you have and whether the users see that what you have is what they need from a functionality and capability perspective. This is throughout the user journey. If a user is just browsing around for a solution, if you have better content than your competitor, they’re most likely to come back to you. If they’re on the verge of just onboarding, they will use technical content to onboard, and so on and so forth.What we are seeing is that documentation portals, which is the home for technical writers, are actually becoming the number one traffic for a company’s users. If you know how to measure that and you can actually see that linear growth in traffic, and you know that part of this traffic is people making a decision to buy your product, this is definitely something that you want to surface up to your leaders and justifies an investment in making your content better. That’s just one example.Another example, which is another value metric that we often measure, is returning users. What we’ve seen is that when people visit your documentation often, and even to be more specific, more than twice in the previous 30 days, they’re twice as likely to actually become a paying customer.”<a href="https://idratherbewriting.com/blog/value-techcomm-zoomin-podcast?trk=feed-detail_main-feed-card_feed-article-content" rel="nofollow noopener noreferrer" target="_blank">https://idratherbewriting.com/blog/value-techcomm-zoomin-podcast?trk=feed-detail_main-feed-card_feed-article-content</a>

JeromeWell designed information is clear, unambiguous, and enhances comprehension and other human performance.The illustration below shows a duration. Several design changes could each have made this usable, such as adding a space: 23:00 09:30 or a word: 23:00 to 09:30<a href="https://mastodon.social/tags/InformationDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InformationDesign</a> <a href="https://mastodon.social/tags/ContentDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ContentDesign</a> <a href="https://mastodon.social/tags/TechComm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechComm</a> <a href="https://mastodon.social/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a> <a href="https://mastodon.social/tags/interface" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#interface</a> <a href="https://mastodon.social/tags/usability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#usability</a> <a href="https://mastodon.social/tags/duration" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#duration</a> <a href="https://mastodon.social/tags/time" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#time</a> <a href="https://mastodon.social/tags/clarity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clarity</a> <a href="https://mastodon.social/tags/comprehension" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#comprehension</a> <a href="https://mastodon.social/tags/accuracy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#accuracy</a> <a href="https://mastodon.social/tags/performance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#performance</a> <a href="https://mastodon.social/tags/UserPerformance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UserPerformance</a>

Keith SoltysThis week's Featured Links post has links to articles about the fascinating life of science fiction author Cordwainer Smith, the crazy eclipse conspiracies of the far right, how a vigilante hacker took down North Korea's internet, and more. <a href="https://coredump3.blogspot.com/2024/04/featured-links-april-8-2024.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://coredump3.blogspot.com/2024/04/featured-links-april-8-2024.html</a><a href="https://twit.social/tags/Books" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Books</a>, <a href="https://twit.social/tags/Design" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Design</a>, <a href="https://twit.social/tags/Disinformation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Disinformation</a>, <a href="https://twit.social/tags/Environment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Environment</a>, <a href="https://twit.social/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Internet</a>, <a href="https://twit.social/tags/Military" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Military</a>, <a href="https://twit.social/tags/Science" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Science</a>, <a href="https://twit.social/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a>, <a href="https://twit.social/tags/SFF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SFF</a>, <a href="https://twit.social/tags/Space" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Space</a>, <a href="https://twit.social/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a>, <a href="https://twit.social/tags/Technology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Technology</a>, <a href="https://twit.social/tags/Typography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Typography</a>

LeanpubAwesome Asciidoctor Notebook by Hubert A. Klein Ikkink (mrhaki) is free with a Leanpub Reader membership! Or you can buy it for $7.99! <a href="http://leanpub.com/awesomeasciidoctornotebook" rel="nofollow noopener noreferrer" translate="no" target="_blank">http://leanpub.com/awesomeasciidoctornotebook</a> <a href="https://mastodon.social/tags/ComputerProgramming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ComputerProgramming</a> <a href="https://mastodon.social/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a>

thegrumpyenbyI’ve now been out of work for 6 months and I’ve just transferred the last bit of my savings into my current account. The job market in tech is a trash fire, but we knew that already. What has surprised me way more is that it’s currently also really hard to find freelance work, something I’ve never had any issues with in the past. Admittedly, I’ve had some bad luck. One potential client fell through because as an American company, they were uncomfortable setting up a contract with someone in Germany (the legal situation for freelancers here is understandably terrifying for US and UK entities). Another one fell through because they can’t currently afford my rates. Because startups. And a third one I can’t get started on because it’s one-off work — and without any long-term clients, I cannot afford the ongoing self-employment insurance payments just for a one-off contract. It’s honestly driving me to despair.I don’t even know if there’s any point to still posting this anywhere or asking you to reshare it because I see that so so many in my network are currently in the same or a similar situation — LinkedIn is depressing af these days. But here we go: If your company needs any ongoing work in what broadly falls under the realm of technical communication — copywriting, content writing, content editing, livestreaming, podcasting, etc. — please, reach out to me! Additionally, I’m really proving my mettle as Program Lead of the Open Source Explorers program at Distribute Aid and am happy to take on more strategic positions as well. Employed or freelance — I’m great at what I do either way.I just really need an income again because it’s getting scary. Thank you for sharing and for thinking about me when you hear about any companies looking for someone with my skill set!<a href="https://tenforward.social/tags/FediHired" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediHired</a> <a href="https://tenforward.social/tags/GetFediHired" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GetFediHired</a> <a href="https://tenforward.social/tags/DeveloperContent" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DeveloperContent</a> <a href="https://tenforward.social/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a> <a href="https://tenforward.social/tags/TechJobs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechJobs</a>

LeanpubPublishing with Emacs, Org-mode and Leanpub by Diego Zamboni is on sale on Leanpub! Its suggested price is $20.00; get it for $10.50 with this coupon: <a href="https://leanpub.com/sh/8VJjcOVk" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://leanpub.com/sh/8VJjcOVk</a> <a href="https://mastodon.social/tags/WritingAndPublishing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WritingAndPublishing</a> <a href="https://mastodon.social/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a> <a href="https://mastodon.social/tags/SelfPublishing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfPublishing</a>

Keith SoltysSo NASA engineers are having to consult "decades old manuals" to figure out how to fix a communications problem with the Voyager 1 spacecraft, which is now almost a light-day away from the Earth.<a href="https://gizmodo.com/nasas-voyager-1-spacecraft-is-speaking-gibberish-1851096904" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gizmodo.com/nasas-voyager-1-spacecraft-is-speaking-gibberish-1851096904</a><a href="https://twit.social/tags/space" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#space</a> <a href="https://twit.social/tags/Voyager" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Voyager</a> <a href="https://twit.social/tags/techcomm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#techcomm</a> <a href="https://twit.social/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a>

LeanpubLanding on a Great Name: A short book on one of programming's most challenging problems. https://leanpub.comlanding-on-a-great-name by Ka Wai Cheung is the featured book on the Leanpub homepage! <a href="https://leanpub.com" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://leanpub.com</a> @developerscode <a href="https://mastodon.social/tags/ComputerProgramming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ComputerProgramming</a> <a href="https://mastodon.social/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a>

LeanpubNode-OPCUA by example - edition 2022 by Etienne Rossignon is on sale on Leanpub! Its suggested price is $249.00; get it for $99.50 with this coupon: <a href="https://leanpub.com/sh/0kXQ05nf" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://leanpub.com/sh/0kXQ05nf</a> <a href="https://mastodon.social/tags/InternetOfThings" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InternetOfThings</a> <a href="https://mastodon.social/tags/Javascript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Javascript</a> <a href="https://mastodon.social/tags/Robotics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Robotics</a> <a href="https://mastodon.social/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnicalCommunication</a>

Recent searches

Search options

Administered by:

Server stats:

#technicalcommunication