<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>General on Simple Enough Blog</title><link>https://blog-dev.simpleenough.net/tags/general/</link><description>Recent content in General on Simple Enough Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 25 Feb 2026 13:00:00 +0100</lastBuildDate><atom:link href="https://blog-dev.simpleenough.net/tags/general/index.xml" rel="self" type="application/rss+xml"/><item><title>A Step Toward Technology</title><link>https://blog-dev.simpleenough.net/blog/steptechnologie/</link><pubDate>Wed, 25 Feb 2026 13:00:00 +0100</pubDate><guid>https://blog-dev.simpleenough.net/blog/steptechnologie/</guid><description>&lt;p>Growing old in Europe is not just about “having more years.” It also means having to navigate a world where access to rights, healthcare, and social connections increasingly happens through screens.&lt;br>
Technology is no longer background scenery. It has become a daily life tool… but also a factor of exclusion when poorly designed.&lt;/p>
&lt;hr>




&lt;h2 id="i-an-ageing-society" class="heading">I. An ageing society&lt;a href="#i-an-ageing-society" aria-labelledby="i-an-ageing-society">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>In France and across Europe, around &lt;strong>22% of the population is aged 65 or over&lt;/strong> (estimate as of January 1, 2026).&lt;/p></description></item><item><title>DevOps Cycle or a Misunderstanding of the Role?</title><link>https://blog-dev.simpleenough.net/blog/devops_cycle/</link><pubDate>Tue, 24 Feb 2026 11:00:00 +0100</pubDate><guid>https://blog-dev.simpleenough.net/blog/devops_cycle/</guid><description>&lt;h2 id="introduction" class="heading">Introduction&lt;a href="#introduction" aria-labelledby="introduction">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>The term &lt;em>DevOps&lt;/em> is frequently used to describe a heterogeneous set of topics: CI/CD, cloud, Kubernetes, security, observability, incident management, cost management, and more. This breadth of meanings creates a recurring confusion: an organization expresses a need for “DevOps” without specifying the expected value, the associated responsibilities, or the target operating model.&lt;/p>
&lt;p>The outcome is well known: a succession of urgent periods, followed by automation initiatives, and then a gradual return to the same difficulties. This is often described as the “DevOps cycle.” In many cases, this cycle is not intrinsic to DevOps itself, but rather the indicator of a &lt;strong>misunderstanding of the role&lt;/strong>: DevOps is used as a compensating function (support, firefighting, implicit ownership of production) instead of as a structuring organizational capability.&lt;/p></description></item><item><title>Upgrading Your Computer Components: Method, Compatibility, Benchmarks… and Mistakes to Avoid</title><link>https://blog-dev.simpleenough.net/blog/componentcomputer/</link><pubDate>Wed, 11 Feb 2026 10:00:00 +0100</pubDate><guid>https://blog-dev.simpleenough.net/blog/componentcomputer/</guid><description>&lt;h1 id="upgrading-your-computer-components-method-compatibility-and-benchmarks" class="heading">Upgrading Your Computer Components: Method, Compatibility, and Benchmarks&lt;a href="#upgrading-your-computer-components-method-compatibility-and-benchmarks" aria-labelledby="upgrading-your-computer-components-method-compatibility-and-benchmarks">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h1>
&lt;p>Upgrading your computer hardware often feels like a &lt;strong>simple and logical process&lt;/strong>:&lt;br>
you identify what feels slow, buy a more powerful component, and install it.&lt;/p>
&lt;p>In practice, many upgrades:&lt;/p>
&lt;ul>
&lt;li>bring &lt;strong>no noticeable performance gain&lt;/strong>,&lt;/li>
&lt;li>introduce &lt;strong>compatibility issues&lt;/strong>,&lt;/li>
&lt;li>or simply move the problem elsewhere.&lt;/li>
&lt;/ul>
&lt;p>So how should you approach it properly?&lt;/p></description></item><item><title>AI, Code, and Design: Why the Most Important Thing Hasn’t Changed</title><link>https://blog-dev.simpleenough.net/blog/codedesign/</link><pubDate>Wed, 21 Jan 2026 10:00:00 +0100</pubDate><guid>https://blog-dev.simpleenough.net/blog/codedesign/</guid><description>&lt;h2 id="i-introduction" class="heading">I. Introduction&lt;a href="#i-introduction" aria-labelledby="i-introduction">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>AI-powered coding assistants are now capable of producing:&lt;/p>
&lt;ul>
&lt;li>syntactically valid code,&lt;/li>
&lt;li>working code,&lt;/li>
&lt;li>and even a certain form of reasoning about code structure.&lt;/li>
&lt;/ul>
&lt;p>Faced with this, a legitimate question arises:&lt;br>
&lt;strong>do we still need to learn how to code, or is it enough to learn design and leave the rest to AI?&lt;/strong>&lt;/p>
&lt;p>This question lies at the heart of a video titled &lt;em>“The Skill That Separates Good Developers from GREAT Ones”&lt;/em> by &lt;strong>Emily Bache&lt;/strong>, which offers a nuanced answer deeply rooted in the fundamentals of software engineering.&lt;/p></description></item><item><title>Developing with AI: What Changes, What Stays, and What Becomes Critical</title><link>https://blog-dev.simpleenough.net/blog/ia/</link><pubDate>Wed, 07 Jan 2026 10:00:00 +0100</pubDate><guid>https://blog-dev.simpleenough.net/blog/ia/</guid><description>&lt;h2 id="i-introduction" class="heading">I. Introduction&lt;a href="#i-introduction" aria-labelledby="i-introduction">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>AI-powered coding assistants have profoundly changed developers’ day-to-day work.&lt;br>
They generate working code in seconds, propose complete implementations, and drastically reduce the time spent on repetitive tasks.&lt;/p>
&lt;p>This evolution raises a central question:&lt;/p>





 &lt;blockquote class="blockquote">
 &lt;p>&lt;strong>If code can be produced easily, where does the developer’s value now lie?&lt;/strong>&lt;/p>
 &lt;/blockquote>
