<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>J Lee</title>
    <link>https://123jlee.xyz/</link>
      <atom:link href="https://123jlee.xyz/index.xml" rel="self" type="application/rss+xml" />
    <description>J Lee</description>
    <generator>Hugo Blox Builder (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Sat, 08 Aug 2026 00:00:00 +0000</lastBuildDate>
    <image>
      <url>https://123jlee.xyz/media/logo.svg</url>
      <title>J Lee</title>
      <link>https://123jlee.xyz/</link>
    </image>
    
    <item>
      <title>I&#39;m the Cook</title>
      <link>https://123jlee.xyz/notes/i-m-the-cook/</link>
      <pubDate>Sat, 08 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://123jlee.xyz/notes/i-m-the-cook/</guid>
      <description>&lt;p&gt;For at least the first decade of my career, everything I built belonged to someone else. Usually it started with some kind of brief, passed down the chain from clients to product and account directors and any other stakeholders. The finished work then worked its way back up through approvals and sign-offs before finding a permanent home (at least until it&amp;rsquo;s inevitably re-briefed).&lt;/p&gt;
&lt;p&gt;When I worked in agencies and larger orgs, I always wondered why there were so many cooks. Especially with work that felt pretty formulaic or even mundane.&lt;/p&gt;
&lt;p&gt;The last few years of working alone have made the answers pretty clear though. Even when the work seems clear cut, you don&amp;rsquo;t know what you don&amp;rsquo;t know, and what&amp;rsquo;s a clearly obvious mistake in someone else&amp;rsquo;s eyes can be a complete blindspot for me. Team members bring the value and experience from the mistakes they&amp;rsquo;ve already paid for in their past.&lt;/p&gt;
&lt;p&gt;But I also remember the other pattern. The thing I knew was broken but wasn&amp;rsquo;t mine to fix. In a big company you learn the line between what you were asked to build and what you can see needs building, and sometimes it&amp;rsquo;s better not to cross it. Make sure it becomes someone else&amp;rsquo;s problem. That may or may not be a joke, but it&amp;rsquo;s a real skill: knowing how to make the broken thing someone else&amp;rsquo;s responsibility and keep moving.&lt;/p&gt;
&lt;p&gt;When you&amp;rsquo;re the only person building and using a system, you inherit all of it: the brief, the decisions, the work, the mistakes, with one set of eyes instead of six. Some of that is freeing; the purpose gets clearer. But the rest is a real cost.&lt;/p&gt;
&lt;p&gt;The layers I used to call overhead turn out to be how a bigger room stays on top of it all. There&amp;rsquo;s no one to hand it to. The broken thing is mine to fix or mine to live with, every morning. I can learn to do it, or I can build something that does it for me. Sometimes both.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m not saying I&amp;rsquo;m the client. But I&amp;rsquo;m the only one here, time is finite, and things need to get done, so I&amp;rsquo;m just building stuff. The brief comes from my own day: what keeps slowing me down? Which decision is taking too much time? What work am I repeating because I never fixed the underlying problem? The goal is simple: make decisions easier, get time back, make the work actually work.&lt;/p&gt;
&lt;p&gt;Even when I&amp;rsquo;m the one coming up with everything, it&amp;rsquo;s been surprisingly hard to keep up. I&amp;rsquo;m making most of it up as I go. So far, it&amp;rsquo;s working. Until the next thing breaks.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title></title>
      <link>https://123jlee.xyz/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://123jlee.xyz/about/</guid>
      <description></description>
    </item>
    
  </channel>
</rss>
