<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on Evgeniy Balashov</title><link>https://balashov.tech/en/posts/</link><description>Recent content in Posts on Evgeniy Balashov</description><generator>Hugo</generator><language>en-us</language><managingEditor>contact@balashov.tech (Evgeniy Balashov)</managingEditor><webMaster>contact@balashov.tech (Evgeniy Balashov)</webMaster><lastBuildDate>Tue, 31 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://balashov.tech/en/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Speed of writing code has never been a problem</title><link>https://balashov.tech/en/posts/2026/03/speed-of-writing-code-has-never-been-a-problem/</link><pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate><author>contact@balashov.tech (Evgeniy Balashov)</author><guid>https://balashov.tech/en/posts/2026/03/speed-of-writing-code-has-never-been-a-problem/</guid><description>&lt;h2 id="the-mirage-of-optimization-or-goldratt-already-said-it-all"&gt;The Mirage of Optimization, or Goldratt Already Said It All&lt;/h2&gt;
&lt;p&gt;As the creator of the
&lt;a href="https://ru.wikipedia.org/wiki/%D0%A2%D0%B5%D0%BE%D1%80%D0%B8%D1%8F_%D0%BE%D0%B3%D1%80%D0%B0%D0%BD%D0%B8%D1%87%D0%B5%D0%BD%D0%B8%D0%B9"&gt;Theory of Constraints&lt;/a&gt;
—
&lt;a href="https://ru.wikipedia.org/wiki/%D0%93%D0%BE%D0%BB%D0%B4%D1%80%D0%B0%D1%82%D1%82,_%D0%AD%D0%BB%D0%B8%D1%8F%D1%85%D1%83"&gt;Eliyahu Goldratt&lt;/a&gt;
— said:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&amp;ldquo;An hour saved anywhere other than the bottleneck is a mirage.&amp;rdquo;&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;optimization outside bottlenecks: improving the work of tools, processes, and
people that are not constraints leads to more work in progress and higher
costs&lt;/li&gt;
&lt;li&gt;focus on constraints: a system&amp;rsquo;s effectiveness is determined by the
performance of its weakest link&lt;/li&gt;
&lt;li&gt;exploiting the constraint: instead of optimizing everything, you should first
identify and eliminate the bottleneck. Real savings appear only when the
bottleneck itself is optimized&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In other words, when you optimize a stage that is not the bottleneck, you do not
get a faster system. You get a less efficient system.&lt;/p&gt;</description></item><item><title>Writing Code by Hand Is a Thing of the Past</title><link>https://balashov.tech/en/posts/2026/03/writing-code-by-hand-is-a-thing-of-the-past/</link><pubDate>Wed, 11 Mar 2026 00:00:00 +0000</pubDate><author>contact@balashov.tech (Evgeniy Balashov)</author><guid>https://balashov.tech/en/posts/2026/03/writing-code-by-hand-is-a-thing-of-the-past/</guid><description>&lt;p&gt;The software development landscape is changing rapidly, right now.&lt;/p&gt;
&lt;p&gt;I have spent more than 15 years working in IT engineering.&lt;br&gt;
I use AI tools actively every day in my work: for building internal tools, automation, analytics, and infrastructure management.&lt;/p&gt;
&lt;p&gt;Over the past year, the nature and intensity of the part of my work related to writing code has changed significantly.&lt;/p&gt;
&lt;p&gt;Very soon, we will look back on writing code by hand as a fond memory from the past — and we will miss it.&lt;/p&gt;</description></item></channel></rss>