Does your constexpr code actually run at compile time?
It's easy to assume that a constexpr function automatically means compile-time execution. Andreas Fertig explains how to distinguish compile-time and runtime evaluation — and how constexpr, consteval and constinit each fit into the picture.
A useful practical tip: force constant evaluation with a context that requires a constant expression.
🎥 Watch the interview: https://t.co/VDYQFnIofL
#Cpp #Constexpr #Cpp20 #EmbeddedCpp
A professional C++ project needs more than API reference.
Think tutorials, getting started guides, examples, how-to guides, explanations, reference docs, release notes, workshops, and more.
Mateusz Pusz explains how the Diátaxis framework can help organize these pieces into a documentation strategy that grows with the project.
🚀 https://t.co/Uo7UacdCx7
#CPP #Documentation #OpenSource #SoftwareDevelopment
Mocks can give you confidence — but are they modelling reality?
Dave Steffen discusses the trade-offs between the Detroit and London schools of testing, and the danger of building a “flat earth” mock that doesn't reflect the real dependencies your software uses.
Use real components where practical, and be thoughtful about what you replace.
🎥 Watch the interview: https://t.co/YgVeNZnuCY
#Cpp #Mocking #UnitTesting #SoftwareEngineering
A 13K-star GitHub repo is built around one painfully obvious idea:
Your coding agent's plan should get a pull-request-style review before it becomes code.
It's called Plannotator, and it turns agent-generated plans into an interactive review workspace where developers can inspect, annotate, and correct decisions before implementation begins.
Think about the usual Claude Code workflow.
The agent proposes a lengthy Markdown plan. You skim through it in the terminal, approve it, and let the agent start coding. Twenty minutes later, you realize it misunderstood a requirement, introduced unnecessary complexity, or chose an architecture you never wanted.
Now you're asking it to undo work that could have been prevented.
Plannotator changes that workflow.
Instead of:
→ Read a wall of Markdown in the terminal
→ Approve an entire plan with one decision
→ Discover incorrect assumptions during implementation
→ Explain the same requirements again
→ Spend another iteration fixing unnecessary code
You can:
→ Highlight the exact section you disagree with
→ Mark unnecessary implementation steps for deletion
→ Add inline comments and suggest replacements
→ Send structured feedback directly to the coding agent
→ Compare the revised plan against the previous version
→ Approve only when the design makes sense
The integration is particularly interesting.
For Claude Code, Plannotator hooks into the plan approval workflow. When the agent submits its plan, the review interface opens in your browser.
Your annotations are converted into structured feedback and returned to the agent. It can revise the plan, and Plannotator shows what changed between iterations.
And the same approach works after implementation.
Run /plannotator-review to inspect uncommitted changes in a proper code-review interface.
You can navigate files, review side-by-side diffs, comment on specific lines, suggest code changes, and send the entire review back to the agent.
There's also support for reviewing HTML artifacts, documents, and pull requests.
But one of the more useful additions is Plannotator Inbox.
If you're running several coding agents, they can leave questions, proposed plans, and code reviews in one local workspace. You can inspect the actual artifacts, make decisions, and send feedback to the appropriate agent session without constantly switching between terminals.
Plannotator integrates with Claude Code, Codex, OpenCode, Pi, Gemini CLI, and other agent environments through supported plugins, hooks, commands, and MCP.
It runs locally, keeps review data on your machine by default, and is open source under MIT/Apache-2.0.
Coding agents are becoming remarkably good at implementing plans.
Plannotator gives developers a better way to make sure those plans are worth implementing.
The best time to catch a bad implementation is when it's still just a paragraph in the plan.
Here's the GitHub Repo: https://t.co/sIgsqNjbA2
I think I'm starting to degrade as an engineer
1. I stopped keeping up with programming languages, libraries, new patterns, systems, and all of that a long time ago. I couldn't care less about what's new in React, what got added to PyTorch, or what's in the latest ES spec. I can't even make myself spend 5 minutes skimming the docs
2. The amount of task context and information I hold in my head has shrunk to a minimum. When I used to research a topic through Google, I'd pick up a ton of interesting things along the way and broaden my horizons. Now an agent sends me something, and without even looking I say: ok, use it
3. My attention span has gotten worse. All I do is wait. On one hand, I think that's better than faking hyperproductivity, burning millions of tokens and degrading the work. I'm a firm believer in the linear approach. On the other hand, a 5-minute wait can stretch into 30. I switch to something else and find it hard to get back to the task
4. My anxiety has gone up. A lot of people call this cyberpsychosis. I wake up thinking about agents. I eat thinking about agents. I go for a walk thinking about agents. I talk to people thinking about agents. Even when I'm not working with agents, I'm thinking about what cool things I could do with them and planning my next session with them
5. I've become hyper-lazy. If something can't be solved with agents, I try not to do it at all
6. My creativity has faded. I may not be the strongest engineer, but I consider myself creative. That was always my strength. I could always come up with something interesting, an interesting solution. But that happened while I was working on something. Running into problems. Taking in new information. My brain was in a continuous flow. Now I've become dull and one-dimensional. I can no longer look at a problem from a different angle
I'm sure everyone who works with AI has these problems at least to some degree, even if few admit it. I worry that humanity will stop developing. AI is not the solution to every problem or a cure for every disease. It's a tool pretending to be an agent in its own right. In its current architectural forms, it will never be able to go beyond its own limits. A human can. But once people slip into the state I'm in, progress may slow down and get locked inside the bubble of what AI is capable of
Claude writes better code when it can verify its work. Checks that used to be expensive, like tests, benchmarks, and end-to-end runs, are now cheap.
Here’s how the Claude Code team thinks about verification:
https://t.co/kPeRO0eCkJ
Why C++ is faster than C on average, according to its creator
Ryan: That was what I was going to ask you. You had said somewhere that C can be more performant than C++, but I tend to think that more abstraction costs you something.
Bjarne Stroustrup (Creator of C++): It's compiled away. This is why I talk about zero overhead abstraction, and people are beginning to take me to task for that because that's understating the ability of the C++ compiler. We can do negative overhead abstraction.
Ryan: What if I was really good at writing assembly and I had all the time in the world to write it? How does that compare?
Bjarne: If you are very smart and you have infinite time, you can do better. By and large, we are not as smart as the optimizers anymore, and we don't have infinite time.
Gli influencer dicono che i video sui social devono durare 30 secondi, massimo un 1 minuto.
Io invece posto un video di 2 ore e mezza: (https://t.co/1UqnFtyxDm).
No, non è mio.
È la puntata di mercoledì scorso de “Una giornata particolare”, il programma settimanale condotto su La 7 dal vice-direttore del Corriere della Sera, Aldo Cazzullo.
(di cui, per i fan della @GialappasB , potrete anche apprezzare l’incredibile somiglianza con l’imitazione che ne fa il bravo Edoardo Ferrario, e speriamo Aldo non si arrabbi)
Questa puntata parla del rapimento e l’omicidio di Aldo Moro. Un evento che questo paese ha dimenticato, salvo i post rituali due volte l’anno, quelli fatti per lavarsi la coscienza.
Che dire, vi consiglio di guardarla questa puntata. Soprattutto i giovani.
Magari a pezzi, nei ritagli di tempo, o in treno. O una sera che piove e non avete voglia di stare con lo smartphone in mano.
Astenersi due categorie: i complottisti patologici (coloro che pensano che tutto sia un complotto) e coloro che pensano che niente sia un complotto.
Eliminare gli estremismi non sarebbe utile solo in politica. Ma anche per guardare con serenità al nostro passato.
Perché, di nuovo, un paese che non conosce bene il suo passato non può capire il presente e non può costruire il futuro.
Ho visto girare ovunque "TSMC è stata hackerata". Allora sono andato a leggere il documento che TSMC ha depositato alla SEC.
Dice un'altra cosa, ma quello che dice, a mio avviso , è comunque grave.👇🏻
Microsoft quietly published 99 ready-made .NET skills for AI Agents.
Most .NET developers have no idea they exist 👇
These skills are official and open source.
They work in Claude Code, Codex, GitHub Copilot and Cursor.
A skill is a folder with instructions.
Your AI agent loads it only when a task needs it.
You write the steps once, and the agent follows them every time.
Microsoft keeps them in the dotnet/skills repo: 14 plugins, 99 skills.
A plugin is a group of related skills. You install a plugin and get all its skills at once.
Here are 5 I'd install first, in this order:
𝟭. 𝗱𝗼𝘁𝗻𝗲𝘁-𝘂𝗽𝗴𝗿𝗮𝗱𝗲
Moves a project from .NET 8 to 10 and turns on nullable reference types.
𝟮. 𝗱𝗼𝘁𝗻𝗲𝘁-𝗱𝗮𝘁𝗮
The optimizing-ef-core-queries skill catches N+1 queries, picks the right tracking mode and removes common EF Core performance traps.
𝟯. 𝗱𝗼𝘁𝗻𝗲𝘁-𝗮𝘀𝗽𝗻𝗲𝘁
Builds Web API endpoints and file-upload endpoints in Minimal APIs the right way.
𝟰. 𝗱𝗼𝘁𝗻𝗲𝘁-𝘁𝗲𝘀𝘁
The biggest plugin: 22 skills to run tests, filter them and move between test frameworks.
𝟱. 𝗱𝗼𝘁𝗻𝗲𝘁-𝗮𝗶
Builds, debugs and tests MCP servers with the C# SDK.
These skills know .NET.
They don't know YOUR project.
They can't tell where you keep your entities, that you don't use repositories, or that your handlers return Result<T>.
Your own skills fill this gap:
→ Microsoft's skills handle general .NET tasks
→ Your skills handle your house rules and conventions
Use both, and your AI agent knows the framework and your style.
2 tips before you install:
→ Don't install all 99. Every skill adds its description to the agent's context, so pick the plugins that match your stack
→ Name the skill in your prompt instead of letting the agent guess which one to use
In my article, I explain the full setup:
→ What a skill is and what's inside one
→ How to write a description so the skill triggers at the right time
→ How to turn your conventions into skills: rich entities, no repositories, full features
→ How to use the Skill Creator to bundle your real code files
→ How to install Microsoft's dotnet/skills in 4 steps
👉 Read the full step-by-step guide here:
↳ https://t.co/UASPgYrc4X
Stop asking Claude to “analyse this.”
Stop asking Claude to “make a plan.”
Stop asking Claude to “give me ideas.”
That barely scratches what it can do.
Use these 5 prompts instead:
Sono stata, come al solito, pesantemente insultata.
So perfettamente come stanno le cose a Gaza. La maggioranza della popolazione vive ammassata nella parte non occupata dall’esercito israeliano, in condizioni drammatiche, sotto la dittatura di Hamas che, anche se militarmente sconfitta, continua a controllare tutto, commettendo crimini che aggravano ulteriormente una situazione già compromessa dalla guerra e impediscono ogni soluzione.
Crimini sui quali i media tacciono, ed è questo che non accetto: la volontà a colpevolizzare Israele di tutto («Israele non fa entrare gli aiuti», «Israele ha distrutto gli edifici»), come se avesse pianificato la distruzione di Gaza. Da qui si arriva alla calunnia criminale del genocidio, che oltre ad aumentare l’antisemitismo nel mondo, cancella le responsabilità di Hamas.
Se non ci fosse Hamas con la sua sete di sangue di ebrei, non ci sarebbero restrizioni a Gaza.
Davanti a queste immagini drammatiche delle inondazioni, si sarebbe dovuto parlare del problema di rimuovere Hamas dal potere, come è stato fatto con l’ISIS a Mosul, non di Israele. Capite? La comunità internazionale dovrebbe innanzitutto proporre una soluzione concreta (esiste poi questa soluzione?) per risolvere la situazione umanitaria a Gaza tenendo conto dell’esigenza di sicurezza di Israele, coinvolgendo anche i Paesi arabi. Invece no, si chiede a Israele di togliere le restrizioni agli aiuti come se per crudeltà o addirittura per volontà di sterminio non li facesse entrare in quantità sufficiente.