MurphyA/hacker-news huggingface dataset:
by incomingpain | 2026-02-18 14:59:18+00:00
>You must be very lucky.

No i wouldnt agree. Post birth surgeries, then age 4 infectious disease that is now taught in Med universities because of how badly that went, one of the few people ever in history. I had my own icu area after surgeries. After I recovered, I did start grade 1 like a normal kid. I made my first ever friend, who then got hit by a car and died.

few years later I had a particularly bad ragweed season and nearly died. Ended up a bubble boy for months. Few years after that the catholic priest thing happened to me.

Ya, I wouldnt say im lucky.

>My grandparents were not rich at all, but they still owned houses and land that I will never be able to buy from the salary of an engineer or programmer. I own my apartment, but its true value is far less than of the big houses and ample lands on which my grandparents lived.

I dont know where you live but in north america there's tons of opportunities like this. I could probably buy and renovate a house in Detroit for a few months salary.

>Moreover, while there is an abundance of cheap and reasonably healthy food around me, I cannot find at any price food with a comparable quality with that which I could eat at my grandparents, which was produced by themselves, from their cultivated land and from their animals.

Homesteading in north america is hard work but very rewarding. The governments practically pay for you to do it. But it is a ton of work.

>In conclusion, while there are plenty of things that are much better than when I was young, there are also a lot of things that are much worse. It hard to say which is the balance between bad and good, especially because the things that have become worse are essential necessities, while those that have become better are mainly optional things, useful for research or entertainment.

When i read your post, it reads like you're doing all the right things but are in the wrong place.

Consider the same water bottle but in different places.

At costco is .25cents.

At restaurant is 1$.

On a flight is 2$.

Middle of a desert, no other store for 50km, 5$.

On the spacestation its 10$.
by bilekas | 2026-02-18 14:59:22+00:00
> 2. Why are they judged by a different standard?

This feels like a frustrated dig at cloudflare for not acting faster. Probably not necessary.

Its usually a few days so maybe you have more info on how long you've waited ?

For your answer, I guess you have to fill in the report : https://abuse.cloudflare.com/phishing

If you have done that there is a review process, I don't know the numbers but I can't even begin to imagine the amount of false requests they get and so they would need to all be verified (or maybe aggregated based on amount of requests but this is just a guess).

So long story short, it's a huge company with a lot of requests for sure and things take time.
by jorvi | 2026-02-18 14:59:23+00:00
Hehe, yeah there's some terms that just are linguistically unintuitive.

"Skill floor" is another one. People generally interpret that one as "must be at least this tall to ride", but it actually means "amount of effort that translates to result". Something that has a high skill floor (if you write "high floor of skill" it makes more sense) means that with very little input you can gain a lot of result. Whereas a low skill floor means something behaves more linearly, where very little input only gains very little result.

Even though its just the antonym, "skill ceiling" is much more intuitive in that regard.
Show HN: Opaal Visual multi-agent prompt designer for Claude Code and agentic AI
by Kinanhamwi | 2026-02-18 14:59:27+00:00
Hi HN!

I built Opaal because writing multi-agent orchestration prompts was becoming tedious and error-prone. Every time I wanted to coordinate 3-5 AI agents on a complex task, I would spend 20+ minutes crafting the prompt by hand.

Opaal (Orchestration Prompts for Agentic AI Launch) lets you design these workflows visually instead. You drag agent cards onto a canvas, organize them into phases (columns), draw connections between them, and the app generates a production-ready prompt automatically. The prompt updates live as you build.

Built with Electron + React + React Flow + Zustand + Tailwind CSS v4.

Key features:
- 15 agent roles (Researcher, Architect, Developer, Reviewer, etc.)
- Smart auto-connections between adjacent phases
- Manual wiring for custom data flow
- 3 starter templates (Code Review, Feature Build, Bug Fix)
- Auto-detects installed Claude Code skills
- Save/load .opaal files, export to CLAUDE.md
- Full keyboard shortcuts, undo/redo, multi-select