&lt;p>To answer it, we must look not at what AI &lt;em>can&lt;/em> do, but at &lt;strong>what it does not take responsibility for&lt;/strong>.&lt;/p></description></item><item><title>“It’s slow”, “it lags”, “it bugs”: but in the end, what does it really mean?</title><link>https://blog-dev.simpleenough.net/blog/cabug/</link><pubDate>Tue, 30 Dec 2025 10:00:00 +0100</pubDate><guid>https://blog-dev.simpleenough.net/blog/cabug/</guid><description>&lt;h2 id="introduction" class="heading">Introduction&lt;a href="#introduction" aria-labelledby="introduction">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>In a family, at work, or within a technical team, it is very common to hear: &lt;strong>“it’s slow”&lt;/strong>, &lt;strong>“it lags”&lt;/strong>, or &lt;strong>“it bugs”&lt;/strong>. These expressions are often used interchangeably… &lt;strong>wrongly&lt;/strong>. They mix together problems that actually have nothing to do with each other.&lt;/p>
&lt;p>Understanding the difference between these three situations makes it possible to &lt;strong>explain what is happening more clearly&lt;/strong>, to &lt;strong>react more quickly&lt;/strong>, and above all to &lt;strong>avoid bad solutions&lt;/strong>. A performance issue is not solved like a bug, and a bug never disappears just because the machine has been made more powerful.&lt;/p></description></item><item><title>Writing a Prompt: Technical Guide</title><link>https://blog-dev.simpleenough.net/blog/prompt/</link><pubDate>Fri, 18 Apr 2025 11:02:00 +0100</pubDate><guid>https://blog-dev.simpleenough.net/blog/prompt/</guid><description>&lt;h2 id="i-understanding-what-a-prompt-is-in-langchain" class="heading">I. Understanding What a Prompt Is in LangChain&lt;a href="#i-understanding-what-a-prompt-is-in-langchain" aria-labelledby="i-understanding-what-a-prompt-is-in-langchain">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>In LangChain, a &lt;em>prompt&lt;/em> is a textual structure designed to guide a language model. A well-constructed prompt includes several key components:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Instruction&lt;/strong>: What you explicitly ask the model to do.&lt;/li>
&lt;li>&lt;strong>Context&lt;/strong>: Additional information to frame the answer.&lt;/li>
&lt;li>&lt;strong>Input Data&lt;/strong>: The specific input provided at runtime.&lt;/li>
&lt;li>&lt;strong>Output Indicator&lt;/strong>: What kind of output is expected.&lt;/li>
&lt;/ul>
&lt;hr>
&lt;p>This format enables clear, framed, and reproducible queries.&lt;br>
Here’s another example using &lt;code>LangChain&lt;/code> in Python with this structure:&lt;/p></description></item><item><title>Hallucinating with LangChain</title><link>https://blog-dev.simpleenough.net/blog/hallucination/</link><pubDate>Mon, 07 Apr 2025 09:22:00 +0100</pubDate><guid>https://blog-dev.simpleenough.net/blog/hallucination/</guid><description>&lt;h2 id="i-what-is-a-hallucination" class="heading">I What is a hallucination?&lt;a href="#i-what-is-a-hallucination" aria-labelledby="i-what-is-a-hallucination">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>A hallucination refers to a response generated by a language model that is factually incorrect, invented, or misinterprets reality. It can range from a minor inaccuracy to a completely fabricated citation or even a made-up technical or historical claim.&lt;/p>
&lt;p>Example:&lt;/p>





 &lt;blockquote class="blockquote">
 &lt;p>“Einstein discovered general relativity in 1975.”&lt;/p>
 &lt;/blockquote>
