<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Notes / Halaska</title><link>https://halaska.com/notes</link><description>Notes from Chris Halaska on product design, AI tools and design engineering.</description><language>en-au</language><item><title>Design to code: why I take my designs into the build</title><link>https://halaska.com/notes/design-to-code</link><guid>https://halaska.com/notes/design-to-code</guid><pubDate>Fri, 13 Nov 2026 00:00:00 GMT</pubDate><description>Why products never quite match the Figma file, and how a product design engineer closes the gap for funded teams.</description></item><item><title>AI interface design beyond chat: what I build instead of a chat window</title><link>https://halaska.com/notes/ai-interface-design-beyond-chat</link><guid>https://halaska.com/notes/ai-interface-design-beyond-chat</guid><pubDate>Wed, 28 Oct 2026 00:00:00 GMT</pubDate><description>A chat box is the quickest AI interface to ship and one of the hardest to use well. Here's what I design instead.</description></item><item><title>Why products built with AI start to feel the same</title><link>https://halaska.com/notes/why-products-built-with-ai-start-to-feel-the-same</link><guid>https://halaska.com/notes/why-products-built-with-ai-start-to-feel-the-same</guid><pubDate>Tue, 06 Oct 2026 00:00:00 GMT</pubDate><description>AI tools pick the most obvious pattern for every screen. Each choice makes sense. The product as a whole rarely does.</description></item><item><title>Why I've changed what I hand over</title><link>https://halaska.com/notes/why-we-ve-changed-what-we-hand-over</link><guid>https://halaska.com/notes/why-we-ve-changed-what-we-hand-over</guid><pubDate>Tue, 06 Oct 2026 00:00:00 GMT</pubDate><description>Teams build faster with AI than any handover file can keep up with. So I've changed what I leave behind.</description></item></channel></rss>