<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Lucas Pinto Blog</title>
		<link>https://lucaspinto.com/blog/</link>
		<description>Recent content on Lucas Pinto Blog</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Tue, 17 Mar 2026 00:00:00 -0300</lastBuildDate>
		
			<atom:link href="https://lucaspinto.com/blog/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>AI Adoption Is a People Problem, Not a Tools Problem</title>
				<link>https://lucaspinto.com/blog/posts/3-ai-adoption-struggles/</link>
				<pubDate>Tue, 17 Mar 2026 00:00:00 -0300</pubDate>
				<guid>https://lucaspinto.com/blog/posts/3-ai-adoption-struggles/</guid>
				<description>&lt;p&gt;Your company probably bought AI tools this year. It probably measured adoption by how many people logged in. And it&amp;rsquo;s probably confused about why nothing really changed.&lt;/p&gt;&#xA;&lt;p&gt;This is the pattern everywhere. BCG surveyed over 10,600 workers across 11 countries and found that 72% are using AI regularly &lt;a href=&#34;#sources&#34;&gt;[1]&lt;/a&gt;. Usage is up. Impact? Not so much. Most companies dropped AI into existing processes and expected magic. Only half actually redesigned workflows around the technology &lt;a href=&#34;#sources&#34;&gt;[1]&lt;/a&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The New Senior Engineer Skill: Knowing When NOT to Use AI</title>
				<link>https://lucaspinto.com/blog/posts/knowing-when-not-to-use-ai/</link>
				<pubDate>Fri, 13 Mar 2026 00:00:00 -0300</pubDate>
				<guid>https://lucaspinto.com/blog/posts/knowing-when-not-to-use-ai/</guid>
				<description>&lt;p&gt;Everyone in tech right now is trying to prove how much AI they&amp;rsquo;re using. I want to talk about the opposite.&lt;/p&gt;&#xA;&lt;p&gt;AI writes 30% of Microsoft&amp;rsquo;s code and a quarter of Google&amp;rsquo;s &lt;a href=&#34;#sources&#34;&gt;[1]&lt;/a&gt;. Meta is tying performance reviews to &amp;ldquo;AI-driven impact&amp;rdquo; &lt;a href=&#34;#sources&#34;&gt;[2]&lt;/a&gt;. Companies that announced AI strategies in 2023-2024 saw their stock prices jump over 6% compared to those that didn&amp;rsquo;t &lt;a href=&#34;#sources&#34;&gt;[3]&lt;/a&gt;. The incentives are loud and clear: more AI, faster, everywhere.&lt;/p&gt;&#xA;&lt;p&gt;I get it. I&amp;rsquo;m not naive about why this is happening. Investors want to see AI adoption metrics. Executives want to show them. When the market rewards you for saying &amp;ldquo;30% of our code is AI-generated,&amp;rdquo; you&amp;rsquo;re going to find ways to hit that number.&lt;/p&gt;</description>
			</item>
			<item>
				<title>15 Years of Building Software: What I&#39;d Tell Myself on Day One</title>
				<link>https://lucaspinto.com/blog/posts/advice-for-younger-devs/</link>
				<pubDate>Mon, 09 Feb 2026 17:39:20 -0300</pubDate>
				<guid>https://lucaspinto.com/blog/posts/advice-for-younger-devs/</guid>
				<description>&lt;p&gt;After 15 years of writing code, leading teams, and shipping products across startups and enterprises, I&amp;rsquo;ve finally decided to start writing. Not because I think the world needs another tech blog — but because the lessons I wish someone had told me earlier deserve to live somewhere other than my head.&lt;/p&gt;&#xA;&lt;p&gt;So here it is. The stuff I&amp;rsquo;d go back and tell junior-me if I could.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-code-is-never-the-hard-part&#34;&gt;The code is never the hard part&lt;/h2&gt;&#xA;&lt;p&gt;Early in my career, I thought being a great engineer meant writing the cleverest code. I optimized prematurely. I over-engineered. I built things that were technically impressive and practically useless.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
