<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Vladimir Izmalkov</title><link>https://izmalk.com/posts/</link><description>Recent content in Blog on Vladimir Izmalkov</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 12 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://izmalk.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>BusyRebar: a LED screen repeater for the BUSY Bar</title><link>https://izmalk.com/posts/busyrebar/</link><pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate><guid>https://izmalk.com/posts/busyrebar/</guid><description>&lt;p&gt;My &lt;a href="https://busy.app/" target="_blank"&gt;BUSY Bar&lt;/a&gt; belongs on my desk. That is where I can reach its buttons, use its timers, and read the secondary (black&amp;amp;white) display. But the best position for me to reach is not necessarily the best position for someone else to see its beautiful main (color) screen.&lt;/p&gt;
&lt;p&gt;Turning it towards the doorway makes it less convenient to use. Moving it outside the room would defeat the point of having it on my desk. So I want another screen that could show the same status somewhere more visible, near the entrance to my home office room, ideally, outside of it.&lt;/p&gt;</description></item><item><title>The Future of Documentation with AI</title><link>https://izmalk.com/posts/ai/</link><pubDate>Mon, 11 Mar 2024 09:14:08 +0000</pubDate><guid>https://izmalk.com/posts/ai/</guid><description>&lt;p&gt;🚀 The Future of Documentation: Ultra-Fast UX Meets AI Integration 🚀&lt;/p&gt;
&lt;p&gt;The demand for quick, efficient learning solutions has never been higher. As a professional technical writer, I’ve observed a significant shift towards ultra-fast learning—a modern trend where documentation is optimized for the fastest possible user experience (UX). This isn’t about the traditional, comprehensive journey through learning materials. Instead, it’s about delivering concise, immediately actionable knowledge with good navigation—perfect for the professional on the run. This approach caters to the modern learner’s desire to solve the task at hand rather than learn a new tool, enabling them to apply new knowledge without skipping a beat in their busy schedules.&lt;/p&gt;</description></item><item><title>Git</title><link>https://izmalk.com/posts/git/</link><pubDate>Mon, 04 Mar 2024 11:27:01 +0000</pubDate><guid>https://izmalk.com/posts/git/</guid><description>&lt;p&gt;💪The Power of Git for Technical Writers&lt;/p&gt;
&lt;p&gt;Git is a formidable tool known for its capacity to track changes and manage versions across all file types, especially plain text documents. For technical writers, Git opens up a world of possibilities, significantly boosting the efficiency and quality of documentation workflows while providing a dependable reference for software product details. Let’s delve into the top reasons why Git is so beneficial for technical writers.&lt;/p&gt;</description></item><item><title>Lightweight Markup Languages for Docs-as-Code</title><link>https://izmalk.com/posts/lightweight-markup-languages/</link><pubDate>Sun, 04 Feb 2024 10:31:05 +0000</pubDate><guid>https://izmalk.com/posts/lightweight-markup-languages/</guid><description>&lt;p&gt;In the innovative landscape of technical writing, the Docs-as-Code approach revolutionizes how we create, manage, and publish documentation. Central to this paradigm shift are three lightweight markup languages: Markdown, reStructuredText, and AsciiDoc. Each brings its unique strengths to the forefront, enabling seamless integration of documentation into the software development workflow.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Markdown&lt;/strong&gt; stands out for its simplicity and widespread adoption. From GitHub repositories to blogging platforms, its straightforward syntax ensures that documentation is easily readable by humans and machines alike, making it the go-to choice for quick, effective content creation.&lt;/p&gt;</description></item><item><title>Technical writing: Balancing Inspiration with Precision</title><link>https://izmalk.com/posts/balance/</link><pubDate>Sun, 21 Jan 2024 20:24:07 +0000</pubDate><guid>https://izmalk.com/posts/balance/</guid><description>&lt;p&gt;📝✨ In the world of sophisticated open-source products, we often find ourselves walking a tightrope between two seemingly conflicting goals: crafting &lt;strong&gt;comprehensive and accurate&lt;/strong&gt; documentation and ensuring that it’s &lt;strong&gt;engaging and inspiring&lt;/strong&gt; for our readers. This balancing act presents a unique set of challenges that I&amp;rsquo;ve come to appreciate in my journey as a technical writer.&lt;/p&gt;
&lt;p&gt;🔍 &lt;strong&gt;Precision vs. Engagement&lt;/strong&gt;: The core challenge lies in presenting technical information in a precise, comprehensive, yet captivating way. When documentation for an open-source product becomes overly intricate and packed with specifics, we risk losing those readers who may lack the time or motivation to delve deep. Yet, we risk alienating readers and losing their trust by making it less accurate and more engaging. At the heart of good technical writing is the delicate task of weaving together technical accuracy with engaging educational content. It&amp;rsquo;s about finding that sweet spot – where comprehensiveness meets readability, making the reader feel confident and interested, not overwhelmed.&lt;/p&gt;</description></item><item><title>Embracing the Docs-as-Code Approach in Software Documentation</title><link>https://izmalk.com/posts/docs-as-code/</link><pubDate>Sun, 14 Jan 2024 20:14:17 +0000</pubDate><guid>https://izmalk.com/posts/docs-as-code/</guid><description>&lt;p&gt;As a technical writer with more than a decade of experience in software development, I&amp;rsquo;ve come to embrace the Docs-as-Code methodology as my preferred approach. This technique, borrowing best practices from software development, transforms the way we handle documentation, treating it much like we do code. It usually involves storing the content in a Git repository as a text file. Our user-facing documentation needs to undergo a building process to create the output format(s) needed: HTML (web page), PDF, &lt;code&gt;.docx&lt;/code&gt;, etc.&lt;/p&gt;</description></item><item><title>Portfolio</title><link>https://izmalk.com/posts/portfolio/</link><pubDate>Thu, 25 Aug 2022 23:53:01 +0300</pubDate><guid>https://izmalk.com/posts/portfolio/</guid><description>&lt;p&gt;This will be a page with links to multiple examples of my finest work.
Unfortunately, it is not ready yet =D.&lt;/p&gt;
&lt;p&gt;You see, most of my current documents are under NDA, so I will try and do some test exercises without any confidential materials and publish them here.&lt;/p&gt;
&lt;p&gt;But for now, I would like to publish a &lt;a href="https://github.com/tarantool/doc/blame/3c348038efb765f87d2162e0542d3a17092d3c1d/doc/reference/reference_rock/vshard/vshard_architecture.rst" target="_blank"&gt;link&lt;/a&gt; to one example of my open-source contribution.&lt;/p&gt;</description></item><item><title>Analytics and information structuring</title><link>https://izmalk.com/posts/analytics/</link><pubDate>Sun, 14 Aug 2022 00:00:03 +0000</pubDate><guid>https://izmalk.com/posts/analytics/</guid><description>&lt;p&gt;I am efficient in learning new technologies and processing vast amounts of data. I have a lot of experience with structuring, formalising, and simplifying information.&lt;/p&gt;</description></item><item><title>Passion for learning</title><link>https://izmalk.com/posts/passion-for-learning/</link><pubDate>Sun, 14 Aug 2022 00:00:02 +0000</pubDate><guid>https://izmalk.com/posts/passion-for-learning/</guid><description>&lt;p&gt;My deepest passion is learning new technologies, products, and user experiences. I am eager to learn, whether it&amp;rsquo;s a new framework, new hardware architecture, or a new web interface.&lt;/p&gt;</description></item><item><title>Team leadership</title><link>https://izmalk.com/posts/team-leadership/</link><pubDate>Sun, 14 Aug 2022 00:00:01 +0000</pubDate><guid>https://izmalk.com/posts/team-leadership/</guid><description>&lt;p&gt;I had two chances to lead a team in my life. Both times I created cross-functional teams of highly-skilled professionals from scratch — teams that I can be proud of.&lt;/p&gt;</description></item><item><title>Documentation engineering</title><link>https://izmalk.com/posts/documentation-engineering/</link><pubDate>Sun, 14 Aug 2022 00:00:00 +0000</pubDate><guid>https://izmalk.com/posts/documentation-engineering/</guid><description>&lt;p&gt;Every word is a bridge, and every page is an invitation to a better user experience.&lt;/p&gt;</description></item><item><title>Very first post to this blog</title><link>https://izmalk.com/posts/first-post/</link><pubDate>Mon, 17 Jun 2013 12:00:00 +0000</pubDate><guid>https://izmalk.com/posts/first-post/</guid><description>&lt;p&gt;This is the very first blog post here, as this site is mostly under construction.&lt;/p&gt;
&lt;p&gt;I am trying to create content here as soon as possible. But it is hard to do when all you have are some scraps of time between work and sleep.&lt;/p&gt;
&lt;p&gt;As of now, I am still working on portal features and looking for better ways to visualise my experience and education here.&lt;/p&gt;
&lt;p&gt;I also have a grand plan for content: a portfolio with some test documents that I wrote, and this blog with insights on the technical documentation industry and technologies.&lt;/p&gt;</description></item></channel></rss>