jimmont

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.

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.

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.

MDN has your answer, built into the browser, ready to go: https://developer.mozilla.org/docs/Web/API/Web_components

If that's not enough, Lit enhances it a bit such that either LitElement and/or litHtml can accommodate whichever style you want: https://lit.dev/

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?

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.

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.

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.

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.

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 https://www.atlantafed.org/research/inflationproject/stickyp... https://www.atlantafed.org/chcs/wage-growth-tracker

prelude to recession, as visible in Sahm rule trends at https://fred.stlouisfed.org/release?rid=456 as well as when the 10 2 yield curve approaches +0.5 https://fred.stlouisfed.org/series/T10Y2Y with near term interest rate cuts, along with other indicators; guessing arrives early next year;

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.

Layers, Not Modules, Not Microservices Like donkeys, onions, caching, networking, my feelings and perceptions.

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.

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

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.

The remedy for this lies with Apple and Google to compete over. They’re naturally incentivized in various ways. Mozilla too but Mozilla can’t seem to figure out what to do until it’s passed by, even when the opportunity is still there. Imagine paying it forward to not have calls and text and voicemails related to your expiring warranty, reliable messages, etc. I don’t think even slack can touch this. Otherwise they would have already. Allow me to point out the planet has been networked for over 100 years and this is the best our lawmakers and tech companies can muster. It’s as though everyone has lost sight of doing something practical (for money).

Werewithal (or werwithal) forthcoming dictionary definition: transformational withal, typically during a full moon, though it regularly manifests in Hacker News posts, causes not yet fully determined. The withals can be complex.

China is more likely to have its government choose a very different leader with resulting policy changes than attack Taiwan. Its economy and along with this politics have increasing problems which are unlikely to reach a plateau or improve in the next decade, possibly longer, and the current leader's policies are accelerating and exacerbating these problems. The only major wild card I see is if the government is able to make a unilateral move against Taiwan in an effort to distract from its internal problems. I don't know how the PRC works well enough to have some notion of how realistic this might be. Given Biden's restatement of the US positions it seems even less likely this would happen. And if it did I'd expect the US and Japan will immediately become involved, promptly followed by other allies if it escalates. What I also cannot gauge is what might happen if action were limited to only a place like Kinmen. If so the arms shipments to Taiwan and would likely immediately change and who knows maybe both Japan and the US would setup military bases there.

Often tech debt stems from political and cultural issues that cannot be (easily) fixed. And even when that's not the issue, are obviously non-trivial costs to resolve. It's been hard for me personally to realize how cultural, even religious Silicon Valley and technology work is. I tend to think there's a common appreciation for certain values, openness and transparency in execution, and these are not the case.

During the first 2 to 6 weeks on a job (it probably varies more than this) most corporate US environments expect significant amount of time to go to processing/onboarding. When providing status updates in meetings just state as much, usually with little to no specifics. I've yet to see anyone respond at all within the first month. What's remarkable to me is the amount of overhead/cost associated with these institutional mechanics, despite tools like Workday, which frankly I don't see as actually being effective. Staff counts of 2 and more (in addition to the new person) with these tools still can't manage to communicate with new staff where to go, where to send equipment, etc which reveals a significant need in the market.

There is no such place in the US. And SF is not it either. San Jose appears to be steadily improving, though this is not a recommendation at all. This is my perspective traveling and living around the northern hemisphere awhile, including substantive time in SF. Manchester NH is within an easy Uber ride of BOS and may be of interest. Winters aren't so great but you can easily fly as far south as Puerto Rico, which has massive crime problems and barely functioning government. There are obviously various options in between. My opinion is that the US is generally inhospitable, SF included, and is unlikely to change substantively in the next several decades. California could start banging out housing, improve transit and reform healthcare delivery and it would probably take at least 20 years to catch up... to what you'll easily find outside the country. America is at the stagnation point in transition through institutional and socio-economic cycles based on what I understand and the solutions aren't super clear at the moment--at least not as clear as the problems.

possibly related: * https://umaar.com/dev-tips/241-puppeteer-recorder/ * https://umaar.com/dev-tips/248-recorder-playback/ * https://developer.chrome.com/docs/devtools/recorder/

I use Deno and its standard library for testing with Puppeteer. I've found unit tests overrated and scenarios underrated (ie testing pyramid).

A tremendously helpful article. Possibly one of the best HN shares I've seen related to software. Most code reviews I've seen professionally over the past decade are almost entirely stylistic one-way brittle dialogs over text of small to large pull/change-requests. When in reality these could, should, recommended to be (as the article shares) side-by-side discussions for dialog to improve the product being contributed to. It's really an effective way to ensure that someone else can pick up the work and go if the other gets hit by a bus, and in my own experience, when I lead with an explanatory walk-through exposes bugs (to myself) along the way--that even the reviewer often doesn't note. Thanks for sharing, software development practice is several decades behind... other practices, and content like this help to improve it.

For the benefit of anyone who doesn't have a lot of experience with call, bind and arrow functions ()=>{}. No, these don't supplant one another and are separately useful in various ways. Reading the linked articles shows some of the related situations.

Yes I’m wondering why these various comments directly challenge this publisher and publication’s credibility? Especially without a substantive explanation since the content is available for this type of dialog. Strange.

Consider submitting this feedback to Nature. It’s generally a reliable source. I’d be curious to see how they respond to your review.

In one project we've been moving the tooling to Deno and it's remarkable how much easier it is to work with than the entire Nodejs ecosystem.

4 is from a decade ago. Perhaps consider what has happened since.

Entertaining, inaccurate article. Weak thesis. If this is the industry status quo, it's remarkable how little depth it has.