<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="/assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Field Notes</title><link>https://janetriley.net/</link><description>Notes from the field</description><atom:link href="https://janetriley.net/rss.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2024 &lt;a href="mailto:hello@janetriley.net"&gt;Janet Riley&lt;/a&gt; </copyright><lastBuildDate>Tue, 21 May 2024 18:15:27 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Nathaniel Schutta and Neal Ford: Communicating Architecture</title><link>https://janetriley.net/notes/technical_communication/nathaniel-schutta-neal-ford-communicating-architecture.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;h2&gt;Summary&lt;/h2&gt;
&lt;p&gt;Neal Ford hosts Software Architecture Hour, a series of live conversations on O'Reilly.
He spoke with Nathaniel Schutta on &lt;a href="https://learning.oreilly.com/live-events/software-architecture-hour-communicating-architecture-with-nathaniel-schutta/0636920077012/0636920077011/"&gt;Communicating Architecture&lt;/a&gt;
on 7/7/2022. &lt;/p&gt;
&lt;h2&gt;Notes&lt;/h2&gt;
&lt;h4&gt;Is presentation patterns still relevant?&lt;/h4&gt;
&lt;p&gt;Yes.&lt;/p&gt;
&lt;p&gt;Ford described new patterns for Zoom:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start with the punchline. You must immediately state what they're going to get out of it so they don't leave.
In-person, people will let it ride for a bit before they get up.&lt;/li&gt;
&lt;li&gt;Paired presentations work better because it's more like a conversation&lt;/li&gt;
&lt;li&gt;Timing is more important. Make something change on the slide every 30 seconds so it's not static and creates a sense of motion.&lt;/li&gt;
&lt;li&gt;Ford:  quoting a professor's advice - you need to do something every 10 minutes to hook people back in.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;What presentation software is best?&lt;/h4&gt;
&lt;p&gt;Keynote or Powerpoint both have good animations. "You want a rich way to manipulate time" .&lt;br&gt;
Info decks have to be complete; presentations are only half complete because the presenter is the other half.&lt;/p&gt;
&lt;h4&gt;Favorite tools&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;The simplest ones. Whiteboards.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://excalidraw.com"&gt;Excalidraw&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://miro.com"&gt;Miro&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Use a tool that has layers. Ford puts the boxes on the bottom layer, protocols on the next, transactional boundaries above that.&lt;/p&gt;
&lt;h4&gt;Favorite diagramming frameworks&lt;/h4&gt;
&lt;p&gt;&lt;a href="https://c4model.com/"&gt;C4&lt;/a&gt;, &lt;a href="https://www.opengroup.org/archimate-forum/archimate-overview"&gt;Archimate&lt;/a&gt;, 
boxes and arrows with a legend. Use the framework that works. Keep diagrams up-to-date.  &lt;/p&gt;
&lt;p&gt;Ford shared a story about a coworker who would draw diagrams by hand as he talked with people, over and over. 
"It was a fantastic stupid human trick." High impact on the audience.   ... "You start to see how they got to [their design]" &lt;/p&gt;
&lt;h4&gt;Miscellaneous:&lt;/h4&gt;
&lt;p&gt;Ask, what nugget or two do I want my audience to leave with?&lt;/p&gt;
&lt;p&gt;Focus on narrative.&lt;/p&gt;
&lt;p&gt;Quiz questions and "raise your hand if..." gets mixed results. Some people are into it, some online audiences are shy&lt;/p&gt;
&lt;h2&gt;Excerpts&lt;/h2&gt;
&lt;p&gt;Ford: "As an architect, I have two folders - Current and Archaeology". Ford updates the Current diagrams, ignores Archaeology.&lt;/p&gt;
&lt;h2&gt;Takeaways&lt;/h2&gt;
&lt;p&gt;With Zoom it's harder than ever to retain attention. &lt;/p&gt;
&lt;p&gt;Use layers in diagrams to add another dimension. I'd like to explore this for breaking up layers as Ford described, 
especially as a way to start with a simple idea and build on it. Something in this and in the 
&lt;a href="https://learning.oreilly.com/library/view/presentation-patterns-techniques/9780132963381/"&gt;Presentation Patterns&lt;/a&gt; chapter on temporal patterns 
reminds me of &lt;a href="https://scottmccloud.com/2-print/1-uc/index.html"&gt;Scott McCloud's Understanding Comics&lt;/a&gt;. 
McCloud shows a sequence of two illustrations, with a person wearing a hat, and in the next panel, raising it. 
Our brains fill in the space between to create a story. Could I tap into that and a sequence to make diagrams convey more? &lt;/p&gt;
&lt;h2&gt;See Also&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://learning.oreilly.com/library/view/thinking-architecturally/9781492034421/"&gt;Thinking Architecturally&lt;/a&gt; by Schutta&lt;/p&gt;
&lt;p&gt;&lt;a href="https://learning.oreilly.com/library/view/presentation-patterns-techniques/9780132963381/"&gt;Presentation Patterns: Techniques for Crafting Better Presentations&lt;/a&gt; and &lt;a href="http://www.presentationpatterns.com"&gt;companion site&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;McCloud on presentations in &lt;a href="https://youtu.be/044MART1uOM?t=49"&gt;A Conversation with Scott McCloud&lt;/a&gt;&lt;/p&gt;</description><category>diagrams</category><category>technical_communication</category><guid>https://janetriley.net/notes/technical_communication/nathaniel-schutta-neal-ford-communicating-architecture.html</guid><pubDate>Tue, 19 Jul 2022 12:57:16 GMT</pubDate></item><item><title>Curling Resources</title><link>https://janetriley.net/notes/fun/curling-resources.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;h2&gt;Overview&lt;/h2&gt;
&lt;iframe width="848" height="477" src="https://www.youtube.com/embed/WXHh_wadqPw" title="Two Minute Guide to the Sport of Curling" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen&gt;&lt;/iframe&gt;
&lt;p&gt;&lt;br&gt;
&lt;br&gt;
&lt;a href="https://youtu.be/d17aZSlpT7M"&gt;How to Watch Curling Like a Pro&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;Technique&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://www.youtube.com/playlist?list=PL9Prr147gJlEdtKFTGny8PPM-V6XDQcJD"&gt;Jamie Sinclair's Learn to Curl series&lt;/a&gt; explains all the basics and then some.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://curlingclass.com"&gt;Curling Class&lt;/a&gt; has &lt;a href="https://curlingclass.com/curling-resources/"&gt;resources&lt;/a&gt; and &lt;a href="https://www.youtube.com/c/CurlingClass"&gt;videos&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=4ztdIxdYSCA&amp;amp;list=PLIkJod9TKX8Dl12_stE1-xs5bcxqaGQ87&amp;amp;ab_channel=MississauguaGolf"&gt;Sweeping Saturdays&lt;/a&gt; has balance and conditioning exercises off the ice. &lt;/p&gt;
&lt;h2&gt;Rules and Strategy&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://worldcurling.org/competitions/rules/"&gt;The Rules of Curling&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=sqZ799ULlvU&amp;amp;ab_channel=ChessonIce"&gt;Basics of Curling Strategy&lt;/a&gt; "covers everything a first-time skip needs to know 
to call a game, and gives insight into the general strategies used."&lt;/p&gt;</description><category>curling</category><guid>https://janetriley.net/notes/fun/curling-resources.html</guid><pubDate>Sun, 19 Jun 2022 20:00:24 GMT</pubDate></item><item><title>Digital Gardens</title><link>https://janetriley.net/notes/digital-gardens.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;&lt;a href="https://notes.andymatuschak.org/"&gt;Andy Matuschak's Evergreen notes&lt;/a&gt; made me curious about starting my own digital garden. 
Matuschak's distills and connects his research, building &lt;a href="https://notes.andymatuschak.org/z6cFzJWgj9vZpnrQsjrZ8yCNREzCTgyFeVZTb"&gt;an accumulation of insight&lt;/a&gt;.
I'd like to capture and link more of what I take in and see what patterns it makes.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/MaggieAppleton/digital-gardeners"&gt;Maggie Appleton's tools and resources for digital gardeners&lt;/a&gt; 
lists tools for creating public or private digital gardens. &lt;/p&gt;</description><category>digital_gardens</category><guid>https://janetriley.net/notes/digital-gardens.html</guid><pubDate>Wed, 15 Jun 2022 00:16:30 GMT</pubDate></item><item><title>How Browsers Work</title><link>https://janetriley.net/notes/tech/how-browsers-work.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;h2&gt;Web Browser Engineering&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://browser.engineering/index.html"&gt;Web Browser Engineering&lt;/a&gt;
Author:Pavel Panchekha &amp;amp; Chris Harrelson&lt;/p&gt;
&lt;h3&gt;Summary:&lt;/h3&gt;
&lt;p&gt;Manchekha and Harrelson explain how browsers work. The textbook guides you through building a basic web browser in Python.&lt;/p&gt;
&lt;h2&gt;Chrome Developer series: Inside Look at Modern Web Browser&lt;/h2&gt;
&lt;h3&gt;Summary:&lt;/h3&gt;
&lt;p&gt;A four part deep dive on Chrome&lt;/p&gt;
&lt;h3&gt;Links:&lt;/h3&gt;
&lt;p&gt;&lt;a href="https://developer.chrome.com/blog/inside-browser-part1/"&gt;Part 1: CPU, GPU, Memory, and Multi-Process Architecture&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://developer.chrome.com/blog/inside-browser-part2/"&gt;Part 2: What happens in navigation&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://developer.chrome.com/blog/inside-browser-part3/"&gt;Part 3: Inner Workings of a Renderer Process&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://developer.chrome.com/blog/inside-browser-part4/"&gt;Part 4: Input is Coming to the Compositor&lt;/a&gt;&lt;/p&gt;</description><category>tech</category><category>web_browsers</category><guid>https://janetriley.net/notes/tech/how-browsers-work.html</guid><pubDate>Sun, 12 Jun 2022 20:48:53 GMT</pubDate></item><item><title>Dan Slimmon: An Incident Command Training Handbook</title><link>https://janetriley.net/notes/leadership/dan-slimmon-an-incident-command-training-handbook.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;Dan Slimmon: &lt;a href="https://blog.danslimmon.com/2019/06/24/an-incident-command-training-handbook/"&gt;An Incident Command Training Handbook&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;Summary&lt;/h2&gt;
&lt;p&gt;How to structure and lead an incident response. The five questions of a status update. How to manage information flow effectively.&lt;/p&gt;
&lt;p&gt;Slimmon's writing style is direct and simple. It's a mid-length article with some detail, but you could follow it
in a high-stress situation (like mid-incident) and benefit immediately. &lt;/p&gt;
&lt;p&gt;Best case scenario is to have the whole team read it ahead of time to understand the structure. 
When it's showtime everyone can slide into their roles and know their responsibilities. &lt;/p&gt;
&lt;h2&gt;Excerpts&lt;/h2&gt;
&lt;pre class="code literal-block"&gt;&lt;span class="nv"&gt;An&lt;/span&gt; &lt;span class="nv"&gt;Incident&lt;/span&gt; &lt;span class="nv"&gt;Commander&lt;/span&gt;’&lt;span class="nv"&gt;s&lt;/span&gt; &lt;span class="nv"&gt;job&lt;/span&gt; &lt;span class="nv"&gt;is&lt;/span&gt; &lt;span class="nv"&gt;to&lt;/span&gt; &lt;span class="nv"&gt;keep&lt;/span&gt; &lt;span class="nv"&gt;the&lt;/span&gt; &lt;span class="nv"&gt;incident&lt;/span&gt; &lt;span class="nv"&gt;moving&lt;/span&gt; &lt;span class="nv"&gt;toward&lt;/span&gt; &lt;span class="nv"&gt;resolution&lt;/span&gt;. 
&lt;span class="nv"&gt;But&lt;/span&gt; &lt;span class="nv"&gt;an&lt;/span&gt; &lt;span class="nv"&gt;Incident&lt;/span&gt; &lt;span class="nv"&gt;Commander&lt;/span&gt;’&lt;span class="nv"&gt;s&lt;/span&gt; &lt;span class="nv"&gt;job&lt;/span&gt; &lt;span class="nv"&gt;is&lt;/span&gt; &lt;span class="nv"&gt;not&lt;/span&gt; &lt;span class="nv"&gt;to&lt;/span&gt; &lt;span class="nv"&gt;fix&lt;/span&gt; &lt;span class="nv"&gt;the&lt;/span&gt; &lt;span class="nv"&gt;problem&lt;/span&gt;.

