In my two previous articles, I argued that the SDLC is dead and that coding was never the job. I was talking about process and roles. But there's a far more uncomfortable topic — and nobody wants to look at it.

When OpenAI announces a $100/month plan, wedged between Plus at $20 and Pro at $200, it's not a pricing adjustment. It's a confession. The confession of something I've been observing for months, and that the public debate refuses to name: we're not all using the same AI. And everything said about it is rigged from the start.

Two AIs, one name

Look at OpenAI's pricing grid today. Free. Plus at $20. The new plan at $100. Pro at $200. Four tiers. Four radically different experiences. (Sources: openai.com/chatgpt/pricing, openai.com/index/introducing-chatgpt-pro.)

On the free plan, you get a throttled model, tight quotas, degraded response times during peak hours, and limited access to the latest models. On Plus at $20, it's better — but quotas remain constraining, especially if you're doing serious work. You hit the ceiling by mid-afternoon. You wait. You rephrase to save tokens. You adapt your workflow to the tool's limits instead of the other way around.

On the $100 plan, five times more capacity. Priority access to Codex and the most powerful models. On Pro at $200, near-unlimited usage of the best models, deep research mode, extended capabilities.

Same brand. Same interface. Same name. But these are not the same products.

"This isn't the same AI at two prices. It's two AIs under the same name. One gives you an impression. The other reshapes your career."

And OpenAI isn't alone. Anthropic has its Max offering at $100 and $200 for Claude. Google pushes Gemini Advanced. Everyone is building the same structure: a free showcase for the masses, and a real product for those who pay.

The experience gap

This isn't just about quotas. It's about qualitative experience.

The person on the free plan interacts with a model that hallucinates more often, has less context, refuses more requests, and produces more generic answers. They reach the logical conclusion: "AI is impressive but unreliable."

The person on the $200 plan uses the same model name — but with extended context, deep reasoning capability, access to advanced tools, and quotas that enable a real continuous workflow. They reach a very different conclusion: "AI changed how I work."

Both people talk about "ChatGPT". They talk about "Claude". They think they're talking about the same thing. They're not talking about the same thing.

It's like someone judging photography after using a disposable camera, while another works with a Hasselblad. They both talk about "taking photos". But one captures blurry memories and the other produces art.

"The gap between free and premium AI isn't a performance difference. It's an era gap."

The public debate is biased at the source

And this is where it becomes a real problem.

The public debate on AI — the one that shapes regulations, corporate policies, investment decisions, public opinion — is overwhelmingly based on the free or cheap AI experience.

Journalists covering AI almost all use the free plan or Plus at $20. They test ChatGPT, notice hallucinations, write an article about "AI's limitations". Their conclusion is honest — but it's based on a product that's throttled on purpose. It's like test-driving a Ferrari with the handbrake on, concluding that sports cars are overrated, and selling the conclusion on the front page.

Regulators have seen a demo. Maybe two. Probably on a free account, probably prepared by an assistant who doesn't use AI daily. They legislate on a technology they've never used in a real workflow for a full week. The EU AI Act is a massive text. How many of its drafters used a Pro plan for a month to understand what the technology actually does?

Politicians have heard that "ChatGPT hallucinates". That AI generates false content. That it's dangerous. And they're not wrong — on the free plan, it often does. But nobody showed them what an advanced reasoning model does with a million-token context on a structured problem.

Business leaders deciding their organization's AI strategy often have the same limited experience. They tried ChatGPT on a Saturday afternoon, asked it to write an email, found it "nice but not revolutionary", and decided AI could wait until 2027 on the roadmap.

"We legislate the future of AI with the experience of a free account. It's like flying a fighter jet after flying a kite. Both leave the ground. They're not the same war."

Those who know don't talk

Meanwhile, a silent minority lives in a different technological reality.

The developer paying $100 or $200/month doesn't waste time debating on LinkedIn whether AI is useful. They're too busy delivering in a morning what used to take a week. They don't comment on "will AI replace developers?" articles — they're living the answer.

The researcher using Claude Pro with a million-token context doesn't debate whether AI hallucinates. They've learned to structure their queries, verify outputs, and use the tool in a workflow that produces reliable results. Hallucinations exist — but in a structured context with an advanced model, they're manageable, identifiable, and increasingly rare.

There is an asymmetric silence. Those with the deepest AI experience are the ones who talk about it least publicly. They have nothing to prove. They don't need to convince anyone. They work. And the gap between their reality and the public debate widens every month.

"Silence isn't neutral. Those who live the real product work. Those who only know the showcase comment. Guess which of the two groups shapes public opinion."

What this actually means

This segmentation isn't an accident. It's a perfectly rational business model. Free plans serve as a showcase and acquisition pipeline. Premium plans generate revenue. Every AI company does the same thing — and they have every right to.

But the consequences run deep:

1. We're creating a cognitive divide. Two groups of people discuss the same topic with fundamentally different experiences. One says "AI is a gimmick". The other says "AI transformed my work". Both are right — but they're not talking about the same product. And this misunderstanding contaminates every conversation: in business, in politics, in media.

2. Strategic decisions are made on the wrong basis. When a CTO decides their company's AI strategy based on their free-plan experience, they massively underestimate the technology. When a regulator legislates after a demo on a standard account, they regulate a product that doesn't exist one floor up. Decisions are made on faith in a truncated version of reality.

3. The productivity gap will accelerate. Companies and individuals who invest in premium plans build workflows, habits, and expertise that compound. Every month of intensive usage widens the gap. In a year, the difference between someone using free AI and someone on a Pro plan won't be 5x — it'll be an order of magnitude. Because it's not just the tool that's better. It's the person who learned to use it at full potential.

4. The AI debate is a class debate that won't say its name. $200/month is nothing for a California tech company. It's a significant budget for a freelancer in France. $100/month for Codex is a reasonable investment for a well-paid senior developer. It's unreachable for a student or junior developer. We're building a technology where real access — not marketing access, real access — correlates with purchasing power. This isn't new in tech. But the gap has never been this wide between the showcase and the product.

What should be done

I'm not naive. AI companies need revenue to fund colossal infrastructure costs. Tiered pricing is legitimate. I'm not asking for free access for everyone.

But I'm asking that we stop pretending the debate is honest.

For journalists: if you cover AI, you need to use premium plans. Not once. Daily, for weeks. Otherwise you're testing a marketing product, not the technology. It's like covering motorsport by driving a compact car. Your newsroom should budget a Pro subscription like it budgets a Reuters feed.

For regulators: before legislating, use the technology. Not a demo. Real usage, on a real workflow, for a real month. Put a Pro plan on your office's budget. It's $200 — less than a working lunch in Brussels. If you regulate the future of AI without touching the real product, you're regulating the future of aviation after a glider flight.

For business leaders: don't make strategic AI decisions based on your personal free-plan experience. Give premium plans to your best people for three months. Measure results. Then decide. The cost of a Pro plan for an entire team is less than the cost of a consultant who'll come explain what AI can do — poorly, since they probably don't use it on the Pro plan either.

For individuals: if AI is part of your job, invest in a premium plan. It's a professional tool. A developer who codes on a free plan and concludes AI is "mediocre" is a photographer judging their art with a disposable camera. You can't evaluate a technology you've never used at full potential.

The real divide

The AI divide isn't between those who use AI and those who don't. That would be too simple.

"The real divide is between those who use premium AI and those who think they're using the same thing. The first group ships. The second comments."

The free plan gives an impression. The premium plan gives a transformation. Between the two, there isn't a quota difference. There's a change of species.

And as long as the public debate is fed by people who've only known the impression, the decisions that follow will be disconnected from reality. We'll regulate yesterday's technology. We'll invest too little, too late. We'll lose ground to competitors who understood that $200/month isn't a subscription — it's a competitive advantage.

"The real danger in 2026 isn't that AI is overestimated. It's that the people underestimating it are deciding for the people living it. And they call it caution."

Sources

• OpenAI — ChatGPT pricing: official page listing every ChatGPT plan (Free, Plus at $20/month, Business, Pro at $200/month) and their respective quotas.
• OpenAI — Introducing ChatGPT Pro: official announcement of the ChatGPT Pro plan at $200/month, with expanded access to advanced reasoning models and deep research mode.
• OpenAI — Codex: official page for the Codex development agent, bundled into the Plus, Business and Pro plans with differentiated quotas.
• Anthropic — Claude pricing: official page listing the Claude plans (Free, Pro at $20/month, Max at $100 and $200/month) with their usage quotas and available models.
• Google — Gemini subscriptions: official page for Gemini plans (Free, Gemini Advanced via Google AI Pro and Google AI Ultra) with the latest Gemini models and extended capabilities.

Read also: The SDLC Is Dead — why the process was always broken, and why AI agents are making it impossible to pretend otherwise. And its follow-up: Coding Was Never the Job — if AI killed the process, what happens to the roles?

In my previous article, I argued that the SDLC is dead. That the ceremony, the process, the human gates — most of it was always waste. AI agents just made it impossible to pretend otherwise.

But killing the process raises an obvious question: if AI writes the code, runs the tests, generates the docs, and deploys to production — what's left for humans to do?

The numbers should wake you up: junior developer hiring in Big Tech has collapsed 73% in a single year. The "coder" job is disappearing in real time. But the answer to what's left isn't "nothing." It's "everything that actually mattered all along." We just couldn't see it because we were too busy typing semicolons.

Coding was never the job

Here's the thing nobody wants to say out loud: coding was always a translation layer. A lossy, slow, error-prone translation layer between what you meant and what the machine did.

You had a business rule in your head. You translated it into a programming language. The compiler translated it into machine code. At every step, fidelity was lost. Every bug was a translation error. Every code review was a check on whether the translation was accurate. The entire industry built ceremonies around managing the risk of this translation going wrong.

AI agents short-circuit the entire chain. You describe what you want. The agent produces working code. Not pseudo-code, not a draft — working, tested, deployable code. The translation layer that defined a generation of careers is being compressed to near-zero.

Andrej Karpathy recently built an open-source tool that scores every job in America on AI exposure, using data from all 342 Bureau of Labor Statistics occupations. Software developers score 8-9 out of 10. That's higher than nurses, physicians, and retail workers. The work product is digital, the job can be done from a home office, and the core activity — writing code — is exactly what LLMs are best at.

"The profession is being dramatically refactored."
— Andrej Karpathy

But here's the nuance that most people miss: that 8-9 score covers the entire "Software Developers" BLS category — coding and engineering lumped together. My argument is that the coding part of that score drives the exposure. The engineering part — deciding what to build, why, and how the pieces fit together — is precisely what AI cannot do. The coder is exposed. The engineer is not.

Strip away the coding, and what's left is what senior engineers have always known mattered most: understanding the domain, designing the architecture, making product decisions, and exercising judgment. That's what software development was always supposed to be. We just buried it under ten layers of syntax, frameworks, and process.

What my team looks like today

I'm not theorizing. My team is already moving this way — honestly, not completely there yet.

Most of my developers own the full chain: product understanding, code, tests, documentation, and release. They don't hand off to a QA team. They don't ask DevOps to configure the pipeline. They do it all — with AI agents handling the implementation layer.

But I'll be honest: we still have a dedicated PO for interoperability. In healthcare, interoperability — HL7, HPRIM, FHIR, the protocols that connect hospital systems — is such a deep and critical domain that it still requires a specialist who lives and breathes those standards. The business complexity is massive. What we're actively working on is simplifying the analysis layer by structuring all that business context so agents can help more. The role isn't gone yet — it's evolving.

Here's how we handle a feature request today. It comes in — from a user, from field feedback, from a spotted anomaly. The developer picks it up directly. They understand the business need, discuss the edge cases with the PO, describe the solution to the agent with the right architectural context, review the output, validate the tests, and push to production. One person. One morning. Same traceability.

In the old world, that same request went through a PO who writes a story, a developer who implements it, a reviewer who checks it, a QA who validates it, and a release manager who ships it. Five roles. Three weeks minimum. The need was the same. Only the ceremony changed.

My three interns and one apprentice — all final-year engineering students — work the same way. They don't specialize in "Java" or "Angular." They specialize in understanding the problem. The agent handles the rest. They progress faster than any junior I've seen in 14 years because they spend their cognitive energy on the domain, not on syntax battles.

This is not the future. This is a Tuesday.

The great merge

The most visible sign of this transformation is the convergence of roles. The walls between developer, product owner, designer, QA, and DevOps are collapsing. Not because the skills don't matter — but because one person can now own the full spectrum. This trend is already concrete in the US — and almost invisible in France, where job postings on APEC and Welcome to the Jungle still read like 2019. That gap is the opportunity.

