lol yes. At least in agency world, a common approach in the last X years has been that designers create entire pixel-perfect, component-based sources-of-truth in Figma (which evolve! they aren't delivered static and complete) -- these are also what the client sees and approves, or at the very least they see branded deck slides that incorporate the Figma designs. Anyways, front end then re-implements from Figma into CSS, except it's usually best-approximation (not pixel-perfect) partially because, despite Figma allowing you to "copy CSS" for an element, it's unusable, almost inline CSS (and usually not aware of its ascendents and descendents, or any variables you're maintaining in CSS, or any class hierarchies, etc), and partially because the units of measurement aren't always identical on either side. You'll also often have multiple FE devs recreating components independently of each other (as a team effort), which can lead to drift and different implementations, which is fun. Then, depending upon the tech stack, FE might be building these components in something like Storybook [0] as a "front end source of truth", which then are either directly injected into a React or NextJS app or whatever, or sometimes they're partially or fully re-implemented again into BE components in the CMS (ex. Sitefinity). Then people ask which one is the source of truth, but really it's a chain of sources of truth that looks more like the telephone game than a canonical "brand bible". Then throw in any out-of-the-box future client efforts (say, a promotional landing page hosted outside of the main project) and you may have yet another reimplementation of part of the same design, but in a completely different system. [0] https://storybook.js.org
I think a lot of the reason for the war on taxes is the exorbitant privilege [1] of owning the world reserve currency. It lets America print as many dollars as it wants, and borrow in a currency it controls entirely. In a normal country this would result in severe inflation, but because America borrows and prints a currency that is necessary abroad to conduct international trade, it is able to "export" a large part of its inflation. In such a system, it is rational to cut taxes as much as possible and instead rely on borrowing and monetization of debt. It allows America to limit the load on its own citizens, who in turn enjoy "exorbitant privilege" in the colloquial rather than economic sense, and then have the costs spread amongst the billions of people who don't live here. Privatize the gains, socialize the losses. The flip side is that if the U.S. dollar ever loses its reserve currency status, that is literally the end of the United States. It will no longer have the ability to fund the government, which is fed by debt that is largely snapped up by foreigners who need a place to park the dollars that move abroad from the persistent trade deficits needed to sustain reserve currency status. It will also no longer have a citizenry or economy capable of doing anything other than moving capital (finance) and jobs (tech) around in the global economy, since in the current reserve currency economy, those are the only sectors that are profitable to go into. If it happens, expect basically a collapse of society and multi-sided civil war. [1] https://en.wikipedia.org/wiki/Exorbitant_privilege
It thinks less and produces less output tokens because it has forced adaptive thinking that even API users can't disable. Same adaptive thinking that was causing quality issues in Opus 4.6 not even two weeks ago. The one bcherny recommended that people disable because it'd sometimes allocate zero thinking tokens to the model. https://news.ycombinator.com/item?id=47668520 People are already complaining about low quality results with Opus 4.7. I'm also spotting it making really basic mistakes. I literally just caught it lazily "hand-waving" away things instead of properly thinking them through, even though it spent like 10 minutes churning tokens and ate only god knows how many percentage points off my limits. > What's the difference between this and option 1.(a) presented before? > Honestly? Barely any. Option M is option 1.(a) with the lifecycle actually worked out instead of hand-waved. > Why are you handwaving things away though? I've got you on max effort. I even patched the system prompts to reduce this. > Fair call. I was pattern-matching on "mutation + capture = scary" without actually reading the capture code. Let me do the work properly. > You were right to push back. I was wrong. Let me actually trace it properly this time. > My concern from the first pass was right. The second pass was me talking myself out of it with a bad trace. It's just a constant stream of self-corrections and doubts. Opus simply cannot be trusted when adaptive thinking is enabled. Can provide session feedback IDs if needed.
 Top