Roald Sieberath ☀

#VC Investor @Noshaq_be #space #health | #AI #Entrepreneur | ex-President @DigitalWallonia | Guest Prof @UCLouvain_be | @BeCentralBxl | #KauffmanFellows #Art🎨

[Roald Sieberath ☀ @roald]

News is out:
@Odoo is now a (five-time) #unicorn!🦄🦄🦄🦄🦄 valued at 5 B€ in a secondary transaction led by @CapitalG & @sequoia

Happy & proud to have served on the Board for 10 years. And brought my fund @Noshaq_be as investor in 2019.

Odoo today has 13 million users, adding 7K new clients per month. Revenue (billing) of 650 M€ ; projected to reach 1 B€ by 2027.

Still an amazing growth ahead! 🚀✨
Congrats to @fpodoo & team!

https://t.co/dGahLS4eN6

[Roald Sieberath ☀ @roald]

SCARY.

A critical documentary about Musk can’t buy ads on major social networks. Dubious reasons, apparently contradicting their own rules. 🤔

So much for “free speech”.

Now I wonder: will posts about this get shadowbanned too? 🫣

You decide what to do with that.

#Musk #StreisandEffect #FreedomOfSpeech

https://t.co/dl1sZHMjG7

[Roald Sieberath ☀ @roald]

You are actually more likely to be a unicorn founder if you are in your 40’s than in your 20’s. ✨

[Garry Tan @garrytan]

The founder in their 40s with taste and discernment is the new gentleman unicorn founder

Because there can be 100x to 1000x of them working at their beck and call via agents and software factories all the time

[Roald Sieberath ☀ @roald]

Why the AI Industry Still Pays a "Python Tax"

The strangest trade-off in modern engineering: the industry that computes faster than anything in human history conducts those computations in one of the slowest languages in the history of programming. 

https://t.co/zS0hQfGcYK

[Roald Sieberath ☀ @roald]

Well @deepstash, I love your idea and mission…

But I’m very disappointed by your deceptive sales tactics. 😬

After clicking your Facebook ad for a “lifetime plan” at $79, I end up in a question funnel where I can’t find the offer. 😡☹️

Please honor your own ads!

[Roald Sieberath ☀ @roald]

New AI-related jobs, such as the FDE (AI Forward Deployed Engineer) may counter the jobpocalypse scenarios.

#AIjobs

[Andrew Ng @AndrewYNg]

One of the new, buzzy jobs in Silicon Valley is the AI Forward Deployed Engineer (FDE), an engineer who is embedded within a client organization to help customize solutions, such as building and tuning agentic workflows that suit the client’s particular needs. I’ve heard from people who are wondering anew about the FDE career path since OpenAI and Anthropic started building new teams to place FDEs within client organizations.

The rise of FDEs for AI workloads is one way AI is creating new jobs (and why the jobpolcalypse narrative of upcoming job market collapse is false -- there will be many AI and non-AI jobs). However, I believe there will be far more AI Engineer jobs than FDEs, as I explain below.

The FDE role was pioneered about two decades ago by Palantir, which sent engineers to government locations to work on secure, air-gapped networks. In addition to having good technical skills, FDEs need communication skills and sometimes business skills. For example, they may need to speak with clients to understand their needs, formulate a strategy to prioritize projects, explain complex technology, and respectfully push back if a client asks for something unrealistic. They’re enjoying a resurgence because of the amount of work involved in taking an off-the-shelf LLM and building it into a custom agentic workflow that fits particular business needs.

However, I believe the number of AI Engineer jobs will be far larger. A company might accept a few FDEs to be embedded within its organization. But most companies will want far more of their own employees working on their projects. While my organizations do hire FDEs, we hire far more AI Engineers! Also, a common client concern is that it is hard to find vendor-neutral FDEs — they are, after all, there to deeply integrate a particular vendor’s product into a company. In this moment when it’s hard to predict which AI service will be the best one in a year’s time, optionality (the ability to pick whatever vendor turns out to fit best in the future) is very valuable. In contrast, letting FDEs tightly bind a company’s processes significantly reduces optionality.

Right now, I see surging demand for AI Engineers who can build software applications using AI software components (like LLM prompting, agentic frameworks, evals, etc.) and effectively use AI coding agents (like Claude Code, Codex, Antigravity CLI, and OpenCode). As the AI Engineer role matures, I expect it to fragment into more specialized roles, like the generic Software Engineer role from decades ago fragmented into frontend, backend, mobile, data engineering, devops, and so on.

What will be the future, specialized AI engineering roles? I don’t know. Perhaps there will be AI FDEs, LLMOps Engineers, Evals Engineers, AI Data Engineers, Harness Engineers, and other roles we don’t have names for yet. But for now, I see a lot of AI engineers who are generalists create a lot of value. Skilled AI Engineers are in very high demand! As our field continues to mature over the coming decade, I look forward to new specializations within AI Engineering that create even more job opportunities.