MIT licensed. Would love feedback on what features would make this more useful for your workflows.
by braza | 2026-02-18 14:59:27+00:00
As a Brazilian, the whole improbable (and beautiful) history of Portugal raised by the "Navegações" and how badly they bottled the whole imperium (especially after the Brazilian independence, but one can argue that João VI opened the ports) and the sheer amount of lack of vision in not investing in production is something that will always amaze me.

One can say that it was one of the longest imperiums in history (ending in 1999 with Macau???), but every time that I spend some time in Portuguese cities, I feel just bad. The good thing is that Brazil will carry its tradition for posterity nevertheless.
by DrewADesign | 2026-02-18 14:59:38+00:00
> Deployment, version management, debugging things like compilation errors or package version mismatch, etc.

I was using tests as an example. The tasks you refer to, as well as tests, are big time sucks in professional environments, or for established ongoing projects. I really, really, really doubt debugging, ops, and housekeeping/administrivia keep people from finishing weekend “theoretically should be simple!” projects.
by WarmWash | 2026-02-18 14:59:47+00:00
I think a better take is from the MIT study last year, the one that found almost all AI pilots failed.

In that study they found that pretty much everyone was using AI all the time, but they were just using their personal accounts rather than the company provided tools (hence the failures)

In light of this, I'd say there is a very good chance that people are offloading their work on AI, and then taking that saved time for themselves i.e. "I can finish the job report in 30 minutes rather than 3 hours now, so by 9:30 I'm done with work until after lunch."

The end result of this will either be layoffs to consolidate work or blocking of non-company monitored AI ensuring they can locate those now empty time slots.
by simonw | 2026-02-18 14:59:50+00:00
Being online few hundred lines of code is a pro, not a con.

It does use transactions in the form of savepoints which means they can be nested: https://github.com/simonw/sqlite-history-json/blob/53e66b279...

Tested here: https://github.com/simonw/sqlite-history-json/blob/53e66b279...
by andreabergonzi | 2026-02-18 15:00:12+00:00
Thanks for the Tennenhouse link, definitely ahead of his time on Proactive Computing. You're right that 'Post-Interface' is a rhetorical hook. We can't eliminate the technical interface (APIs/protocols). My argument is about eliminating the cognitive interface for the end user. Right now, even our smartest agents are still reactive because they wait for a prompt. I see generative UI as the bridge to true proactivity: instead of a static dashboard waiting for input, the system constructs a temporary UI only when it senses intent via context/API. The goal isn't no interface, but zero friction interface where the UI is a generated byproduct of the agent's action, not a prerequisite for it.
by kimixa | 2026-02-18 15:00:14+00:00
AMD's implementation very much doesn't have that issue - it throttles slightly, maybe, but it's still a net benefit. The problem with Intel's implementation is that the throttling was immediate - and took noticeable time to then settle and actually start processing again - from any avx512 instruction, so the "occasional" avx512 instruction (in autovectorized code, or something like the occasional optimized memcpy or similar) was a net negative in performance. This meant that it only benefitted large chunks of avx512-heavy code, so this switching penalty was overcome.

But there's plenty in avx512 the really helps real algorithms outside the 512-wide registers - I think it would be perceived very differently if it was initially the new instructions on the same 256-wide registers ALA avx10 in the first place, then extended to 512 as the transistor/power budgets allowed. AVX512 was just tying too many things together too early than "incremental extensions".
by jsheard | 2026-02-18 15:00:40+00:00
ARMs Neoverse IP does support SVE, so it's at least already relevant in cloud applications. Apparently AWS Graviton3 has 256bit vectors, but Graviton4 regressed back to 128bit vectors for some reason?

https://ashvardanian.com/posts/aws-graviton-checksums-on-neo...
by appreciatorBus | 2026-02-18 15:01:13+00:00
Conversely, what if we lower the generally acceptable threshold of light intensity from neighbours to zero?

At some level, we all have to get along, and we all have to accept that our neighbours actions are going to affect us in myriad small ways.

I’m all for critical examination and regulation of externalities inflicted on third parties as a result of private activity, but if we start counting photons, I worry that we’ve lost the plot and are simply caving to people who don’t actually want to live in society with others.