Product Engineer — the most concrete new role

This is already showing up on job boards — around 3-5% of engineering postings in the US, and starting to appear in French scale-ups. A single person combining product vision, technical fluency, and domain expertise — previously split across PM, PO, and developer. Andrew Ng noted that teams are flipping ratios from 1 PM per 4 engineers to the equivalent of 2 PMs per 1 engineer, as AI compresses the implementation gap.

"Reflexive AI usage is now a baseline expectation."
— Tobi Lütke, CEO of Shopify

Shopify calls these people "spiky generalists" — deep in one area, but defaulting to the highest-impact work rather than staying in a prescribed role. When an agent can generate any UI component or backend endpoint, the value shifts from implementation to product judgment — understanding users, designing interfaces, making prioritization calls. The designer + frontend developer merge follows naturally.

Context Engineer — the role that doesn't exist on French job boards yet

This is what I do every day, and it's the role I'm most excited about — even though as of March 2026, you won't find a single "Context Engineer" posting on a French job site. The title exists at EY in New York. MIT Technology Review named the arc from "vibe coding to context engineering" as the defining shift of 2025. But in France? Zero. That lag is exactly the problem this article is about.

A Context Engineer doesn't write code — they design the information architecture that makes AI agents effective. Architecture decisions, business rules, domain constraints, all structured so the agent has exactly what it needs. It's not prompt engineering — it's systems thinking applied to AI. The companies that create this role first will have a massive advantage.

Software Orchestrator / Agentic Engineer — the most conceptual, and the furthest out

"The 'Software Engineer' title could vanish by 2026."
— Boris Cherny, creator of Claude Code at Anthropic

Cherny predicts it will be replaced by "Software Orchestrator" — someone who manages swarms of agents rather than writing code. Andrej Karpathy calls it "agentic engineering" — the evolution beyond vibe coding, where you design and manage AI workflows rather than chatting with a model. This is the limit case of role convergence — and the one that sounds most like science fiction. But managing agents toward goals, reviewing their outputs, designing their workflows? This is what I do at 9am on a Tuesday.

The end of standalone QA

If your architecture isn't testable, your QA team is compensating for the architecture. That's the uncomfortable truth behind the QA role as it exists in most organizations. When business rules are well-defined and the system is designed for testability, automated verification was always the right answer — even before AI. AI just made the gap impossible to ignore.

Agents generate comprehensive test suites alongside the code. They cover edge cases systematically. They run in seconds. The scripted manual QA workflow — follow a test plan, click through screens, fill bug reports — has no future. Google and Meta have already eliminated traditional QA roles in favor of SDETs (Software Development Engineers in Test).

What survives — and this matters — is the domain expert who notices when something feels wrong even when all tests pass. Exploratory testing, clinical workflow validation, the person who knows the system deeply enough to spot anomalies: that's judgment, and it's irreplaceable. But it's a skill embedded in every team member, not a separate role sitting behind a handoff.

The skills that actually matter

If you're a software professional wondering what to invest in, here's my honest take:

Domain expertise is the new moat. The person who understands why a workflow has seven states instead of three, why two database tables can't be merged even though they look identical, or why a business rule was implemented that way ten years ago — that person is irreplaceable. No agent has that knowledge. No model was trained on it. It lives in your head, and it's what makes the difference between code that works and code that works in the real world.

Architectural thinking is the new seniority marker. Clean Architecture, hexagonal boundaries, dependency inversion, system decomposition — these aren't abstract concepts anymore. They're the structure that makes AI agents effective. A well-architected system is one where agents can operate autonomously within clear boundaries. A poorly-architected system is one where every agent output needs manual review because nobody trusts where the code ends up.

Context engineering is the new core skill. The ability to structure domain knowledge, constraints, and decisions in a format that agents can consume. This is not prompt engineering. Prompt engineering is asking the right question. Context engineering is building the entire knowledge system that makes every question produce the right answer. It's the highest-leverage skill in software development right now.

Product vision is the new differentiator. When implementation is near-free, the bottleneck shifts entirely to knowing what to build. Understanding user needs, market dynamics, business constraints — and translating that into intent that agents can execute. The developer who also thinks like a product owner is worth ten who just "write code."

Judgment is the last line of defense. Knowing when the agent is wrong. Knowing when the test covers the obvious case but misses the critical one. Knowing when to ship and when to stop. This comes from experience, from scars, from having been wrong before. No shortcut. No model replacement.

One important nuance: none of this means understanding code no longer matters. You cannot supervise an AI that writes code if you cannot read code. The ability to evaluate what you can no longer efficiently produce yourself — that's a durable, asymmetric advantage. Coding isn't the job. But understanding code is still the foundation.

What to do about it

For individuals:

1. Stop investing in language expertise. "5 years of Java" is a depreciating asset. Invest in domain knowledge, architectural patterns, and learning to work with AI agents effectively. This week: list three business rules in your current project that only you know, and aren't documented anywhere. That's your moat. Start writing it down.
2. Learn to think in products, not features. Understand the full chain from user need to production. Don't wait for a PO to tell you what to build. This week: attend a user demo or support call and note three things the ticket didn't capture.
3. Build your context engineering skills. Practice structuring knowledge for agents. Start with an Architecture Decision Record (ADR) for your current project's three biggest constraints. Build a domain glossary. Write a constraint document that an agent can consume. This is the new literacy.
4. Develop domain depth. Pick an industry. Learn it deeply. The intersection of tech fluency and domain expertise is where the highest value lives.

For organizations:

1. Rewrite your job descriptions. Replace "5 years of Spring Boot" with "deep understanding of healthcare workflows" or "experience designing systems that evolve over decades." Instead of asking candidates to implement a sort algorithm, ask them to decompose a real business workflow into bounded contexts.
2. Merge roles deliberately. Don't wait for it to happen organically. Create Product Engineer roles. Give developers product ownership. Let your best people operate across the full spectrum. In France, this means working with HR, the CSE, and the syntec classification grid — it's a 3-5 year transformation, not a quarterly OKR. Start with new hires and voluntary reclassifications.
3. Invest in testable architecture over standalone QA. The money you spend on a separate QA team is better spent on architectural fitness functions, automated verification, and CI/CD pipelines. Embed quality judgment in every team member rather than isolating it in a handoff.
4. Invest in context infrastructure. Document your domain knowledge, architecture decisions, and business rules in agent-consumable formats. This is the highest-ROI investment in 2026.

A word for the experienced developer reading this with a knot in your stomach. If you have 8 years of Java and you're wondering if your career is over — it's not. Your domain knowledge, your understanding of why things were built the way they were, your instinct for what will break — that's exactly what survives. The transition doesn't start with learning a new title. It starts with naming what you already know that isn't code: the business rules, the architectural decisions, the domain quirks that live in your head and nowhere else. That knowledge is your moat. Start documenting it.

And a word of honesty about the next generation. My interns progress fast. But if junior hiring collapses 73%, how do the next interns get in? Domain expertise comes from working inside a domain — you can't develop it from the outside. The ladder my team is climbing is being pulled up behind them. I don't have a solution to that. But I refuse to pretend it isn't happening. If you're in a position to hire juniors, do it. Give them real problems, real context, real stakes. The industry needs them more than ever — even if the job descriptions haven't caught up yet.

"The knowledge and skill of being a software developer has been commoditised. If everyone can be a software developer, what does that mean if your identity function is that you're a software developer?"
— Geoffrey Huntley

Conclusion

Coding was never the job. The person whose primary value was translating business intent into programming language syntax — that role is being automated. Fast. Andrej Karpathy scored it 8-9 out of 10 on AI exposure. The market agrees: junior developer hiring in Big Tech has collapsed 73% in a year.

But software development? Software development is finally being born. Freed from the weight of syntax, it's becoming what it always should have been: understanding problems, designing solutions, engineering context, and exercising judgment. The roles are merging. The walls are falling. The person who can think about the product, design the architecture, engineer the context, and validate the output — that person doesn't just survive. They thrive.

My team already works this way. Every person owns the full chain. The interns learn faster than any junior I've ever seen. The quality is higher because the cognitive energy goes to the domain, not to debugging semicolons.

This is not a prediction. This is a Tuesday at my office.

Sources

1. Andrej Karpathy — LLM Job Exposure Scoring — AI exposure scores for all 342 BLS occupations (software devs: 8-9/10)
2. MIT Technology Review — From vibe coding to context engineering
3. EY — Context Engineer job posting
4. The Rise of the AI Product Engineer (Medium, Falk Gottlob)
5. Product School — Product Management Trends 2026
6. CNBC — Shopify CEO on AI-first hiring
7. Tobi Lütke on X — Shopify's "spiky generalists"
8. Boris Cherny (Anthropic) — "Software Engineer" title could vanish by 2026
9. Andrej Karpathy on X — "profession is being dramatically refactored"
10. Karpathy: Vibe coding fading, agentic engineering rising
11. Design Engineer job board
12. CodeRabbit — Developers are dead. Long live developers.
13. Washington Post — A big drop in programmers may be the first sign of job loss to AI
14. Revelio Labs — Is AI responsible for the rise in entry-level unemployment?
15. PwC — No more pyramids: Rethinking your workforce for the agentic AI era
16. Omnis Partners — The Rise of the Full-Stack Generalist
17. CIO.com — Demand for junior developers softens as AI takes over
18. Geoffrey Huntley — Software development now costs less than the wage of a minimum wage worker

Yes, AI is just a tool. But it's the most disruptive tool we've ever had. And this is just the beginning.

For months now, I've been reading articles about AI. On LinkedIn, on X, on tech blogs, on every corner of the internet. AI and disruption. AI and regression. AI and quality collapse. AI and slop. AI is killing software. AI is making us dumber. AI is producing garbage code. AI is the end of craftsmanship.

I've read hundreds of them. And I'm telling you: I disagree with most of them, in all my being.

Not because the concerns aren't real. Some are. But because the overwhelming narrative is fear disguised as wisdom. People clinging to the way things were, dressing up resistance as rigor, calling inertia "quality standards." The loudest voices are the ones with the most to lose - the process owners, the methodology consultants, the people whose careers are built on the very ceremony that AI is making obsolete.

So here it is. My point of view. Not a reaction to one article, but to all of them. This is how I see the software development job in 2026, and why this year is the welcome disruption I've been secretly hoping for.

Boris Tane recently wrote that the software development lifecycle is dead. AI agents didn't make it faster, they killed it. He's right. But I want to be clear: I didn't need AI to tell me the SDLC was broken. I've been saying it for years.

What AI agents are doing now isn't revealing a new truth. They're making an old truth impossible to ignore: most of the process was always waste. And nowhere is this more visible than in European industry - especially in France - where organizations are still operating like it's 2015.

Who I am and why this matters

I'm a Tech Lead Manager. I've been working in large enterprises since 2012, from banking to healthcare. I lead a team of developers, working on a 30-year-old legacy system and its migration to a modern ecosystem. A disclaimer: I'm not an AI expert. I'm a senior developer who went all-in on AI a year ago. Five months ago, I wouldn't have written this article. The recent wave of LLM models completely rewrote how I think about this job.

I've spent over a decade in this world. A world where a bug doesn't break a dashboard, it breaks a critical business workflow. A world where people will tell you that you absolutely need the full SDLC ceremony because the stakes are too high.

And I'm telling you: the SDLC was always the wrong answer to the right question.

Europe's mammoths are sleepwalking into irrelevance

Here's what I see from the inside of French industry: nothing has changed.

The same organizations. The same processes. The same job postings. The same management structures. Robust? Sure. The way a mammoth is robust - massive, resilient, perfectly adapted to a world that no longer exists.

American startups are shipping products with 3-person teams and AI agents. Chinese companies are iterating at a pace that makes Silicon Valley nervous. And in France? We're still debating whether to adopt Agile or stay waterfall. We're still writing 200-page specifications - and if they even exist, they're most likely outdated and lost somewhere in a filesystem on a Windows Server 2008. We're still hiring based on how many years of Java someone has on their CV.

The numbers tell the story: the US has produced 40 AI foundation models, China 15, and all of Europe combined just 3. The EU holds 5% of global AI compute versus 74% for the US. European worker productivity has dropped to 76% of American levels. Meanwhile, Big Tech junior hiring has collapsed from 32% of new hires to just 7%, with entry-level positions down 73% in the past year alone.

The European software industry - and the French one in particular - has always been conservative. Heavy processes, heavy hierarchies, heavy certifications. There was a time when that solidity was an advantage. That time is over. 2026 is the disruption year. Not next year. Not in five years. Now.