&lt;p>That’s incorrect (it was in 1915), but the model might produce this kind of statement if it lacks the proper context or is too confident in its reasoning.&lt;/p></description></item><item><title>How to Count Tokens Effectively</title><link>https://blog-dev.simpleenough.net/blog/token/</link><pubDate>Tue, 01 Apr 2025 17:52:00 +0100</pubDate><guid>https://blog-dev.simpleenough.net/blog/token/</guid><description>&lt;h2 id="i-what-is-a-token" class="heading">I. What Is a Token?&lt;a href="#i-what-is-a-token" aria-labelledby="i-what-is-a-token">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>A &lt;strong>token&lt;/strong> is a unit of text that the model processes. It could be a full word, part of a word, or even a special character.&lt;/p>




&lt;h3 id="concrete-examples" class="heading">Concrete Examples&lt;a href="#concrete-examples" aria-labelledby="concrete-examples">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h3>






 






&lt;table class="table">
 &lt;thead>
 
 
 &lt;tr>
 &lt;th >Text&lt;/th>
 &lt;th >Number of Tokens&lt;/th>
 &lt;/tr>
 
 &lt;/thead>
 &lt;tbody>
 
 
 &lt;tr>
 &lt;td >Hello&lt;/td>
 &lt;td >1&lt;/td>
 &lt;/tr>
 
 
 
 &lt;tr>
 &lt;td >I am a developer&lt;/td>
 &lt;td >4&lt;/td>
 &lt;/tr>
 
 
 
 &lt;tr>
 &lt;td >Artificial intelligence is fascinating!&lt;/td>
 &lt;td >5&lt;/td>
 &lt;/tr>
 
 
 
 &lt;tr>
 &lt;td >GPT is a powerful model.&lt;/td>
 &lt;td >6&lt;/td>
 &lt;/tr>
 
 &lt;/tbody>
&lt;/table>



