<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Gábor Till</title>
    <description>The latest articles on DEV Community by Gábor Till (@gabor-till).</description>
    <link>https://dev.to/gabor-till</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3470834%2F1c4e90e1-7bb1-4dc9-860b-524f90abd3f5.jpg</url>
      <title>DEV Community: Gábor Till</title>
      <link>https://dev.to/gabor-till</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/gabor-till"/>
    <language>en</language>
    <item>
      <title>Want to be a tech lead, but don’t know how to get started?</title>
      <dc:creator>Gábor Till</dc:creator>
      <pubDate>Mon, 15 Dec 2025 13:57:15 +0000</pubDate>
      <link>https://dev.to/gabor-till/want-to-be-a-tech-lead-but-dont-know-how-to-get-started-5fbf</link>
      <guid>https://dev.to/gabor-till/want-to-be-a-tech-lead-but-dont-know-how-to-get-started-5fbf</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fq3ldczgfc3lww03exjro.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fq3ldczgfc3lww03exjro.png" alt="Tips to start leading in tech" width="800" height="560"&gt;&lt;/a&gt;I moved from developer to team lead and ran into chaos: missed deadlines, team conflict, and endless overtime. Jumping into a leadership role without experience backfired, and I made a bunch of mistakes.&lt;/p&gt;

&lt;p&gt;The truth is, those mistakes could have been avoided if I’d built a few leadership skills first – and you can do the same. There are three simple things any developer can try now to gain real leadership experience before getting the title.&lt;/p&gt;

&lt;p&gt;If you’re interested in what those steps are, read the short article I wrote on my newly revamped site.&lt;/p&gt;

&lt;p&gt;👉 &lt;a href="https://www.gabortill.com/posts/i-want-to-be-a-leader" rel="noopener noreferrer"&gt;https://www.gabortill.com/posts/i-want-to-be-a-leader&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>The Developer’s Handbook: Thriving When Promotions Don’t Exist</title>
      <dc:creator>Gábor Till</dc:creator>
      <pubDate>Mon, 06 Oct 2025 08:37:28 +0000</pubDate>
      <link>https://dev.to/gabor-till/the-developers-handbook-thriving-when-promotions-dont-exist-hm5</link>
      <guid>https://dev.to/gabor-till/the-developers-handbook-thriving-when-promotions-dont-exist-hm5</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8hp402hp0dqjitsh1jdt.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8hp402hp0dqjitsh1jdt.png" alt="Career fulfillment through skills and network" width="800" height="800"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Ever felt stuck because your org doesn’t have a traditional ladder?&lt;/p&gt;

&lt;p&gt;I just published a concise guide that shows you how to &lt;strong&gt;own your growth&lt;/strong&gt; without waiting for a new title. Here’s a taste of what you’ll find:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Define your own “growth”&lt;/strong&gt; – skill, impact, and visibility goals.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Quarterly roadmaps&lt;/strong&gt; – pick a focus, set a success metric, iterate.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mentor hunting&lt;/strong&gt; – peer, cross‑team, or reverse mentors.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Showcase wins&lt;/strong&gt; – weekly updates, monthly demos, internal blogs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Stretch assignments&lt;/strong&gt; – treat them like mini‑promotions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reflect &amp;amp; iterate&lt;/strong&gt; – monthly reviews, quarterly reflections, leader check‑ins.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;👉 &lt;strong&gt;Read the full article here:&lt;/strong&gt; &lt;a href="https://techleadmastery.substack.com/p/developers-handbook-thriving-without-promotions" rel="noopener noreferrer"&gt;https://techleadmastery.substack.com/p/developers-handbook-thriving-without-promotions&lt;/a&gt;&lt;/p&gt;

</description>
      <category>career</category>
      <category>productivity</category>
      <category>mentorship</category>
      <category>programming</category>
    </item>
    <item>
      <title>Clean code = Happy teams! But how?</title>
      <dc:creator>Gábor Till</dc:creator>
      <pubDate>Tue, 23 Sep 2025 09:58:20 +0000</pubDate>
      <link>https://dev.to/gabor-till/clean-code-happy-teams-but-how-57k0</link>
      <guid>https://dev.to/gabor-till/clean-code-happy-teams-but-how-57k0</guid>
      <description>&lt;p&gt;Tech debt creeps in when we ship fast without looking ahead. However, this often results in slower development cycles, endless bug fixes, and frustrated teammates.&lt;/p&gt;

