Two execution traces can look completely different even when nothing important changed.
Timestamps, random IDs, and event ordering create noise that makes real changes hard to spot.
Built TraceDiff: feed it two traces, get back only what actually changed.
Demo Link Below
qfbr
Over the past week, I’ve been overwhelmed by the love and support of friends, industry colleagues, and people I've never met. Thank you to everyone who has shown kindness to my family and me. It means the world to me.
I came to the United States 53 years ago, and becoming an American citizen is one of the greatest gifts and proudest moments of my life. NVIDIA has been my life’s work. Building it into the company it is today alongside my colleagues has been a privilege and an honor. Nowhere but in America could a company like NVIDIA be possible. I love our country, and I love NVIDIA.
I did not live up to the standards expected of everyone at NVIDIA, and I have made serious mistakes in my personal life. I created problems for the Board that I deeply regret. I own my mistakes completely, and I am committed to cooperating with the Board’s independent investigation.
Since my departure, I’ve seen an outpouring of calls from NVIDIA’s employees, investors, business partners, and customers for me to return as CEO. Many continue to reach out to me directly as the company navigates complex technology, market, competitive, and geopolitical dynamics. NVIDIA is a once-in-a-generation company. If the Board of Directors decides that my return is in the best interest of our shareholders, our employees, the company, and America, I would be honored to answer these calls and return as CEO.
Thank you again to everyone who has shared their good wishes. I am profoundly humbled by your support. To my family: I love you, and I will spend the rest of my life being worthy of yours.
Jensen
1
7
211
maaz retweeted
Everyone is building sandboxes.
But a sandbox is only 10% of the infrastructure you need to run AI agents. You're left building the other 90% in-house: deployment, persistent state, monitoring, recovery, scaling
You're trying to sell agents. Somehow you're building a cloud.
Today we're launching Maritime out of YC F26 🚢
Maritime is a managed cloud for AI agents. We handle the infrastructure so you can focus on your product.
maaz retweeted
Hey everyone,
I am currently looking for my next role in backend, systems, or ai infrastructure engineering. preferably remote-first. i'm based in india (ist) and comfortable working across us/eu time zones.
i mostly work with go, along with python and typescript. i enjoy building things from scratch, understanding how they work under the hood, and occasionally going a little too deep into the details.
some things i've built:
mini-rpc — an rpc framework in go over raw tcp, with custom framing, serialization, and code generation.
mini-protoc — a lightweight protocol buffers compiler in go for mini-rpc, with a hand-written lexer, parser, ast, schema validator, and go code generation for message structs and service/client stubs.
pony — a go runtime for orchestrating multiple ai coding agents, with process lifecycle management and pty support.
krafta — a kafka-inspired log system in java, with partitions, offsets, consumer groups, and multi-broker coordination.
newsletter backend — built using go, postgresql, rabbitmq, and redis, with a focus on async processing, idempotency, and rate limiting.
recently, i've been spending more time exploring the infrastructure side of ai —agent runtimes, llm gateways, mcp, and the engineering challenges involved in making these systems reliable.
i'm open to junior / entry level opportunities in backend, go, systems, or ai infrastructure. remote roles would be ideal, but i'm also open to opportunities in bengaluru/hyderabad.
if you're building something interesting, know of an opening, or think there might be a good fit somewhere, feel free to reach out. referrals and introductions are always appreciated.
website: akansharoy.site
github: github.com/akansha204
my dms are open!