&lt;h3 id="specifics-of-tokenization" class="heading">Specifics of Tokenization&lt;a href="#specifics-of-tokenization" aria-labelledby="specifics-of-tokenization">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h3>
&lt;ul>
&lt;li>In English, short words are often 1 token (e.g., &lt;code>&amp;quot;Hello&amp;quot;&lt;/code> = 1 token).&lt;/li>
&lt;li>In French and other languages, longer words can be split into multiple tokens (e.g., &lt;code>&amp;quot;développeur&amp;quot;&lt;/code> or &lt;code>&amp;quot;intelligence&amp;quot;&lt;/code> = 2 tokens).&lt;/li>
&lt;li>Punctuation also counts as tokens.&lt;/li>
&lt;li>Spaces are included with the following word.&lt;/li>
&lt;li>Acronyms are usually treated as 1 token.&lt;/li>
&lt;/ul>
&lt;p>On average, 100 tokens correspond to roughly 75 words, though this can vary depending on the language and writing style.&lt;/p></description></item><item><title>What is a Bundle? Understanding the Concept</title><link>https://blog-dev.simpleenough.net/blog/bundleconcept/</link><pubDate>Mon, 03 Feb 2025 10:00:00 +0100</pubDate><guid>https://blog-dev.simpleenough.net/blog/bundleconcept/</guid><description>&lt;p>The term &lt;strong>&amp;ldquo;bundle&amp;rdquo;&lt;/strong> is widely used in web development and DevOps. It refers to a &lt;strong>grouping of files, resources, or elements&lt;/strong> to simplify their management and improve performance.&lt;/p>
&lt;p>However, a &lt;strong>bundle&lt;/strong> does not have the same meaning everywhere. In this article, we will explore its &lt;strong>different uses&lt;/strong> in three key areas:&lt;/p>
&lt;p>&lt;strong>Hugo (static site generator)&lt;/strong>&lt;br>
&lt;strong>CSS &amp;amp; JavaScript (front-end development)&lt;/strong>&lt;br>
&lt;strong>DevOps (Docker, Kubernetes, Helm, etc.)&lt;/strong>&lt;/p>
&lt;hr>




&lt;h2 id="1-bundle-in-hugo-organizing-files-smartly" class="heading">1. Bundle in Hugo: Organizing Files Smartly&lt;a href="#1-bundle-in-hugo-organizing-files-smartly" aria-labelledby="1-bundle-in-hugo-organizing-files-smartly">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>In Hugo, a &lt;strong>bundle&lt;/strong> is a folder containing a page and its associated resources (images, JSON files, etc.). There are two types of &lt;strong>Page Bundles&lt;/strong>:&lt;/p></description></item><item><title>A Brief History of AWS Architectures</title><link>https://blog-dev.simpleenough.net/blog/history/</link><pubDate>Fri, 20 Dec 2024 09:56:41 +0100</pubDate><guid>https://blog-dev.simpleenough.net/blog/history/</guid><description>&lt;h1 id="i-the-early-days-of-aws-and-cloud-computing-2002---2006" class="heading">I. The Early Days of AWS and Cloud Computing (2002 - 2006)&lt;a href="#i-the-early-days-of-aws-and-cloud-computing-2002---2006" aria-labelledby="i-the-early-days-of-aws-and-cloud-computing-2002---2006">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h1>




&lt;h3 id="context-the-origin-of-the-aws-project" class="heading">Context: The Origin of the AWS Project&lt;a href="#context-the-origin-of-the-aws-project" aria-labelledby="context-the-origin-of-the-aws-project">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h3>
&lt;p>Before AWS became a cloud giant, Amazon.com (the e-commerce site) had to manage a massive IT infrastructure to support its rapid growth. The company invested in expensive data centers and had to anticipate server capacity for peak traffic periods (such as Black Friday). However, much of this capacity remained unused outside of high-demand periods.&lt;/p></description></item></channel></rss>