I have no idea what the truth of the matter in this case is, but reading the appeal, the guy just sounds like a crank who got a new neighbours who live differently than he does, and he doesn’t like it.
by urmane | 2026-02-18 15:01:32+00:00
I see TFA mentions Solarized. I've been using Solarized light for longer than I can remember, even on Windows where I can (eg VSCode), and it goes a long way to making my eyes happy. I share the irritation with dark blue on black and can't stand dark mode (maybe I'm now old and no longer 31337 ... alas ...)

For my ncurses brothers, saw this but have not used yet:
https://github.com/dankamongmen/notcurses

For my plan9 brothers: one day we will have a new acme, written in common lisp and displaying all the correct colors, and lo it will be glorious.
by kakacik | 2026-02-18 15:01:47+00:00
Well, its maintained by humans to start with, peer reviewed by humans. They fuck up from time to time in extremely limited scope, depending on how much given company is willing to invest into getting quality work, but nothing like this. Humans are clearly not the weak link to be automated away, in contrary.

I work in one of the special legal jurisdictions, such fubar would normally mean banning such product from company for good. Its micro$oft so unfortunately not possible yet, but oh boy are they digging their grave with such public incompetence, with horrible handling of the situation on top of that. For many companies, this is top priority right behind assuring enough cash flow, not some marginal regulatory topic. Dumb greedy amateurs.
by docmars | 2026-02-18 15:01:55+00:00
This is correct, but part of the issue is that it significantly increases token usage costs. Some companies are doing:

- PRD and spec fulfillment review
- code review
- corrections from results
- security review
- those corrections
- addl. test coverage and tidying
- addl. type checks and tidying
- addl. lint checks and tidying
- maybe more I haven't listed

And these are run after each commit, so you can only imagine the costs per engineer doing this 10, 20, 50+ times per day depending on how much work they're knocking out.
by rvz | 2026-02-18 15:02:03+00:00
Translation: Even cheaper labor.

The great off-shoring is also one of the true definitions of AGI as labor, knowledge work and prices eventually all goes to zero.

This is how they think and just put it this way:

Why pay for 8 qualified staff software engineers at $400k+ (with expensive mortgages) in the US each when you can lay all of them off, out-source just 1 job to a junior grad + AI and open offices in India and announce "deals" at the AI summit?

Surely that is going to work for AI. All that outsourcing worked for Boeing really well. [0][1][2][3][4] /s

So after reading that even aerospace software is already out-sourced to unqualified individuals, would you ever board a Boeing?

[0] https://www.forbes.com/sites/stevebanker/2024/02/12/boeing-i...

[1] https://www.industryweek.com/supply-chain/article/22027840/b...

[2] https://www.lemonde.fr/en/economy/article/2025/06/12/boeing-...

[3] https://www.businessinsider.com/boeing-outsourced-737-max-re...

[4] https://www.computerworld.com/article/2513787/boeing-and-the...
by KallDrexx | 2026-02-18 15:02:13+00:00
This study came up on my feed but I'm not seeing much chatter on it. I'm interested in some perspectives from people who are better at reading if studies are quality or not.

> Abstract
>
> AI assistants, like GitHub Copilot and Cursor, are transforming software engineering. While several studies highlight productivity improvements, their impact on maintainability requires further investigation. [Objective] This study investigates whether co-development with AI assistants affects software maintainability, specifically how easily other developers can evolve the resulting source code. [Method] We conducted a two-phase controlled experiment involving 151 participants, 95% of whom were professional developers. In Phase 1, participants added a new feature to a Java web application, with or without AI assistance. In Phase 2, a randomized controlled trial, new participants evolved these solutions without AI assistance. [Results] Phase 2 revealed no significant differences in subsequent evolution with respect to completion time or code quality. Bayesian analysis suggests that any speed or quality improvements from AI use were at most small and highly uncertain. Observational results from Phase 1 corroborate prior research: using an AI assistant yielded a 30.7% median reduction in completion time, and habitual AI users showed an estimated 55.9% speedup. [Conclusions] Overall, we did not detect systematic maintainability advantages or disadvantages when other developers evolved code co-developed with AI assistants. Within the scope of our tasks and measures, we observed no consistent warning signs of degraded code-level maintainability. Future work should examine risks such as code bloat from excessive code generation and cognitive debt as developers offload more mental effort to assistants.
by giancarlostoro | 2026-02-18 15:02:15+00:00
I know Claude will read through code from Go libraries it has imported to ensure it is doing things correctly, but I do have to wonder for other languages and those small libraries, if we'll start seeing things like AGENT_README.md a file that describes the project, then describes what functionality is where in the code, and if necessary drills on a source file by source file basis (unless it's too massive - context limits are still limits). In any regard, I could see that becoming more common. Especially if you link to said file from the README.md for the model to go to. ;)
by yurishimo | 2026-02-18 15:02:29+00:00
IMO Bun and Vite are best suited for slightly different things. Not to say that there isn't a lot of overlap, but if you don't need many of the features Bun provides, it can be a bit overkill.