&lt;span class="nv"&gt;As&lt;/span&gt; &lt;span class="nv"&gt;Incident&lt;/span&gt; &lt;span class="nv"&gt;Commander&lt;/span&gt;, &lt;span class="nv"&gt;you&lt;/span&gt; &lt;span class="nv"&gt;shouldn&lt;/span&gt;’&lt;span class="nv"&gt;t&lt;/span&gt; &lt;span class="nv"&gt;touch&lt;/span&gt; &lt;span class="nv"&gt;a&lt;/span&gt; &lt;span class="nv"&gt;terminal&lt;/span&gt; &lt;span class="nv"&gt;or&lt;/span&gt; &lt;span class="nv"&gt;search&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="nv"&gt;a&lt;/span&gt; &lt;span class="nv"&gt;graph&lt;/span&gt; 
&lt;span class="nv"&gt;or&lt;/span&gt; &lt;span class="nv"&gt;kick&lt;/span&gt; &lt;span class="nv"&gt;off&lt;/span&gt; &lt;span class="nv"&gt;a&lt;/span&gt; &lt;span class="nv"&gt;deploy&lt;/span&gt; &lt;span class="nv"&gt;unless&lt;/span&gt; &lt;span class="nv"&gt;you&lt;/span&gt;’&lt;span class="nv"&gt;re&lt;/span&gt; &lt;span class="nv"&gt;absolutely&lt;/span&gt; &lt;span class="nv"&gt;the&lt;/span&gt; &lt;span class="nv"&gt;only&lt;/span&gt; &lt;span class="nv"&gt;person&lt;/span&gt; &lt;span class="nv"&gt;available&lt;/span&gt; &lt;span class="nv"&gt;to&lt;/span&gt; &lt;span class="k"&gt;do&lt;/span&gt; &lt;span class="nv"&gt;it&lt;/span&gt;. 
&lt;span class="nv"&gt;This&lt;/span&gt; &lt;span class="nv"&gt;may&lt;/span&gt; &lt;span class="nv"&gt;feel&lt;/span&gt; &lt;span class="nv"&gt;uncomfortable&lt;/span&gt;, &lt;span class="nv"&gt;especially&lt;/span&gt; &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="nv"&gt;your&lt;/span&gt; &lt;span class="nv"&gt;background&lt;/span&gt; &lt;span class="nv"&gt;is&lt;/span&gt; &lt;span class="nv"&gt;in&lt;/span&gt; &lt;span class="nv"&gt;engineering&lt;/span&gt;. 
&lt;span class="nv"&gt;It&lt;/span&gt; &lt;span class="nv"&gt;will&lt;/span&gt; &lt;span class="nv"&gt;probably&lt;/span&gt; &lt;span class="nv"&gt;feel&lt;/span&gt; &lt;span class="nv"&gt;like&lt;/span&gt; &lt;span class="nv"&gt;you&lt;/span&gt;’&lt;span class="nv"&gt;re&lt;/span&gt; &lt;span class="nv"&gt;not&lt;/span&gt; &lt;span class="nv"&gt;doing&lt;/span&gt; &lt;span class="nv"&gt;enough&lt;/span&gt; &lt;span class="nv"&gt;to&lt;/span&gt; &lt;span class="nv"&gt;help&lt;/span&gt;. 
&lt;span class="nv"&gt;What&lt;/span&gt; &lt;span class="nv"&gt;you&lt;/span&gt; &lt;span class="nv"&gt;need&lt;/span&gt; &lt;span class="nv"&gt;to&lt;/span&gt; &lt;span class="nv"&gt;remember&lt;/span&gt; &lt;span class="nv"&gt;is&lt;/span&gt; &lt;span class="nv"&gt;this&lt;/span&gt;: &lt;span class="nv"&gt;whatever&lt;/span&gt; &lt;span class="nv"&gt;your&lt;/span&gt; &lt;span class="nv"&gt;usual&lt;/span&gt; &lt;span class="nv"&gt;job&lt;/span&gt;, &lt;span class="nv"&gt;when&lt;/span&gt; &lt;span class="nv"&gt;you&lt;/span&gt;’&lt;span class="nv"&gt;re&lt;/span&gt; &lt;span class="nv"&gt;the&lt;/span&gt; &lt;span class="nv"&gt;Incident&lt;/span&gt; &lt;span class="nv"&gt;Commander&lt;/span&gt;, &lt;span class="nv"&gt;your&lt;/span&gt; &lt;span class="nv"&gt;job&lt;/span&gt; &lt;span class="nv"&gt;is&lt;/span&gt; &lt;span class="nv"&gt;to&lt;/span&gt; &lt;span class="nv"&gt;be&lt;/span&gt; &lt;span class="nv"&gt;the&lt;/span&gt; &lt;span class="nv"&gt;Incident&lt;/span&gt; &lt;span class="nv"&gt;Commander&lt;/span&gt;.
&lt;/pre&gt;
&lt;p&gt;&lt;code&gt;Managing information flow is the single most important responsibility of the Incident Commander.&lt;/code&gt;&lt;/p&gt;
&lt;h2&gt;Takeaways&lt;/h2&gt;
&lt;p&gt;Sometimes the most effective thing you can do is coordinate the experts. &lt;/p&gt;</description><category>communication</category><category>leadership</category><guid>https://janetriley.net/notes/leadership/dan-slimmon-an-incident-command-training-handbook.html</guid><pubDate>Thu, 26 May 2022 18:30:55 GMT</pubDate></item><item><title>John Graham: Building an Engineering Roadmap</title><link>https://janetriley.net/notes/leadership/john-graham-building-an-engineering-roadmap.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;John Graham: &lt;a href="https://johngrahamdev.com/Building-An-Engineering-Roadmap/"&gt;Maximize your team. How I created an Engineering Roadmap&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;Summary&lt;/h2&gt;
&lt;p&gt;Graham walks through creating his first engineering roadmap. Goals, format, ranking criteria.&lt;/p&gt;</description><category>leadership</category><category>planning</category><guid>https://janetriley.net/notes/leadership/john-graham-building-an-engineering-roadmap.html</guid><pubDate>Thu, 26 May 2022 18:07:36 GMT</pubDate></item><item><title>Nikola Resources</title><link>https://janetriley.net/notes/tech/nikola-resources.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;Nikola is the static site generator used to render this site. It's written in Python. &lt;/p&gt;
&lt;h2&gt;Getting Started&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://getnikola.com/handbook.html"&gt;The Nikola handbook&lt;/a&gt;
&lt;a href="https://getnikola.com/creating-a-site-not-a-blog-with-nikola.html"&gt;Creating a site (not a blog) with Nikola&lt;/a&gt;
&lt;a href="https://getnikola.com/creating-a-theme.html"&gt;Creating a Nikola theme&lt;/a&gt; and &lt;a href="https://getnikola.com/theming.html#built-in-templates"&gt;Theming&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;Plugins&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://miyakogi.github.io/blog_nikola/stories/extending/"&gt;Extending Nikola&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://bryanwweber.com/writing/2018-12-22-writing-task-plugins-for-nikola.html"&gt;Writing task plugins for Nikola&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://bryanwweber.com/writing/2018-12-20-controlling-plugin-task-execution-order.html"&gt;Controlling task execution order in Nikola&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Nikola uses &lt;a href="https://pydoit.org/"&gt;DoIt&lt;/a&gt;. Plugin classes are derived from DoIt Tasks. &lt;/p&gt;
&lt;h2&gt;Migrations&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://www.brainsorting.com/posts/create-a-blog-with-nikola/"&gt;Some practical details&lt;/a&gt; - adding search, 
enabling notebooks, teasers, auto-posting to other sites&lt;/p&gt;
&lt;p&gt;&lt;a href="https://jiaweizhuang.github.io/blog/nikola-guide/"&gt;More customization notes from Louis Tiao&lt;/a&gt;&lt;/p&gt;</description><category>nikola</category><category>tech</category><guid>https://janetriley.net/notes/tech/nikola-resources.html</guid><pubDate>Thu, 26 May 2022 17:33:41 GMT</pubDate></item><item><title>Docs for Developers: An Engineers Field Guide to Technical Writing</title><link>https://janetriley.net/notes/technical_communication/book_docs_for_developers.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;&lt;a href="https://docsfordevelopers.com/"&gt;Docs for Developers: An Engineer's Field Guide to Technical Writing&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://link.springer.com/book/10.1007/978-1-4842-7217-6"&gt;Publisher's Page&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Author: Jared Bhatti, David Nunez, Jen Lambourne, Zachary Sarah Corleissen, Heidi Waterhouse&lt;/p&gt;
&lt;h3&gt;Summary&lt;/h3&gt;
&lt;p&gt;How to write maintainable docs that help your customers use your software.&lt;/p&gt;
&lt;h3&gt;Excerpt&lt;/h3&gt;
&lt;p&gt;&lt;quote&gt;"Docs for Developers demystifies the process of creating great developer documentation, following a team of software developers as they work to launch a new product. At each step along the way, you learn through examples, templates, and principles how to create, measure, and maintain documentation, which you can adapt to the needs of your own organization."&lt;/quote&gt;&lt;/p&gt;
&lt;h3&gt;Takeaways&lt;/h3&gt;
&lt;p&gt;This struck me as the devops of documentation - turn these high level ideas into something we can live in. On my To Read pile. &lt;/p&gt;</description><category>books</category><category>communication</category><category>technical communication</category><category>technical writing</category><guid>https://janetriley.net/notes/technical_communication/book_docs_for_developers.html</guid><pubDate>Wed, 25 May 2022 17:00:00 GMT</pubDate></item><item><title>Gitlab: Technical Writing Fundamentals</title><link>https://janetriley.net/notes/technical_communication/gitlab__tech_writing_fundamentals.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;&lt;a href="https://about.gitlab.com/handbook/engineering/ux/technical-writing/fundamentals/"&gt;GitLab's Technical Writing Fundamentals course&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;Summary&lt;/h3&gt;
&lt;p&gt;Written to help contributors write and edit GitLab documentation. The first three parts are grammar and style guidance.
Session 4 covers how to approach four topic types: concepts, tasks, references, and troubleshooting. &lt;/p&gt;
&lt;p&gt;The page links to the recorded versions on YouTube.&lt;/p&gt;</description><category>communication</category><category>tech writing</category><category>technical communication</category><guid>https://janetriley.net/notes/technical_communication/gitlab__tech_writing_fundamentals.html</guid><pubDate>Wed, 25 May 2022 17:00:00 GMT</pubDate></item><item><title>Google: Tech Writing Resources for Developers</title><link>https://janetriley.net/notes/technical_communication/google__tech_writing_resources_for_developers.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;&lt;a href="https://developers.google.com/tech-writing"&gt;Google's Tech Writing Resources for Developers&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;Summary&lt;/h3&gt;
&lt;p&gt;Google's Technical writing courses and resources for engineers and engineer-adjacent folks. &lt;/p&gt;
&lt;h3&gt;Excerpt&lt;/h3&gt;
&lt;p&gt;"This collection of courses and learning resources aims to improve your technical documentation. Learn how to plan and author technical documents."&lt;/p&gt;</description><category>communication</category><category>tech writing</category><category>technical communication</category><guid>https://janetriley.net/notes/technical_communication/google__tech_writing_resources_for_developers.html</guid><pubDate>Wed, 25 May 2022 17:00:00 GMT</pubDate></item></channel></rss>