
Staff software engineer: @upbound_io | maintainer: @crossplane_io | ex: @controlplaneio, @cloudnativepg @ @EDBPostgres, @sighup_
Milano, Lombardia
Joined November 2009
- Tweets3.3K
- Following1.6K
- Followers565
- Likes25.7K
phisco retweeted
Periodic reminder: Good security architecture minimizes the number of bugs and CVEs you have to care about.
phisco retweeted
The actual AI frontier isn’t the labs anymore - it’s us. It’s figuring out how we build new software that moves us out of the theoretical and into the practical. LLMs are plenty good enough today.
phisco retweeted
Compute isn't the bottleneck. The missing control loop is. @CoreWeave runs @kubernetesio all the way down. No VMs, just containers and a reconcile loop.
That's not a coincidence, it's the only pattern that survives at AI scale. @bassamtabbara explains on Hello, Agent! 👇🎧
The largest inference operations share one pattern: a declarative reconcile loop.
@bassamtabbara, Founder and CEO at @upbound_io, points to CoreWeave, running Kubernetes to no VMs, just containers.
Click here for the "Hello, Agent!" episode. bit.ly/4gUOAv6
#RealTimeData #DataStreaming #Redpanda
phisco retweeted
Crossplane v2.4.0 is now available! 🎉
Required resource watches, scale to zero for safe-start providers, vulnerability scannable images, tons of reliability fixes 🛠️
v1.20 will reach end of life (EOL) in November 2026, upgrade to v2 soon!
Full details:
github.com/crossplane/crossp…
phisco retweeted
My mom called me just to tell me she thinks software is more buggy than it's ever been and she is sick of it. She asked me if it was AIs fault.
Fellas, we are so back
phisco retweeted
I think I finally figured out how to use AI at scale
of course, the fact Fable is good is part of it. but I also changed how I work, and it all comes down to one key realization: you don't need to audit the code, but you NEED to audit the *choices* it made. if you just do that, things will work out, and you'll never lose a codebase to chaos. with Fable at least, the following seems to hold:
if I give it a good decision:
Fable implements it PERFECTLY
if I let it decide instead:
Fable may make some bad choices
that's how I see Fable: as a perfect execution machine capable of converting good decisions into good codebases, no matter how large. given a concrete plan, it lands its implementation. but when anything is underspecified, it can, and will, make bad choices. that's what you must audit.
"while working on this, which choices did you make that you're not confident of? list all."
then, you just review that. not the git diff, not 1000's of lines of code. just the choices it made along the way.
below is a fresh example. overnight, I asked Fable to fix an issue related to MatMul parallelizing worse than expected. it tracked the culprit with perfection, and landed a solution that DID work. but the solution was not general. it just doubled a buffer, which coincidently fixed the program at hands, but the underlying issue was still present.
when it completed the job, it declared success. if I just merged it blindly, the issue would still be dormant. that's the main mistake one can do with AI. instead, I asked it to spell out all decisions it made, spotted the bad one, corrected its course, and now the codebase is clean, correct and the issue is gone for good
I really think that if you do that religiously - i.e., NEVER merge without this "which decisions you made?" audit - you can go VERY far without ever reading a single line of code. at least on Bend, this is working incredibly well. despite heavy use of AI to implement an ungodly amount of features I could never dream of, the codebase is still in a superb state, with no signs of degradation
fresh example below ↓
phisco retweeted
betting on open weights + open source stacks. anything else feels like feudalism. i like market mechanics. i hate feudalism.
phisco retweeted
Someone DM'd me saying they're using /grill-me in technical interviews
Watch the candidate work. See how they answer questions and push back. See whether the AI drives them, or they drive the AI.
Honestly genius
This. Most tricks quickly become useless with new models, but this approach has proven useful for a few generations already.
phisco retweeted
yall im ngl its way harder to get joy and satisfaction out of building with ai than it was before
constantly straddling burn out, being far less immersed in hard problems, constant context switching
i’m tired of the uncertainty of where this is going and how to do it well
phisco retweeted
Today we’re open sourcing Modelplane, the open source control plane for AI inference.
Open-weight models changed who runs AI. As inference expands across clouds, accelerators, and regions, operators need a fleet layer above the cluster.
That’s @ModelplaneAI. Join us.
modelplane.ai/blog/open-cont…
phisco retweeted
This was common knowledge ten years ago and sometimes I forget that common knowledge needs to be shared: containers do not provide security isolation. If you run arbitrary code in one, assume it can access the entire host.





