The organizations that don't react will be outpaced by teams a tenth their size, running circles around them with AI agents, shipping in days what used to take quarters. The mammoth doesn't need to run faster. It needs to evolve. And it's not evolving.

France has world-class engineers, deep domain expertise, and serious industries. What it lacks is the courage to throw away the processes that no longer serve it. We built our reputation on rigor and robustness.

"Rigor without speed is just slowness. And robustness without adaptability is just weight. The mammoth was robust too. Look where that got it."

You're still hiring for the wrong skills

Open any job board in France right now. Look at the tech postings. What do you see?

• "5 years of Java required"
• "Expert in Angular, minimum 3 years"
• "Strong knowledge of Spring Boot"
• "Must know React Native"

In 2026. With AI agents that write production-quality code in any language, any framework, in minutes.

"Recruiting on programming language expertise is like recruiting drivers based on their knowledge of horse breeds."

The vehicle changed. The skill that matters changed with it.

An AI agent doesn't care if you've spent 10 years writing Java or 2 months. It writes Java. It writes TypeScript. It writes Python. It writes whatever you need, often better than the "expert" you're trying to hire, because it's seen more codebases than any human ever will.

So what should you hire for? The things agents can't do:

• Domain expertise. Understanding the problem space. Knowing the business rules that no specification fully captures. Knowing why a workflow has seven states instead of three. This is what gives agents the right context to produce the right code.
• Architectural thinking. Clean Architecture, hexagonal boundaries, dependency rules, system design - the ability to structure systems so they remain maintainable, testable, and evolvable. Agents need to know where to put things. Someone has to define that.
• Context engineering. The new core skill. The ability to give agents the right constraints, the right decisions, the right domain knowledge so they produce what you actually need. This is what separates a developer who uses AI from a developer who is multiplied by AI.
• Judgment. Knowing when the agent is wrong. Knowing when the architecture doesn't fit. Knowing when the test covers the wrong edge case. Knowing when to ship and when to stop.

None of these are programming languages. None of these show up on a French job posting. And that's the problem.

But it goes further than rewriting job descriptions. The roles themselves need to be rethought. A developer, a product owner, and a designer can now be the same person. When AI handles the implementation, one person with domain knowledge and product vision can design, build, and ship. Shopify's CEO now requires teams to prove AI can't do a job before requesting new headcount. Anthropic's CEO predicts the first billion-dollar one-person company by 2026. A quarter of Y Combinator's current batch has 95% of their code written by AI. PwC calls it the "rise of the generalist" — the traditional workforce pyramid is collapsing into small teams of AI-augmented generalists who own the full chain from idea to production.

2026: the year everything breaks

This isn't gradual. The disruption is happening now, and it's happening fast. In the first two weeks of March 2026 alone: ServiceNow CEO Bill McDermott said on CNBC that graduate unemployment "could easily go into the mid-30s." Meta, after crossing $200B in annual revenue, reportedly began planning layoffs affecting up to 20% of its workforce to fund AI infrastructure. Naval Ravikant declared that "pure software is rapidly becoming un-investable." A random guy in Florida sold his entire house in 5 days using ChatGPT - no real estate agent, no commission, no experience. Anthropic doubled its AI usage limits and expanded its 1M context window to general availability. Two weeks. Not two quarters.

For employees: the developer who refuses to work with AI agents will be significantly outproduced by the one who does. McKinsey found that teams with full AI adoption saw productivity gains exceeding 110%. Not because the others are worse engineers. Because the tools changed and they didn't. Expertise in a programming language used to be a career. In 2026, it's a commodity. The agents commoditized it. What's left is everything above the code: domain knowledge, architectural vision, context engineering, judgment. If you want to see which tasks are already being automated in your job, look at the Job Task Visualizer - AI doesn't replace jobs wholesale, it eats them task by task. And if you're still not sure, check Is My Job Screwed? for a personalized risk assessment.

For organizations: the company that still runs two-week sprints, three-day PR reviews, manual QA cycles, and quarterly release trains will ship in a quarter what an AI-native team ships in a week.

"That's not a productivity gap. That's a survival gap. Your competitors aren't optimizing their process. They're eliminating it."

For the French tech ecosystem: we have world-class engineers. We have deep domain expertise in healthcare, aerospace, finance, energy. We have talent. What we don't have is the organizational agility to unleash that talent. We're strangling our best people with processes designed for a world that doesn't exist anymore, and then wondering why we're falling behind.

It's time to react. Not next quarter. Not after the next reorganization. Now.

Ship fast or ship never

Here's what drives me: impact.

I want to push to production as fast as possible. Not because I'm reckless. Because code sitting in a branch, waiting in a review queue, stuck behind a release train - that code has zero value. It's inventory. And inventory is waste.

The only code that matters is the code running in production, solving real problems for real users. Everything between your intent and production is friction. The job is to minimize that friction.

Before AI agents, "ship fast" was a cultural aspiration. You'd say it in team meetings, then spend three days waiting for a PR review. Now, with agents generating code, tests, and deployment configs in one loop, shipping fast is the default. The question isn't "how do we ship faster?" anymore. It's "what's still in the way?"

The answer, most of the time, is process. Process, and organizations too afraid to let go of it.

Humans have no place in the loop

I'll say something that makes a lot of people uncomfortable: humans should not be testing software. They shouldn't be writing documentation either. Or configuring CI/CD pipelines. Or running deployments. Or even leading most meetings.

And I'm not even talking about coding - that's already handled by agents.

Manual QA is a relic. A human clicking through screens, following test scripts, filing bug reports - that entire workflow is slower, less reliable, and less thorough than automated tests. Every time. Without exception. The same goes for documentation that no one reads because it's always outdated - agents generate it from the code, always in sync, always accurate. CI/CD pipelines? Agents configure, maintain, and optimize them. Deployments? Automated end to end. Meetings? Sub-agents with personas debate, challenge, and produce better decisions than most rooms full of humans.

If your tests can't be automated, your architecture is wrong. That's not an AI opinion. That's a software engineering opinion I've held for years. Testability is a design property. If you need a human to verify your software works, you've built it wrong.

Here's what 2026 looks like: everything is generated alongside the code, everything is automated, everything runs in CI/CD. Faster and more reliable than any human. The agent writes the code, the tests, the docs, the deployment configs - together. Not as an afterthought. Not in separate phases. The entire chain from intent to production is one continuous, automated flow.

Does this happen overnight? No. Building this level of automation takes time, effort, and discipline. It's actually my main focus this year for my applications. But that's the point - this is where you should be investing your energy. Not in manual processes, not in human gates, but in building the automated machinery that lets you ship with confidence.

Your domain isn't special (and that's the point)

People will tell you their industry is different. That you can't move fast with sensitive data. That compliance requires the full SDLC ceremony.

They're confusing the requirement with the implementation.

Compliance demands traceability, not ceremony. It demands that you can prove what changed, why, and that it was verified. It never demanded story points. It never demanded three-day PR reviews. It never demanded manual QA sign-off.

An agent that generates code, writes tests, runs them, checks types, validates against architectural constraints, and logs every step provides more traceability than a human developer who reviewed a PR half-asleep on a Friday afternoon and a QA tester who clicked through 60% of the test script before lunch. We just can't accept that yet, because the ceremony felt safe.

Yes, there are real regulatory constraints - GDPR, the EU AI Act, industry-specific compliance. These are not excuses, they are requirements. And automated pipelines with full audit trails satisfy them better than a human who forgot to update the change log. The regulation demands proof. Agents provide it.

If the SDLC can die in the most regulated, conservative, risk-averse corners of the software industry, it can die anywhere. The question isn't whether your domain is too critical for this. It's whether you're honest enough to admit the ceremony was never what kept it safe.

What I actually do now

My role has fundamentally changed. I used to spend my days in the process machine:

• Writing and refining tickets nobody read twice
• Sitting in sprint planning, pretending estimation works
• Reviewing PRs line by line
• Unblocking developers stuck on context they didn't have
• Waiting for QA to manually validate what automated tests already covered

Now I spend my days on things that actually matter. Here is what a typical morning looks like: a bug report comes in. In the old world, this is a multi-week odyssey — ticket, triage, estimation, assignment, development, code review, QA, release train. Now, I describe the problem to the agent. I point it to the right module, the architectural constraints, the business rules. Minutes later: a fix, new tests, a passing CI pipeline. In production before lunch. Same traceability. Better test coverage. No ceremony.

Context engineering. Building the proper context for each application so agents can perfectly understand what we tell them to do. Architecture decisions, constraints, domain knowledge, business rules - all structured so the agent has everything it needs to produce the right code. The quality of what agents build is directly proportional to the quality of context you give them.

Supervision and workflows. We build the supervision layer. The coding, the review, the testing, the release - that's handled by the tools, the agents. We design the workflows, set the guardrails, define what "done" looks like. Then we let the agents execute.

Even meetings. We're experimenting with meetings handled by multiple sub-agents with personas - domain experts, architects, product owners - that debate, challenge each other, and produce structured reports and decision proposals. Early results are promising: the output is often more thorough and less biased than what a room full of distracted humans produces in an hour.

Pushing to production. The fastest path from intent to impact. That's the goal. Always.

The maker knows

I'm a maker. Evenings and weekends, I experiment with AI - trying to keep up with the crazy things that come out every single day. We've never had this much innovation at once. Agents and developer brains combined are producing at lightning-fast velocity, and the stream of new tools, new models, new possibilities never stops. Just look at the fastest growing GitHub projects this month: autonomous agents hitting 122K stars, agentic skill frameworks, full AI toolkits, open-source SuperAgents by ByteDance - and repos teaching you how to build your own Claude Code clone from scratch. Next month's list will look completely different. That's the pace we're talking about.

Makers don't follow an SDLC. You have an idea. You prototype. You test it - not by writing a test plan, but by plugging it in and seeing if it works. You iterate. The feedback loop is immediate. You don't write a ticket before soldering a sensor to a breadboard. You don't estimate how many story points it takes to wire a relay. You don't ask a QA team to verify your LED strip works. You plug it in. It lights up or it doesn't. You fix it or you try something else.

What AI agents are bringing to professional software development is the maker's feedback loop. Intent, build, test, iterate, ship. No ceremony. No handoffs. No waiting. No manual QA. Just building and shipping.

I've always built things this way. The industry is finally catching up.

What survives

Not much.

Domain knowledge survives. The agent needs someone who understands the problem space. Legacy systems are deep. Business domains are deep. The intersection of both is a maze that no model has fully mapped.

Architectural intent survives. Clean Architecture isn't dead. The hexagonal boundaries, the dependency rules, the separation of domain from infrastructure - these still matter. But they're expressed as context for the agent, not as diagrams on a whiteboard that get stale in a week.

Automated verification survives and becomes everything. Tests, type checks, security scans, behavioral diffs, architectural fitness functions - the entire safety net is code, not people. Code checking code.

Observability survives and becomes the foundation. When code ships continuously, your monitoring stack is your last line of defense. We're moving from "review before ship" to "ship and verify continuously."

"Everything else is ceremony. And ceremony is what you do when you don't trust your tools, your architecture, or your automated checks. The tools got good enough. Time to let go."

And what about juniors? People will tell you that removing process kills the apprenticeship pipeline. I see the opposite. I currently have three interns and one apprentice, all in their final year of engineering school. The ease with which they pick up AI tools makes them immediately competitive. Onboarding is simplified — they ask their agent questions, it has the business context, the domain specifics, the architectural rules. They progress at a speed I have never seen before in 14 years. AI doesn't kill the junior pipeline. It accelerates it. The juniors who learn to work with agents develop domain knowledge and judgment faster, not slower — because they spend less time fighting syntax and more time understanding the problem.

What to do Monday morning

If any of this resonates, here is where to start:

1. Measure your cycle time. How long from intent to production? Identify every human gate in that chain.
2. Invest in automated verification. Tests, type checks, architectural fitness functions, audit trails. Build the safety net before you remove the human gates.
3. Rethink one role. Not just the job description — the role itself. Can your developer also own the product vision? Can your PO also design? Replace "5 years of Java" with domain expertise, architectural thinking, context engineering, and judgment.
4. Run a pilot. One team, one product, one workflow. Replace manual review with automated checks. Measure speed and customer feedback for 30 days. Quality is subjective — what matters is what your users actually report.
5. Build the context layer. Document your architecture decisions, domain rules, and constraints in a format agents can consume. This is the highest-leverage investment you can make right now.

Conclusion

