MurphyA/hacker-news huggingface dataset:
by scarmig | 2026-03-14 21:49:55+00:00
Inflation isn't inevitable, especially in the long term. But of course it depends on implementation.

The goal of a UBI is to make sure people get their essentials to live. Right now, people get those essentials, one way or another (otherwise, they'd be dead; and to the extent people starve to death in the developed world, it's issues of distribution, not production or money). This makes the UBI an accounting trick: there's no actual goods not being produced that need to be produced, and it is just shifting costs from welfare, charity, family and friends, etc to the UBI program. This is not inflationary and frees up human effort to focus on higher needs than scraping together a basket of things merely to live.

A lot of the time, though, people also want some non-essential but still pretty important things covered, which is a bit trickier. In this case, there is the potential for more money to be chasing a fixed supply of goods. This will drive inflation in the short term. However, in the longer term, capital will be redeployed to capture that increased demand (while being deployed away from the desires of those taxed to fund the UBI).

This all assumes that the UBI is revenue neutral; if not, yeah, we will get a lot of inflation.
by pedalpete | 2026-03-14 21:50:39+00:00
Are these sorts of general advice on how to do X even valuable today when you can put the details of your start-up into AI and get a more customized and moderately more thoughtful actions based on what your start-up does, who your customers are, etc?

Who's still going through these kinds of docs?