Personally, I write a lot of Vue, so using a "first party" environment has a lot of advantages for me. Perhaps if you are a React developer, the swap might be even more straightforward.

I also think it's important to take into consideration the other two packages mentioned in this post (oxlint & oxfmt) because they are first class citizens in Vite (and soon to be Vite+). Bun might be a _technically_ faster dev server, but if your other tools are still slow, that might be a moot point.

Also, Typescript also "just works" in Vite as well. I have a project on work that is using `.ts` files without even an `tsconfig` file in the project.

https://vite.dev/guide/features#typescript
by llm_nerd | 2026-02-18 15:02:44+00:00
Ignoring that most, like Trump, just outright admitted it, simple logic dictates that reality.

When something has overwhelming scientific and medical evidence in its favour, and the alternative are a bunch of high school dropout conspiracy nuts cheered on by simpletons like Joe Rogan, odds overwhelmingly lean towards the connected and rich going in one direction. Like, this is so blatantly obvious that I find your scepticism laughable.
by jsheard | 2026-02-18 15:03:05+00:00
Throttling was mainly an issue with AVX512, which is twice the width of AVX2, and only really on the early Skylake (2015) implementation. From your own source Ice Lake (2019) barely flinches and Rocket Lake (2021) doesn't proactively downclock at all. AMDs implementation came later but was solid right out of the gate.
by jamiemallers | 2026-02-18 15:03:07+00:00
The dynamic system map (.md file) approach is the most interesting part of this to me. The hardest problem in automated alert triage isn't the deduplication or even the RCA -- it's that the agent doesn't know what "normal" looks like for your system.

I've seen teams try to solve this by feeding every alert directly into an LLM (like nojs describes above), and the failure mode is predictable: the model treats each alert as an isolated incident because it has no topology awareness. It doesn't know that Service A calling Service B with 500ms latency is fine on Tuesday mornings because of the batch job, but a P1 on Wednesday afternoons.

The real question is how you keep that system map accurate as architecture evolves. In my experience, the map drifts within weeks unless it's generated from runtime data (traces, dependency graphs from actual traffic) rather than maintained manually. Static architecture docs are lies within a quarter.

Also curious about the severity scoring -- are you using user impact signals (error rates on user-facing endpoints, session replay data) or purely technical signals? The gap between "this looks bad in logs" and "users are actually affected" is where most alert fatigue comes from. A 500 error on an internal health check endpoint generates the same Sentry noise as a 500 on the checkout flow, but they're not remotely the same priority.
by gaoshan | 2026-02-18 15:03:50+00:00
This smells of "I like to solve puzzles and fiddle with things" and reminds of hours spent satisfyingly tweaking my very specific and custom setups for various things technical.

I, too, like to fiddle with optimizations and tool configuration puzzles but I need to get things done and get them done now. It doesn't seem fast, it seems cumbersome and inconsistent.
by jamiemallers | 2026-02-18 15:03:52+00:00
This is the underappreciated angle. Shipping faster creates a downstream cost that nobody's accounting for: more code in production means more surface area to monitor, more potential failure modes, and more on-call burden.

