SCHWEICH

[SCHWEICH @DamienSchweich]

@toxavanger La violence du programme, juste pour les retraite: Porter progressivement l’âge de départ à 65 anset durée de cotisation à 45 ans en moins de dix ans

En France 22 ans, mais l'âge moyen d'accès à un premier emploi stable (type CDI) 27 ans

retraite 67 à 70 en moyenne... WTF

[Camille Roux @CamilleRoux]

ZapFast : un client WhatsApp natif en Rust et egui pour Linux, macOS et Windows, sans moteur de navigateur.

Il s'ouvre en moins d'une seconde et consomme environ 200 Mo de RAM au repos, contre 1,13 Go pour WhatsApp Web (test sous Linux).

Open source sous licence MIT. ⬇️

[Camille Roux @CamilleRoux]

🔗 https://t.co/4n7PdG4qsB

[Sarah Drasner @sarah_edo]

💥Modern Web Guidance has reached 1.0!

Coding models get stuck in old training data, MWG is a set of skills that’s vetted by industry experts. It helps with perf, a11y, security, and state of the art web tech

Easy to get started:
🛠️ npx modern-web-guidance@latest install
Or you can do a per agent install.

https://t.co/0Ya7769h39

[Davor Minchorov @davorminchorov]

Most software engineers have no idea how to design software properly.

And experience doesn't fix it on its own: 10, 15 or 20 years in, some still design code the way they did in year 4.

Here are the 10 most common misconceptions about design patterns and principles.

1. They treat patterns as rules.

"Always inject dependencies. Always use value objects."

A rule ignores the team size, the product's age and how often the code changes, so it gets applied where nothing needs it.

Treat each pattern as "use this when X" and check that X is true.

2. They reach for whatever they read about last.

The pattern is fresh in their head and feels professional, so it goes in whether the codebase asked for it or not.

Pick a pattern for a pain you have today, not the one you read about last.

3. They copy the shape of a pattern and miss its point.

I've seen repositories return Eloquent models from one method and plain arrays from the next, so the code calling them still knows about the database.

4. They write patterns off as overkill.

Then they hand-code a worse version of the same thing, because they never recognized the problem it solves.

When you catch yourself rebuilding the same thing, look for the pattern that already solves it.

5. They learn patterns from bad examples.

Most examples are toy code that never shows the problem the pattern solves, so the benefit never lands.

Try a pattern on one real feature before you judge it.

6. They're scared of files.

A DTO is one more file, so the data stays in an untyped array nobody can read.

7. They think SRP means "a class should do one thing".

"One thing" has no boundary.

The real rule is that a class should have one reason to change.

8. They skip repositories because "we'll never replace the database".

Replacing the database isn't the main payoff.

The swap you make every day is an in-memory version in your tests.

9. They think TDD means 100% coverage.

TDD is a design tool, not a coverage target.

10. They read "favor composition over inheritance" as "never inherit".

Then they rewrite a clean two-level hierarchy just to satisfy the principle.

I made most of these mistakes myself over the years, before I understood what these tools are for.

Patterns and Principles, my 45-lesson course, covers every one of these misconceptions.

The course is complete and free.

If you'd rather learn inside your AI agent, connect Claude Code, Cursor or ChatGPT to the Codyssey MCP server and ask it about any lesson.

The third course, Architectures, goes live next Monday, 16 November: 15 lessons on the shape of the whole application, from layers and Hexagonal Architecture to a modular monolith.

Every weekday from now on, I'll post one pattern or principle from the course and when it pays off.

Follow me or @Codysseydev so you don't miss them, and join the newsletter for one email a month with what shipped on Codyssey.

https://t.co/1dvVErXqz0

[Hugo "Kocal" Alliaume 🍉 @HugoAlliaume]

Today is a special day 🎂 but also a release day 🎉

🚀 Symfony UX 3.7.2
🔁 Symfony Reprise 1.4.0
📦 Webpack Encore 7.2.1
🧩 Webpack Encore Bundle 2.4.3
🧠 symfony-contribution-skills 0.2.0
🔍 phpstan-symfony-ux 1.4.0

Details in the thread 👇

[Brattani @Bratt_world]

This data was shocking 😳

[beamnxw ./ @beamnxw]

Before you blame Opus 5.5, learn these 15 official Anthropic commands

15 essentials to get more out of Opus 5.5:

less busywork → parallel agents → faster iteration

steal the cheat sheet ↓

01 /goal → keep working toward a defined finish line
https://t.co/JznJdmit2l

02 /batch → split big changes across parallel agents
https://t.co/wxjwlPZZZS

03 /subtask → delegate with the current context
https://t.co/TmCoXiL4ot

04 /deep-research → get research with sources
https://t.co/5QFUiNJbTN

