<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Jules GAY--DONAT | Systems &amp; Engineering</title><description>Official RSS feed of Jules GAY-DONAT, young enthusiast of computer science, artificial intelligence, and cryptography.</description><link>https://julesgd.dev/</link><language>en-en</language><item><title>The Era of AI-Assisted Development: Why Coding Is No Longer Enough</title><link>https://julesgd.dev/en/articles/ai-assisted-dev/</link><guid isPermaLink="true">https://julesgd.dev/en/articles/ai-assisted-dev/</guid><description>Refusing the assistance of LLMs and agents has become counterproductive. Tomorrow&apos;s core skill won&apos;t be writing code, but deeply understanding systems.</description><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;h2&gt;An Indispensable Tool for Competitiveness&lt;/h2&gt;
&lt;p&gt;In the software industry, a debate persists: is using artificial intelligence to generate, audit, or restructure code a form of &quot;cheating&quot; or a natural evolution? Stubbornly hand-coding every single line has now become not only a misplaced act of resistance but a dangerously counterproductive stance.&lt;/p&gt;
&lt;p&gt;The use of LLMs (Large Language Models) and autonomous agents makes it possible to automate boilerplate code, drastically speed up testing phases, and simplify massive refactors. Refusing to leverage these tools is equivalent to a mathematician forbidding themselves from using a calculator to solve a complex equation system. To remain competitive—whether as a freelancer, a startup, or a tech giant—AI-assisted development must become the absolute standard.&lt;/p&gt;
&lt;h2&gt;The End of Programming as a Sole Competency&lt;/h2&gt;
&lt;p&gt;For decades, the &quot;ability to program&quot; (knowing the syntax of a language, knowing how to implement a loop or a SQL query) was an end in itself. With generative AI, this skill has become heavily commoditized. Writing raw code is no longer the true bottleneck of software engineering.&lt;/p&gt;
&lt;p&gt;If anyone can generate a Python or Rust function with a simple prompt, syntax inherently loses its value. What gains value instead is architecture and true engineering.&lt;/p&gt;
&lt;h2&gt;The Rise of the Systems Engineer&lt;/h2&gt;
&lt;p&gt;In this new paradigm, the cardinal skill shifts toward two extremes: high-level abstraction and low-level understanding. Tomorrow&apos;s developers will no longer be mere &quot;coders,&quot; but system architects and critics.&lt;/p&gt;
&lt;p&gt;True experts will distinguish themselves through:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A deep understanding of algorithms:&lt;/strong&gt; Knowing how to evaluate the time and space complexity of AI-generated code and identifying its mathematical or logical flaws.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Systemic vision:&lt;/strong&gt; Knowing how to make services interact flawlessly, guarantee the security of an entire infrastructure, and optimize data flows at scale.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Low-level mastery:&lt;/strong&gt; While AI excels at generating high-level boilerplate, we will desperately need engineers capable of diving into memory management, multithreading, assembly, or system calls to solve critical performance bottlenecks that models cannot comprehend.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Embracing AI in our daily work does not mean abandoning our craft; it means rising above simple syntax to focus on what makes computer science fascinating: true engineering.&lt;/p&gt;
</content:encoded></item><item><title>Artificial Intelligence, Ecology, and the Sovereignty Gamble</title><link>https://julesgd.dev/en/articles/ai-ecology/</link><guid isPermaLink="true">https://julesgd.dev/en/articles/ai-ecology/</guid><description>Why rejecting data centers in the name of ecology could lead to far more dangerous dependencies and foreign interference.</description><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;h2&gt;The False Dilemma of Data Centers&lt;/h2&gt;
&lt;p&gt;Lately, a recurring narrative has taken root in public debate: Artificial Intelligence consumes too much energy, and building new data centers is an ecological heresy. While concerns about energy consumption and carbon footprints are fundamentally legitimate, the systematic rejection of these infrastructures hides a much more insidious danger.&lt;/p&gt;
&lt;p&gt;We are treating AI as if it were a mere digital convenience or a passing trend. In reality, Artificial Intelligence is rapidly becoming one of the most critical strategic resources of the 21st century.&lt;/p&gt;
&lt;h2&gt;AI as a Sovereignty Resource&lt;/h2&gt;
&lt;p&gt;Refusing to build our own AI infrastructures in the name of environmental sobriety is tantamount to outsourcing our cognitive, technological, and industrial future. If we do not possess our own models and compute power, we will be forced to rely on those of others.&lt;/p&gt;
&lt;p&gt;Not possessing this resource can cause extremely serious problems in the future:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Loss of competitiveness:&lt;/strong&gt; Companies that fail to use AI will be swept aside. Those relying on foreign AI will be entirely dependent on the pricing and terms of service of external entities.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Interference and cultural bias:&lt;/strong&gt; AI models reflect the values, norms, and sometimes the propaganda of their creators.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Censorship and technological blackmail:&lt;/strong&gt; We already had a taste of this with the recent &quot;Fable&quot; outage, where dependency on a single provider exposed our sheer vulnerability. What will happen when AI is deeply integrated into our critical infrastructures?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;A Mandatory Investment&lt;/h2&gt;
&lt;p&gt;We do not have the luxury of waiting. Investing in Artificial Intelligence and building the data centers needed to run it is mandatory, whether we like it or not.&lt;/p&gt;
&lt;p&gt;This is not about abandoning ecology, but rethinking it within the framework of technological realpolitik. Rather than rejecting these infrastructures, our challenge must be to make them as green as possible: optimizing water consumption, utilizing low-carbon energy, and recovering waste heat to warm our cities.&lt;/p&gt;
&lt;p&gt;Surrendering our technological sovereignty today for symbolic ecological victories means ensuring we have absolutely no say in the future of tomorrow&apos;s world.&lt;/p&gt;
</content:encoded></item><item><title>Why I&apos;m passionate about computers and hardware</title><link>https://julesgd.dev/en/articles/passion-pc/</link><guid isPermaLink="true">https://julesgd.dev/en/articles/passion-pc/</guid><description>A look back at my journey, from my first Linux PC at age 5 to my current rig, and why I love (maybe a bit too much) fixing my relatives&apos; computers.</description><pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;It all started when I was 5 years old. My dad bought me my very first PC, a modest machine running Linux. Even before I could read properly, I was completely hooked. I literally haven&apos;t let go of a keyboard since.&lt;/p&gt;
&lt;p&gt;At age 11, I reached a milestone for any tech enthusiast: using my own savings, I built my first PC from scratch. The specs were humble, but it was &lt;em&gt;my&lt;/em&gt; machine:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;An AMD Ryzen 5 4600G CPU (the integrated graphics were a lifesaver, as I couldn&apos;t afford a dedicated GPU).&lt;/li&gt;
&lt;li&gt;16GB of DDR4 RAM.&lt;/li&gt;
&lt;li&gt;A rather low-end MSI motherboard.&lt;/li&gt;
&lt;li&gt;And the famous &quot;Amazon mistake&quot; that worked in my favor: I received a 1TB SSD instead of the smaller one I ordered!&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Since that first build, my PC has become a continuous project. Thanks to successive upgrades gathered every Christmas and birthday, the machine has slowly transformed. Today, I work (and game) on a Ryzen 5 7600X paired with an RTX 5070 and 32GB of DDR5. It&apos;s safe to say it&apos;s come a long way from the little 4600G.&lt;/p&gt;
&lt;h3&gt;The love for Linux and the Dual Boot burden&lt;/h3&gt;
&lt;p&gt;Having started on Linux at such a young age, the OS holds a special place in my heart. Today, I&apos;m an avid &lt;strong&gt;Arch Linux&lt;/strong&gt; user (I use Arch, btw). I love the absolute control, the lightweight footprint, and the elegance of the ecosystem.&lt;/p&gt;
&lt;p&gt;Yet, a necessary evil persists: the Windows dual boot. The culprit, of course, is gaming. Even though tools like Proton have made giant leaps, some titles (especially those with invasive anti-cheats) still force me to keep a Windows partition on my drive. It breaks my heart a little, but it&apos;s the price to pay to play...&lt;/p&gt;
&lt;h3&gt;The family &quot;Tech Guy&quot;&lt;/h3&gt;
&lt;p&gt;My passion for systems and hardware comes with what I jokingly call the &lt;em&gt;IT curse&lt;/em&gt;. I&apos;ve inevitably become the official PC repairman for my friends and family. A stubborn printer? A Windows install that won&apos;t boot? A virus on a laptop? That&apos;s on me. I do it often—maybe a bit &lt;em&gt;too&lt;/em&gt; often—but deep down, it&apos;s what taught me patience, how to diagnose unlikely hardware failures, and how to tinker with motherboards.&lt;/p&gt;
&lt;p&gt;This relentless curiosity about hardware is what pushed me toward systems engineering. Understanding exactly how hardware and software interact has become an everyday learning process for me. And it all started with a little Linux machine, 11 years ago.&lt;/p&gt;
</content:encoded></item></channel></rss>