<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: pglevy</title><link>https://news.ycombinator.com/user?id=pglevy</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sun, 05 Jul 2026 14:49:21 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=pglevy" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by pglevy in "Local Git Remotes"]]></title><description><![CDATA[
<p>I recently did a similar thing to get all my private repos off GitHub while keeping the same git workflows and accessibility for other machines on my home network. Now my Pi is the remote for those repos.</p>
]]></description><pubDate>Fri, 29 May 2026 16:55:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=48325886</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=48325886</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48325886</guid></item><item><title><![CDATA[New comment by pglevy in "Ferrari Luce"]]></title><description><![CDATA[
<p>I didn't realize initially Marc Newson was involved. Definitely echoes of the 021C.<p><a href="https://marc-newson.com/ford-021c-concept-car/" rel="nofollow">https://marc-newson.com/ford-021c-concept-car/</a></p>
]]></description><pubDate>Tue, 26 May 2026 12:28:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=48278841</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=48278841</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48278841</guid></item><item><title><![CDATA[New comment by pglevy in "Google's Antigravity Bait and Switch"]]></title><description><![CDATA[
<p>> Antigravity, as part of the Google AI Ultra plan, is my daily driver, my workhorse.<p>There's your mistake right there. There is history. User beware.</p>
]]></description><pubDate>Thu, 21 May 2026 16:04:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=48224989</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=48224989</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48224989</guid></item><item><title><![CDATA[New comment by pglevy in "VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage"]]></title><description><![CDATA[
<p>Wondering what else I'm using from MS that might be at risk. <glances at TypeScript></p>
]]></description><pubDate>Sun, 03 May 2026 02:41:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=47992795</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=47992795</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47992795</guid></item><item><title><![CDATA[New comment by pglevy in "Amateur armed with ChatGPT solves an Erdős problem"]]></title><description><![CDATA[
<p>Can't help but think of this I re-read recently from Nietzche:<p>> When I analyze the process that is expressed in the sentence, "I think," I find a whole series of daring assertions that would be difficult, perhaps impossible, to prove; for example, that it is <i>I</i> who think, that there must necessarily be something that thinks, that thinking is an activity and operation on the part of a being who is thought of as a cause, that there is an "ego," and, finally, that it is already determined what is to be designated by thinking—that I <i>know</i> what thinking is.</p>
]]></description><pubDate>Sun, 26 Apr 2026 14:14:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=47910516</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=47910516</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47910516</guid></item><item><title><![CDATA[New comment by pglevy in "Axios compromised on NPM – Malicious versions drop remote access trojan"]]></title><description><![CDATA[
<p>I was thinking about this as a bull case for human developers. Seems if you're worried enough to do this you're not going to have LLMs write the new code.</p>
]]></description><pubDate>Tue, 31 Mar 2026 07:07:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=47583760</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=47583760</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47583760</guid></item><item><title><![CDATA[New comment by pglevy in "Ask HN: What are you working on? (February 2026)"]]></title><description><![CDATA[
<p>Just tried out Opus 4.6 to make a ground-up new version of a perennial side project: static site podcast player.<p>For this one I focused on loading speed and reducing interaction with repo. So it processes the images (converting to webp) and loads the feed list from a Gist. Also used the "frontend-design" skill. From brief to ready-to-use took about a couple hours.<p><a href="https://github.com/pglevy/typod" rel="nofollow">https://github.com/pglevy/typod</a></p>
]]></description><pubDate>Mon, 09 Feb 2026 12:44:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=46944620</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=46944620</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46944620</guid></item><item><title><![CDATA[New comment by pglevy in "Management as AI superpower: Thriving in a world of agentic AI"]]></title><description><![CDATA[
<p>> I think many people have the skills they need, or can learn them, in order to work with AI agents - they are management 101 skills.<p>I like his thinking but many professional managers are not good at management. So I'm not sure about the assumption that "many people" can easily pick this up.</p>
]]></description><pubDate>Tue, 27 Jan 2026 17:34:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=46783284</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=46783284</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46783284</guid></item><item><title><![CDATA[New comment by pglevy in "AI is a horse (2024)"]]></title><description><![CDATA[
<p>Moped for the mind has a nice ring to it</p>
]]></description><pubDate>Fri, 23 Jan 2026 17:49:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=46735430</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=46735430</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46735430</guid></item><item><title><![CDATA[New comment by pglevy in "Show HN: Figma-use – CLI to control Figma for AI agents"]]></title><description><![CDATA[
<p>I'm curious to understand more about your use case. I've been working on getting fellow designers out of Figma since it's easier to express intent in code now using LLMs.</p>
]]></description><pubDate>Sun, 18 Jan 2026 15:26:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=46668552</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=46668552</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46668552</guid></item><item><title><![CDATA[New comment by pglevy in "First impressions of Claude Cowork"]]></title><description><![CDATA[
<p>He literally brings up a concern he calls the "lethal trifecta" when it's even remotely relevant.</p>
]]></description><pubDate>Fri, 16 Jan 2026 03:27:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=46642653</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=46642653</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46642653</guid></item><item><title><![CDATA[New comment by pglevy in "Show HN: Minimalist editor that lives in browser, stores everything in the URL"]]></title><description><![CDATA[
<p>Thanks for sharing! I tried a similar content-in-url approach for a family grocery list app but I couldn't get the url that short. (It worked but it was a bit cumbersome sharing over Whatsapp.) Will see what I can learn from this!</p>
]]></description><pubDate>Wed, 24 Dec 2025 21:16:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=46379317</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=46379317</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46379317</guid></item><item><title><![CDATA[New comment by pglevy in "Incomplete list of mistakes in the design of CSS"]]></title><description><![CDATA[
<p>At least one person. <a href="https://tonsky.me/blog/centering/" rel="nofollow">https://tonsky.me/blog/centering/</a></p>
]]></description><pubDate>Thu, 11 Dec 2025 13:21:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=46231032</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=46231032</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46231032</guid></item><item><title><![CDATA[New comment by pglevy in "AI should only run as fast as we can catch up"]]></title><description><![CDATA[
<p>I've been thinking about something like this from a UI perspective. I'm a UX designer working on a product with a fairly legacy codebase. We're vibe coding prototypes and moving towards making it easier for devs to bring in new components. We have a hard enough time verifying the UI quality as it is. And having more devs vibing on frontend code is probably going to make it a lot worse. I'm thinking about something like having agents regularly traversing the code to identify non-approved components (and either fixing or flagging them). Maybe with this we won't fall further behind with verification debt than we already are.</p>
]]></description><pubDate>Tue, 09 Dec 2025 00:34:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=46199788</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=46199788</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46199788</guid></item><item><title><![CDATA[New comment by pglevy in "Ask HN: What are you working on? (October 2025)"]]></title><description><![CDATA[
<p>For context, I'm a UX Designer at a low-code company. LLMs are great at cranking out prototypes using well-known React component libraries. But lesser known low-code syntax takes more work. We made an MCP server that helps a lot, but what I'm working on now is a set of steering docs to generate components and prototypes that are "backwards compatible" with our bespoke front end language. This way our vibe prototyping has our default look out of the box and translates more directly to production code. <a href="https://github.com/pglevy/sail-zero" rel="nofollow">https://github.com/pglevy/sail-zero</a></p>
]]></description><pubDate>Mon, 13 Oct 2025 03:01:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=45564310</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=45564310</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45564310</guid></item><item><title><![CDATA[New comment by pglevy in "To AI or not to AI"]]></title><description><![CDATA[
<p>Our low-code expression language is not well-represented in the pre-training data. So as a baseline we get lots of syntax errors and really bad-looking UIs. But we're getting much better results by setting up our design system documentation as an MCP server. Our docs include curated guidance and code samples, so when the LLM uses the server, it's able to more competently search for things and call the relevant tools. With this small but high-quality dataset, it also looks better than some of our experiments with fine tuning. I imagine this could work for other docs use cases that are more dynamic (ie, we're actively updating the docs so having the LLM call APIs for what it needs seems more appropriate than a static RAG setup).</p>
]]></description><pubDate>Mon, 29 Sep 2025 16:46:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=45415881</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=45415881</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45415881</guid></item><item><title><![CDATA[New comment by pglevy in "Scammed out of $130K via fake Google call, spoofed Google email and auth sync"]]></title><description><![CDATA[
<p>> I answered.<p>I never answer the phone.</p>
]]></description><pubDate>Tue, 16 Sep 2025 21:12:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=45268122</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=45268122</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45268122</guid></item><item><title><![CDATA[New comment by pglevy in "Don't Build Multi-Agents"]]></title><description><![CDATA[
<p>Not an engineer but I think this is where my mind was going after reading the post. Seems like what will be useful is continuously generated "decision documentation." So the system has access to what has come before in a dynamic way. (Like some mix of RAG with knowledge graph + MCP?) Maybe even pre-outlining "decisions to be made," so if an agent is checking in, it could see there is something that needs to be figured out but hasn't been done yet.</p>
]]></description><pubDate>Tue, 02 Sep 2025 02:39:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=45098586</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=45098586</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45098586</guid></item><item><title><![CDATA[New comment by pglevy in "What makes Claude Code so damn good"]]></title><description><![CDATA[
<p>Mine is a much simpler use case but sharing in case it's useful. I wanted to be able to quickly generate and iterate on user flows during design collaboration. So I use some boilerplate HTML/CSS and have the LLM generate an "outline" (basically a config file) and then generate the HTML from that. This way I can make quick adjustments in the outline and just have it refresh the code when needed to avoid too much back forth with the chat.<p>Overall, it has been working pretty well. I did make a tweak I haven't pushed yet to make it always writes the outline to a file first (instead of just terminal). And I've also started adding slash commands to the instructions so I can type things like "/create some flow" and then just "/refresh" (instead of "pardon me, would you mind refreshing that flow now?").<p><a href="https://github.com/pglevy/breadboarding-kit" rel="nofollow">https://github.com/pglevy/breadboarding-kit</a></p>
]]></description><pubDate>Sun, 24 Aug 2025 14:34:57 +0000</pubDate><link>https://news.ycombinator.com/item?id=45004566</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=45004566</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45004566</guid></item><item><title><![CDATA[New comment by pglevy in "Claude Opus 4 and 4.1 can now end a rare subset of conversations"]]></title><description><![CDATA[
<p>But not Sonnet?</p>
]]></description><pubDate>Fri, 15 Aug 2025 22:13:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=44917874</link><dc:creator>pglevy</dc:creator><comments>https://news.ycombinator.com/item?id=44917874</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44917874</guid></item></channel></rss>