05 /design → create editable artboards
https://t.co/vh8wvUNGfc

06 /plan → review the plan before code changes
https://t.co/iFY3a4UxbU

07 /memory → manage project instructions
https://t.co/3KXIdFjKAQ

08 /compact → compress context around key decisions
https://t.co/gruQHVjONK

09 /branch → explore a separate conversation branch
https://t.co/vh8wvUNGfc

10 /rewind → restore a tracked checkpoint
https://t.co/9kPcEhWXNB

11 /mcp → manage connected tools
https://t.co/MkXDn7Rl95

12 /loop → repeat checks in a running session
https://t.co/kBIlEWP1j6

13 /schedule → automate recurring cloud tasks
https://t.co/lmGnxpr1aT

14 /simplify → clean up code with parallel reviewers
https://t.co/vh8wvUNGfc

15 /remote-control → continue the local session from your phone
https://t.co/GrvSOh1M3Y

start here: /plan → /goal → /simplify

save this, then read the full guide for Opus 5.5 Harness Engineering ↓

[M 🇫🇷 🇧🇷 𝍎𝌆󠁦󠁲 @__Dorak__]

moi avec wow forever

[ryou @ryouxbt]

This is f*cking insane. Google hired this engineer at $500K-$1.2M a year because he knows how to make AI agents write code that doesn't break

In this 41-minute workshop, he shows exactly how to build that system from scratch

Prompts → Agent Skills → Harness → Agents That Ship Without You

step 1 → Refine the idea - drop in a vague thought, the agent interviews you and comes back with 3 directions

step 2 → Write the spec - success criteria, stack and open questions locked before a single line of code

step 3 → Plan in small tasks - each one gets acceptance criteria and a list of files it's allowed to touch

step 4 → Build test-first - red to green, slice by slice, so nothing that already works breaks

step 5 → Verify and review - the agent opens the app in a browser, checks security and simplifies its own code

He open-sourced all 24 skills, and the repo is close to 100K stars

Google calls this "agentic engineering"

Most people spend weeks building this by hand

You don't have to

Bookmark it and watch it tonight

Then read how to wrap skills like these into a full harness in the harness engineering guide below ↓

[Jason Burne @Monty_Brogan69]

Le décryptage des images, tout bonnement génial.

[Jon @jonvolio]

https://t.co/CQ7DlxCaZj

[Chase @0xChaseTM]

this is f***ing gem

SpaceXAI engineer Lauren Tan explained her method for teaching agents to test real features

“...to delegate 80% of a workflow, I turn my manual checks into a reusable verification skill.”

in this guide, she breaks down how "pstack" routes each request to a playbook and selects the skills it needs:

→ Build a runnable verifier (create-verification-skill)

The generated procedure must:

1. launch the app and confirm the instance is ready
2. reach a feature, perform the actions and inspect the result
3. retain evidence and clean up its processes and temporary data

trial the instructions on one real feature before reusing them

→ Require proof that fits the change:

> UI - the completed journey and observed result
> CLI - the command, output and exit status
> storage - the value read back after writing
> performance - profiles with comparable builds, cache states and workloads

/benchmark-checklist - helps catch misleading measurements

when the same correction returns, use /correct to strengthen the repo. prefer an architectural constraint, then types, lint or CI, then a behavioral test

The safeguard must catch the original failure

predictable mechanical steps belong in scripts the next agent can reuse

Watch this before launching more coding agents

[John Leguizamo @JohnLeguizamo]

We did it! You did it! Redemption time! Repudiation time! Checks and balances and watch dogs! We must fix this cesspool!

[C dans l'air @Cdanslair]

L’invité de #cdanslair : #Midterms : #Trump "est un gangster (…) Je suis assez optimiste. Ce sera assez serré ce soir, mais si on gagne le Sénat et le Congrès, on va émasculer Trump". @DouglasLKennedy

[IRIS C2 @C2IRIS]

Asked one of our developers how he uses his AI agents and he just sent me this:

[Syhix 🐈��⬛ 🚦 @SyhixTV]

https://t.co/MyL5GWjLFN

[Ubuntu @ubuntu]

Fixes available in -proposed pocket for CVE-2026-98432. Read the blog for more details: https://t.co/3nUuCEVeDy

[Vincenzo Petrucci @nahime0]

A PHP Hello World, compiled by elephc: one 791 KB static binary. 🐘

No PHP installed. No shared libraries: ldd says "not a dynamic executable".
Compiles in ~115 ms, runs in 0.5 ms.

Ship PHP as a single file.

https://t.co/fHuAH5eOau

[Mathias @0xCordeiro]

If you're running Ubuntu or Red Hat on a public server and cannot patch this yet the solution is:

sudo sysctl -w net.mptcp.enabled=0