<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="https://www.btucker.net/feed.xml" rel="self" type="application/atom+xml" /><link href="https://www.btucker.net/" rel="alternate" type="text/html" /><updated>2026-03-19T16:25:58-05:00</updated><id>https://www.btucker.net/feed.xml</id><title type="html">why not ben</title><subtitle>Personal website and blog of Ben Tucker</subtitle><entry><title type="html">The Fuzzy Front End, in High Fidelity</title><link href="https://www.btucker.net/blog/2026/03/19/the-fuzzy-front-end-in-high-fidelity/" rel="alternate" type="text/html" title="The Fuzzy Front End, in High Fidelity" /><published>2026-03-19T00:00:00-05:00</published><updated>2026-03-19T00:00:00-05:00</updated><id>https://www.btucker.net/blog/2026/03/19/the-fuzzy-front-end-in-high-fidelity</id><content type="html" xml:base="https://www.btucker.net/blog/2026/03/19/the-fuzzy-front-end-in-high-fidelity/"><![CDATA[<p>There’s a phase in product development people call “the fuzzy front end.” It’s the messy beginning – when you’re not sure what you’re building, who it’s really for, or whether the idea even holds together. Sketches on napkins was the trope, but by necessity artifacts wore their roughness openly. Appearance matched the maturity of the thinking.</p>

<p>AI broke that link.</p>

<p>Now you can go from a half-formed thought to a polished slide deck in minutes. You can generate a product spec, a competitive analysis, a functional prototype — all with the sheen of something that’s been through many rounds of review. The fuzzy front end can now look like a finished product.</p>

<p>And that’s genuinely disorienting.</p>

<p>But I’m starting to think the disorientation is useful. Polish was a lousy proxy for rigor. AI just made it obvious.</p>]]></content><author><name></name></author><summary type="html"><![CDATA[There’s a phase in product development people call “the fuzzy front end.” It’s the messy beginning – when you’re not sure what you’re building, who it’s really for, or whether the idea even holds together. Sketches on napkins was the trope, but by necessity artifacts wore their roughness openly. Appearance matched the maturity of the thinking.]]></summary></entry><entry><title type="html">…and we’re back</title><link href="https://www.btucker.net/blog/2026/03/12/and-were-back/" rel="alternate" type="text/html" title="…and we’re back" /><published>2026-03-12T00:00:00-05:00</published><updated>2026-03-12T00:00:00-05:00</updated><id>https://www.btucker.net/blog/2026/03/12/and-were-back</id><content type="html" xml:base="https://www.btucker.net/blog/2026/03/12/and-were-back/"><![CDATA[<p>I last published on this blog 20 years ago. The final post was in February 2006: a “reblog” of <a href="https://www.tbray.org/ongoing/When/200x/2006/02/15/Beatles-Juggling">a link from Tim Bray</a> to an incredible juggling performance (<a href="https://www.youtube.com/watch?v=AAILqBg_cJo">now available on YouTube</a>).</p>

<p>At the time, I was a sophomore at Carnegie Mellon. When I moved into my dorm, I brought with me a Shuttle “mini PC” (probably the size of 10 Mac minis), which was plugged into the ethernet jack in my room. CMU allowed students to register static IPs, and you were permitted to use them to host websites, provided they were on <code class="language-plaintext highlighter-rouge">.org</code> TLDs (an odd rule). I quickly registered <code class="language-plaintext highlighter-rouge">btucker.org</code>, and this blog lived there until I moved out and took the server with me.</p>

<p>Twenty years is a long time. I graduated, sold a company, built another, got married, moved to Boston, then San Francisco, and finally Chicago. I spent the first decade primarily as a Ruby on Rails consultant, then the second as an engineering leader at Chegg.</p>

<p>And now I’m starting a new chapter of exploration in the incredible, paradigm-shifting, delirium-inducing world where code can be written through conversation and systems can spring to life in the time it used to take to call a meeting.</p>

<p><a href="https://www.linkedin.com/in/matthew-ramirez-21826774/">Matthew Ramirez</a> first explained language models to me in 2018 and, I’ll be honest, I didn’t get it. They seemed like a clever way to make better predictive text systems, but that was about it. I even remember playing with the GPT-3 API in 2020, and it still didn’t click. It wasn’t until the <a href="https://arxiv.org/abs/2203.02155">InstructGPT paper</a> that it hit me what this was. You can just tell a computer to do something… in English… and it will… do it!? It still seemed like a far-off fantasy, but wow! So this is what they meant by “AI.”</p>

<p>Fast forward to the ChatGPT era and we can all see that the “far-off fantasy” wasn’t so far off.</p>

<p>I plan to use this blog to write about what I’m exploring, learning, and thinking about. It’s been a blast to become <a href="https://github.com/btucker">active on GitHub</a> again, and I have a few projects I can’t wait to talk about.</p>]]></content><author><name></name></author><summary type="html"><![CDATA[I last published on this blog 20 years ago. The final post was in February 2006: a “reblog” of a link from Tim Bray to an incredible juggling performance (now available on YouTube).]]></summary></entry></feed>