you're correct that being good with language is a useful skill for operating LLMs, and fortunately you get to practice and improve that skill whenever you work with an LLM. being well-read helps too, being precise with vocabulary is important and idioms/metaphors can pack a lot of semantic meaning into a few sentences.
just because you don't know how to swim doesn't mean people can't swim.
$250 doesn't buy you out of them monetizing your data. last year they started selling what content is being watched. next money grab will be selling the list of what's in your media library, all they have to do is update their terms to allow it, like they did last year.
agentic coding is a soft drug, so taking 'the only way out is through' approach is pretty viable. once you figure out how to swim and have claude running for an hour+ at a time and only bugging you with either high-level taste decisions or 'done, how's it look?' it's pretty low stress
if you're overloaded with PRs, build LLM-based systems to take the load off. don't be a senior engineer, be an engineering manager.
isn't this the expected/intended outcome of the economic policy we've held for a generation or two?
the capital/labor class gap increases when total returns on capital investment exceed total wages+redistribution to the labor class, and the gap shrinks when that's reversed. the market ~controls the capital gains and labor wages knobs, and society decides where to set the redistribution knob.
the article investigating the post-covid drop and concluding that it's normal is an interesting rhetorical device. on one hand, relief that nothing crazy is happening. on the other hand, disappointment that we've accepted a growing inequality gap as normal. the gap was already at a post-war max going into covid, the floor gave out 20 years earlier and covid was just gas on the fire.
advancements in automation and tax codes that benefit capex over payroll will continue to incentivize business to shift budgets from labor to robots.
OpenAI/et al. selling an IP laundering service under the name 'max subscription' may force the world to accept the perspective that Intellectual Property isn't a thing. The business model of extracting value from creators via rent seeking IP may not be viable in a world where LLMs can generate anything on demand. We might be transitioning to the Lockean view that for something to be ownable as property, it must be a scarce resource, and information is not a scarce resource.
From that property rights perspective, the property that's created when new information is created is not the information itself, rather, it's the act of creation (claim to authorship) that's the scarce resource.
I don't know what a world looks like where the only form of IP is non-transferable and owned by the original creator. Maybe that new form of IP creates less value over all, and maybe that's ok if the creator is getting 100% of the smaller pie instead of crumbs from media labels. Companies like Red Hat could be an example of a viable business model if IP laws follow the current winds.
Companies like Corgi will need to rely on internal talent to ensure that their product is better than what someone looking at their product can vibe code a copy of, which from my perspective as a consumer, sounds like a better route than Corgi relying on an internal legal team to send a cease and desist letter.
the same technique you use to get a human engineering team to generate a deterministic and repeatable result 100% percent of the time. i know that's a flippant (but true!) answer, it's just a pretty tough problem :) setting the bar lower than 100% makes it a lot more tractable
for me, it's less 'still' and more 'again'. claude code + API tokens means i no longer have to suffer the user-hostile design of many webpages. using full-screen claude code feels like finding my old DOS teddy from childhood buried in the back of a closet.
this is the type of thing you need to build a foundation sturdy enough to let you operate higher up the stack and ratchet to design-by-metaphor and then design-by-philosophy. those design skills are taught in humanities departments, not engineering departments, so this is a weird feeling place for those of us that wandered over from a technical field.
because they need to make as many employees quit as quickly as possible if they hope to avoid bankruptcy. i don't think they'll be able to avoid that outcome, instead they'll die trying. maybe their capital and network will be enough to buy them time to fully pivot to hw, though that's probably less of a moat than i believe it is while wearing the rosy glasses of an EE
software is now free, at least for the people that know the proper incantations required to manifest it into existence. software-only companies have no future. sending old-world SWEs into the undiscovered country results in high costs to the unprepared SWEs and high costs to their financiers who lose control as soon as the boots on the ground realize the wildfire is too close for comfort and new winds are blowing
the only viable way to separate assets from liabilities (payroll) fast enough for large corps to catch up with the growing number of claude-unicorn centaurs, and small herds of them, will be bankruptcy (could be wrong, i'm no lawyer)
it sounds like we share a vice for information gluttony. i have a similar workflow where i continuously scan the digital horizon for useful ideas and continuously feed them into my personal toolkit. i've kind of always been like that as a person and an engineer (the two aren't really separable for me), and claude code has been like switching from coffee to meth, and, um, there's some downsides to doing meth. it's hard not to build a house of cards that you end up abandoning when it starts feeling wobbly and you see a greenfield next door
as an example, i built tooling that lets me open claude code and say 'add MSP430FR2476TRHBR to the library' and a few minutes later there's a schematic symbol and footprint in my kicad library with parameter fields consistent with my organization's internal standards. i'll be waiting a while for anthropic to add that feature to claude code.
agents are everywhere nowadays, one left a long pointless comment on a bug report i submitted on github. well, a bug report that an agent submitted on my behalf. agents all the way down. maybe i'm part of the problem.
This reminds me so much of my own experience with AI fueled dev mania. Rapidly build semi-functional wonders, then pivot to something shiny and new to avoid the QA trudge of polishing that wonderous turd.
It uses your existing subscriptions and supports all the major CLI and API providers. There's no cloud features of Omnispect itself, it runs locally except for calls to the LLM providers.
Claude Opus 4.5 is used as a routing agent, which selects the most appropriate LLM provider and model tier to delegate a task to. For example, the routing agent might delegate a single large task to GPT-5, which in turn delegates multiple small tasks to Haiku agents in parallel, then Gemini reviews all the work.
Omnispect lets you view the delegation tree of prompts and responses that spawn from your initial prompt.
https://katamari64.se/posts/2026/odin-wikipedia/
a little over the etiquette line for HN, the lack of joke comments here is awesome and i shouldn't be part of lowering our collective brows