<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Lev Kazakov on Medium]]></title>
        <description><![CDATA[Stories by Lev Kazakov on Medium]]></description>
        <link>https://medium.com/@lev.kazakov?source=rss-9a8e111a4d54------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*06XjDQ-UyskUCwcGroN7iA.jpeg</url>
            <title>Stories by Lev Kazakov on Medium</title>
            <link>https://medium.com/@lev.kazakov?source=rss-9a8e111a4d54------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:26:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lev.kazakov/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Mitigating Context Switches]]></title>
            <link>https://medium.com/@lev.kazakov/mitigating-context-switches-37e330377c1d?source=rss-9a8e111a4d54------2</link>
            <guid isPermaLink="false">https://medium.com/p/37e330377c1d</guid>
            <category><![CDATA[focus]]></category>
            <category><![CDATA[google-apps-script]]></category>
            <category><![CDATA[context-switch]]></category>
            <category><![CDATA[on-call]]></category>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[Lev Kazakov]]></dc:creator>
            <pubDate>Mon, 25 Jun 2018 09:48:14 GMT</pubDate>
            <atom:updated>2018-06-25T17:14:45.559Z</atom:updated>
            <content:encoded><![CDATA[<h4>A simple solution for an everyday problem</h4><p>Complicated tasks require a great deal of concentration.</p><p>When someone interrupts you in the middle of a task, that’s a context switch.<br>Content switches are in general unpleasant, and in a team level, can hurt velocity.</p><p>One type of disruptions we find often in our working environment is of the following nature:<br>A person enters your room and issues a question into the void.<br>After a couple of seconds, you realise your teammates have abandoned you in this frontier, and you hop into a 30min–1hr adventure of explaining the essence of your domain to this anonymous person.</p><p>In our team, we solved this issue by introducing a new On Call schedule, dedicated to these type of disruptions.</p><p>We found that having one team member assigned for this task every day decreases tension between teammates, contributes to knowledge sharing, increases happiness (especially when today is not your shift) and improves the level of service to other teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/1*l1CxYrbWkF4EEElkc0YsYg.png" /></figure><p>Wanna get started? Check out the following <a href="https://script.google.com/d/148poVkm9pvuqRfbgriPv9cUnwUwhMz-FW7UiYJByzJTY4qee4g5G0m51/edit?usp=sharing">Google Apps Script &lt;&gt; Slack integration</a>. With this script, you will be able to notify on callers via Slack once their shift starts, and query Slack for the current on caller with a Slack <a href="https://slack.com/apps/A0F82E8CA-slash-commands">Slash Command</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37e330377c1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build, develop and debug Node.js source code on macOS]]></title>
            <link>https://medium.com/@lev.kazakov/build-develop-and-debug-node-js-source-code-on-macos-e155ad451986?source=rss-9a8e111a4d54------2</link>
            <guid isPermaLink="false">https://medium.com/p/e155ad451986</guid>
            <category><![CDATA[clion]]></category>
            <category><![CDATA[macos]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[gyp]]></category>
            <category><![CDATA[cmake]]></category>
            <dc:creator><![CDATA[Lev Kazakov]]></dc:creator>
            <pubDate>Tue, 27 Feb 2018 21:25:12 GMT</pubDate>
            <atom:updated>2018-03-28T11:06:03.405Z</atom:updated>
            <content:encoded><![CDATA[<p>TL;DR: Follow <a href="https://github.com/lev-kazakov/node-cmake-generator#instructions">these</a> instructions.</p><p>You’ve decided to contribute to <a href="https://github.com/nodejs/node">Node.js</a> source.<br>Wait, not so fast, you just want to debug the source code in search for enlightenment.<br>If you’re a mac person, Visual Studio is out of reach.<br>If you’re an IDE person, you’d wanna go for JetBrains <a href="https://www.jetbrains.com/clion/">CLion</a>. But…</p><p>Node uses <a href="https://gyp.gsrc.io/">gyp</a> as its build system, <br>and no IDE for mac is known to support gyp, not even CLion :(</p><p>Luckily, CLion supports the <a href="https://cmake.org/">CMake</a> build system, and with some tricks and tweaks, it is possible to make gyp output a compatible CMake config.</p><p>These tricks and tweaks are now wrapped and published as an npm module, under the name ‘<a href="https://www.npmjs.com/package/node-cmake-generator">node-cmake-generator</a>’.</p><p>To get started, type in the following commands:</p><pre>git clone <a href="/service/mailto:git@github.com">git@github.com</a>:nodejs/node.git<br>cd node<br>npm install -g node-cmake-generator<br>node-cmake-generator</pre><p>Now open Clion, build the <em>node</em> target, enjoy :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e155ad451986" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>