<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Patrick Contes blog</title><link>https://pconte.tech/</link><description>Recent content on Patrick Contes blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 27 Sep 2026 22:44:00 +1000</lastBuildDate><atom:link href="https://pconte.tech/index.xml" rel="self" type="application/rss+xml"/><item><title>The "Everything" engineer: Why industry expectations are getting out of hand</title><link>https://pconte.tech/p/the-everything-engineer-why-industry-expectations-are-getting-out-of-hand/</link><pubDate>Sun, 27 Sep 2026 22:44:00 +1000</pubDate><guid>https://pconte.tech/p/the-everything-engineer-why-industry-expectations-are-getting-out-of-hand/</guid><description>
&lt;p&gt;I&amp;rsquo;m a frequent user of Reddit. I find it fascinating some of the stories that I read, from AusCorp, where someone is complaining about having to do a white collar role for the next 40 years and being miserable. To a post on GardeningAustralia, asking if yukkas are a good idea to keep long term. Everyone has something to ask, something to share, and something to ponder.&lt;/p&gt;
&lt;p&gt;Recently, I came across a post in the AustraliaIT sub-reddit with this picture:&lt;/p&gt;</description></item><item><title>The Jevons Paradox: Why AI Won't Kill Software Engineering</title><link>https://pconte.tech/p/the-jevons-paradox-why-ai-wont-kill-software-engineering/</link><pubDate>Fri, 05 Jun 2026 00:00:00 +1000</pubDate><guid>https://pconte.tech/p/the-jevons-paradox-why-ai-wont-kill-software-engineering/</guid><description>
&lt;p&gt;&amp;ldquo;White collar roles are dead&amp;rdquo;. That seems to be the common theme for most of the stuff I see on LinkedIn, Medium and anywhere else that likes to fear monger. I get it: AI is confronting, and is unlike anything we have seen before. These titles honestly annoy me because they are click-baity and sometimes lack substance. By that, I mean the content of these posts generally is unfounded and misses a whole heap of information. Let me give you an example. You may see a post claiming that a leading SaaS platform is no longer needed, because Little Johnny was able to vibe code a replacement in 8 hours. Or, Little Jane doesn&amp;rsquo;t need to work anymore because she has an army of agents to do everything her role requires. Congratulations, you solved the meaning of life! Little Johnny&amp;rsquo;s app works perfectly fine on localhost, and Little Jane was most likely going to be made redundant anyway!&lt;/p&gt;</description></item><item><title>Tailwind CSS: A warning for open source projects in the age of AI</title><link>https://pconte.tech/p/tailwind-css-a-warning-for-open-source-projects-in-the-age-of-ai/</link><pubDate>Mon, 02 Feb 2026 10:05:32 +1000</pubDate><guid>https://pconte.tech/p/tailwind-css-a-warning-for-open-source-projects-in-the-age-of-ai/</guid><description>
&lt;p&gt;AI is rapidly evolving. This is a known fact and should come as no surprise. The next frontier will likely emerge in the agentic space, focused on fully working out how to make agents do the bidding of their overlords. As of early 2026, the latest trend is &lt;a href="https://agentskills.io/home"&gt;&lt;em&gt;Agent Skills&lt;/em&gt;&lt;/a&gt; — a powerful mechanism that allows you to define a structured set of instructions within a given context or framework, controlling how an agent performs a specific set of tasks.&lt;/p&gt;</description></item><item><title>Designing Egress in AWS</title><link>https://pconte.tech/p/designing-egress-in-aws/</link><pubDate>Tue, 08 Jul 2025 22:00:32 +1000</pubDate><guid>https://pconte.tech/p/designing-egress-in-aws/</guid><description>
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;AWS networking is fairly straightforward in a small setup. As a singular environment, you will generally have a single VPC that consists of:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Subnets&lt;/li&gt;
&lt;li&gt;Route tables&lt;/li&gt;
&lt;li&gt;Network ACLs (NACLs)&lt;/li&gt;
&lt;li&gt;Security groups&lt;/li&gt;
&lt;li&gt;An Internet Gateway (IGW)&lt;/li&gt;
&lt;li&gt;NAT Gateway(s)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There are other components, and even some of the ones mentioned here may not be required. You might have a single subnet for all of your resources. Likewise, a NAT Gateway may not even be necessary (this is rare — and anyone exposing private workloads to the internet unnecessarily is not following best practice).&lt;/p&gt;</description></item><item><title>Perfect vs Practical: How to know when an IT Solution is ready</title><link>https://pconte.tech/p/perfect-vs-practical-how-to-know-when-an-it-solution-is-ready/</link><pubDate>Thu, 12 Jun 2025 22:20:32 +1000</pubDate><guid>https://pconte.tech/p/perfect-vs-practical-how-to-know-when-an-it-solution-is-ready/</guid><description>
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Designing IT solutions is a challenging task. Not only do you need to take several factors into consideration, but you also need to understand the lifecycle of what you’re designing. Questions will inevitably pop into your head, like:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;How long does this solution need to last?&lt;/li&gt;
&lt;li&gt;Is it going to be perpetual?&lt;/li&gt;
&lt;li&gt;How do we handle high availability and disaster recovery?&lt;/li&gt;
&lt;li&gt;When will I know it&amp;rsquo;s complete?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That last point—&lt;em&gt;when will I know it&amp;rsquo;s complete?&lt;/em&gt;—can be ambiguous. Does it mean the solution is fully fleshed out and working at the desired end state? Or does it mean it&amp;rsquo;s ready once a Minimum Viable Product (MVP) has been constructed?&lt;/p&gt;</description></item></channel></rss>