<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Productivity on {IT}</title><link>https://igortkanov.com/computers/productivity/</link><description>Recent content in Productivity on {IT}</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2026 {IT}. All rights reserved. Unless otherwise stated, all text, images, diagrams, and other original content on this blog may not be reproduced, distributed, or used without prior written permission.</copyright><lastBuildDate>Mon, 25 May 2026 19:19:04 +0000</lastBuildDate><atom:link href="https://igortkanov.com/computers/productivity/index.xml" rel="self" type="application/rss+xml"/><item><title>STATUS.md: a shared file for multi-agent work</title><link>https://igortkanov.com/status-md-for-multi-agent-work/</link><pubDate>Mon, 25 May 2026 19:19:04 +0000</pubDate><guid>https://igortkanov.com/status-md-for-multi-agent-work/</guid><description>&lt;p&gt;When I work on a bigger task – a new feature, a Terraform change, a small PoC – I usually run it across multiple agents at once. Claude Code in one window for the code, a Cowork session in another for planning and content, sometimes Desktop Claude in a third.&lt;/p&gt;
&lt;p&gt;The split works well until I switch between them and have to type some flavour of &amp;ldquo;where are we?&amp;rdquo; so the agent can guess. Each one has its own TODO list. None of them can see the others&amp;rsquo;. And so I end up as the human message bus, with the context windows filling up with status updates instead of actual work.&lt;/p&gt;</description></item><item><title>Billion-dollar brains: the real cost of AI</title><link>https://igortkanov.com/the-real-cost-of-ai/</link><pubDate>Mon, 26 May 2025 19:31:59 +0000</pubDate><guid>https://igortkanov.com/the-real-cost-of-ai/</guid><description>&lt;p&gt;AI-assisted coding feels like magic. You type what you want, and out comes working code. (well, maybe after a few hours of setup – but still)&lt;/p&gt;
&lt;p&gt;Like all magic, though, it has a cost. And right now, that cost is mostly hidden – even as the invoices show up every month. What makes it work is a stack of expensive infrastructure: thousands of GPUs, power-hungry data centers, and cloud contracts worth billions.&lt;/p&gt;</description></item><item><title>A convenient homelab SSH jumphost (without the drama)</title><link>https://igortkanov.com/convenient-homelab-ssh-jumphost/</link><pubDate>Sat, 08 Mar 2025 06:44:00 +0000</pubDate><guid>https://igortkanov.com/convenient-homelab-ssh-jumphost/</guid><description>&lt;p&gt;Managing a homelab is all fun and games until you&amp;rsquo;re knee-deep in IP addresses, SSH keys, and trying to remember if &lt;em&gt;this&lt;/em&gt; server was the one with Kubernetes or the one you broke last Tuesday.&lt;/p&gt;
&lt;p&gt;SSH-ing into multiple machines gets messy fast – unless you love memorizing IPs and usernames like some sort of 2000s hacker movie character.&lt;/p&gt;
&lt;p&gt;I didn&amp;rsquo;t 🤷‍♂️&lt;/p&gt;
&lt;p&gt;So, I set out to build an SSH jumphost that keeps a list of all servers and lets me connect to any of them by simply picking a friendly name from a menu. No more mental gymnastics – let me show you how I did it.&lt;/p&gt;</description></item><item><title>Passkeys – the future of secure authentication</title><link>https://igortkanov.com/passkeys-the-future-of-secure-authentication/</link><pubDate>Mon, 02 Dec 2024 13:44:25 +0000</pubDate><guid>https://igortkanov.com/passkeys-the-future-of-secure-authentication/</guid><description>&lt;p&gt;As a long-term fan of &lt;strong&gt;&lt;a href="https://www.yubico.com" target="_blank" rel="noopener noreferrer"&gt;Yubikeys&lt;/a&gt;&lt;/strong&gt;, I quickly got curious about this relatively new concept called &amp;ldquo;&lt;strong&gt;passkeys&lt;/strong&gt;&amp;rdquo;. Big companies like Apple, Amazon, and Mastercard are nudging their users to adopt passkeys and use them instead of passwords. The &lt;em&gt;&amp;ldquo;instead of passwords&amp;rdquo;&lt;/em&gt; part really got me curious!&lt;/p&gt;
&lt;p&gt;&lt;figure class="alignright" style="max-width:322px"&gt;&lt;img src="https://igortkanov.com/passkeys-the-future-of-secure-authentication/yubikdy.jpg" alt="" width="322" loading="lazy"&gt;&lt;/figure&gt;&lt;/p&gt;
&lt;p&gt;Since forever, passwords have been a part of our online lives for as long as we can remember. But let&amp;rsquo;s be honest: most of us have a &lt;em&gt;love-hate&lt;/em&gt; relationship with them. They&amp;rsquo;re either too easy to guess or so complex that we forget them entirely. Yes, even if it&amp;rsquo;s just one master password to a password vault like Bitwarden or LastPass.&lt;/p&gt;</description></item><item><title>Say “yes” to SBOMs!</title><link>https://igortkanov.com/say-yes-to-sboms/</link><pubDate>Fri, 22 Nov 2024 14:11:03 +0000</pubDate><guid>https://igortkanov.com/say-yes-to-sboms/</guid><description>&lt;p&gt;&lt;strong&gt;Picture this&lt;/strong&gt;: your software application is running smoothly in production, serving thousands of users. Then, you hear about a new critical vulnerability affecting open-source libraries, and panic sets in. Is your application exposed? If so, which part is at risk? Without a clear map of your software’s components, answering these questions can feel like searching for a needle in a haystack.&lt;/p&gt;
&lt;p&gt;This is where a &lt;strong&gt;Software bill of materials&lt;/strong&gt;, or SBOM, becomes invaluable. An SBOM is like a recipe list for your software, cataloging every ingredient − libraries, dependencies, and components making up your application. Just as food labels provide transparency (‑ish) about what you’re consuming, an SBOM ensures full visibility into what’s inside your apps.&lt;/p&gt;</description></item><item><title>Getting things done with to-do lists</title><link>https://igortkanov.com/to-do-lists-for-work/</link><pubDate>Mon, 18 Jul 2022 03:23:00 +0000</pubDate><guid>https://igortkanov.com/to-do-lists-for-work/</guid><description>&lt;p&gt;Is this another piece on to-do lists? Yes and no: we will cover the topic of using a to-do list for work, however, from a highly practical standpoint.&lt;/p&gt;
&lt;p&gt;&lt;figure class="alignright" style="max-width:214px"&gt;&lt;img src="https://igortkanov.com/to-do-lists-for-work/pexels-natalie-dupin-8724275-638x1024.jpg" alt="" width="214" loading="lazy"&gt;&lt;/figure&gt;&lt;/p&gt;
&lt;p&gt;Thinking about it, the human brain did not evolve to keep track of the jillion things we think about daily, but we still expect it to remember tasks from the three projects at work, home chores, social follow-ups, free time activities, and much more. And let&amp;rsquo;s not forget we want it all structured and prioritized.&lt;/p&gt;</description></item></channel></rss>