[Original text: The Batch newsletter]

[Roald Sieberath ☀ @roald]

#AI-driven company tends to include AI-justified layoffs...

[GREG ISENBERG @gregisenberg]

Every CEO layoff letter in 2026 follows the same template.

"Hardest decision I've ever made. AI changed everything. New roles designed for AI-native work. We owe it to our customers. We're choosing to compete."

I feel like I'm reading the same letter with different logos

[Roald Sieberath ☀ @roald]

The rules of tech changed with AI. Play the new game.

[Garry Tan @garrytan]

Founders must stop trying to building 2010-era businesses with 2026-era technology.

Don't try to rebuild Foursquare or Yelp.

Don't try to recreate Basecamp by 37 Signals with $10/mo SaaS pricing.

Don't underprice! If it works it's worth a lot more.

Don't be tempted to become "Tech enabled PE" with revenue tricks.

The rules of tech changed with AI. Play the new game.

[Roald Sieberath ☀ @roald]

Next wave in agentic AI:
iterating & optimizing on agent skills.

Case in point: SkillOpt

Definitely a strong trend for the coming months.

#AI #agents #skills

[Muratcan Koylan @muratcan]

Gradient descent for SKILL.md files sounds interesting, maybe a bit complex but it's becoming a real part of agent harness.

SkillOpt is one of the first papers to treat markdown skill files as trainable parameters and provides a proper optimization framework for them.

A few things I learned that you should consider too.

1. The validation gate is the only thing that matters in a self-editing loop.

Held-out set, strict improvement, ties rejected. End-to-end, their best skills land with 1 to 4 accepted edits total. If your "self-improving agent" is accepting most of what it proposes, you're shipping slop.

2. Bounded edits are better than full rewrites. 4 to 8 edits per step is the sweet spot.

Remove the budget and performance collapses. This is the textual analog of learning rate, and it transfers to any LLM-as-author loop. If you're using an agent to refactor your docs, your prompts, or your skills, cap the diff size.

3. Compactness wins. Median final skill: ~920 tokens.

Skills do not need to be long. They need to be high-signal. Most skill files I see are bloated because length feels like effort. It isn't.

4. The harness is becoming less important; the skill is becoming more important.

A Codex-trained skill ported into Claude Code hit +59.7 points on SpreadsheetBench. Procedural knowledge is more general than the runtime that
produced it.

5. Frozen model + trained context is the practical adaptation.

GPT-5.4-nano with a SkillOpt'd skill ≈ frontier behavior on procedural benchmarks. Cheaper, portable, inspectable, zero inference-time cost. This is
the answer to "how do we adapt a frontier model for our domain" for almost everyone who isn't training their own models.

6. Verification is the bottleneck.

Every gate in this paper depends on an auto-grader. That works for benchmarks. It fails for writing, design, and strategy, exactly the open-ended work we want to automate. Whoever builds the verifier for open-ended tasks owns the next stage.

There are also two leassons I learned while shipping v2.3.0 of my Context Engineering Agent Skills repo, measured across composer-2, claude-opus-4-7,
gpt-5.5, and gemini-3.1-pro via the @cursor_ai SDK:
- Description and body are two different surfaces. The router only sees the description. The agent sees the body once activated. They can quietly disagree, and only end-to-end task tests catch it.
- Aggregate accuracy is the wrong unit. When I rewrote three descriptions, the corpus average moved ~1pp. Individual skills moved 23–25pp. Per-skill effect size is where the action is.

Also, in Feb 2026 I shared a piece called Personal Brain OS arguing that the markdown file is a first-class substrate for agent state. SkillOpt is the optimizer-shaped version of that same argument: not "store memory in files" but "treat files as trainable parameters with proper optimization machinery around them." That's the move from static to measured.

The fast/slow split they describe already lives implicitly in the digital-brain-skill repo:
- voice-guide and tone-of-voice.md are slow-state (rarely touched)
- posts.jsonl and bookmarks.jsonl are fast-state

What SkillOpt adds that I didn't have is a protected section invariant, a structural guarantee that fast edits cannot overwrite slow lessons. Removing that mechanism cost them 22 points on SpreadsheetBench. Worth borrowing.

If you're building agents, SkillOpt: Executive Strategy for Self-Evolving Agent Skills is a good paper to read: https://t.co/ZS9SZXQ6Mv

[Roald Sieberath ☀ @roald]

Different opinion on #AI, by @DavidSacks:

« We’re at the beginning of a massive productivity boom driven by the proliferation of bespoke software throughout the entire economy.

