<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: jimmont</title><link>https://news.ycombinator.com/user?id=jimmont</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 03 Sep 2026 09:47:18 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=jimmont" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by jimmont in "AI is removing the middle class of software engineering?"]]></title><description><![CDATA[
<p>Clearly that article shipped to production without QA. Having no testable definition of good, it must be bad. Fired.</p>
]]></description><pubDate>Thu, 13 Aug 2026 07:28:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=49282761</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=49282761</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49282761</guid></item><item><title><![CDATA[New comment by jimmont in "What I'm Finding About LLM Code Style and Token Costs"]]></title><description><![CDATA[
<p>That's an excellent idea I plan to try, thanks—re using structured JSON with schema. The most success I've had is saying "be brief" or an explicit size, like one line, or do not explain, etc. I haven't measured other instructions so extensively. They do work but the more specific the better. Other strategies around outputs that are more natural language seem to be hands-down the direction to take, and get away from the machine language habits we've used in the past. It's super interesting seeing this new practice emerging and more or less inventing parts of it along the way. Right now I'm at the place where my brute force and elaborate explanations were reaching their limit and in the frustration just realized I need to take a few days and try to figure out the tool. Across all these the pattern seems entirely that the constraints bound the probability space, whether it's the format like you suggested, or the instruction we give, including the space we point it toward (Web APIs, runtime, schema, etc). In all instances where it's not working the solution seems to be what does the pattern reduce to, and what specifics are the do/don't to go with that, and most of the time the results improve immediately. Your tip seems excellent for this. An easy-button.</p>
]]></description><pubDate>Thu, 25 Jun 2026 06:39:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=48669807</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=48669807</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48669807</guid></item><item><title><![CDATA[New comment by jimmont in "What I'm Finding About LLM Code Style and Token Costs"]]></title><description><![CDATA[
<p>Reviewing my experience using LLMs, to improve results, reduce churn and token usage. Discovering the gap between what they produce and what I'd normally do is a significant source of output cost, regressions and surfacing a bit of why and how to fix it. Notably Claude is remarkably bad at/about this, producing errors even when directed toward modern Web solutions—that cut token use a lot, like toward 90% occasionally, which together with the frustrating churn led me to review how I'm working, what is happening and generate this article.</p>
]]></description><pubDate>Thu, 25 Jun 2026 00:52:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=48667410</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=48667410</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48667410</guid></item><item><title><![CDATA[What I'm Finding About LLM Code Style and Token Costs]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.jimmont.com/llm-style-token-costs">https://www.jimmont.com/llm-style-token-costs</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48667409">https://news.ycombinator.com/item?id=48667409</a></p>
<p>Points: 38</p>
<p># Comments: 17</p>
]]></description><pubDate>Thu, 25 Jun 2026 00:52:40 +0000</pubDate><link>https://www.jimmont.com/llm-style-token-costs</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=48667409</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48667409</guid></item><item><title><![CDATA[Show HN: HWT (Hash Web Tokens) – minimalist protocol for auth state]]></title><description><![CDATA[
<p>My frustration solving auth with JWTs led to reinventing the wheel for more predictable token integrity and transparency, while improving flexibility. The mix of features separates concerns more cleanly than what's been available, allowing higher throughput, custom codecs, delegation to both services and domains while easing key rotation and other practicalities.<p>The design is focused on the token as state guarantee, not creation, revocation and the range of other separate concerns and application responsibilities. The spec conventions attempts to ease development with jurisdiction/data sovereignty and authorization in the authz field. It also enables and eases delegation between services and domains without centralized service exposure. The implementation is standalone and has demos for Deno, Cloudflare, etc in <a href="https://github.com/hwt-protocol" rel="nofollow">https://github.com/hwt-protocol</a><p>Feedback and critique of the security logic and approach appreciated.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47778646">https://news.ycombinator.com/item?id=47778646</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 15 Apr 2026 13:24:26 +0000</pubDate><link>https://www.jimmont.com/hwt/</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=47778646</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47778646</guid></item><item><title><![CDATA[New comment by jimmont in "Ask HN: What can we do about explosion of self promotion in HN comments"]]></title><description><![CDATA[
<p>Turn off the ability to add hyperlinks and use words instead? Is that what comments were intended for anyway? Seems a bit convoluted, but limiting comments, to comments, would be fairly natural. It'll get subverted anyway, but likely affects. A policy could say don't use hyperlinks, feel free to say where to go. Which would be an interesting policy to technically enforce, and still have the discretion to operate on.</p>
]]></description><pubDate>Wed, 18 Mar 2026 15:32:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=47427052</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=47427052</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47427052</guid></item><item><title><![CDATA[The Org Chart Is the Product: Software as Case Study for Intellectual Work]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.jimmont.com/org-chart-is-the-product">https://www.jimmont.com/org-chart-is-the-product</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47425504">https://news.ycombinator.com/item?id=47425504</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 18 Mar 2026 13:23:49 +0000</pubDate><link>https://www.jimmont.com/org-chart-is-the-product</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=47425504</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47425504</guid></item><item><title><![CDATA[New comment by jimmont in "Ask HN: How does one build large front end apps without a framework like React?"]]></title><description><![CDATA[
<p>MDN has your answer, built into the browser, ready to go:
<a href="https://developer.mozilla.org/docs/Web/API/Web_components" rel="nofollow">https://developer.mozilla.org/docs/Web/API/Web_components</a><p>If that's not enough, Lit enhances it a bit such that either LitElement and/or litHtml can accommodate whichever style you want: <a href="https://lit.dev/" rel="nofollow">https://lit.dev/</a></p>
]]></description><pubDate>Fri, 17 Oct 2025 11:41:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=45615557</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=45615557</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45615557</guid></item><item><title><![CDATA[New comment by jimmont in "AI adoption linked to 13% decline in jobs for young U.S. workers: study"]]></title><description><![CDATA[
<p>Organizations are choosing to eliminate workers rather than amplify them with AI because they'd rather own 100% of diminished capacity than share proceeds from exponentially increased capacity. That's the rent extraction model consuming its own productive infrastructure.
The Stanford study documents organizations systematically choosing inferior economic strategies because their rent-extraction frameworks cannot conceptualize workers as productive assets to amplify.
This reveals that these organizations are economic rent-seekers that happen to have productive workers, not production companies that happen to extract rents. When forced to choose between preserving rent extraction structures or maximizing value creation, they preserve extraction even at the cost of destroying productive capacity. So what comes next?</p>
]]></description><pubDate>Fri, 29 Aug 2025 02:54:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=45059611</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=45059611</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45059611</guid></item><item><title><![CDATA[New comment by jimmont in "Updates to Consumer Terms and Privacy Policy"]]></title><description><![CDATA[
<p>I think it's just general lack of awareness of the effect, or in many instances having alternate economic incentives, like academics who want to commoditize their intellectual outputs to all available distribution channels. Tyler Cowen for example. The AI companies are in a race to the bottom.</p>
]]></description><pubDate>Thu, 28 Aug 2025 18:47:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=45055577</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=45055577</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45055577</guid></item><item><title><![CDATA[New comment by jimmont in "Updates to Consumer Terms and Privacy Policy"]]></title><description><![CDATA[
<p>For those that use AI/LLM's that retrain on your input, I assume you realize this commoditizes your intellectual work? And effectively makes use of it like they already used copyrighted intellectual property. This is effectively the same as the commons appropriations made for railroad development, reinterpreting fair use, etc.</p>
]]></description><pubDate>Thu, 28 Aug 2025 17:46:30 +0000</pubDate><link>https://news.ycombinator.com/item?id=45054937</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=45054937</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45054937</guid></item><item><title><![CDATA[New comment by jimmont in "Google Being Forced to Sell Chrome Is Not Good for the Web"]]></title><description><![CDATA[
<p>It's interesting to see where the economics align with software. Web advertising paired with search and a browser. And it worked. I can't recall a better outcome supporting modern communication than Chrome and all it contains. The harmony between the business, software and market need was very well aligned. 
That's falling apart now due to LLM's taking over much of what previously was search, and Google's innovator's dilemma between AI/LLM and traditional search. While the revenues are stronger than ever this seems unlikely to continue long term. So the dynamic is changing naturally.
Reminds me of how a strange contemporary religion where believers families take over a planet, resulted in this group building an amazing genealogy web service (familysearch.org). Or how US hegemony naturally leads to it's military, or how the theocratic monarchy of ancient Egypt was good for the masonry industry--even affecting modern tourism, or how Roman roads form the paths leading to today's major European cities.</p>
]]></description><pubDate>Sat, 15 Mar 2025 06:17:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=43370409</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=43370409</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43370409</guid></item><item><title><![CDATA[New comment by jimmont in "Apple's Siri Chief Calls AI Delays Ugly and Embarrassing, Promises Fixes"]]></title><description><![CDATA[
<p>It's a demonstration of what an entity can do, and will do. The only innovation from Apple since Job's died were unfinished efforts that completed under Cook. There will be no future innovation from Apple. There maybe acquisitions and optimizations around current and existing positions, nothing more. Apple is IBM now and has been for some time. Apple doesn't know how to develop software or deliver it to market. It has no leadership, only management, and managers are not known for relinquishing their position so I don't see any reason this will ever change. This pattern is endemic in Silicon Valley as old products have run their course. It's like the automobile from the 1900s just playing itself out. Phones and computers are a commodity I don't expect any differentiation within anymore. As to Siri and AI it's an emerging space that Apple can't even deliver on a strategic partnership for within 2 complete phone and iOS release cycles. I'm not sure how an institution like Apple can or will ever overcome its own misaligned culture. Which brings me back to it being IBM.</p>
]]></description><pubDate>Sat, 15 Mar 2025 04:54:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=43370090</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=43370090</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43370090</guid></item><item><title><![CDATA[New comment by jimmont in "Bosses Are Finding Ways to Pay Workers Less"]]></title><description><![CDATA[
<p>the article is consistent with sticky cpi, as can be seen in the transient and sticky cpi and wage tracking, in fact we appear to be in deflationary territory but I'm not an economist so my interpretation might be off
<a href="https://www.atlantafed.org/research/inflationproject/stickyprice" rel="nofollow">https://www.atlantafed.org/research/inflationproject/stickyp...</a>
<a href="https://www.atlantafed.org/chcs/wage-growth-tracker" rel="nofollow">https://www.atlantafed.org/chcs/wage-growth-tracker</a></p>
]]></description><pubDate>Thu, 29 Aug 2024 07:38:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=41388309</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=41388309</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41388309</guid></item><item><title><![CDATA[New comment by jimmont in "Bosses Are Finding Ways to Pay Workers Less"]]></title><description><![CDATA[
<p>prelude to recession, as visible in Sahm rule trends at <a href="https://fred.stlouisfed.org/release?rid=456" rel="nofollow">https://fred.stlouisfed.org/release?rid=456</a> as well as when the 10 2 yield curve approaches +0.5 <a href="https://fred.stlouisfed.org/series/T10Y2Y" rel="nofollow">https://fred.stlouisfed.org/series/T10Y2Y</a> with near term interest rate cuts, along with other indicators; guessing arrives early next year;</p>
]]></description><pubDate>Thu, 29 Aug 2024 05:08:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=41387539</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=41387539</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41387539</guid></item><item><title><![CDATA[New comment by jimmont in "Things you forgot (or never knew) because of React"]]></title><description><![CDATA[
<p>captain obvious here, Polymer became LitElement which became the invisible Lit.dev (branding direction on par with twitter becoming x); pretty much state of the art on top of web components; not that anyone noticed, as I said--meetup.com keeps prompting me to take over one of the web component meetups where the (or one of) lead of the project can't seem to muster the effort. a bit frustrating when the lack of awareness is so profound and extensive--as evidenced by many of these comments, over many years. I'm sure many more projects will make the mistake of choosing React and Svelte before the conclusion mentioned here bubbles up.</p>
]]></description><pubDate>Thu, 17 Aug 2023 00:06:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=37155533</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=37155533</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=37155533</guid></item><item><title><![CDATA[New comment by jimmont in "Modules, not microservices"]]></title><description><![CDATA[
<p>Layers, Not Modules, Not Microservices Like donkeys, onions, caching, networking, my feelings and perceptions.</p>
]]></description><pubDate>Tue, 03 Jan 2023 18:01:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=34235125</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=34235125</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=34235125</guid></item><item><title><![CDATA[New comment by jimmont in "Breaking up with JavaScript front ends"]]></title><description><![CDATA[
<p>the primary solution to all this is to remove technologies which are not required and especially those that duplicate what the web as a platform provides (ie works in browsers/runtime directly); for example React has been technically obsolete a few years, yet that doesn't mean anyone understands what to do instead, regardless of whether those technical implementations were ubiquitous 1 year ago or 15 years ago; I find it remarkable to read job listings for up and coming concerns (eg Anduril, BioNTech, etc) basing their platforms on long outdated notions and implementations, which bring with them multiple vectors for risk to security and more (unnecessary) costs to developer productivity, complexity; SASS and npm/yarn are other obvious examples of tech that costs more than it benefits in modern work.</p>
]]></description><pubDate>Mon, 12 Dec 2022 00:11:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=33949132</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=33949132</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=33949132</guid></item><item><title><![CDATA[New comment by jimmont in "Cloud.gov"]]></title><description><![CDATA[
<p>if that were true it would have already happened in healthcare, so they can extract more from sick people in the States; these existing systems optimize around different problems, goals and bounds</p>
]]></description><pubDate>Mon, 15 Aug 2022 18:24:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=32473391</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=32473391</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=32473391</guid></item><item><title><![CDATA[New comment by jimmont in "Do data-driven companies win?"]]></title><description><![CDATA[
<p>Intuition and judgement come from changing the context of the analysis--the time range/history, the details included. Geopolitical and economic forecasting appear to fit this pattern. The question posed about whether data-driven companies win seems simplistic and formulaic to me personally. Often outcomes can be better fortunes and circumstantial than from over analyzing and using the right approach. Of course both together tend to be where we'd see success looking backward.</p>
]]></description><pubDate>Fri, 29 Jul 2022 16:28:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=32278968</link><dc:creator>jimmont</dc:creator><comments>https://news.ycombinator.com/item?id=32278968</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=32278968</guid></item></channel></rss>