<?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 Nico Anastasio on Medium]]></title>
        <description><![CDATA[Stories by Nico Anastasio on Medium]]></description>
        <link>https://medium.com/@anastasionico?source=rss-8f4cd41336f5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Xyn4Urw3fyNSWyN6</url>
            <title>Stories by Nico Anastasio on Medium</title>
            <link>https://medium.com/@anastasionico?source=rss-8f4cd41336f5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:08:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anastasionico/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[I Wouldn’t Learn to Code the Same Way in the Age of AI]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/predict/i-wouldnt-learn-to-code-the-same-way-in-the-age-of-ai-db2c4d613956?source=rss-8f4cd41336f5------2"><img src="https://cdn-images-1.medium.com/max/2600/0*-PVxcsjFKllo5Uke" width="8103"></a></p><p class="medium-feed-snippet">If I could go back and start learning software development today, I wouldn&#x2019;t do it the same way.</p><p class="medium-feed-link"><a href="https://medium.com/predict/i-wouldnt-learn-to-code-the-same-way-in-the-age-of-ai-db2c4d613956?source=rss-8f4cd41336f5------2">Continue reading on Predict »</a></p></div>]]></description>
            <link>https://medium.com/predict/i-wouldnt-learn-to-code-the-same-way-in-the-age-of-ai-db2c4d613956?source=rss-8f4cd41336f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/db2c4d613956</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Nico Anastasio]]></dc:creator>
            <pubDate>Tue, 22 Sep 2026 17:56:12 GMT</pubDate>
            <atom:updated>2026-09-22T17:56:12.258Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[AI Won’t Take Your Job. But Another Developer Using AI Might]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/predict/ai-wont-take-your-job-but-another-developer-using-ai-might-eb1149421714?source=rss-8f4cd41336f5------2"><img src="https://cdn-images-1.medium.com/max/2600/0*Pj35NJTSBsAUReeA" width="6000"></a></p><p class="medium-feed-snippet">A few years ago, I would have laughed if someone told me that I could work on a new application from discovery to production in a week.</p><p class="medium-feed-link"><a href="https://medium.com/predict/ai-wont-take-your-job-but-another-developer-using-ai-might-eb1149421714?source=rss-8f4cd41336f5------2">Continue reading on Predict »</a></p></div>]]></description>
            <link>https://medium.com/predict/ai-wont-take-your-job-but-another-developer-using-ai-might-eb1149421714?source=rss-8f4cd41336f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb1149421714</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Nico Anastasio]]></dc:creator>
            <pubDate>Wed, 16 Sep 2026 01:20:49 GMT</pubDate>
            <atom:updated>2026-09-16T01:20:49.091Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[You Don’t Need to Solve 500 LeetCode Problems to Get a Software Job]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/codex/you-dont-need-to-solve-500-leetcode-problems-to-get-a-software-job-1ba8d1807c13?source=rss-8f4cd41336f5------2"><img src="https://cdn-images-1.medium.com/max/2600/0*nr0kvAXW-NDuxf7I" width="6000"></a></p><p class="medium-feed-snippet">I solved fewer than 100 LeetCode problems.</p><p class="medium-feed-link"><a href="https://medium.com/codex/you-dont-need-to-solve-500-leetcode-problems-to-get-a-software-job-1ba8d1807c13?source=rss-8f4cd41336f5------2">Continue reading on CodeX »</a></p></div>]]></description>
            <link>https://medium.com/codex/you-dont-need-to-solve-500-leetcode-problems-to-get-a-software-job-1ba8d1807c13?source=rss-8f4cd41336f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ba8d1807c13</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leetcode]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Nico Anastasio]]></dc:creator>
            <pubDate>Sun, 23 Aug 2026 20:46:01 GMT</pubDate>
            <atom:updated>2026-08-23T20:46:01.190Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[If I Were a Junior Developer in 2026, I’d Be Worried About This]]></title>
            <link>https://medium.com/predict/if-i-were-a-junior-developer-in-2026-id-be-worried-about-this-4ebe035801c0?source=rss-8f4cd41336f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ebe035801c0</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Nico Anastasio]]></dc:creator>
            <pubDate>Tue, 18 Aug 2026 19:53:04 GMT</pubDate>
            <atom:updated>2026-08-18T19:53:04.221Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*R9ceBmVnTKclKoEr" /><figcaption>Photo by <a href="https://unsplash.com/@resumegenius?utm_source=medium&amp;utm_medium=referral">Resume Genius</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When I was starting my career, becoming a junior developer meant one thing:</p><p><strong>You needed to learn how to code.</strong></p><p>That was the entry ticket.</p><p>You didn’t need to know everything. You didn’t need to be particularly fast. You certainly didn’t need to understand every architectural pattern.</p><p>You just needed to show that you could learn.</p><p>A more experienced developer would review your code, explain what you got wrong, give you increasingly difficult tasks, and eventually you would become less junior.</p><p>That’s how the industry worked.</p><p>I’m not sure it will work that way for much longer.</p><p>If I were 22 years old, had no professional experience, and wanted to become a software engineer today, <strong>I would be worried.</strong></p><p>Not because I think programming is dead.</p><p>And not because I think AI is going to make every developer unemployed tomorrow.</p><p>I’d be worried because <strong>the traditional entry point into software engineering is becoming much harder to justify.</strong></p><p>And I think we should be honest about that.</p><h3>I have been a junior developer twice</h3><p>I’ve actually experienced being a junior developer in two different countries.</p><p>The first time was in my home country.</p><p>I worked at a startup with several other people and learned an enormous amount.</p><p>It was exciting.</p><p>It was also not particularly well paid.</p><p>I learned firsthand what it means to work for very little money and sometimes work double shifts because you want to prove yourself.</p><p>The second time I was a junior was after moving to England.</p><p>That experience wasn’t nearly as exciting, but there was something else I valued enormously:</p><p><strong>regulation and employee rights.</strong></p><p>I knew that even if the job wasn’t perfect, I was building a career in a place where the rules offered me some protection.</p><p>Both experiences taught me something important.</p><p>Being junior isn’t just about knowing less.</p><p>It’s a stage of your career where <strong>other people invest in you.</strong></p><p>Someone has to be willing to teach you.</p><p>Someone has to review your work.</p><p>Someone has to give you opportunities to make mistakes.</p><p>And that’s exactly where AI creates an uncomfortable problem.</p><h3>Who is going to train the juniors?</h3><p>When I was starting out, I needed experienced engineers.</p><p>I needed people to explain things.</p><p>I needed someone to tell me why my solution was bad.</p><p>I needed someone to show me a better approach.</p><p>Finding the right mentor was actually one of the biggest challenges I faced.</p><p>Sometimes the team was too small.</p><p>Sometimes there simply weren’t enough senior engineers.</p><p>And sometimes my curiosity took me in directions that my leads at the time weren’t particularly interested in exploring.</p><p>So I did what a lot of self-taught developers do.</p><p>I went to YouTube.</p><p>I read books.</p><p>I experimented.</p><p>I taught myself.</p><p>And I’m incredibly grateful that so much information was available to me.</p><p>But not everyone is lucky enough to start their career surrounded by experienced engineers.</p><p>And here’s the question I keep coming back to:</p><p><strong>What happens when companies decide they don’t need as many juniors anymore?</strong></p><p>Because juniors aren’t just employees.</p><p>They’re the future senior engineers.</p><h3>The business case for AI is brutally simple</h3><p>I don’t want to pretend I know exactly what every company is thinking.</p><p>But I understand how businesses work.</p><p>Managers and executives ultimately care about revenue and the bottom line.</p><p>If a company believes that AI can do the work of ten junior developers for a fraction of the cost, the incentive is obvious.</p><p>They’ll use the AI.</p><p>You can tell me that AI is expensive.</p><p>And it is.</p><p>But I don’t think that’s necessarily the point.</p><p>The companies building these AI systems desperately want businesses to adopt them before their competitors do.</p><p>So we’re seeing aggressive pricing, discounts, enterprise deals and enormous investment to make adoption attractive.</p><p>From the perspective of a business, the question isn’t:</p><blockquote><em>“Is AI expensive?”</em></blockquote><p>It’s:</p><blockquote><strong><em>“Is AI cheaper than the alternative?”</em></strong></blockquote><p>And if the answer becomes yes, that’s enough.</p><h3>It’s not just juniors who should be worried</h3><p>This is where I think the conversation gets interesting.</p><p>It’s tempting to frame this as:</p><p><strong>AI will replace junior developers.</strong></p><p>Maybe.</p><p>But if AI can dramatically increase the productivity of a junior developer, it can also increase the productivity of a mid-level developer.</p><p>And a senior developer.</p><p>And a manager.</p><p>And potentially entire teams.</p><p>The economics don’t stop at entry level.</p><p>A senior developer costs more than a junior.</p><p>A manager costs more than a developer.</p><p>If AI changes how much output one person can produce, companies will eventually start asking whether they need the same number of people at every level.</p><p>That’s not necessarily good news for anyone.</p><p>The difference is that experienced people have something juniors haven’t had the opportunity to develop yet:</p><p><strong>years of accumulated judgment.</strong></p><h3>So what should a junior actually learn?</h3><p>If I were starting from zero today, I wouldn’t abandon programming.</p><p>But I wouldn’t make traditional programming my entire plan either.</p><p>I’d learn AI.</p><p>Not just how to call an API.</p><p>I’d want to understand how modern AI systems actually work.</p><p>I’d learn things like:</p><ul><li>attention</li><li>embeddings</li><li>RAG</li><li>context windows</li><li>agents</li><li>evaluation</li><li>AI-assisted development</li><li>the basics of machine learning</li></ul><p>And if I were good at mathematics, I’d seriously consider going deeper into ML.</p><p>The goal wouldn’t be:</p><blockquote><em>“Become the person who writes the most Python.”</em></blockquote><p>It would be:</p><blockquote><strong><em>“Become the person who understands what to build and knows how to use AI to build it.”</em></strong></blockquote><p>That’s a much more interesting skill set.</p><h3>But don’t stop learning programming</h3><p>There’s a strange contradiction here.</p><p>I’m telling you that programming might become less valuable as a marketable skill.</p><p>I’m also telling you to learn it.</p><p>Why?</p><p>Because <strong>understanding programming and getting paid to write programming aren’t the same thing.</strong></p><p>I’m self-taught.</p><p>The amount of information available online today is incredible.</p><p>If you genuinely want to understand programming, you can learn an enormous amount without ever attending a computer science degree.</p><p>And I still think you should.</p><p>Programming teaches you how to think.</p><p>It teaches you how to break down problems.</p><p>It teaches you how systems behave.</p><p>It keeps your brain sharp.</p><p>And, honestly, <strong>it’s fun.</strong></p><p>But I wouldn’t make a 22-year-old a promise that learning to code today guarantees them a software engineering career in 2029.</p><p>I don’t think anyone can honestly make that promise.</p><h3>Learn system design instead of memorizing syntax</h3><p>If I were a junior today, I’d spend considerably more time learning <strong>how systems work</strong>.</p><p>Not just how to write a function.</p><p>I’d want to understand:</p><ul><li>databases</li><li>APIs</li><li>distributed systems</li><li>caching</li><li>queues</li><li>scalability</li><li>reliability</li><li>networking</li><li>deployment</li><li>architecture</li></ul><p>Because AI is getting very good at generating syntax.</p><p>It’s getting very good at implementing things.</p><p>But someone still needs to decide <strong>what should be built.</strong></p><p>And that’s a much harder problem.</p><h3>Learn to communicate</h3><p>There’s another skill I’d prioritise that doesn’t get enough attention in programming tutorials:</p><p><strong>interpersonal skills.</strong></p><p>Learn how to communicate.</p><p>Learn how to explain technical concepts to non-technical people.</p><p>Learn how to run a meeting.</p><p>Learn how to disagree without being an asshole.</p><p>Learn how to ask for help.</p><p>Learn how to talk to your manager.</p><p>Learn how to understand what the product team actually wants.</p><p>As I’ve progressed through my career, I’ve realized how important it is to build good relationships with managers and bosses.</p><p>I still suck at it sometimes.</p><p>But I’m increasingly convinced that being technically excellent isn’t enough.</p><p>A company isn’t just a collection of code.</p><p>It’s a collection of people trying to build something together.</p><h3>Don’t let AI become your brain</h3><p>This is probably the biggest mistake I would avoid.</p><p>I’ve already made it myself.</p><p>AI is incredibly convenient.</p><p>You ask it to do something.</p><p>It does it.</p><p>You run the tests.</p><p>They pass.</p><p>You move on.</p><p>Except there’s a problem.</p><p>I’ve noticed that AI can produce <strong>massively overengineered solutions</strong>.</p><p>It has consumed books about clean code and clean architecture.</p><p>So when you ask it to implement a tiny feature, it sometimes behaves as though you’re asking it to design the next Google.</p><p>Suddenly your small pull request has hundreds of lines.</p><p>More files.</p><p>More abstractions.</p><p>More opportunities for bugs.</p><p>The code might be technically “clean.”</p><p>But it’s harder to understand.</p><p>And every additional piece of complexity is another thing that can go wrong.</p><p>I’ve started forcing myself to read <strong>every line of code</strong> the AI produces.</p><p>Not because I don’t trust AI.</p><p>Because I don’t trust myself to remain a good engineer if I stop understanding what I’m shipping.</p><h3>AI can actually make you better</h3><p>There’s a positive side to this.</p><p>Almost every chat I start with AI now has some variation of:</p><blockquote><strong><em>“Explain to me why you did this.”</em></strong></blockquote><p>Or:</p><blockquote><strong><em>“Teach me how this works.”</em></strong></blockquote><p>That has helped me enormously.</p><p>Instead of simply accepting the solution, I can turn the interaction into a lesson.</p><p>AI can be an incredibly powerful tutor.</p><p>But there’s a difference between:</p><blockquote><strong><em>“Write this for me.”</em></strong></blockquote><p>and:</p><blockquote><strong><em>“Help me understand how to write this.”</em></strong></blockquote><p>The first one makes you faster.</p><p>The second one can make you better.</p><p>You need both.</p><h3>Here’s the problem nobody has solved</h3><p>There’s one question about AI and junior developers that I don’t think we have a good answer to yet.</p><p><strong>If companies stop hiring juniors, how do we get senior developers?</strong></p><p>Seriously.</p><p>Senior engineers don’t appear out of thin air.</p><p>At some point, they were juniors.</p><p>They made terrible pull requests.</p><p>They misunderstood requirements.</p><p>They broke production.</p><p>They wrote horrible code.</p><p>Someone reviewed it.</p><p>Someone taught them.</p><p>Someone gave them another chance.</p><p>If companies stop hiring people at the bottom of the ladder, eventually there won’t be many people climbing it.</p><p>I have a somewhat pessimistic prediction about this.</p><p>I don’t know if I’m right.</p><p>But I could imagine a future where there are far fewer traditional “junior → mid → senior” engineering careers.</p><p>Current developers might gradually move toward management, product, architecture, AI engineering, or completely different industries.</p><p>And perhaps the product teams themselves will become much more capable of creating software with AI.</p><p>Maybe the traditional software engineering career ladder will look completely different.</p><p>Nobody knows.</p><p>That’s precisely why I’d be cautious about building your entire future around today’s version of the industry.</p><h3>So should you become a software engineer?</h3><p>If you’re asking me:</p><blockquote><strong><em>“Should I spend three years learning to code so I can guarantee myself a software engineering job?”</em></strong></blockquote><p>No.</p><p>I wouldn’t make that promise.</p><p>But if you’re asking:</p><blockquote><strong><em>“Should I learn programming because I genuinely enjoy it?”</em></strong></blockquote><p>Absolutely.</p><p>Programming is amazing.</p><p>It’s creative.</p><p>It’s challenging.</p><p>It can be relaxing.</p><p>It forces you to think.</p><p>It gives you the ability to create things that didn’t exist before.</p><p>Those are good reasons to learn it even if the job market changes completely.</p><p>Just understand that <strong>a skill can remain valuable without remaining highly marketable.</strong></p><p>That’s an important distinction.</p><p>You can love programming and still eventually work in something else.</p><p>And that’s okay.</p><h3>If I were a junior developer in 2026…</h3><p>I’d do something very different from what I would have done ten years ago.</p><p>I’d learn programming fundamentals.</p><p>But I’d combine them with AI.</p><p>I’d learn how AI works.</p><p>I’d build projects using AI.</p><p>I’d learn system design.</p><p>I’d learn how products work.</p><p>I’d practice communicating.</p><p>I’d learn how to work with AI agents rather than competing with them.</p><p>And most importantly, I’d build projects that <strong>prove I know how to use AI properly.</strong></p><p>Not:</p><blockquote><em>“Look, ChatGPT generated my application.”</em></blockquote><p>But:</p><blockquote><em>“Here’s a problem I identified, here’s the architecture I designed, here’s how I used AI to accelerate the implementation, here’s what it got wrong, here’s how I tested it, and here’s why I made these decisions.”</em></blockquote><p>That’s a portfolio worth looking at.</p><h3>The one thing I wouldn’t do</h3><p>If I were a junior developer in 2026, the one thing I absolutely wouldn’t do is:</p><p><strong>rely on AI without understanding what it produced.</strong></p><p>We’ve been doing a version of this for years.</p><p>Developers copied code from Stack Overflow.</p><p>I did it too.</p><p>We searched Google for an error, found a snippet that worked, pasted it into the application and moved on.</p><p>The problem is that this approach doesn’t compound.</p><p>You might fix today’s problem.</p><p>But you don’t necessarily become better at solving tomorrow’s problem.</p><p>AI can make this dramatically worse because the output is now much more convincing.</p><p>The code looks professional.</p><p>The explanation sounds confident.</p><p>The tests might even pass.</p><p>And you can still have no idea what you just shipped.</p><p><strong>That doesn’t pay dividends in the long term.</strong></p><h3>If you’re scared, I understand</h3><p>If you’re a junior developer right now and you’re thinking:</p><blockquote><em>“Why should I spend three years learning to code if AI can already do it?”</em></blockquote><p>My honest answer is:</p><p><strong>You shouldn’t , if your only reason is to get a guaranteed software engineering job.</strong></p><p>The market might look completely different three years from now.</p><p>But if you genuinely enjoy programming?</p><p>Learn it.</p><p>If you enjoy solving problems?</p><p>Learn it.</p><p>If you love building things?</p><p>Learn it.</p><p>Just don’t assume that the job you get afterwards will look exactly like the software engineering job that exists today.</p><p>The horse didn’t become a better horse when the automobile arrived.</p><p>The world simply found a different way to move people around.</p><p>AI might be doing something similar to software engineering.</p><p>And if I were starting today, I’d rather learn how to drive the new vehicle than spend my entire career trying to prove that horses are still better.</p><h3>One final thought</h3><p>The most important thing for a junior developer in 2026 isn’t to become <strong>better at writing code than AI</strong>.</p><p>That’s probably a losing game.</p><p>It’s to become the person who understands:</p><p><strong>what to build, why to build it, how it should work, how to use AI to build it faster, and how to tell when the AI is wrong.</strong></p><p>That’s a much harder skill.</p><p>And, for now at least, it’s still a very human one.</p><h3>Want more?</h3><p>I’m writing about <strong>AI, software engineering, careers, interviews, and money for developers, </strong>without pretending the tech industry isn’t changing.</p><p>If you want the next article delivered directly to your inbox, <a href="http://eepurl.com/dIZqjf"><strong>subscribe to my free email list</strong>.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ebe035801c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/predict/if-i-were-a-junior-developer-in-2026-id-be-worried-about-this-4ebe035801c0">If I Were a Junior Developer in 2026, I’d Be Worried About This</a> was originally published in <a href="https://medium.com/predict">Predict</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Isn’t Replacing Software Engineers. It’s Replacing This Kind of Engineer]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/predict/ai-isnt-replacing-software-engineers-it-s-replacing-this-kind-of-engineer-7fc7527eb504?source=rss-8f4cd41336f5------2"><img src="https://cdn-images-1.medium.com/max/2600/0*N8YWYfoKBx_uEzgE" width="4000"></a></p><p class="medium-feed-snippet">A few years ago, my approach to AI-assisted programming was pretty primitive.</p><p class="medium-feed-link"><a href="https://medium.com/predict/ai-isnt-replacing-software-engineers-it-s-replacing-this-kind-of-engineer-7fc7527eb504?source=rss-8f4cd41336f5------2">Continue reading on Predict »</a></p></div>]]></description>
            <link>https://medium.com/predict/ai-isnt-replacing-software-engineers-it-s-replacing-this-kind-of-engineer-7fc7527eb504?source=rss-8f4cd41336f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fc7527eb504</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Nico Anastasio]]></dc:creator>
            <pubDate>Sat, 15 Aug 2026 16:37:21 GMT</pubDate>
            <atom:updated>2026-08-15T16:37:21.659Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Exploring Go’s Built-in Packages and Libraries (in 2024)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://faun.pub/exploring-gos-built-in-packages-and-libraries-in-2024-f0fb094fda81?source=rss-8f4cd41336f5------2"><img src="https://cdn-images-1.medium.com/max/1024/1*zAGs02Y5fxl6uLSTp2NFLQ.jpeg" width="1024"></a></p><p class="medium-feed-snippet">Dive into the world of Go&#x2019;s standard library and explore its rich collection of built-in packages.</p><p class="medium-feed-link"><a href="https://faun.pub/exploring-gos-built-in-packages-and-libraries-in-2024-f0fb094fda81?source=rss-8f4cd41336f5------2">Continue reading on FAUN.dev()  »</a></p></div>]]></description>
            <link>https://faun.pub/exploring-gos-built-in-packages-and-libraries-in-2024-f0fb094fda81?source=rss-8f4cd41336f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0fb094fda81</guid>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[go]]></category>
            <category><![CDATA[golang-tutorial]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Nico Anastasio]]></dc:creator>
            <pubDate>Sun, 14 Apr 2024 14:36:19 GMT</pubDate>
            <atom:updated>2024-04-14T14:36:19.265Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[5 tricks to make your code reusable in Golang (part 2)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://faun.pub/5-tricks-to-make-your-code-reusable-in-golang-part-2-1d3b10c1913b?source=rss-8f4cd41336f5------2"><img src="https://cdn-images-1.medium.com/max/1024/1*BZ2gIQduGejfVv-2CMG6_g.jpeg" width="1024"></a></p><p class="medium-feed-snippet">Take your Golang coding skills to the next level with our guide to code reusability. Explore 5 expert tricks to optimize your development</p><p class="medium-feed-link"><a href="https://faun.pub/5-tricks-to-make-your-code-reusable-in-golang-part-2-1d3b10c1913b?source=rss-8f4cd41336f5------2">Continue reading on FAUN.dev()  »</a></p></div>]]></description>
            <link>https://faun.pub/5-tricks-to-make-your-code-reusable-in-golang-part-2-1d3b10c1913b?source=rss-8f4cd41336f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d3b10c1913b</guid>
            <category><![CDATA[golang-tutorial]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[go]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[golang]]></category>
            <dc:creator><![CDATA[Nico Anastasio]]></dc:creator>
            <pubDate>Tue, 09 Apr 2024 07:47:01 GMT</pubDate>
            <atom:updated>2024-04-10T14:52:55.587Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[5 tricks to make your code reusable (in Golang)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://faun.pub/5-tricks-to-make-your-code-reusable-in-golang-3cf4ccb1f776?source=rss-8f4cd41336f5------2"><img src="https://cdn-images-1.medium.com/max/1024/1*Edmv-FzIvZHPQfsMHqQE0Q.jpeg" width="1024"></a></p><p class="medium-feed-snippet">Master the art of code reuse in Golang with these 5 practical tricks. Learn how to write cleaner, more efficient code for your projects</p><p class="medium-feed-link"><a href="https://faun.pub/5-tricks-to-make-your-code-reusable-in-golang-3cf4ccb1f776?source=rss-8f4cd41336f5------2">Continue reading on FAUN.dev()  »</a></p></div>]]></description>
            <link>https://faun.pub/5-tricks-to-make-your-code-reusable-in-golang-3cf4ccb1f776?source=rss-8f4cd41336f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3cf4ccb1f776</guid>
            <category><![CDATA[golang-development]]></category>
            <category><![CDATA[golang-tutorial]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[backend]]></category>
            <dc:creator><![CDATA[Nico Anastasio]]></dc:creator>
            <pubDate>Mon, 08 Apr 2024 11:07:08 GMT</pubDate>
            <atom:updated>2024-04-08T11:07:08.293Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[What is the Difference Between Functions and Methods in Go? (in 2024)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://faun.pub/what-is-the-difference-between-functions-and-methods-in-go-in-2024-72ef369e3f7a?source=rss-8f4cd41336f5------2"><img src="https://cdn-images-1.medium.com/max/1024/1*NZNY2P7cozKcP2FPGOc0rA.jpeg" width="1024"></a></p><p class="medium-feed-snippet">Dive deep into the heart of Go programming. Explore the defining disparities between functions and methods to level up your coding game</p><p class="medium-feed-link"><a href="https://faun.pub/what-is-the-difference-between-functions-and-methods-in-go-in-2024-72ef369e3f7a?source=rss-8f4cd41336f5------2">Continue reading on FAUN.dev()  »</a></p></div>]]></description>
            <link>https://faun.pub/what-is-the-difference-between-functions-and-methods-in-go-in-2024-72ef369e3f7a?source=rss-8f4cd41336f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/72ef369e3f7a</guid>
            <category><![CDATA[go]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[golang-tutorial]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Nico Anastasio]]></dc:creator>
            <pubDate>Mon, 01 Apr 2024 05:31:00 GMT</pubDate>
            <atom:updated>2024-04-01T05:31:00.284Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Is Golang good for beginners? (in 2024)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/codex/is-golang-good-for-beginners-in-2024-553b08fe5a9b?source=rss-8f4cd41336f5------2"><img src="https://cdn-images-1.medium.com/max/1024/1*aUUbjmIzHQ7bbXiYwg376Q.jpeg" width="1024"></a></p><p class="medium-feed-snippet">Curious about Go programming? Our beginner&#x2019;s guide demystifies the language and sets you on the path to programming greatness</p><p class="medium-feed-link"><a href="https://medium.com/codex/is-golang-good-for-beginners-in-2024-553b08fe5a9b?source=rss-8f4cd41336f5------2">Continue reading on CodeX »</a></p></div>]]></description>
            <link>https://medium.com/codex/is-golang-good-for-beginners-in-2024-553b08fe5a9b?source=rss-8f4cd41336f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/553b08fe5a9b</guid>
            <category><![CDATA[golang-tutorial]]></category>
            <category><![CDATA[go]]></category>
            <category><![CDATA[golang-development]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Nico Anastasio]]></dc:creator>
            <pubDate>Wed, 27 Mar 2024 09:04:39 GMT</pubDate>
            <atom:updated>2024-03-27T09:04:39.993Z</atom:updated>
        </item>
    </channel>
</rss>