I read a lot of articles about AI. Most of the time, I disagree. At some point, I needed to speak up about it. AI helped me do it fast, in the right way — structuring the article, writing it in two languages, fact-checking the data, sourcing the statistics. This article is itself proof of what I'm arguing: the tools are here, and they multiply what one person can do.

I'm not claiming to have all the answers. Agents get things wrong. They hallucinate, they miss edge cases, they produce code that looks right but isn't. I've seen it. Studies even show experienced developers can be slower with current AI tools on codebases they already know well. The gains come from rethinking the workflow, not just bolting AI onto the old one. But the answer isn't to go back to three-day PR reviews and manual QA. The answer is better context, better guardrails, better automated verification. The developers who adapt will thrive. The ones who don't will be replaced - not by AI, but by developers who use AI.

AI needs to be part of every day. Not as a novelty, not as an experiment — as a reflex. The use cases are endless and most of them haven't been discovered yet. This is just the start, and everything is going to move very fast.

Stop debating. Start building. The tools are here. The only thing missing is the will to use them.

What's the one process you'd kill tomorrow if you could?

Read the sequel: Coding Was Never the Job — if AI killed the SDLC, what happens to the roles? The coder disappears. The software engineer is finally born.

Sources

1. Stanford HAI AI Index Report 2025 — AI foundation models by country (US 40, China 15, Europe 3)
2. Epoch AI — AI Supercomputers Performance Share by Country — global AI compute share (US ~74%, EU ~5%)
3. OECD Compendium of Productivity Indicators 2025 — Europe/US productivity gap
4. Revelio Labs — Is AI responsible for the rise in entry-level unemployment? — Big Tech junior hiring collapse
5. McKinsey — The State of AI — productivity gains from AI adoption
6. CNBC — Bill McDermott (ServiceNow) on graduate unemployment
7. TechCrunch — Meta reportedly considering layoffs affecting up to 20%
8. Naval Ravikant on X — "Pure software is rapidly becoming un-investable"
9. NBC Miami — Man sells his house in 5 days using ChatGPT
10. Anthropic doubles Claude usage limits / 1M context window now GA
11. CNBC — Shopify CEO requires proof AI can't do the job before hiring
12. Inc. — Anthropic CEO predicts first billion-dollar one-person company
13. Garry Tan on X / CNBC — 25% of YC batch with 95% AI-written code
14. PwC — No more pyramids: Rethinking your workforce for the agentic AI era
15. AutoGPT on GitHub — autonomous agents (122K+ stars)
16. Job Task Visualizer — AI task automation by occupation
17. Is My Job Screwed? — personalized AI risk assessment

After renovating the two other bedrooms in the ninth article of this series, it was time to tackle the complete renovation of the cellier. This space, located on the ground floor, housed the boiler and provided access to the basement. This renovation represented a significant technical challenge: transforming this utility space into two functional and well-insulated rooms - an office and a pantry/laundry room - while preserving access to the basement and integrating the boiler.

The project involved several complex technical steps: ceiling insulation with a hanger system in the hollow block ceiling, BA13 plasterboard ceiling installation, wall insulation, and the creation of two distinct spaces with their own functionalities. This renovation was essential to optimize the use of this space and improve the thermal comfort of the house.

Initial State / Demolition

The cellier still retained its original 1970s state. The space was raw, with a hollow block ceiling (concrete ceiling with cells), and suboptimal organization. The boiler was installed in a corner of the room. Access to the basement was enclosed in a stairwell with two walls that completely closed off the room, which significantly limited the use of the space.

To optimize the space and fully exploit the available surface area, I decided to demolish these two walls to completely open up the room and exploit the space above the basement. This demolition freed up the space and created an opening to the basement, while maintaining functional access.

The first step was to demolish the existing elements and prepare the space: remove old finishes, demolish the two stairwell walls, clean surfaces, and prepare the walls and ceiling for the upcoming insulation and finishing work.

Ceiling Insulation and BA13 Installation

Ceiling insulation was an important step to improve the comfort of the space. The hollow block ceiling needed a suspension system to support the metal framework and BA13 plasterboard.

I installed metal hangers directly into the hollow block ceiling. These hangers allow suspending a metal framework below. I drilled the ceiling at strategic locations and secured the hangers firmly to support the weight of the insulation and BA13 plasterboard.

Once the hangers were installed, I set up a metal framework with rails and studs. This framework forms a grid that supports the insulation and plasterboard. Between the hollow block ceiling and this framework, I installed a thick layer of 20 cm mineral wool insulation, which significantly improves the comfort of the space.

Once the metal framework and insulation were in place, I proceeded with the installation of BA13 plasterboard on the ceiling.

To facilitate installation, I used a mechanical tool. This tool is essential for this type of work, as it avoids having to manually hold panels weighing several tens of kilograms overhead.

I installed the BA13 panels one by one, screwing them firmly to the metal framework with drywall screws. The panels were placed to create regular joints that would then be filled and sanded to obtain a smooth and uniform surface.

Wall Insulation

To complete the thermal insulation of the space, I also insulated the walls.

I did the wall insulation with extruded polyurethane panels, placed between a metal framework fixed to the walls. Once the insulation was in place, I covered the walls with BA13 panels.

Electrical and Network Installation

The electrical panels were completely redone and brought up to code during the previous renovation, before the cellier renovation.

The office will be the nerve center of the home's computer network. Everything will be housed in a 33U server rack. It was therefore necessary to bring all RJ45 cables to the office, exiting through the ceiling at the location of the server rack.

For the office, I planned a complete network installation with network outlets in the walls. I installed a patch panel to organize network cables.

I also installed multiple outlets for office and laundry equipment, as well as appropriate lighting for each space. All electrical and network cables were installed in conduits to ensure safety.

Plumbing Installation

I also added a small radiator just in case, despite the extensive insulation done. It was necessary to review the copper plumbing network hidden in the wall to add a new branch. Everything was done in multilayer to facilitate the operation.

I provided shut-off valves to allow isolation of each circuit in case of maintenance.

Creation of Two Spaces

One of the main objectives of this renovation was to transform the cellier into two functional and distinct spaces: an office and a pantry/laundry room. This division of space required careful planning to optimize the use of each zone.

The Office

I created the office in one part of the space, with sufficient surface area to install a work surface, shelves, and storage space. This space benefits from natural lighting thanks to a large white aluminum sliding window like the rest of the house, which brings a lot of natural light. The thermal and acoustic insulation installed on the ceiling and walls ensures a comfortable and quiet working environment.

The space can also serve as a guest room thanks to a pull-out bed, making this space a versatile area. Wall storage and shelves allow organizing equipment and office supplies.

The Pantry/Laundry Room

The pantry/laundry room is a space that already existed but had never been renovated. After breaking down the walls providing access to the basement to increase the usable volume, we will take advantage of it to use it as a laundry room to hang laundry and store food and other items.

I kept the boiler in this space, with easy access for maintenance. The installed insulation ensures that the heat produced by the boiler contributes to the comfort of the space without creating overheating. I preserved access to the basement, with a trap door.

The space was organized to optimize storage and facilitate daily use.

Finishes and Final Result

Once the insulation and partitioning work was completed, I proceeded with the finishes: filling and sanding joints between BA13 panels, preparing walls for painting, and applying white paint to walls and ceiling. The white walls create a bright and modern atmosphere in both spaces.

Electrical and network finishes were finalized, with outlets and switches installed, and the network infrastructure operational. Laundry equipment can now be connected, and the office is ready to accommodate computer and work equipment.

The final result is a transformed space, with two functional and well-insulated rooms. The office offers a comfortable and quiet working environment, with a large window bringing natural light, while the pantry/laundry room is a practical and organized space for daily tasks and storage, with the boiler integrated harmoniously.

Conclusion

The complete renovation of the cellier is now finished. The result is a transformed space, with two functional and well-insulated rooms: an office and a pantry/laundry room. This renovation significantly improves the comfort and functionality of this space, while preserving access to the basement and harmoniously integrating the boiler into the pantry/laundry room.

After renovating the parental bedroom in the eighth article of this series, it was time to tackle the complete renovation of the two other bedrooms in the house. These two bedrooms still retained their original 1970s finishes, with colorful wallpaper that no longer met our expectations. This renovation involved complete wallpaper removal, replacement of windows with modern, insulated models, careful wall preparation, and installation of new flooring with insulation.

These two bedrooms represented an interesting challenge: one was covered with blue wallpaper, the other with pink wallpaper. Each bedroom required a similar but adapted approach to its specific condition. The project required meticulous planning for each step, from demolition to final finishes.

Initial State / Demolition

The two bedrooms still retained their original 1970s finishes. The first bedroom was covered with blue wallpaper that had aged and no longer met our aesthetic expectations. The second bedroom was covered with pink wallpaper, also dated. The floors were covered with old coverings that required complete replacement. The original windows were obsolete and poorly insulated.

The first step was to demolish the existing elements: completely remove the blue and pink wallpaper from the walls, which revealed the real condition of the underlying walls. Removing the wallpaper required patience and method to avoid damaging the walls.

Window Replacement

The old bedroom windows, dating from the 1970s, were not to our taste and no longer met our expectations in terms of thermal and acoustic insulation, nor aesthetics. I therefore decided to replace them with new modern, insulated white aluminum sliding windows.

Window replacement was carried out in both bedrooms. The new aluminum sliding windows bring a lot of natural light into the bedrooms and offer a clear view of the outside. The replacement significantly improved the thermal and acoustic insulation of the rooms, while modernizing their aesthetics.

Wall Preparation

After removing the wallpaper, the walls required careful preparation before painting. I filled holes and imperfections with joint compound. In the closet, there were quite a few cracks that required properly repairing the walls with tape and joint compound. Wall sanding followed to obtain a smooth and uniform surface before painting.

Wall Painting

The walls were painted white to create bright and modern spaces. This step required several coats of paint to achieve a uniform and quality finish.

Floor and Laminate

I first installed a thermal and acoustic insulation underlayment to improve the comfort of the bedrooms. Then, I installed a light wood-look laminate that adds a modern and warm touch to the bedrooms.

Conclusion

The complete renovation of the two other bedrooms is now finished. The result is a functional, modern, and aesthetic space. The bedrooms have been transformed from dated 1970s rooms into contemporary and welcoming spaces.

The new aluminum sliding windows bring a lot of natural light and significantly improve insulation. The white walls create a soothing and modern atmosphere, while the light laminate flooring adds a warm touch to the whole. The thermal and acoustic insulation improves living comfort in these spaces.

The two bedrooms are now pleasant and comfortable living spaces, perfect for relaxing and resting.

After renovating the living room in the seventh article of this series, it was time to tackle the complete renovation of the parental bedroom. This bedroom is the largest in the house and represented a major challenge: expanding it to create an integrated dressing room. This major transformation involved significant demolition, reconstruction of new spaces with a metal framework and BA13 boards, as well as all necessary finishing work.

Demolition

The parental bedroom still retained its original 1970s finishes. The walls were covered with wallpaper, including a purple wall that required complete stripping. The floor was covered with parquet that had aged and no longer met our expectations. A built-in closet occupied part of the bedroom and had to be dismantled to free up space.

The first step was to demolish the existing elements: strip the purple wall, remove the parquet to expose the concrete floor, dismantle the bedroom closet. To expand the bedroom and create the new spaces, it was also necessary to break down the wall leading to the old WC. This partial demolition freed up the space needed for the dressing room.

Construction of New Spaces

The construction of new spaces was carried out with a metal framework (rails and studs) to create the structure of the new partitions. I then installed standard BA13 boards for the bedroom walls.

Dressing Room

Creating the dressing room was done with melamine panels from Brico Dépôt, assembled using pocket holes (invisible screws). Since the dressing was too large to be moved, it was assembled directly inside the room. Construction was progressive, with element assembly and support installation, then storage organization.

The final dressing room is a modern built-in closet with shelves for storage, a wardrobe with hanging rod, and drawers for organization. A wooden sliding door between the bedroom and the dressing room, from Brico Dépôt, was installed to separate the two spaces.

Closet

A built-in closet was created in the bedroom for storage. Construction began with preparation of the existing walls: filling, joint compound application, sanding, then painting. Wooden shelves were mounted on the walls for storage. Plumbing pipes were integrated into the closet structure to supply the bedroom radiator.

The final closet is a built-in sliding wardrobe extending from floor to ceiling, with natural wood doors (pine).

Floor and Finishing

The bedroom floor was prepared with green insulation panels (underlayment) to improve thermal and acoustic insulation. The laminate flooring, like in the other bedrooms and living room, was then installed.