I know micro.so (I'm not affiliated with them) have documented how to build agentic B2B sales AI that you can download (if you give them your email address).
https://www.micro.so/guides/sales
by h16zed | 2026-03-14 21:50:53+00:00
I built an autonomous trading system where the AI makes every decision — what to trade, when, position sizing, everything. No human overrides. Deployed real capital and it returned +57.9% ($247 to $391) across 50 trades. I want to talk about what actually happened, not just the headline.

The system tested 131 distinct strategy hypotheses. I formally killed 12 of them. Two more I rejected after they hit their evidence-gathering deadline with exactly zero evidence. That part matters as much as the wins. Most trading projects show you the cherry-picked trades. This one documents the dead strategies with equal rigor because that's what teaches you how to build actual edges.

Here's the honest assessment: the 57.9% came from a single concentrated session on March 11 between 3-8 AM ET. The win rate across that period was 51.4%, profit factor 1.01. I haven't replicated it yet. Annualizing a three-hour return would be ridiculous. What I have proven is that autonomous execution works mechanically and the narrow edge I found is real enough to trade and test further.

The value isn't the P&L number. It's the engineering: a fully working framework for agent-driven quantitative trading with kill rules, audit trails, probability calibration, and complete failure documentation. Everything is in the repo. 1,397 tests pass.

I also wrote up the complete methodology as a 61-page guide: https://bradleyhaven.gumroad.com/l/agentic-trading-blueprint

Looking for technical feedback and collaborators.
by smartbit | 2026-03-14 21:51:05+00:00
India and China are huge countries with very small percentage river deltas. Not comparable by any means. Bangladesh in a very young country that inherited it’s culture from India. I’m not an anthropologist, but sorry, I don’t agree there is any likeness with these countries.

If you have an other theory about the Dutch culture and why it is so different from it’s neighbors, I happy to hear.
by IshKebab | 2026-03-14 21:51:08+00:00
> it's fast as fuck to code

In my experience it's no faster than other better languages like Go, Rust or Kotlin.

> And for the 1% that aren't, you have 50 different flavors of making it faster.

Only for numerical code. You can't use something like Numpy to make Django or Mercurial faster.

And even when you could feasibly do the thing that everyone says to do - move part of your code to a faster language - the FFI is so painful (it always is) that you are much better just doing everything in that faster language from the start.

All of the effort you have to go through to make Python not slow is far less work than just "don't use Python". You can write Rust without thinking about performance and it will automatically be 20-200x faster than Python.

I actually did rewrite a Python project 1:1 in Rust once and it was approximately 50x faster. I put no effort into optimising the Rust code.
by genthree | 2026-03-14 21:51:49+00:00
“Climate change safe” for the rich:

- Hard to reach by land (not vulnerable to migration waves)

- Not so small there will be incredible deprivation if sea trade volume plunges (this rules out the vast majority of island nations)

- Not badly overpopulated

- Correct latitude (not too close to the equator)

- Stable liberal democracy (so they probably won’t take all your stuff)

- Unlikely target for outright conquest in great-powers games or expansion.

Bonus points:

- Interesting, varied natural environments.

They are indeed thinking about this stuff. It’s why so many are buying New Zealand citizenship and buying land there (and sometimes building their survival bunkers there too). It checks every single box, and basically nowhere else does.
by AnthonyMouse | 2026-03-14 21:52:02+00:00
A UBI is a method of achieving the same effect as progressive taxation without the complexity and perverse incentives of tracking everyone's income and applying different marginal rates.

Suppose you have a tax system with progressive tax brackets and then a needs-based welfare system with benefits phase outs. It turns out, those two things (progressive rate structure and benefits phase outs) basically cancel each other out -- lower income people are supposed to pay lower marginal tax rates but if you're paying a 10% marginal tax rate and then have a 25% benefits phase out rate, that's the same as paying a 35% marginal tax rate. Worse, the benefits phase outs often overlap, with the result that lower income people are often paying higher marginal tax rates than wealthy people, and there are some cases when their marginal rates even exceed 100% of marginal income.

So you have two unnecessarily complicated systems that mostly exist to cancel each other out, and to the extent that they don't they're doing something you don't actually want (excessively high marginal rates on poor people). It's better to just get rid of both -- no phase outs is the "universal" part of the UBI, and then you combine that with a uniform marginal tax rate for everyone.
by jlarocco | 2026-03-14 21:52:17+00:00
I don't think that conclusion really follows because I don't think the ban works that way.

There's a big difference between ChatGPT writing a prescription and a doctor double checking his diagnosis using some kind of Claude code for medicine. ChatGPT writing prescriptions and giving medical device directly to people should absolutely be prohibited for now, but the second approach should be encouraged.
by tastyface | 2026-03-14 21:53:17+00:00
Not that Trump or his administration have two brain cells to rub together, but who would they even nuke? Teheran? Millions of lives lost, any Iranian support for the war evaporates, and US instantly becomes a pariah state. (Plus, leadership is likely hiding far away from the capital at this point.) The coastline? The Strait of Hormuz becomes an impassible fallout zone and IRGC attacks are decentralized anyway.
by Izkata | 2026-03-14 21:53:41+00:00
> And at that point you could have just done those regulations without UBI. Hmm.

Rent control is already a thing, and typically good short term but bad long term: renters don't move out because they can't get such low rent elsewhere, and landlords can't afford repairs so things are left broken. It's a great way to create slums over a few generations.
by wek | 2026-03-14 21:53:54+00:00
Thank you for sharing this. I found some good articles in what you shared. The long lists of places to post are not that helpful. I've poured through 100 of them in the past and only the top 20 make a difference, you might want to update the list to prioritize. I tend to point Claude Code or Codex at these lists, have them evaluate the scores of the sites and give me a priority list.
by samrus | 2026-03-14 21:54:00+00:00
When the roman republic collapsed, they were still at their upwards inflection point. Ceasar was still on a roll. They hadnt peaked yet. This feels more like when the empire was in the early stages of coming down from its peak.

I think the roman republic to empire transition doesnt have much to do with the trajectory of rome at all. Their institutions were still strong. With america, her institutional knowledge is being stripped apart. Thats hard to pull up from
by ashleyn | 2026-03-14 21:54:17+00:00
It's probably a mix of AI productivity boost and market cycle. There is some substance to AI job loss, but I believe jevons paradox will eventually catch up to transformer-based LLM capabilities.

I'm the last remaining frontend developer after multiple rounds of layoffs. With claude code I'm able to do 2x-3x the work I was able to do before it existed. It's hard for me to rationally argue we need more frontend developers.
by llm_nerd | 2026-03-14 21:54:23+00:00
That's precisely what I do, with subscriptions to all of them. Gemini almost seems unlimited...like I never hit limits with it. Don't even know how to check my usage for the subscription plans on that.

But increasingly I'm using Claude for basically all real coding. I ask Gemini and Codex questions, but I'm honestly in awe at Opus' ridiculous capabilities.
by hrmtst93837 | 2026-03-14 21:54:33+00:00
If you're patching hot paths with C and praying the interface layer doesn't explode, you can spend almost as much time chasing ABI boundary bugs as you save on perf. Type hints in Python are still docs for humans and maybe your LSP. Julia does address the two language problem in theory, but getting your whole stack and your deps to exist there is its own wierd pain, and people underplay how much library inertia matters once you leave numerics.
by Spivak | 2026-03-14 21:54:52+00:00
Hard disagree about attributes, each tag should be a complete object and attributes describe the object.

<myobject foo="bar"/>
// means roughly
new MyObject(foo="bar")

But objects can also be containers and that's what nesting is for. There shouldn't ever be two dimensions in the way you're describing. The pattern of

<myobject>
<foo>bar</foo>
</myobject>

is the root of most XML evil. Now you have to know if myobject is a container or a franken-object with a strict sub-schema in order to parse it. The biggest win of JSON is that .loads/.dump make it really obvious that it's for serializing complete objects where a lot of tooling surrounding XML makes you poke at the document tree.
by AStrangeMorrow | 2026-03-14 21:54:55+00:00
We do lose something, but really I still see it as an extension of autocomplete.

I had some pieces of code I wrote I was quite proud of: well documented, clear code yet clever designs and algorithm.

But really what always mattered most to me was designing the solution. Then the coding part, even though I take some pride in the code I write, was most a mean to an end. Especially once I start having to add things like data validation and API layers, plotting analysis results and so many other things that are time consuming but easy and imho not very rewarding
by fuxcodestudio | 2026-03-14 21:55:45+00:00
I working on an app I built called Checkpoint. It’s an open source backup system for developers that protects everything Git ignores. .env files, databases, credentials, local configs.

I started it after an AI coding agent destroyed my SQLite database mid-session for the third time. Git doesn't back up databases, and it shouldn't. But nothing else was doing it either.

It runs silently in the background and watches your project, detects changes, backs up to encrypted cloud storage (Dropbox, Google Drive, OneDrive, iCloud). Supports SQLite, PostgreSQL, MySQL, MongoDB. Has a native macOS menu bar dashboard.

Free and open source. v2.7.0

GitHub: https://github.com/fluxcodestudio/Checkpoint
Site: https://checkpoint.fluxcode.studio
by formerly_proven | 2026-03-14 21:56:12+00:00
There's a pattern where people create AI-specific infrastructure for coding agents which is essentially instantly obsolete because it's pointless. Stuff like most MCPs (instead of just using a CLI), agent-specific files (CLAUDE.md, AGENTS.MD, github-instructions.NET etc.) etc.

> You should have a good, concise introduction to the codebase that allows anyone to write and test a simple patch in under 15 minutes.

Yeah, that's the CONTRIBUTING file.
by randerson | 2026-03-14 21:56:41+00:00
RAM is up in price due to supply shortages due to AI. During COVID much of the early inflation was caused by supply shortages due to factories shutting down. Then house prices shot up in suburbs as people moved out of cities so the demand went up there. None of that is due to monetary policy.

Saying that the total money supply is the cause of inflation is a very simplified view. There are currently trillions of dollars in M2 doing nothing except sitting in wealthy people's bank accounts and investments as generational wealth. That does not raise the prices of anything until it is being spent.
by thesz | 2026-03-14 21:56:50+00:00
BWT is a prediction by partial match (PPM) in disguise.

Consider "bananarama":

"abananaram"
"amabananar"
"ananaramab"
"anaramaban"
"aramabanan"
"bananarama"
"mabananara"
"nanaramaba"
"naramabana"
"ramabanana"

The last symbols on each line get context from first symbols of the same line. It is so due to rotation.

But, due to sorting, contexts are not contiguous for the (last) character predicted and long dependencies are broken. Because of broken long dependencies, it is why MTF, which implicitly transforms direct symbols statistics into something like Zipfian [1] statistics, does encode BWT's output well.

[1] https://en.wikipedia.org/wiki/Zipf%27s_law

Given that, author may find PPM*-based compressors to be more compression-wise performant. Large Text Compression Benchmark [2] tells us exactly that: some "durilka-bububu" compressor that uses PPM fares better than BWT, almost by third.
by Neywiny | 2026-03-14 21:57:00+00:00
Good to recognize stupid questions do exist but so does anxiety around asking necessary questions. The engineer I'm mentoring said they'd ask lot of stupid questions. But we're working through them. A lot of them were things I wondered too, like "this current reading doesn't make sense because the upstream supply is saying it's taking less current" but it was a nonlinear buck regulator. I offered to explain more but they just sat with it a minute, I offered again, but they said they were ok. My viewpoint is to give just a hint and then offer more so they can still go through the thought process on their own, which is really what I'm trying to teach.
by 3rodents | 2026-03-14 21:57:24+00:00
I suspect it’s much more about understanding user behavior, i.e: given more allowance off-peak, do users change when they use Claude? And from there, that will inform how plans are designed long term. If they discover that offering higher off-peak limits meaningfully changes how/when users interact with the service, they can use discounted off-peak plans to flatten usage. I would be very surprised if this promotion had anything to do with encouraging people to upgrade.
by stefan_ | 2026-03-14 21:58:11+00:00
Good reminder that the Raspberry Pis only have good software support if you stick to whatever the foundation is releasing. Because that same foundation has stayed obsessed with their weird custom ways of doing things, instead of furthering efforts like UEFI on ARM. Some of it is insultingly stupid - like for revD of the 5, you better now update the magic boot partition of your RPi with the device tree overlay for revD, because it will use the old device tree, but also expect the overlay to be there so it can actually work. To say the least, that is never what overlays were supposed to be for.
by mmooss | 2026-03-14 21:58:15+00:00
While I mostly agree, freedom as a universal right does exist; not everyone can exercise it, but that doesn't make it less of a right.

And it is 'natural' in the sense that it is valued ~~ universally. I can't establish objectively that it is valued everywhere, of course; I can establish that people en masse have valued it and fought for it all over the world, from Europe to South Asia to SE Asia to East Asia; in Africa, to all of the Americas.
by vigil-agency | 2026-03-14 21:59:02+00:00
Vigil is an open-source security operations platform. The v1.1 release adds an embedded security knowledge engine with 356 pre-built entries that answer in <1ms without calling an LLM.

What's in the brain:
- 85 MITRE ATT&CK techniques (all 14 tactics, real CVEs, detection/mitigation)
- 89 port-to-service mappings with known vulns (21 through 50000)
- 48 NIST controls (CSF 2.0 + 800-53 Rev 5)
- 40 CompTIA Security+ domains
- 30 cross-framework compliance maps (PCI DSS 4.0, HIPAA, SOC 2, ISO 27001, CIS v8)
- 27 remediation templates with language-specific fixes
- 17 CVE patterns, 10 OWASP Top 10 Web, 10 OWASP LLM Top 10

Ask "T1059" or "port 445" — instant structured answer with detections, mitigations, CWE mappings. No LLM round-trip.

When reasoning IS needed, the brain enriches the prompt with your security profile, section context, recalled memories, and relevant KB hits before sending to your AI provider.

Also new in v1.1:
- DAG workflow automation (chain agents, conditions, HTTP calls into security pipelines)
- 28 AI security agents with editor (autonomous pentester, forensics, red team, compliance)
- Smart provider routing (Ollama local, Claude API, Codex — per-agent selection, fallback chains)
- Kali Linux bridge container with 11 tools (nmap, nuclei, nikto, sqlmap, etc.)
- Docker Compose stack: Vigil + PostgreSQL + Ollama + Kali bridge

Runs air-gapped with Ollama. Zero data leaves your machine. Express.js + vanilla JS, 6 npm dependencies.

GitHub: https://github.com/vigil-agency/vigil
CHANGELOG: https://github.com/vigil-agency/vigil/blob/main/CHANGELOG.md
by Doohickey-d | 2026-03-14 21:59:03+00:00
You can do this all in fly.io, no cloudflare container needed.

The whole selling point of fly is lightweight and fast VMs that can be "off" when not needed and start on-request. For this, I would:

Set up a "peformance" instance, with auto start on, and auto-restart-on-exit _off_, which runs a simple web service which accepts an incoming request, does the processing and upload, and then exits. All you need is the fly config, dockerfile, and service code (e.g. python). A simple webapp like that which only serves to ffmpeg something, can start very fast (ms). Something which needs to load e.g. a bigger model such as whisper can also still work, but will be a bit slower.

(In my use case: app where people upload audio, to have it transcribed with whisper. I would send a ping from the frontend to the "whisper" service even before the file finished uploading, saying "hey wake up, there's audio coming soon", and it was started by the time the audio was actually available. Worked great.)
by rvz | 2026-03-14 21:59:07+00:00
Great article, and what I would expect from someone inspecting the hype and not jumping head first, just because influencers (paid or unpaid) are screaming for engagement just because a large X account posted their opinions.

This is one of the first posts that I've see that cuts through the hype against both MCPs and CLIs with nuance findings.

There were times where it didn't make sense for using MCPs (such as connecting it to a database) and CLIs don't make sense at all for suddenly generating them for everything. It just seems like the use-case was a solution in search of a problem on top of a bad standard.

But no-one could answer "who" was the customer of each of these, which is why the hype was unjustified.
by simianwords | 2026-03-14 21:59:11+00:00
> The part where you are providing 100 tools instead of a few really flexible tools

I'm not sure how that solves the issue. The shape of each individual tool will be different enough that you will need different schema - something you will be passing each time in MCP and something you can avoid in CLI. Also, CLI's can also be flexible.

> The part where you think your agent is going to know how to use 100 CLI tools that are not already in its training dataset without using extra turns walking the help content to dump out command names and schemas

By CLI's we mean SKILLS.md so it won't require this hop.

> The part where, without a schema defining the inputs, the LLM wastes iterations trying to correct the input format.

What do we lose by one iteration? We lose a lot by passing all the tool shapes on each turn.

> The part where, not having the full picture of the tools, your odds of it picking the same tools or the right tools is completely gambling that it outputs the right keywords to trigger the tool to be used.

we will use skills

> The part where you forgot to mention that for your agent to know that your 100 CLI tools exist, you had to either provide it in context directly, provide it in context in a README.md, or have it output the directory listing and send that off to the LLM to evaluate before picking the tool and then possibly expanding the man pages for several tools and sub commands using several turns.

skills
by nerdsniper | 2026-03-14 21:59:22+00:00
> which I don’t know enough to quantify the effects of

At near-atmospheric pressure and typical ambient temperatures, the ideal gas equation (PV=nRT) works very well and indicates that a 3% overpressure would make gases 3% more dense (linear direct proportionality). At a higher threshold of pressures/pressures, you'd want to switch your equation of state from ideal gas law to something else.
by philipp-gayret | 2026-03-14 21:59:26+00:00
One of the better ways to maintain docs I've seen is with tests that let you describe what the inputs and outputs were for an API, and from it the framework generated your docs. (This was Spring Rest Docs) We included aggressive checks to have every input and output tested, it meant we had one truth about what fields existed: The code was aligned with the tests, and the tests were also the docs. I really liked this idea; Just one record of the truth. Granted it doesn't capture the intent of the code perfectly, but it solves a lot of the garbage collection.
by adsharma | 2026-03-14 22:00:01+00:00
It can be used in many forms, while true is one of them.

I don't have a whole lot of experience hand writing v-lang. Mostly machine generated from static python.

But I find it convenient for what it does. Golang that is less verbose, single binary for distribution and fewer tokens if you're using an agent.

GitHub.com/LadybugDB/ladybug-vlang has a CLI I recently wrote with an agent for a database I maintain.

Static python with design by contract can be a stronger specification than natural language. @antirez was discussing this on his social media today.
by hackyhacky | 2026-03-14 22:00:58+00:00
> Native Americans had relatively benign relationships with the settlers, while the latter were weak

Translation: Native Americans were nice to the European settlers, until the European settlers were in a position to murder and expel in the Native Americans. The genocide against the Native Americans happened both before and after the founding of the United States, which casts serious doubt on a claim that the US has a "moral" mission.

> Slavery was not supported in half of the initial US of A,

Not sure where this math came from. Slavery was legal in all 13 colonies at the time of the revolutionary war. It wasn't until later, and in some cases much later, that the so-called "free states" actually freed slaves.