<?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>Career on Egor Lynko</title>
    <link>https://yegor.me/tags/career/</link>
    <description>Recent content in Career on Egor Lynko</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 10 Jan 2026 21:26:18 +0100</lastBuildDate>
    <atom:link href="https://yegor.me/tags/career/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>My 2025 wrap-up and a look into 2026</title>
      <link>https://yegor.me/posts/my-2025-wrap-up-and-a-look-into-2026/</link>
      <pubDate>Sat, 10 Jan 2026 21:26:18 +0100</pubDate>
      <guid>https://yegor.me/posts/my-2025-wrap-up-and-a-look-into-2026/</guid>
      <description>&lt;p&gt;It’s been quite a while since my last post here. Honestly, 2025 was an incredibly overwhelming year for me professionally. I finally found the time to sit down and write this slightly delayed wrap-up, reflecting on what happened and where it’s all heading.&lt;/p&gt;
&lt;p&gt;The biggest shift for me was not just that AI tools became better, but that my role started changing around them: from writing more code myself to organizing work, context, quality, and small agent-driven workflows. This post is my attempt to make sense of that shift: the productivity gains, the stress, the documentation paradox, and why I think 2026 will be less about hype and more about control.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