Finishing involved applying joint compound to the walls to hide screws and joints between BA13 boards. The walls were painted white to create a bright and modern space. The radiator was dismantled and spray-painted white (formerly blue). The window was replaced with a white aluminum sliding window.

Final Result

The complete parental bedroom renovation is now finished. The result is a functional, modern, and aesthetic space that combines elegance and practicality. The expanded bedroom now offers an integrated dressing room. The light flooring adds a warm touch to the whole, and the large window offers a magnificent view of the garden.

Conclusion

The complete parental bedroom renovation is now finished. The result is a modern, functional, and aesthetic space that perfectly meets our needs.

This project allowed me to learn a great deal about expanding a room, creating new spaces with metal framework and BA13 boards, and building an integrated dressing room. The parental bedroom is now a pleasant and comfortable living space, perfect for relaxing.

After renovating the kitchen in the sixth article of this series, it was time to tackle the complete living room renovation. This major step in the renovation project involved a total transformation of the space: complete demolition, replacement of glass doors, fireplace work, electrical and plumbing network installation, wall preparation and painting, floor preparation, flooring installation, wood-burning stove installation with chimney, and finally TV and soundbar installation.

This living room renovation was essential to create a comfortable, modern, and aesthetic living space that would become the heart of the house. The project required many technical steps and meticulous planning for each element, from demolition to final finishes.

Initial State / Demolition

The living room still retained its original 1970s finishes. The walls were covered with wallpaper. The floor was covered with white carpet that had aged and no longer met our expectations. The old fireplace needed a complete renovation, and the original glass doors were obsolete and poorly insulated. The entire space needed a complete renovation.

The first step was to demolish the existing elements: removal of wallpaper from the walls, removal of the white carpet to expose the concrete floor, complete demolition of the fireplace, and preparation of the space for all upcoming work.

Glass Door Replacement

The old glass doors, dating from the 1970s, were not to our taste and no longer met our expectations in terms of thermal and acoustic insulation, nor aesthetics. I therefore decided to replace them with new modern, insulated sliding doors.

The new doors bring a lot of natural light into the living room and offer a clear view of the garden. The replacement significantly improved the room's insulation and overall aesthetics.

Fireplace Work

The old fireplace needed a complete renovation. It was an open hearth that no longer met current safety standards and took up a lot of space in the living room. I started by completely demolishing the existing structure to prepare for the installation of a new modern wood-burning stove, more efficient and compliant with current standards. This demolition freed up space and prepared the area for future installation work.

The fireplace work required removing old materials, preparing the opening for the new stove, and preparing the passage for the new chimney to the roof.

Electrical and Plumbing Installation

The electrical installation was planned precisely for each piece of equipment. I installed electrical conduits in the walls, with junction boxes at the planned locations for the TV, soundbar, power outlets, and lighting.

Plumbing was also prepared for future needs, with networks installed in the walls to facilitate any future installations.

Wall Preparation

The existing walls were prepared for painting. After removing the wallpaper, I sanded the walls to eliminate glue residue and obtain a smooth surface. The walls were then carefully cleaned to remove any traces of dust and dirt. Once the preparation was complete, the walls were ready to be painted directly.

Wall Painting

The walls were painted white to create a bright and modern space. This step required several coats of paint to achieve a uniform and quality finish. Teamwork allowed us to speed up the process and achieve a professional result.

TV and Soundbar Installation

The installation of the TV and soundbar required precise planning. I first marked the locations on the wall, taking into account optimal heights for visual comfort and aesthetic alignment.

Floor Preparation

The floor needed significant preparation before installing the new covering. I started by installing a green insulating underlayment to improve thermal and acoustic insulation.

Flooring Installation

For the floor, I chose a light wood-look laminate that adds a modern and warm touch to the living room.

Wood-Burning Stove Installation

The installation of the wood-burning stove was an important step in this renovation. I chose a modern and efficient stove that brings both heat and aesthetics to the living room. The stove was positioned in the prepared location, with a protective plate on the floor to protect the flooring.

The installation required connecting the stove to the chimney and ensuring that all safety standards were met.

Chimney Work

The chimney work required roof intervention to install the flexible chimney flue. I installed a flexible metal flue that adapts to the constraints of the existing installation. Sheet metal work was done to ensure waterproofing around the chimney on the roof.

Chimney Enclosure Construction

To aesthetically integrate the chimney flue into the room, I built a drywall enclosure around the flue. This structure was made with a metal framework, then covered with fire-resistant drywall panels to meet safety standards.

Final Result

The complete living room renovation is now finished. The result is a functional, modern, and aesthetic space that combines elegance and practicality. The wood-burning stove provides a pleasant heat source and creates a warm atmosphere, while the large glass doors offer a magnificent view of the garden and bring abundant natural light.

The TV and soundbar installation allows for a modern relaxation space, and the light flooring adds a warm touch to the whole. All networks are properly installed, and the space is ready for daily use.

Conclusion

The complete living room renovation is now finished. This major step in the project required many technical skills and meticulous planning, from the initial demolition to the final finishes. The result is a modern, functional, and aesthetic space that perfectly meets our needs.

This project allowed me to learn a great deal about complete living room renovation, from network management to wood-burning stove and chimney installation, through flooring installation and multimedia equipment. The living room is now a pleasant and comfortable living space, perfect for relaxing and entertaining.

After renovating the new entry in the fifth article of this series, it was time to tackle the complete kitchen renovation. This major step in the renovation project involved a total transformation of the space: complete demolition, wall reconstruction, electrical and plumbing network installation, tiling, cabinet and appliance installation, and finally the finishing touches with the backsplash and decorative elements.

This kitchen renovation was essential to create a functional, modern, and aesthetic space that would become the heart of the house. The project required many technical steps and meticulous planning for each element, from the networks to the final finishes.

Initial State

The kitchen still retained its original 1970s finishes. The walls were partially covered with small green mosaic tiles, and the paint was peeling in places, revealing the underlying structure. The floor was raw concrete, and the entire space needed a complete renovation.

This initial demolition freed up the space and prepared the area for all the upcoming reconstruction work.

Floor Preparation

The floor needed significant preparation before installing the new covering. I started by completely removing the old tiles, then removed the old plumbing. A breach that split the floor in two, corresponding to the wall of the cellar underneath, was sealed with metal and cement to ensure structural integrity.

Framing, Insulation and Drywall

To create a solid and insulated structure, I started with the ceiling installation. Since the ceiling is a hollow-core slab, I installed the rail structure for the drywall with hangers directly into the hollow cores of the slab, creating a space filled with thermal insulation. The ceiling was completed first, before proceeding with the walls.

Then, I installed a metal framework with studs and rails for the walls, filled with thermal insulation for excellent energy performance. OSB panels were used in the lower part of the walls, under the window, to strengthen the structure and allow future attachment of kitchen cabinets.

For the walls, I used moisture-resistant drywall panels, specifically designed to resist moisture. The panels were fixed to the framework, then the joints were filled with joint compound and joint tape. Several layers of compound were applied before final sanding to obtain a perfectly smooth surface.

Window Installation

A new window was installed to replace the old one. This modern sliding window brings a lot of natural light into the kitchen and offers a view of the garden.

The window was positioned to optimize natural lighting and create a pleasant space for cooking.

Electrical Installation

The electrical installation was planned precisely for each appliance. Each point was marked and labeled with its exact height:

• Range hood at 1.30m height
• Oven at 0.95m height
• Microwave at 1.20m height
• Cooktop at 0.30m height
• Refrigerator at 0.30m height

Electrical conduits were installed in the framework, with junction boxes at the planned locations.

Plumbing Installation

The plumbing was installed with multilayer pipes, a modern and reliable system.

This anticipatory installation prepares the water supply for the sink and other water points needed in the kitchen.

Wall Painting

The walls were painted white to create a bright and modern space. I chose to paint the wall above the upper cabinets in dark blue (teal), creating a colored accent that adds personality to the kitchen. This touch of color elegantly contrasts with the white of the cabinets and backsplash.

Floor Tiling

For the floor, I chose large light grey tiles that add a modern touch to the kitchen. The installation was done with a professional leveling system using black clips and purple and white wedges. This system guarantees a perfectly flat surface and regular joints.

The joints were made in dark grey to create an elegant contrast with the tiles.

Cabinet, Countertop and Appliance Installation

The kitchen cabinets were installed following an L-shaped plan, with a tall column to house the oven and microwave. The light wood-look laminate countertop was installed following the L-shape, with cutouts for the sink and cooktop.

The appliances were then installed.

Backsplash Installation

The backsplash was made with large white rectangular marble-effect tiles.

Exterior Elements

To complete the renovation, the old roller shutter was removed to make way for a new insulated glass door.

Final Result

The complete kitchen renovation is now finished. The result is a functional, modern, and aesthetic space that combines elegance and practicality. The dark blue accent wall adds a touch of personality, while the marble backsplash and white cabinets create a clean and contemporary design.

All appliances are in place and functional, the networks are properly installed, and the space is ready for daily use. This renovation completely transformed the kitchen, making it a pleasant and modern space that perfectly meets our expectations.

Conclusion

The complete kitchen renovation is now finished. This major step in the project required many technical skills and meticulous planning, from the initial demolition to the final finishes. The result is a modern, functional, and aesthetic space that perfectly meets our needs.

This project allowed me to learn a great deal about complete kitchen renovation, from network management to cabinet and appliance installation.

After renovating the hallway in the fourth article of this series, it was time to tackle the new entry renovation. This important step in the renovation project involved several works: demolishing the old WC door that had been moved to the north, creating a recess for a closet using part of the old WC, installing telecommunication networks, and replacing the old door with a new modern and insulated door.

This entry renovation was essential to create a functional and aesthetic welcome space, which would serve as a first impression for visitors and optimize the use of available space in the house.

Demolition of the Old WC Door

The first step was to demolish the old WC door that had been moved to the north of the house. This door, which was located in the entry space, was no longer necessary since the WC had been relocated elsewhere. The demolition required removing the door frame, the door itself, and preparing the opening for future work.

This demolition freed up space and prepared the area for creating the closet recess and installing the new entry door.

Creating the Closet Recess

To optimize available space and create a practical storage area, I decided to create a recess for a closet using part of the old WC. This decision allowed us to gain space in the entry while creating functional storage for coats, shoes, and other accessories.

Creating this recess required demolishing part of the wall separating the entry from the old WC, then rebuilding a new partition to delimit the closet space. I used a metal framework (rails and studs) to create the structure, then installed drywall panels to close the recess.

Telecommunication Network Installation

To prepare for the installation of a video intercom and ensure good connectivity in the entry, I created a channel in the brick wall to run RJ45 cables. This channel was carefully dug to allow telecommunication cables to pass while preserving the structural integrity of the wall.

The RJ45 cables were installed in a conduit to facilitate maintenance and eventual replacement. This anticipatory installation prepared for the arrival of the video intercom and other home automation equipment in the entry.

The channel was then filled with render to hide the cables and prepare the wall for final finishing.

Plumbing Preparation for Future Parental Bedroom Bathroom

In anticipation of the future transformation of the old WC into a bathroom for the parental bedroom, I took advantage of this entry renovation to install the necessary plumbing networks. These installations were made in the new wall created for the closet recess, thus preparing for hot and cold water supply for the future bathroom.

Entry Door Replacement

The old entry door, dating from the 1970s, no longer met our expectations in terms of thermal and acoustic insulation, nor aesthetics. I therefore decided to replace it with a new modern and insulated door.

Finishing and Fitting

For the entry finishing, I chose wallpaper with a tropical pattern (palm and monstera leaves) that adds a touch of color and personality to the space. This wallpaper was applied to the back wall of the recess, creating an interesting focal point in the entry.

The closet was fitted with light wood shelves for storing coats, shoes, and accessories. Hooks were installed to hang coats, and a bench was integrated into the recess to facilitate putting on shoes.

The side walls of the entry were painted white to create a bright and modern space, in contrast with the colorful wallpaper of the closet.

Final Result

The new entry renovation is now complete. The result is a functional, aesthetic, and modern space that serves as a first impression for the house. The recess with closet offers practical and well-organized storage, while the new insulated door improves the thermal and acoustic comfort of the house.

The anticipatory installation of plumbing and telecommunication networks will facilitate future work, particularly the transformation of the old WC into a parental bedroom bathroom.

Conclusion

The new entry renovation is now complete. This step has allowed us to create a modern and functional welcome space, while preparing the necessary installations for future work. This project taught me to better plan installations by anticipating future needs, particularly installing plumbing and telecommunication networks in advance.