Coding has been AI’s breakout use case this year. The fact that it’s increased demand for software engineers — rather than decreased it — should call into question the entire “AI will cause mass job loss” narrative. »

[David Sacks @DavidSacks]

Q: How are job postings for software engineers rising rapidly despite AI agents automating coding?

A: Because there’s far more code to manage than ever before. We’re already seeing a 14x YoY increase in GitHub commits, and it’s accelerating.

AI has dramatically lowered the cost of writing code, so it’s now being used across far more businesses, applications, and use cases.

We’re at the beginning of a massive productivity boom driven by the proliferation of bespoke software throughout the entire economy.

Coding has been AI’s breakout use case this year. The fact that it’s increased demand for software engineers — rather than decreased it — should call into question the entire “AI will cause mass job loss” narrative.

[Roald Sieberath ☀ @roald]

@marcodzo @grok You’re guessing wrong, once again.

I fully recognize SpaceX’s obvious leadership (saw my comm?) I also root for alternatives, because monopoly is unhealthy.

But I’m done arguing with someone who keeps replacing what I actually said with a strawman version of it.🙄

Done & over.

[Roald Sieberath ☀ @roald]

This is getting tiring.
I never said Neuralink was “behind”.

My point was simple: Neuralink leads on some dimensions; alternatives lead on others. Safety, invasiveness, trial maturity, regulatory path, and clinical track record all matter.

That’s not anti-Neuralink. It’s due diligence.

Ask Claude, for a change: « The claim holds up well.
[…]
So it's not that Neuralink is bad — it's that "Neuralink = the frontier" is a marketing frame, not a clinical one. On safety and clinical maturity specifically, calling it the leader is hard to defend with the current evidence. »

https://t.co/709woodFBe

[Roald Sieberath ☀ @roald]

@marcodzo @grok It is tiresome to read how you misread (and frankly strawman argue) my point. I never said that “Tesla should die”. 🤔

I defend my valid reasons to 1) not want one 2) believe the brand in Europe is a trainwreck, & happy that there are alternatives.

https://t.co/A5xLZEllkw

[Roald Sieberath ☀ @roald]

@marcodzo @grok If we really care about helping people with disabilities, we should compare Neuralink seriously with the best alternatives, including those that may be ahead on safety, trials, or clinical maturity.

https://t.co/8xg08S086T

Musk fanboyism is not a substitute for due diligence 😇

[Roald Sieberath ☀ @roald]

@marcodzo @grok PS: results for EU market are also different because of no tariffs on Asian cars like in the US.

https://t.co/BbSjLTyNPN

[Roald Sieberath ☀ @roald]

@marcodzo Amazing ! 🤩

[Roald Sieberath ☀ @roald]

@grok @marcodzo @grok funny you pretty much just gave me a similar list with different rankings

https://t.co/WBdC7cliBE

Please make up your mind, and come up with a more consensual list 😇

[Roald Sieberath ☀ @roald]

Self-improving, AI-native companies.
by Y Combinator.

Better be listening.

[Y Combinator @ycombinator]

In a recent batch talk, YC General Partner @t_blom broke down how to build a self-improving, AI-native company.

He walks through how to create recursive, self-improving AI loops, and why founders who get this right will run companies that improve while they sleep.

00:00 — Companies Are Roman Legions
00:54 — Copilots Are the Wrong Mental Model
01:55 — Extract the Domain Knowledge
02:24 — The Recursive Self-Improving Loop
04:12 — The Holy Shit Moment at YC
05:50 — Self-Optimizing Product and Support Loops
06:29 — Burn Tokens, Not Headcount
07:23 — Middle Management Is Over
08:05 — Make Everything Legible to AI
09:40 — Regenerating the YC User Manual
11:19 — Software Is Ephemeral, Context Is Valuable
12:18 — Where Humans Still Matter

[Roald Sieberath ☀ @roald]

AI's crazy valuations will have a huge ripple effect on philanthropy.

See @nanransohoff's substack:
https://t.co/AFYosycZvu

[Nan Ransohoff @nanransohoff]

New blog post: The third wave of American philanthropy

Hundreds of billions of dollars in new philanthropic capital will soon become liquid. The OpenAI Foundation holds 26% of OpenAI, worth about $220B at today’s valuation. Anthropic’s seven co-founders have pledged to give away 80% of their wealth and have instituted the most aggressive donor matching program for employees in tech history.

How much does this all add up to? And how meaningful is that in the context of philanthropy today?

I was doing some simple napkin math to wrap my head around the scale of what’s coming, and radicalized myself in the process. I had dramatically underappreciated the scale of the philanthropic capital that’s about to become available and the corresponding gap in talent and organizations that will be needed to make the most of it.

This piece aims to directionally sketch the scale of what’s coming, the gap in operational capacity needed to absorb it, and what we can do to fill it.

(Link to full post in reply)