&lt;p&gt;Here is how to start today:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Tag every debt item in the backlog with a label and log its impact.&lt;/li&gt;
&lt;li&gt;Reserve 10‑20% of each sprint for debt tickets—treat them like any feature story.&lt;/li&gt;
&lt;li&gt;Add quality gates in CI (lint, complexity, coverage) so bad code can’t slip through.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Want the full playbook—real‑world examples, step‑by‑step checklists, and metrics to prove the impact? Check out the article on &lt;a href="https://techleadmastery.substack.com/p/tech-debt-management" rel="noopener noreferrer"&gt;techleadmastery.substack.com/p/tech-debt-management&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>cleancode</category>
      <category>techdebt</category>
    </item>
    <item>
      <title>95% of AI Pilots Crash – Engineers are paying the price</title>
      <dc:creator>Gábor Till</dc:creator>
      <pubDate>Mon, 08 Sep 2025 08:24:50 +0000</pubDate>
      <link>https://dev.to/gabor-till/95-of-ai-pilots-crash-engineers-are-paying-the-price-ifk</link>
      <guid>https://dev.to/gabor-till/95-of-ai-pilots-crash-engineers-are-paying-the-price-ifk</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ffupcdhgw4t89qjsdcdy1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ffupcdhgw4t89qjsdcdy1.png" alt="AI pilot projects often fail to deliver ROI" width="800" height="671"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A fresh MIT study just uncovered a shocking truth: $35‑40 B spent on AI pilots, and 9‑out‑of‑10 deliver zero ROI.&lt;/p&gt;

&lt;p&gt;Why do so many experiments stall?&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Scope creep – trying to solve everything at once dilutes impact.&lt;/li&gt;
&lt;li&gt;In‑house models – custom builds eat time, talent, and budget.&lt;/li&gt;
&lt;li&gt;Wrong targets – low‑value, high‑visibility tasks rarely pay off.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The winning formula is to pick one narrow problem, grab a battle‑tested off‑the‑shelf tool, and set a clear KPI. Teams that did this turned no revenue into $20 M in a year.&lt;/p&gt;

&lt;p&gt;Check the AI Disaster Report article, a practical checklist, and a ready-to-copy email template to help you avoid common pitfalls in your next AI experiment.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://techleadmastery.substack.com/p/ai-disaster-report-95-percent-pilots-fail-checklist" rel="noopener noreferrer"&gt;https://techleadmastery.substack.com/p/ai-disaster-report-95-percent-pilots-fail-checklist&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to organize an effective, 30-min retro as a dev</title>
      <dc:creator>Gábor Till</dc:creator>
      <pubDate>Sun, 31 Aug 2025 09:40:39 +0000</pubDate>
      <link>https://dev.to/gabor-till/how-to-organize-an-effective-30-min-retro-as-a-dev-lb9</link>
      <guid>https://dev.to/gabor-till/how-to-organize-an-effective-30-min-retro-as-a-dev-lb9</guid>
      <description>&lt;p&gt;Ever walked out of a retro feeling like nothing changed? 🙋‍♂️ I had the same conversation with a lead dev—great ideas, but no follow‑up.&lt;/p&gt;

&lt;p&gt;The trick? A 30‑minute retro that ends with just one or two clear actions and an owner for each.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Warm‑up &amp;amp; goal reminder&lt;/li&gt;
&lt;li&gt;Quick check‑in on past actions&lt;/li&gt;
&lt;li&gt;Silent brainstorm&lt;/li&gt;
&lt;li&gt;Voting on top pain points&lt;/li&gt;
&lt;li&gt;Define the next steps and lock them in&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Check out the detailed flow in my article 👇&lt;br&gt;
&lt;a href="https://techleadmastery.substack.com/p/sprint-retro-flow-boost-velocity" rel="noopener noreferrer"&gt;techleadmastery.substack.com/p/sprint-retro-flow-boost-velocity&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>scrum</category>
      <category>performance</category>
    </item>
  </channel>
</rss>
