Fernando

Innovating on what software collaboration and understanding could be!
Ex-Google, Ex-Airbnb

[Fernando @Principal_ADE]

Starting a new open source project with the aim of developing an artifact standard for verifiable system diagrams. Check out some of the demo diagrams https://t.co/4qXQutdopF

[Fernando @Principal_ADE]

Doing an analysis of the constructs for the human layer repo

[dex @dexhorthy]

its time. https://t.co/ZtdR29DhML

[dax @thdxr]

i think i kept seeing people say "monorepos are good for agents"

but we just switched to multi repos. i have a hard time caring about the benefits of monorepos anymore

[Fernando @Principal_ADE]

@thdxr Yay!!! My prediction is coming true!!

[Fernando @Principal_ADE]

@icanvardar This helps https://t.co/bsmNDPKsok

[Fernando @Principal_ADE]

Starting a new open source project with the aim of developing an artifact standard for verifiable system diagrams. Check out some of the demo diagrams https://t.co/4qXQutdopF

[Justin Bennett @just_be_dev]

@dillon_mulroy Thoughts: https://t.co/gKxqmSn8a7

[Fernando @Principal_ADE]

@OhansEmmanuel Hey! Big fan of your ui exploration! We are experimenting measuring codebases as constructs, like number of functions and seeing how they churn. It doesn’t look like they churn as fast as you think so there is reason to believe just approving and reading functions is valuable

[Fernando @Principal_ADE]

Today we are working on focusing on a metric that you only see in a post mortem after an incident if you have them at all. Mean Time To Understanding.
Every other metric in software is getting automated. MTTD. MTTR. All getting faster.
But Mean Time to Understanding? Getting worse.
Agents fix things faster than humans can comprehend what changed.
That's what needs to get solved.

[Fernando @Principal_ADE]

@thdxr Name1

[David Boyne @boyney123]

I've been working on a new visualisation experience for users in @event_catalog .

With "Levels" you can now decide what view of your diagram you wish to see.

Level 1 - Domains, systems and actors
Level 2 - Services and data
Level 3 - Messages and channels

These new levels can help your teams understand your architecture through different lenses either staying at a high level or diving deeper.

Now live 🙌

[Fernando @Principal_ADE]

@theo @jacobgraf @t3dotcodes This project achieves that but it is added complexity and a registry

[Tarun Sachdeva @tarunsachdeva]

We've been working on building trace intelligence across all your company sessions. We're building dimensions of trace data especially relevant to the offices of a CTO, CISO, and CFO. You'll be able to answer things like "how often do files in your codebase show up in agent read operations and how much does it cost" (an example visual below)

This is a fun but gnarly data engineering challenge. But IMO the real story is all the software we are creating along the way. We're building internal tools to evaluate schema choices, we use data from our agent to evaluate the types of queries to optimize for (using Jev and Luna to classify), we build visual profiling tools test query performance throughout. Making software now is so much more fun and interesting.

Anyways, I can't wait to show this stuff off. Your agent trace data contains multitudes and you need many ways to look at it. Also, if this is interesting enough that you might want to run a pilot, please DM!

[boris @boristane]

I spent the majority of my career building observability tooling

this tooling should be used to close the loop between production and coding agents, in service of self-improving software

I put my thoughts down

https://t.co/JHBckGpEhz

[Nix 🔳 @NixFred]

People ask me how I ship omarchy sw so fast. 🧵

The answer is Clarity.

Clarity is where all my projects live, from the first idea to running live. Every project gets a map, a status, its questions and decisions, a backlog, testing and its GitHub, in one place. Every AI chat I open reads from it before it starts.

Made with Clarity with a buddy of mine, lets call him Daniel, not on X and wont be.

Here's Blip, my iMessage app for Linux, going through it.

[Fernando @Principal_ADE]

@andyhtran_ How is it?

[raulk @raulvk]

Code is cheap now. Understanding isn't.

Introducing Spinal: a low-latency, predictive surface to grok and keep up with any codebase. From weekend hacks to mature behemoths.

Linux kernel, 1.48M commits: first search results in <20 ms.

Waitlist: https://t.co/xoO4wEjipb

[Fernando @Principal_ADE]

@ryanvogel @thdxr OpenCode connection error
App: OpenCode 0.1.0 (230)
Report generated at: 2026-10-08T21:23:13Z
Phase: Pair
Server: https://t.co/cwXlnfmD39
Attempt: 1

Message:
Couldn’t reach the OpenCode server

[Mathieu @miniapeur]

👀👀 "[…] we provide several examples of AI mistranslations of natural language (NL) statements and proofs into Lean in practice, resulting in mismatches between NL proofs and their Lean 'verifications'. These include OpenAI's announced Navier-Stokes proof. In particular, we show that the formalised Lean proof does not correspond to the NL proof of blow-up of solutions to the Navier-Stokes equations."
https://t.co/9OzsRydu3X

[Fernando @Principal_ADE]

@markoa @semaphoreci Interested in this role. I think it aligns with the kind of work I like to do https://t.co/N96xuwWBnu

[Fernando @Principal_ADE]

The hardest part of software engineering was never how do you write code that does what you want, but how do you know that your mental model is accurate. This is the problem other tools fail to solve, surfacing what happens and where so you have confidence in your system

[Fernando @Principal_ADE]

@theo I understand how cool the tsc-rust port is given how it has the potential to change the deployment paradigm in a way that I always thought would be possible but didn't know how long it would take for the technologies to be created to make it feasible

[Fernando @Principal_ADE]

@lordspline Sent a dm