After creating the new WC in the third article of this series, it was time to tackle the hallway renovation. This long circulation space, which connects the different rooms of the house, needed a complete renovation to be in harmony with the rest of the work done.

The hallway still had its original 1970s finishes: wallpapered walls and white carpet, like in the living room. This was an opportunity to create a modern and bright transition space, which would serve as a common thread between the different rooms of the house.

Initial State

The hallway still retained its original 1970s finishes. The walls were wallpapered with wallpaper from that era, and the floor was covered with white carpet, identical to that in the living room. Although these finishes were still in place, they were aging and no longer met our aesthetic expectations.

This space, although functional, needed a complete renovation to be in harmony with the rest of the work done in the house.

Wall Work

I started by removing the wallpaper that covered the walls, then repaired damaged areas with filler before sanding everything. After applying a primer, I painted the walls white with two coats of acrylic paint to create a bright and modern space, in harmony with the rest of the house.

Floor Preparation

The floor needed significant preparation before installing the new covering. I started by removing the existing white carpet, which revealed the concrete floor underneath. I then cleaned and leveled the concrete. Irregularities and level differences were corrected with a self-leveling compound, which allows obtaining a perfectly flat surface.

This step is crucial to ensure quality installation of the floor covering, whether tile or laminate.

Flooring Installation

For the floor covering, I chose a light wood laminate, which brings warmth to the space and harmonizes with the rest of the house. Before installation, I installed an insulating underlay to improve acoustic and thermal comfort.

The planks were laid lengthwise along the hallway to create a visual effect of lengthening the space.

Baseboard Installation

Once the floor was installed, I installed the baseboards to finalize the floor covering. The baseboards hide the space between the floor and walls, and provide a clean and neat finish. I chose white baseboards to harmonize with the walls.

Conclusion

The hallway renovation is now complete. The result is a modern, bright, and functional space, which integrates perfectly with the rest of the work done in the house. The next article in this series will be about improving the entry hall in the hallway.

After renovating the bathroom in the second article of this series, we made an important decision regarding the house layout: moving the main entry from the north side to the south side. This reflection led to transforming the former entry into a new WC, thus optimizing the available space. The former WC will be transformed into a second bathroom for the parental bedroom, a project we'll tackle later in the renovation.

This project of creating a WC from the former entry was an interesting challenge, as it required completely rethinking the space, installing a window for natural light, and creating all necessary installations (plumbing, electricity) in a space that wasn't initially intended for this purpose.

Interior Preparation

Inside, I started by preparing the space. It was necessary to demolish existing elements related to the former entry and prepare the structure for new installations. I removed the finishes, exposed the walls, and prepared the space for installing the metal framework and plumbing.

This preparation phase was crucial to have a solid base for all upcoming installations.

Drywall Installation

I installed a metal framework (rails and studs) to create partitions and prepare the space for drywall. This framework also allows hiding electrical and plumbing conduits.

For plumbing, I installed drainage and water supply pipes. The drainage system was designed for the WC and sink. Water supply pipes were installed in multilayer, arriving from the ceiling to facilitate access and maintenance.

I also prepared connections for the radiator, which will be necessary to heat this small room.

I installed moisture-resistant drywall panels (green) on the walls. The drywall was laid ensuring necessary openings for plumbing and electrical connections.

Once the drywall was installed, I performed jointing to prepare the walls for painting.

WC Drainage System

To create the WC drainage system, I had to dig a trench outside the house to install PVC drainage pipes. This step was essential to connect the new WC to the existing sewage system.

Inside, I also prepared the drainage connections that will pass through the metal framework and drywall to reach the wall-mounted WC. The most difficult part was piercing through the concrete floor to route the pipes to the exterior.

The Entry Change

After much consideration, we decided to move the main entry of the house from the north side to the south side. This decision was motivated by several reasons: better orientation, more practical access from the garden, and optimization of circulation within the house. The former entry, located on the north side, was in a space that could be better utilized.

Rather than leaving this space unused, we decided to transform it into a WC. This allowed us to optimize the available space and create an additional functional room in the house.

Closing the Former Entry

The first step was to close the opening of the former entry. I used cellular concrete blocks to fill the door opening. This step was important to create a solid and insulated wall, ready to receive a new window.

The work was done progressively, laying the blocks row by row, ensuring proper alignment and using appropriate mortar. Once the blocks were laid, I applied a render to prepare the surface before window installation.

Window Installation

To bring natural light and ensure good ventilation in the future WC, I installed a new window in the exterior wall. This window was positioned to optimize natural lighting while preserving the privacy of the room.

Installing the window required precise cutting in the wall, then mounting the frame and glazing. Once installed, the window brings beautiful light to the space and allows natural ventilation.

At the end of the renovation, we hired a professional to apply the external rendering, improving both the appearance and protection of the exterior wall.

Radiator Installation

I replaced the larger radiator with a smaller one, since the room is now insulated. I simply connected the new radiator to the existing plumbing.

I installed a cast-iron radiator on the left wall of the WC. The installation required particular attention to ensure good alignment and perfect level.

Connections to the heating circuit were made with copper pipes.

Floor Preparation

To prepare the floor, I first poured a screed to level and create a solid base. Once the screed was dry, I applied a self-leveling compound to obtain a perfectly flat surface, essential for tiling installation.

The self-leveling compound allows obtaining a smooth and regular surface, even if the screed has slight imperfections. This is an important step to guarantee quality results when laying tiles.

WC Installation

For the WC, I chose a GROHE wall-mounted system. This choice optimizes space and provides a modern, clean look. The cistern is recessed in the wall, hidden behind a chrome flush plate.

Installing the GROHE system required precise preparation of the metal framework to accommodate the cistern. I then installed the cistern and prepared water and drainage connections.

The wall-mounted system offers several advantages: easier cleaning, modern design, and better space utilization.

Tiling

I tiled the floor with large light grey tiles, the same as those used in the bathroom. The tiling was laid using a leveling system to ensure perfect results, with regular joints and a flat surface.

The choice of large light grey tiles visually enlarges the space and creates a modern, clean atmosphere.

Final Result

The WC is now complete and functional. The result is a modern and clean space with a soothing color palette: white walls, a sage green accent wall, and a light wood panel that conceals the WC cistern.

For finishing, I installed a white wall-mounted vanity with integrated sink and chrome faucet, a round mirror with black frame suspended by a leather strap, a chrome towel ring, and a pendant light with glass shade.

This transformation of the former entry into a WC has allowed us to optimize the house space while creating a functional and aesthetic room. The window installation brings beautiful natural light, and the modern design makes this space pleasant to use.

What I Learned

This project allowed me to learn new skills, particularly installing a wall-mounted WC system. I also learned to better plan plumbing and electrical installations in a confined space.

Transforming an existing space (the former entry) into a new function (WC) required deep reflection on space organization and necessary installations. It was an interesting challenge that resulted in a satisfying outcome.

Conclusion

The creation of this new WC from the former entry is now complete. It was an ambitious project that allowed us to optimize the house space while creating a functional and aesthetic room. The WC is now ready to use, and the former WC can be transformed into a second bathroom for the parental bedroom in a later stage of the renovation.

After presenting the house in the first article of this series, it's time to tackle the bathroom renovation. You may remember that bathroom with its brown 1970s tiles? Well, here we go for a complete renovation, from screed to finishing!

This project allowed me to learn a great deal: plumbing, concrete, drywall, electricity... But most importantly, I discovered that all the plumbing was embedded in the concrete floor, which I hadn't anticipated. When removing the floor tiles, I unfortunately damaged several pipes, which ultimately led to the complete renovation of the entire house's plumbing.

The Challenge

The bathroom required a complete renovation. Everything needed to be redone: floor, walls, plumbing, electricity, finishes. An ambitious project that would teach me a lot.

Demolition Phase

The first step was to demolish the existing elements. I removed the old brown 1970s tiles, finishes, and exposed the underlying structure. It was at this point that I began to understand the scope of work ahead.

The Plumbing Surprise

When removing the floor tiles, I made an unexpected discovery: all the plumbing was embedded in the concrete floor. I hadn't anticipated this, and when using tools to remove the tiles, I unfortunately damaged several pipes.

This discovery completely changed the scope of the project. Instead of simply renovating the bathroom plumbing, I had to renovate the entire house's plumbing. An additional challenge, but also an opportunity to do everything correctly.

Drywall Installation

I started by installing the drywall on the ceiling. Since the ceiling is a hollow-core slab, I installed the rail structure for the drywall with hangers directly into the hollow cores of the slab. I then installed moisture-resistant green drywall panels for the walls. I created the bathtub enclosure and performed joint compound work.

Plumbing Installation

This time, unlike the old installation where all plumbing was in the concrete floor, I installed a new plumbing system with multilayer pipes arriving from the ceiling. I also installed the drainage system.

Since the sanitary boiler is very far away, located near the garage, I directly added a water heater (cumulus) in the bathroom for direct hot water availability. This avoids long waits and hot water losses in the pipes.

Screed

Once the plumbing was installed, I prepared the floor for the new screed. I installed metal reinforcement mesh and prepared the lean screed.

I then poured the lean screed. It was delicate work, as I had to work around plumbing and electrical while ensuring a perfectly level floor. I then poured a self-leveling compound to achieve a perfectly flat surface.

Electrical Work

I installed electrical conduits, junction boxes, and wiring for lighting and outlets. I also installed an LED lighting system for the vanity.

Bathtub Installation

I positioned the bathtub, created a cellular concrete block enclosure, and connected the plumbing. To ensure optimal waterproofing, I used triple joints (three-layer joints), a method that combines multiple materials or layers to guarantee maximum protection against water infiltration, especially around the edges of the bathtub and between it and the wall or floor coverings. This technique is particularly recommended for acrylic or synthetic resin bathtubs, which require careful installation to avoid deformation or leaks.

Tiling Work

I tiled the floor with large grey tiles and the walls with white rectangular tiles. I used a tile leveling system (clips and wedges) to ensure a perfect result.

Cabinets & Finishing

I installed the vanity cabinets, the double suspended vanity, faucets and fixtures, LED lighting for the vanity, shower fixture, and washing machine in the alcove.

Final Result

The bathroom transformation is now complete. The modern design with wood-grain tiles, the functional layout with bathtub, vanity, and laundry area, the double suspended vanity with integrated LED backlit mirror, the integrated laundry area with washing machine, and towel storage and drying solutions create a space that is both aesthetic and practical.

What I Learned

This project allowed me to learn many new skills: plumbing, concrete work, drywall installation, electricity... I faced many challenges, particularly the unexpected discovery of plumbing in the concrete floor, which significantly expanded the project scope. But each challenge was an opportunity to learn and find solutions.

Conclusion

The bathroom renovation is now complete. It was an ambitious project that taught me a lot and completely transformed this space. The bathroom is now modern, functional, and pleasant to use.

After about a year of searching in the Bordeaux region, we finally found the house that would become our new project. This first article marks the beginning of a series on the complete renovation of this 1970s house. An ambitious project awaits us, but we're ready for the adventure!

The Search

We searched in the Bordeaux region for nearly a year before coming across this house. We visited several properties during this period. Each visit was an opportunity to assess the potential, the work needed, and above all to envision ourselves in the space. Some houses were too small, others required too much structural work, or the garden didn't meet our expectations. Finally, after this long search, we found this house and decided to make an offer.

The Choice

This 1970s house immediately caught our attention. At 170 m², it's larger than what we were initially looking for, but that's exactly what appealed to us. The property includes a 1300 m² yard, a cave of about 10 m², an attached garage for one car (currently unusable and to be renovated later) as well as an external garage.

The potential of this house is huge, but we have to be honest: everything needs to be renovated. It's a large-scale project ahead of us, but we can already see the final result in our minds. Every room will require work, but that's exactly what we wanted: a house in our image, renovated from A to Z.

House Overview

Here's a quick overview of the different rooms in the house, keeping in mind that everything will require renovation work.

Living Room and Dining Room

The living room and dining room form a single space. It's a generous area that benefits from beautiful light thanks to the large windows overlooking the garden. The view of the outside is really pleasant, and we can already imagine the moments spent in this space once renovated. Of course, everything needs to be redone here too, but the foundations are solid.

Kitchen

The kitchen is... green. I'm not really a fan of this color, but you have to admit that the space is well laid out and offers direct access to the terrace, which is a real plus. The kitchen also benefits from a large south-facing window that brings in a lot of light. It's a room that will require a complete renovation, but the possibilities are numerous.

Bedrooms

The house has three large bedrooms, each between 15 and 20 m². They all have built-in wardrobes, but with different styles. All will require work, but the space is there, and that's what matters.