I've watched teams go from deploying weekly to deploying 5x/day after adopting AI coding tools. Their velocity metrics looked incredible. Their incident rate also tripled. Not because the code was worse per se, but because they were changing more things faster than their observability and testing could keep up with.

The bottleneck was never typing speed. It was always understanding -- understanding the system, understanding the user, understanding what "correct" even means in a given context. AI makes the typing-equivalent part nearly free, which just exposes that the hard parts were always the hard parts.

The teams I've seen get the most out of AI coding tools are the ones that used the time savings to invest more in understanding, not to ship more features. More time with users, more time reading production logs, more time thinking about edge cases. The ones that just shipped faster ended up spending the saved time on incident response instead.
by gus_massa | 2026-02-18 15:03:58+00:00
Bugs? Try removing bugs from a pile of hay.

In particular, here in Argentina in some areas this is common https://en.wikipedia.org/wiki/Chagas_disease One of the problems with the homes of poor people is that the walls are not "nice" and have little holes where the bugs can hide.

(In my home, I notice that white walls make mosquitoes easier to spot and kill with an electrical fly swatter.)

(I just searched 8sleep. It looks too fancy, expensive and probably the improvement is minimal.)
by mystraline | 2026-02-18 15:04:10+00:00
Absolutely, yes. When China's civil war with Chaing Kai-Shek happened, the communists won.

After that, landlords, business owners, and industrial owners were presented with an ultimaturm, of which many took. And that was to return to being a worker, or be jailed.

Given how capitalists amass wealth and options to evade all governments, this does seem like a valid solution.

A modern viewing is after Jack Ma (CEO of Alibaba) publicly criticized the monetary policy of China. He lost most of his standing, and the attempt of an IPO for his payments company. Note that he lives and is still CEO, just not as a Influential power in China.
by riskable | 2026-02-18 15:04:24+00:00
> Do you use an agent harness to have it review code for you before you do?

Right now you need to be Uncle Moneybags to do this in your personal life.

If you're lucky, your employer is footing the bill but otherwise... Ugh. It's like converting your app running perfectly fine on a cheap VPS to AWS Lambda. In theory, it's fine but in reality the next bill you get could make you faint.
by Ithildin | 2026-02-18 15:04:29+00:00
If I do something faster by pairing with AI, why should my employer reap the benefit? Why would I pass the savings on to my employer?

Could it be that employers are not seeing the difference because most employees are doing something else with the time they've saved by using AI?

There's been massive wage stagnation, benefits are crap, they play games with PTO. Most people I talk to who use AI as a part of their workflow are taking advantage of something nice that has come their way for a change.
by intrasight | 2026-02-18 15:04:41+00:00
True about semantics. "Capturing", "Creating", and "Value" are all rather fuzzy.

But false about my meaning, which was precisely the opposite of "a euphemistic way to describe pushing producer surplus towards 100% and consumer surplus to 0%"

My original comment "They capture exactly the value they create" was my (failed) attempt to restate the basic premise of capitalism, that profits tend towards zero, using the words at play in this discussion.
by austin-cheney | 2026-02-18 15:04:43+00:00
Any method for front end tooling is potentially the fastest. It always comes to what you measure and how you measure it. If you don't have any measures at all then your favorite method is always the fastest no matter what, because you live in a world without evidence.

Even after consideration of measurements radical performance improvements are most typically the result of the code's organization and techniques employed than the language its written in. But, of course, that cannot be validated without evidence from comparison of measurements.

The tragic part of all this is that everybody already knows this, but most front end developers do not measure things and may become hostile when measurements do occur that contradict their favorite techniques.
by ssgodderidge | 2026-02-18 15:04:52+00:00
I agree that it isn't always a good thing. The assumption is that writing code, at some level, is one of the bottlenecks to delivery. If you "widen" the bottleneck by removing the time it takes to generate the code, your new throughput is going to create stress on other delivery areas: gathering feedback, testing, validation, approval processes, etc. I think the most effective results would come from a holistic approach to removing other bottlenecks in addition to reducing time required for producing code