Nicolas Bustamante
@nicbstme • 24,983 subscribers
AI for knowledge workers at @Microsoft. Prev: CEO @fintoolx (acq. Microsoft), CEO @doctrine (Acq. Summit Partners)
Shorts
Videos
We are entering the age of just-in-time software. Some of my coworkers are visiting San Francisco this week, so I asked Claude Fable to design an extremely detailed HTML map of San Francisco so I can explain the city to them. The HTML is wild. It has all the street names, their exact dimensions, the relief of the city, the fog, the sun exposure etc. Everything it real. I was super surprised but it went and found the city's actual data, then built a cartographic engine around it. So I have: - Every street from the SF Public Works centerline survey: 15,905 segments, 2,502 named streets, 54,989 surveyed vertices, with the official address ranges per block - The relief from 14,151 municipal elevation contour points, interpolated into a 168,000-vertex terrain model - 9,672 buildings with lidar-measured heights from an SF Planning study - Every Muni Metro line, the cable cars and BART from the official GTFS feed: real route shapes, real 10-minute headways, real speeds. 76 little trams move on the map at their scheduled pace, and the K dims when it passes under 175 meters of Twin Peaks because it knows the tunnel portals (wtf!) - Fog modeled as marine-layer advection over the terrain, calibrated on NREL satellite irradiance and a decade of ASOS weather observations. Claude did totally overkilled stuff like the fog model's 50% line landed at longitude -122.437 which is... Divisadero Street (every San Franciscan knows the fog stops there) The whole thing is one self-contained HTML file, 1.2 MB, with a WebGL engine. No libraries, no API calls, no network. It runs offline forever. We talk about scaling and benchmarks all day. Sometimes the bitter lesson is simpler: give the machine real data and real verification loops, and it builds you the city. I'm spending the evening exploring the map; it's too good!
Nicolas Bustamante158,574 views • 1 month ago
When people say data centers use millions of gallons of water, they're describing an old technology. Before, water went into evaporative cooling towers. Warm water pulled heat off the AI chips, then evaporated into the air to shed it. It was effective, but it burned through fresh water continuously, which is where the headline numbers come from today around "data centers use a massive amount of water." The data centers we revealed at Build today don't work that way. The cooling loop is closed. Water is added once during construction and recirculates indefinitely between the servers and the chillers. No evaporation, no fresh-water resupply! Satya put the scale in plain terms: a full year of water use is roughly what a single restaurant uses. Keep in mind that for us, every liter and every watt is an optimization target. The economics and the environment push in the same direction!
Nicolas Bustamante140,420 views • 2 months ago
I turned Thariq's article into an interactive HTML! I was a markdown boy but since I started working at Microsoft I'm using HTML more and more. Our engineers love to send AI-generated HTML to coordinate between SWE/PM on projects since it's easier to read than markdown.
Nicolas Bustamante148,885 views • 2 months ago
Models like GPT 5.6 or Fable 5 are accelerating the commodification of software. For instance, I gave Fable a screenshot of the Stripe, OpenAI, and Anthropic websites with a simple prompt: “Create a pixel-perfect reproduction of this website.” It took only seconds and a simple prompt to duplicate the design. This is exciting because there are so many poorly designed websites, but now they are just a prompt away from achieving world-class design!!
Nicolas Bustamante37,754 views • 1 month ago
No more content to load