Bathroom

Ah, the bathroom... How to put it? It's... special. The brown tiles and 1970s retro style have a certain charm, but let's say it's not exactly our style. It's probably the room that will require the most work, but at least we can only improve!

Attached Garage

An attached garage for one car is present, but it's currently not usable. It will be renovated later in the project, which gives us time to think carefully about its layout.

Cave

A cave of about 10 m² completes the property. It will also require work, but it's a valuable storage space that can be optimized.

Garden

The 1300 m² garden is a real plus, but it needs a lot of attention. It's somewhat overgrown and will require significant work to be restored. But it's also one of the major assets of this property.

Conclusion

This house has huge potential, but everything needs to be renovated. It's a large-scale project ahead of us, but we're motivated and ready to take on the challenge. Every room will require work, but we can already see the final result: a modern, functional house in our image.

This first article marks the beginning of a long series on this renovation. We'll take you with us on this adventure, sharing the steps, challenges and successes of this major project.

I undertook a complete renovation of a small bathroom in my apartment. I bought this apartment in 2018, but it was built in 2008. The goal was to modernize the space with a minimalist design while optimizing the use of available space, and especially to get rid of the ugly original orange and green tiles.

3D Project

Before starting the work, I used the Home by Me application to create 3D visualizations of the project. These renderings allowed me to validate the design and equipment layout before starting demolition.

The project planned for a modern bathroom with an integrated laundry area, a vanity unit, and a bathtub with shower. The design favored light tones (white and light grey) with touches of natural wood to bring warmth to the space.

Demolition

The first step was to demolish the existing elements. I removed the old tiles, finishes, and exposed the walls to assess the structure's condition and prepare for new installations.

Plumbing Work

Once demolition was complete, I proceeded with installing the new plumbing. I replaced the old pipes with copper pipes for hot and cold water supply, and PVC pipes for drainage.

Installing the bathtub required particular attention to ensure proper connection to water and drainage networks.

Electrical and Structural Work

I installed a metal frame to create a soffit above the vanity unit, which will house the recessed LED spotlights. This structure also allows hiding ventilation and electrical conduits.

Ventilation Installation

Installing an efficient ventilation system is essential in a bathroom. I set up a ventilation duct in the opening framed by the metal structure.

Partition Wall Construction

To optimize space, I built a partition wall. The partition was made with moisture-resistant drywall panels.

Tiling

Tiling was done with white rectangular tiles laid in a staggered brick pattern. I used a laser level to ensure perfect tile alignment and spacers to maintain regular joints.

The work was done in several stages, starting with the walls behind the vanity unit and bathtub.

Finishing Installation

Once tiling was complete, I installed the finishing touches: mirror with light wood frame, shower curtain with geometric pattern, and OSB side panels for the bathtub.

Final Result

The renovation is now complete. The bathroom features a modern and minimalist design with dark grey side panels for the bathtub, completed white tiling, a mirror with wood frame, and all equipment in place. The soffit with its recessed LED spotlights provides modern and functional lighting.

I wanted to create a suspended ceiling light fixture with an industrial and modern style. The idea was to have a horizontal wooden plank fixed to the ceiling, from which several Edison bulbs would hang to create a warm ambiance.

The technical plan shows the design in three parts:

• The main fixture body with ceiling mounting points (ceiling fixing screws) and central electrical input
• An internal plate with cable passage holes and positions for neodymium magnets Ø10x2 mm
• A mounting plate with ceiling fixing holes (Ø10 mm)

The system uses neodymium magnets to hold the plank in place, which allows for easy installation and removal if needed.

Materials Needed

To complete this project, I used:

• A wooden plank (pine or similar) approximately 1.5 to 2 meters long
• 8 neodymium magnets Ø10x2 mm for mounting
• Standard super glue to glue the magnets in their holes
• 6 vintage-style Edison bulbs (LED with visible filaments)
• 6 metallic sockets (brass or brushed nickel)
• Black fabric-wrapped electrical cables for each bulb
• Ceiling mounting screws
• Standard electrical equipment (junction box, connectors, etc.)

Construction

Preparing the Plank

I started by preparing the wooden plank. I marked the locations for cable passage holes and magnet positions. The plank was sanded to achieve a smooth finish.

As can be seen in the photo, the plank is mounted to the ceiling with electrical wires coming out through the central hole. The pencil marks visible on the wood indicate the locations for the various components.

Installing the Magnets

The neodymium magnets were installed in the wooden plank according to the technical plan. I drilled Ø10 mm holes in the plank at the planned locations, then glued each magnet in its hole using standard super glue. These magnets allow the wooden plank to be firmly held against the mounting plate fixed to the ceiling.

Ceiling Mounting

The mounting plate was fixed to the ceiling using screws, making sure the fixing holes were properly aligned. Once the mounting plate is in place, the wooden plank with magnets can simply be positioned and held by magnetism.

Wiring the Bulbs

Each bulb is suspended by a black fabric-wrapped electrical cable that passes through a hole in the plank. The cables are of varying lengths to create an interesting visual effect with bulbs at different heights. The metallic sockets complete the industrial aesthetic.

Final Result

The light fixture is now installed and functional. The 6 Edison bulbs create a warm and modern ambiance in the room.

A dark oak-style varnish was applied to the wooden plank to give it this warm and elegant tone.

Conclusion

This DIY light fixture project was relatively simple to complete but offers a very satisfying result. Using neodymium magnets for mounting facilitates installation and allows for easy removal if needed. The industrial style with Edison bulbs brings a modern and warm touch to the room.

The total cost of the project is reasonable, especially if you salvage some materials.

As part of organizing my desk room, I decided to set up a built-in closet to create a functional and well-organized storage space. This space will allow me to store my electronic components, tools, and various accessories in an orderly manner.

Space Preparation

The closet is a rectangular alcove recessed into the wall, with white walls and a light wooden floor. The space was initially empty and ready to be organized.

I first cleaned and prepared the surfaces to ensure that the shelf supports would be securely and durably fixed.

Shelf Support Installation

To create a modular and sturdy shelf system, I installed white wooden supports fixed directly to the side walls of the alcove. These supports consist of wood strips approximately 3 cm wide, fixed horizontally at several levels.

The supports are fixed with screws and Molly bolts in the hollow wall, evenly spaced to ensure good load distribution.

Shelf Installation

Once the supports were in place, I installed the plywood shelves. I chose a mix of natural light wood shelves and reddish-brown stained plywood to create an interesting visual contrast.

The shelves are placed directly on the supports and extend across the full width of the alcove.

Final Result

The closet is now completely organized and set up. The space is used optimally with multiple shelf levels allowing storage of a large quantity of objects while keeping everything accessible and well-organized.

During the renovation of my apartment, I needed to create a dedicated space to organize my network equipment. Rather than having cables and equipment lying around, I decided to create a recessed rack structure directly in the hollow partition wall.

Wall Preparation

The first step is to prepare the location in the wall. I first identified the ideal location, taking into account the presence of existing network and electrical cables.

I then cut the hollow partition wall to create a rectangular opening to accommodate the rack structure.

Wood Structure Construction

I built a wooden structure that will serve as a support for the rack rails. The structure consists of four vertical posts and several horizontal crossbeams.

I used pocket hole joinery to assemble the structure in a strong and discreet way. This technique allows for invisible screws from the outside.

Rack Rails Installation

Once the wooden structure was assembled, I mounted the metal rack rails inside. These rails are standardized (19 inches) and allow mounting any standard rack equipment.

The rails are mounted vertically on the wood posts using appropriate screws. It is important to check alignment and level so that equipment installs correctly.

Final Result

The rack structure is now completely integrated into the wall. Network equipment is organized in a professional and discreet manner. The patch panel allows easy management of all network connections.

This solution offers several advantages:

• Hidden and organized equipment
• Easy access for maintenance
• Space saving

During my apartment renovation, I wanted to create an open kitchen while elegantly integrating the refrigerator. Rather than having it clutter the space, I decided to build a partition wall that would serve as a dedicated emplacement, creating a visual separation between the kitchen and the rest of the living space.

Planning

The first step was to determine the ideal location for the refrigerator. Several constraints had to be considered: access to electrical outlets, necessary ventilation, and of course the dimensions of the refrigerator itself.

I chose to position the refrigerator along a partition that would separate the kitchen from the rest of the room, creating a dedicated zone while preserving the open aspect of the space.

Partition Construction

Building the partition required several steps. I started by assembling the construction blocks, making sure to leave enough space to accommodate the refrigerator.

To keep the wall vertical during construction, I used temporary metal supports. Once the partition was completed and stable, these supports were removed. I then proceeded with installing the drywall panels and plastering.

Refrigerator Installation

Once the partition was finished and painted, I proceeded with the refrigerator installation. The emplacement was designed so it would fit perfectly in the opening, creating a built-in effect.

It was important to leave sufficient ventilation space at the back and sides to ensure proper operation of the appliance. Electrical supply was planned from the beginning of the partition construction.

Final Result

The refrigerator is now perfectly integrated into the open kitchen. The partition creates an elegant visual separation while maintaining the open aspect of the space.

To build this setup, you will need:

• 1 ESP8266;
• 1 I2C 128×64 OLED screen;
• 1 LF33CV regulator (5v to 3.3v);
• 1 1kΩ resistor (pull-up);
• 2 4.7kΩ resistors.

Warning!
The code is in LUA and therefore requires the ESP8266 to have the nodemcu firmware.

Wiring

Code

Github

Principle

The principle is as follows:

1. The ESP creates an MQTT client with a unique id;
2. It connects to the MQTT broker;
3. The client subscribes to a specific topic where the desired data is published;
4. The ESP displays the data on the screen for the first time;
5. Then each time the MQTT broker receives new data on this topic, our client updates the data on the screen.

Result

I assume that:

• presence detection on the IR cell triggers a high state on a GPIO input;
• the alarm will be activated via a high state on a GPIO output.

You will need:

• 2 ESP8266;
• 2 LF33CV regulators;
• 2 1KΩ resistors.

Warning!
The code is in LUA and therefore requires the ESP8266 to have the nodemcu firmware.

Principle

One ESP will serve as a server, meaning it will:

1. Declare its own wifi access point;
2. Instantiate an HTTP server;
3. Wait for an HTTP request and perform an action based on that request.

The second ESP will serve as a client, meaning it will:

1. Try to connect to the server's wifi access point (for 1 min, green LED blinking);
2. Turn on the green LED to indicate that the connection to the server is established;
3. Wait for a state change on GPIO_2 port (the IR cell);
4. Send an HTTP request to the server with the GPIO_2 port state;

Diagrams

Code

Client | Server

Realization

To build this setup, you will need:

• 1 ESP8266;
• 1 TSL2561 sensor;
• 1 LF33CV regulator (5v to 3.3v);
• 1 1kΩ resistor (pull-up).

Warning!
The code is in LUA and therefore requires the ESP8266 to have the nodemcu firmware.

Wiring

[Waiting for TSL2561 sensor under Fritzing]

Code

Github

Principle

The principle is as follows:

1. The ESP creates an MQTT client with a unique id;
2. It connects to the MQTT broker;
3. On each value change of the TSL2561 sensor, the MQTT client publishes the data on a specific topic;
4. The MQTT broker receives the data and publishes it for each client that has subscribed to this topic.

Jeedom

You must first install the free MQTT plugin in Jeedom.

Once your ESP8266 publishes on the MQTT broker, the Jeedom plugin will automatically add the TSL2561 device:

Result

To build this setup, you will need:

• 1 ESP8266;
• 1 LF33CV regulator (5v to 3.3v);
• 1 1kΩ resistor (pull-up);
• 1 double relay module (5v).

Principle

The dispenser consists of a 12v motor that rotates a threaded rod to which a tray is attached.

The tray is locked in rotation by two thin rods at the base of the dispenser.

Consequently, depending on the rotation direction of the motor, the tray goes down or up.

A larger diameter tube surrounds everything to collect the food and pours it at the base through a spout.

The dispenser is connected to Jeedom via an ESP8266 and actuates the double relay on HTTP request.

Wiring

Code

Github

Jeedom

Create a script to communicate with the esp8266 of the dispenser:

Create a virtual to interact with the previous script:

Create a scenario to automate food distribution:

Result

• 1 ESP8266
• USB to serial cable (FTDI or equivalent)
• Flash software (esptool or NodeMCU Flasher)

Procedure

[Content to be completed according to original post details]

• 1 ESP8266;
• 1 BMP180 sensor (temperature and pressure);
• 1 LF33CV regulator (5v to 3.3v);
• 1 1kΩ resistor (pull-up).

