{"version":"https://jsonfeed.org/version/1.1","title":"Jack Lau","home_page_url":"https://www.thejacklau.com","feed_url":"https://www.thejacklau.com/feed.json","description":"Jack Lau's personal home for writing, life experience, reading notes, tools, and founder updates.","icon":"https://www.thejacklau.com/jack-lau-profile-512.png","favicon":"https://www.thejacklau.com/favicon-32x32.png","language":"en-US","authors":[{"name":"Jack Lau","url":"https://www.thejacklau.com","avatar":"https://www.thejacklau.com/jack-lau-profile-512.png"}],"items":[{"id":"https://www.thejacklau.com/writing/hello-im-jack-lau","url":"https://www.thejacklau.com/writing/hello-im-jack-lau","title":"Hello, I'm Jack Lau","summary":"The first post for this personal site and the start of a more durable writing archive.","content_html":"<p>This is the first post on my personal site. The goal is simple: make one place that can hold my story, projects, notes, and longer reflections without scattering them across feeds and half-finished documents.</p>\n<h2>Why this site exists</h2>\n<p>A personal website should do more than introduce a name. It should become a living record:</p>\n<ul>\n<li>what I have worked on</li>\n<li>what I am learning now</li>\n<li>what I want to remember later</li>\n<li>what I can share with people who want context quickly</li>\n</ul>\n<p>The first version is intentionally small. It gives the site a clear shape, then leaves room for real history, better project pages, and deeper writing.</p>\n<h2>What comes next</h2>\n<p>I want this blog to become a useful archive rather than a loud publishing calendar. Some posts will be short notes. Some will be technical writeups. Some will be personal reflections that explain the path behind the work.</p>\n<p>This post marks the starting line.</p>","content_text":"This is the first post on my personal site. The goal is simple: make one place that can hold my story, projects, notes, and longer reflections without scattering them across feeds and half-finished documents.\n\n## Why this site exists\n\nA personal website should do more than introduce a name. It should become a living record:\n\n- what I have worked on\n- what I am learning now\n- what I want to remember later\n- what I can share with people who want context quickly\n\nThe first version is intentionally small. It gives the site a clear shape, then leaves room for real history, better project pages, and deeper writing.\n\n## What comes next\n\nI want this blog to become a useful archive rather than a loud publishing calendar. Some posts will be short notes. Some will be technical writeups. Some will be personal reflections that explain the path behind the work.\n\nThis post marks the starting line.","image":"https://www.thejacklau.com/og?title=Hello%2C%20I%27m%20Jack%20Lau","date_published":"2026-05-26T00:00:00.000Z","authors":[{"name":"Jack Lau","url":"https://www.thejacklau.com"}]},{"id":"https://www.thejacklau.com/writing/what-this-blog-will-cover","url":"https://www.thejacklau.com/writing/what-this-blog-will-cover","title":"What This Blog Will Cover","summary":"A quick map of the themes this blog can grow into: history, projects, technical notes, and personal essays.","content_html":"<p>This blog is the writing layer for the site. It does not need to be complicated at the beginning. It just needs a few clear lanes.</p>\n<h2>Personal history</h2>\n<p>The history section on the homepage gives a high-level timeline. Blog posts can go deeper into specific chapters: decisions, turning points, influences, and lessons that are easier to understand with context.</p>\n<h2>Project notes</h2>\n<p>Every project has details that disappear if they are not written down:</p>\n<ul>\n<li>what problem started it</li>\n<li>what tradeoffs mattered</li>\n<li>what shipped</li>\n<li>what failed</li>\n<li>what changed after using it</li>\n</ul>\n<p>Those notes are useful for future me and for anyone trying to understand how I work.</p>\n<h2>Technical writing</h2>\n<p>Technical posts can be practical and direct: setup notes, debugging logs, architecture decisions, library comparisons, and walkthroughs.</p>\n<figure data-rehype-pretty-code-figure=\"\"><pre tabindex=\"0\" data-language=\"ts\" data-theme=\"min-light min-dark\"><code data-language=\"ts\" data-theme=\"min-light min-dark\" style=\"display: grid;\"><span data-line=\"\"><span style=\"--shiki-light:#D32F2F;--shiki-dark:#F97583\">type</span><span style=\"--shiki-light:#6F42C1;--shiki-dark:#B392F0\"> BlogPost</span><span style=\"--shiki-light:#D32F2F;--shiki-dark:#F97583\"> =</span><span style=\"--shiki-light:#24292EFF;--shiki-dark:#B392F0\"> {</span></span>\n<span data-line=\"\"><span style=\"--shiki-light:#24292EFF;--shiki-dark:#B392F0\">  title</span><span style=\"--shiki-light:#D32F2F;--shiki-dark:#F97583\">:</span><span style=\"--shiki-light:#1976D2;--shiki-dark:#79B8FF\"> string</span><span style=\"--shiki-light:#24292EFF;--shiki-dark:#B392F0\">;</span></span>\n<span data-line=\"\"><span style=\"--shiki-light:#24292EFF;--shiki-dark:#B392F0\">  lesson</span><span style=\"--shiki-light:#D32F2F;--shiki-dark:#F97583\">:</span><span style=\"--shiki-light:#1976D2;--shiki-dark:#79B8FF\"> string</span><span style=\"--shiki-light:#24292EFF;--shiki-dark:#B392F0\">;</span></span>\n<span data-line=\"\"><span style=\"--shiki-light:#24292EFF;--shiki-dark:#B392F0\">  usefulLater</span><span style=\"--shiki-light:#D32F2F;--shiki-dark:#F97583\">:</span><span style=\"--shiki-light:#1976D2;--shiki-dark:#79B8FF\"> boolean</span><span style=\"--shiki-light:#24292EFF;--shiki-dark:#B392F0\">;</span></span>\n<span data-line=\"\"><span style=\"--shiki-light:#24292EFF;--shiki-dark:#B392F0\">};</span></span></code></pre></figure>\n<p>The test for a technical post is whether it would help someone move faster next time.</p>\n<h2>Essays</h2>\n<p>Some ideas need a little more room. Essays can cover taste, systems, learning, career decisions, or whatever keeps showing up across projects.</p>\n<p>The blog can start small and get sharper as the site fills with real work.</p>","content_text":"This blog is the writing layer for the site. It does not need to be complicated at the beginning. It just needs a few clear lanes.\n\n## Personal history\n\nThe history section on the homepage gives a high-level timeline. Blog posts can go deeper into specific chapters: decisions, turning points, influences, and lessons that are easier to understand with context.\n\n## Project notes\n\nEvery project has details that disappear if they are not written down:\n\n- what problem started it\n- what tradeoffs mattered\n- what shipped\n- what failed\n- what changed after using it\n\nThose notes are useful for future me and for anyone trying to understand how I work.\n\n## Technical writing\n\nTechnical posts can be practical and direct: setup notes, debugging logs, architecture decisions, library comparisons, and walkthroughs.\n\n```ts\ntype BlogPost = {\n  title: string;\n  lesson: string;\n  usefulLater: boolean;\n};\n```\n\nThe test for a technical post is whether it would help someone move faster next time.\n\n## Essays\n\nSome ideas need a little more room. Essays can cover taste, systems, learning, career decisions, or whatever keeps showing up across projects.\n\nThe blog can start small and get sharper as the site fills with real work.","image":"https://www.thejacklau.com/og?title=What%20This%20Blog%20Will%20Cover","date_published":"2026-05-26T00:00:00.000Z","authors":[{"name":"Jack Lau","url":"https://www.thejacklau.com"}]}]}