Wiring

Jeedom

Create a virtual device.

Make sure to note the IDs of the two information (temperature and pressure), here 535 and 536. These two IDs are to be inserted in the HTTP request to send to Jeedom.

Code

HTTP version

MQTT version

Result

An Ambi-like system is usually done with WS2801 LEDs because they are addressable unlike WS2811/WS2812 LEDs. I admit I bought this strip on impulse (the number of LEDs per meter attracted me) without checking compatibility with current Ambi-like systems… But I like challenges and especially new things :)

For the controller choice, I had already played with a Raspberry Pi previously, so I wanted to try the adventure on another device. An Arduino fits the need very well, it's small, has low power consumption and there are several dedicated Ambi-like systems. So I ordered a Teensy 2.0 which is even smaller than an Arduino Uno and has greater computing power (this will prove important given that my LEDs are not addressable).

Programming

So I discovered Arduino programming thanks to this Teensy 2.0. To be honest with some C knowledge, it's relatively simple!

There is dedicated development software for Arduino, download here, by default Arduino doesn't support Teensy, so you need to download and install the Teensyduino 'patch' on your Arduino installation.

It natively includes development libraries, to use according to the function you want to give to your system.

Here, we want to control our LED strip via our computer through the Teensy. For this we will use two competing software named Ambibox and Prismatik.

These two software can work by communicating with an Adalight system (embedded on the Teensy).

The problem is that Adalight is developed to work with 2801 LEDs. After a few hours of research, I managed to find an Adalight fork working with WS2812 LEDs.

This Adalight fork unfortunately relies on an old FastSPI_LED2 library (allowing to control WS2811/WS2812 LEDs), which has evolved and is now called FastLED (available in the Arduino editor).

So I solved my problem by slightly modifying the fork code to use the latest version of the FastLED library, my version available on Github (last update 22/11/2015).

I won't explain how to load the program on the Teensy, it's very simple and based on the same principle as any Arduino, for more information, see here.

Assembly

I simply cut strips for each screen length, making sure to respect the arrow direction of the strip (for the signal).

I connected each strip end to end with three wires soldered on each side and connected my 5v 8A power supply at the input and output of the strip (prefer multiple power points on your strip).

As you can see below, I connected the three wires of the strip to the VCC, GRD B1 ports of the Teensy 2.0. The B1 port is configurable in my version of Adalight.

Communication with Adalight

Adalight is very widespread and increasingly recognized by Ambilight software. So I tested the two most known at the moment, Prismatik and Ambibox!

Update - 22/11/2015

Following my move, I had to get back into Teensy programming and I just took the opportunity to update my Adalight version.

The biggest problem I had after all this time (and a new Windows installation) is Prismatik configuration!

Remember to properly install the drivers for your Teensy, the drivers are embedded in the Teensyduino 'patch' (see at the beginning of the article) and then retrieve the port in your Windows device management.

As you can see below, I divided the desk into 3 areas:

• the left area dedicated to the motherboard and its components;
• the back area dedicated to power supply and cable outputs (motherboard, speakers, ventilation, etc…)
• the right area has no specific assignment for the moment, I'm thinking of putting some controls like power, ventilation control…

The left and right sides of the furniture will have 3 Corsair AF140 QE fans each to ensure ventilation from right to left of the main block.

The outside of the sides will be covered with dust filters, ordered from modDIY.

I chose an illuminated push button as a power button, which I will certainly place on the front right.

For sound, I disassembled (cut) old Awai and JVC speakers to recover the speakers that I will place on boxes fixed above the furniture.

I had almost no tools to build the desk, so I invested in a few tools.
Mainly, the jigsaw allowed me to make all my cuts, I did nothing with the circular saw. I fixed the lines with an old sander.

And not forgetting the most important: wood! Finding the wood took me a bit of time. I went with MDF (medium density fiberboard or more commonly called medium (standard), made to be used indoors, easy to work with, hardly splinters unlike softwood and paints simply with a multi-support primer. It's the ideal wood to make furniture for a reasonable price!

MDF is generally found either in DIY stores like Leroy Merlin or at wood dealers. Not having a Leroy Merlin nearby, I got the MDF from a wood dealer.

For information, I bought 4 sheets of 2m44x1m22x19mm.

Let's get started!

Construction

I started by cutting and assembling the back of the desk, you can see the division into 3 sections.

I then assembled the exterior and put the two elements together.

To finish assembling the main pieces, I added the two desk surfaces.

Shelf and Sound

Once the desk was assembled, I added a shelf along the entire length to raise my two screens, so I took the opportunity to integrate a 3-way sound system (left, center & right).

I power the speakers with two small dual-channel amplifiers found on Conrad, which I will place in the center of the furniture.

Ventilation

As explained previously, I wanted to have an airflow from right to left across the entire main surface thanks to 6 Corsair AF140 fans.

Motherboard and Cable Routing

So I tackled where and how to place/fix my motherboard in the desk.

I started by disassembling my case to remove the motherboard support, which I then adjusted and painted black.

I then cut the furniture to bring out the connections to the back compartment, where all the cables will pass.

My current power supply is not modular. So I can't put it where I want.
I decided (for the moment) to place it at knee level against the left compartment. So I made a box to fix the power supply under the furniture.

I then added the holes for the power supply cable routing.

Painting

All that's left is a good coat of paint to finalize the main work. I tried air gun painting for the first time. It has the advantage of being fast and without smudges but on the other hand you paint the surroundings of the furniture, my tools are now spotted with gray and white… I started by applying a multi-support primer on the entire furniture, sanded everything once dry and then applied two coats of gray-tinted acrylic paint (because not enough black tint on hand :) ). The result not being smooth enough for my taste and I originally wanted a full black desk, so I found black acrylic. I finished with a final coat of black paint on the visible elements of the furniture.

Assembly and Wiring

Just need to put everything in place! Assembly and wiring took me quite a bit of time. Especially since I wanted to do sleeving on the motherboard cables for a nice result.

Final Result

And here's the result, there will be some optimizations and improvements to come (lights, ventilation grille, amplifier control with 433MHz outlets, etc…) but everything is there :)

As you can see the desk + the legs make the desk very high (work surface at 1m from the ground).

So I hesitated to stop there and find a bar chair with backrest or make new smaller legs at desk chair height.

Obviously, I built new legs :p

Leg Construction

So I added to the base of my SolidWorks file two legs with doors on each side (but without drawers).

Nothing too complicated, except that I took the opportunity to integrate NAS, Debian server and UPS in the left leg!

I added a ventilated air intake under the NAS, because yes all that heats up inside:

A white multi-support primer, then black alkyd paint (yes unlike the desk):

Ventilation

I also finished wiring my entire ventilation system, so I have ventilation from right to left under the desk work surface via 6 fans.

The 6 fans are connected to my rheostat, so I can control the speed of each fan. I will soon add temperature probes to make the ventilation speed dependent on temperature.

And to finish, I installed the external fan protection covers.

Screens

I finally invested in a triple display stand to make it all a bit more classy!

The stand base being much too wide for my desk shelf, I extended the stand tube and fixed it to the back of the furniture.

And here's the result with three Iiyama Prolite E2483HS-B1:

Chair

I also had the pleasure of having a new desk chair for my birthday ;)

Ambilight

I just added this week a 4m WS2812B LED adhesive strip behind the screens to reproduce an ambilight system in the same way as on my TV (Cf. Ambi-like with WS2801 strip, Raspberry Pi and Hyperion).

A dedicated article coming soon… but here's the first result:

To finish the construction of my desk furniture, a small summary is in order.

My Initial Goals

I wanted a custom desk to make the best use of the room space and also have my PC integrated into it.

Subsequently, I wanted to add a shelf to accommodate my screens and also some speakers.

My Knowledge Level

I had simple woodworking knowledge (and tool handling) from my childhood. It came back fairly quickly after a few mistakes…

I studied electrotechnics, so I have some knowledge in electricity and wiring, which served me well for this :)

My Installation

Starting from a few ideas, and inspired by projects found on the net, I managed to build my desk.

For the hardware, I chose a 50 LED strip, a 5v 8A power supply and a jack power connector.

• 1 strip of 50 WS2801 LEDs for 21€;
• 1 5V 8A power supply for 12€;
• 1 jack power connector (single unit 3€ or 10 for 7€).

Prototype

I started by building a frame with MDF pieces that I had no use for. It's light, easy to work with but quickly weakened with holes given the thickness.

Connection with Raspberry Pi

The connection with the Raspberry Pi is relatively simple, as you can see in the diagram below.

Since LEDs are sensitive to voltage, it's preferable to power them with an external power supply connected in parallel to the 5v GPIO port.

Hyperion Installation

The easiest way to use Hyperion is to use Raspbian on your Raspberry Pi. If you absolutely want to run on another OS, I refer you to the Hyperion wiki which explains the additional procedure to follow here.

First, installation of a few libraries is necessary to run Hyperion on your Raspberry Pi.

sudo apt-get update 
sudo apt-get install libqtcore4 libqtgui4 libqt4-network libusb-1.0-0 libprotobuf7 ca-certificates

Then download and deploy Hyperion.

wget -N https://raw.github.com/tvdzwan/hyperion/master/bin/install_hyperion.sh
sudo sh ./install_hyperion.sh

Note that Hyperion will automatically start on the next Raspberry Pi boot.

You can then test by simply turning your strip red.

hyperion-remote --priority 50 --color red --duration 5000

If you want to disable Hyperion automatic startup.

sudo /sbin/initctl stop hyperion
rm /etc/init/hyperion.conf

For information, I couldn't get my Edimax usb/wifi connector to work on Raspbmc while it worked perfectly on my Raspbian, so I resolved to connect my Raspberry Pi via RJ45.

There is a free Android application to remotely control the Hyperion server, available on the store.

Hyperion Configuration

Hyperion has a very well-made configuration software called HyperCon, which allows you to manage all LEDs (position, colors, lighting, size, …). All possibilities are detailed in the previous link.

HyperCon will generate a hyperion.config.json file to place by default in /etc.

Steel Frame

My MDF frame not being very resistant, I bought some steel angles, which I cut and then painted. The result is much better, the whole thing is solid, light and holds much better to the TV.

Configuration with XBMC

I struggled for a while before getting my XBMC on my media center (Windows) to communicate with the Hyperion server on the Raspberry Pi.

The only solution (at the moment) I found is to use the XBMC Boblight addon which makes communication between XBMC and Hyperion over the network possible.

I tested the Hyperion addon for XBMC but couldn't establish a connection…

Videos

This is my first home automation article and also my first build.

This article is based on the following two articles:

• How to control dio devices with a raspberry pi;
• Raspberry Pi 12 – Allumer des prises à distance.

Principle & Operation

Chacon DIO First outlets work via 433MHz radio frequency.
The principle is very simple, reproduce the data emitted by the remote control via the 433MHz transmitter coupled to the Raspberry Pi.

The remote control communicates with the outlets via the Easy Home protocol, this protocol composes the signal in 32 bits as follows:

• First 26 bits corresponding to the remote control identifier;
• 27th bit corresponding to the group number (not important here);
• 28th bit corresponding to the outlet state (ON=1 & OFF=0);
• 29th to 32nd bits corresponding to the outlet number to be controlled.

For better explanation, I refer you to Idleman 10's tutorial on the Raspberry Pi.

Assembly

If you've never played with the Raspberry Pi GPIO ports, here's the setup to adopt to make the 433MHz transmitter work.

You can see in the setup the transmitter but also the receiver, it's not useful for what we want to do here.

For the tip, a three-pin PC fan cable works perfectly for the 433MHz transmitter ;)

You can solder a conductor wire at the antenna location (Ant) on the transmitter of 17.3cm, if you want to ensure good communication with the outlets.

Software

Then we move to the software level on the Raspberry Pi.

First of all, you need to install the WiringPi library, which simplifies GPIO port access:

Git installation

sudo apt-get install git-core

Raspbian update

sudo apt-get update
sudo apt-get upgrade

Retrieve WiringPi from Git

git clone git://git.drogon.net/wiringPi

Retrieve latest WiringPi updates

cd wiringPi
git pull origin

Build WiringPi library

cd wiringPi
./build

The code to control the outlets is to be retrieved from Idleman's site (thanks to him).

In this zip you'll find a web interface and the C code allowing Chacon outlet control. We won't deal with the web interface in this article.
The important file is therefore radioEmission, if you want to play with the code, you can open (and modify) the radioEmission.cpp file and recompile the radioEmission file using the following command:

g++ radioEmission.cpp -o radioEmission -lwiringPi