MurphyA/hacker-news huggingface dataset:
by Sayrus | 2026-03-14 15:22:14+00:00
Emergency situations are defined by two situations: severe accidents and manual press of the button. Article 6 covers the data being sent, Article 5 covers the manufacturer's obligations. Your audio during the accident and your last three locations may leak, but the eCall system is not designed for a permanent phone-home system. If I remember correctly, you can't even use the eCall SIM for tracking as that'd encourage people to disable safety features.

All the things you are talking about, permanent phone-home, tracking of location, audio and video, driving habits, are tracked, sent and resold. That's what smart cars do. But it is not done through the eCall system. See it from the company perspective: why would they risk penalties for non-compliance when they can gather and resell all personal data with no risks using their own system instead of a safety one?
by perfect-blue | 2026-03-14 15:22:37+00:00
My thoughts exactly. I reads a lot like they are trying to minimize the state's power to regulate AI. I'm not sure that's such a good thing. Regulation is one of the only ways that we can manage the ``bads'' that come with any new technology. In the US, we've never been very good at regulating new technologies before industry stakeholders entrench themselves in the lobbying circuit.
by Jonverrier | 2026-03-14 15:22:39+00:00
A few months ago I shared C4-Agent, an MCP server that generates C4-style docs and Mermaid diagrams from your codebase while you work in the IDE. It’s flexible and interactive, but depends on MCP, and the Agents, even now, seem to drift off on large code bases.

C4-Auto is the other half: a CLI-only tool that does the same kind of thing in a more boring, repeatable way. No MCP, no Agent integration-just a command you run (locally or in CI) that:

- Walks your TypeScript/TSX tree (skips node_modules, dist, .git)
- Uses an LLM to add or refresh a short module-level header comment in each file (with a date so you only regenerate when stale)
- Builds C4 Component and Context diagrams in Mermaid from those headers and a Component and a Context diagram per directory

You pick a time window (--one-week, --two-weeks, --one-month) so you’re not re-running the LLM on everything every time. Same “just enough” C4 idea: docs generated from the code so they don’t rot.

Repo and more detail: https://github.com/jonverrier/C4-Auto
MIT License

So: C4-Agent = MCP, interactive, “fun”. C4-Auto = CLI, scriptable, more reliable. Happy to answer questions or take feedback.
by well_ackshually | 2026-03-14 15:22:47+00:00
no, I truly do not want to read IHeartHitler88's opinion on jews, or donttreadonme09's bright opinions about how the economy would be better if we listened to Ayn Rand. I'll be very happy when they're out of my sight. If I want to have a miserable day, sure, I'll turn it off.

Fact of the matter is, most posts on the internet are already dogshit. Now they're also populated by AI, but the point stands. Most of what you will say online is at best useless.
by ramoz | 2026-03-14 15:23:24+00:00
Thanks for the transparency. Sorry for the noise.

I think I'd be okay with a smaller, more narrative-detailed plan - not so much about verbosity, more about me understanding what is about to happen & why. There hadn't been much discourse once planning mode entered (ie QA). It would jump into its own planning and idle until I saw only a set projected code changes.
by SoftTalker | 2026-03-14 15:23:46+00:00
How does Norway handle self-employment? There are a lot of people with self-employment income in the USA, including a lot of tradespeople, freelancers, and contractors. The IRS knows nothing about this until you tell them.

In the simple case of working for one employer all year, no complicated investments or other income, standard deductions, your tax filing in the USA is equally simple and you can complete it in 15 minutes on paper for the cost of a postage stamp.

There are many reasons the US tax situation is complicated. Among them are that it's used to drive behavior (tax credits or deductions for various things), there are people invested in it being complicated (tax prep industry), but a big one is that if your situation is complicated, the IRS simply does not have the information it needs until you report it.
by lokar | 2026-03-14 15:24:05+00:00
Context matters.

You communicate differently in person vs with async text.

If you don’t have your thoughts together, if you see a problem but are not sure of the fix, just say that.

Make it clear why you are communicating with me, do you have a specific request? A question? Just want to chat? Have a general discussion about an issue?

All fine, just be clear
by parker-3461 | 2026-03-14 15:24:28+00:00
> The Center for Strategic and International Studies (CSIS) is a bipartisan, nonprofit policy research organization dedicated to advancing practical ideas to address the world’s greatest challenges.

Sorry, may I get more information on why this is considered Chinese army propaganda?

My understanding is that CSIS (https://www.csis.org/about) is an US based organisation that provides analysis on topics which include Chinese organisations/military.
by kenjin4096 | 2026-03-14 15:24:51+00:00
I implemented most of the tracing JIT frontend in Python 3.15, with help from Mark to clean up and fix my code. I also coordinated some of the community JIT optimizer effort in Python 3.15 (note: NOT the code generator/DSL/infra, that's Mark, Diego, Brandt and Savannah). So I think I'm able to answer this.

I can't speak for everyone on the team, but I did try the lazy basic block versioning in YJIT in a fork of CPython. The main problem is that the copy-and-patch backend we currently have in CPython is not too amenable to self-modifying machine code. This makes inter-block jumps/fallthroughs very inefficient. It can be done, it's just a little strange. Also for security reasons, we tried not to have self-modifying code in the original JIT and we're hoping to stick to that. Everything has their tradeoffs---design is hard! It's not too difficult to go from tracing to lazy basic blocks. Conceptually they're somewhat similar, as the original paper points out. The main thing we lack is the compact per-block type information that something like YJIT/Higgs has.

I guess while I'm here I might as well make the distinction:

- Tracing is the JIT frontend (region selection).

- Copy and Patch is the JIT backend (code generation).

We currently use both. PyPy uses meta-tracing. It traces the runtime itself rather than the user's code in CPython's tracing case. I did take a look at PyPy's code, and a lot of ideas in the improved JIT are actually imported from PyPy directly. So I have to thank them for their great ideas. I also talk to some of the PyPy devs.

Ending off: the team is extremely lean right now. Only 2 people were generously employed by ARM to work on this full time (thanks a lot to ARM too!). The rest of us are mostly volunteers, or have some bosses that like open source contributions and allow some free time. As for me, I'm unemployed at the moment and this is basically my passion project. I'm just happy the JIT is finally working now after spending 2-3 years of my life on it :). If you go to Savannah's website [1], the JIT is around 100% faster for toy programs like Richards, and even for big programs like tomli parsing, it's 28% faster on macOS AArch64. The JIT is very much a community effort right now.

[1]: https://doesjitgobrrr.com/?goals=5,10

PS: If you want to see how the work has progressed, click "all time" in that website, it's pretty cool to see (lower is faster). I have a blog explaining how we made the JIT faster here https://fidget-spinner.github.io/posts/faster-jit-plan.html.
by barnabee | 2026-03-14 15:24:55+00:00
I like designing data, algorithms, and systems. I like picking the right tools for the job. I like making architectural and user interface (CLI, configuration format, GUI, whatever) decisions.

Actually typing code is pretty dull. To the extent that I rarely do it full time (basically only when prototyping or making very simple scripts etc.), even though I love making things.

So for me, personally, LLMs are great. I'm making more software (and hardware) than ever, mostly just to scratch an itch.

Those people that really love it should be fine. Hobbies aren't supposed to make you money anyway.

I don't have much interest in maintaining the existence of software development/engineering (or anything else) as a profession if it turns out it's not necessary. Not that I think that's really what's happening. Software engineering will continue as a profession. Many developers have been doing barely useful glue work (often as a result of bad/overcomplicated abstractions and tooling in the first place, IMO) and perhaps that won't be needed, but plenty more engineers will continue to design and build things just more effectively and with better tools.
Show HN: BetterGit – Free, simple, no frills, Git GUI
by aggregator-ios | 2026-03-14 15:25:12+00:00
On a recent screen share with our designer at my FT job, I watched as our designer struggled with checking out a repository. It was painful because existing Git clients are confusing and nearly user hostile. Us software engineers are used to Git and terrible UX, but it shouldn't have to be that way.

So, I wanted to make something better. Been working on this one for a while now, and while it's still very early stages, it's stable enough that I feel comfortable sharing it with the world :)

I wanted a few things to be really easy and clear:
- Merging between branches is explained before you do it
- Creating branches and tags is just a + button
- Discarding all changes automatically creates a stash so you can go back if it was an accident

It's fully free. Cross platform. There are no signups, no accounts. No noise. No banners. No advertisements. No trackers. No AI.

Check it out and let me know what you think! Here to improve on the DX for everyone and hope to make our lives just a little bit better.
by jcalvinowens | 2026-03-14 15:25:42+00:00
> Communication is mind control. The point isn't the words, it is literally trying to get a person to do something.

You're describing manipulating people, not communicating with them.

The point of communication between engineers is usually to establish a mutual understanding, not make them do something you want. Through that mutual understanding you both come to agree on what should be done.

Often, coming to that mutual understanding on complex projects with experienced engineers can be difficult, because we're human and we inevitably misunderstand complex systems in a multitude of ways on our path to understanding them.

Being able to be brutally honest with each other about our misunderstandings is what the author is talking about. When you work with people who get that individuals misunderstanding things is part of the process, and nobody takes or imputes it personally, you are suddenly free to focus on the actual meat of the problem instead of worrying how people may or may not feel about it.
by gwerbin | 2026-03-14 15:26:04+00:00
> Strict limits on governmental regulation wherein any restrictions must be demonstrably necessary and narrowly tailored to a compelling public safety or health interest.
> Mandatory safety protocols for AI-controlled critical infrastructure, including a shutdown mechanism and compulsory annual risk management reviews.

Read: industry can do whatever we want, but the government also has to put up barriers to entry that favor large incumbents.

This has nothing to do with rights or even computing, it's just regulatory capture.
by ProllyInfamous | 2026-03-14 15:26:20+00:00
>the least-bad residential ISP I've dealt with

It's because lobbyists have prevented your local community from implementing anything close to what Chattanooga/EPB [0] has done with their city-owned fiber infrastructure. They literally cannot expand outside their power delivery area (by court order), and were only initially allowed to offer internet services because "it helped monitor their smartgrid technologies for power delivery." National ISPs have spent millions campaigning against EPB-like ISP expansion.

It's a racket.

[0] Electric Power Board ISP, is incredible: <https://en.wikipedia.org/wiki/EPB> 300mbps synchronous fiber, $58.99/month (1gbps is ~$75; 20gps is $250), four-port fiber/copper bridge (supplied) direct to your techshed. EVERY service address gets one power-drop and one 4-fiber service drop, whether or not you use internet(s).

I don't even know why other national ISPs advertise here — they specifically lock certain apartment complexes into EPB-exclusion contracts... and don't tell potential renters this during leasing/contracts. It's shitty.

It's a racket.
by pxoe | 2026-03-14 15:26:44+00:00
4) The Bluetooth standard is just kinda bad. Technically there should be enough bandwidth for better quality audio, but the existing profiles like headset mode drop audio quality down to 8-16 kHz sampling rate in mono, not just for mic but for audio you're listening to as well. It's a huge flaw and it's been bad for decades with seemingly no improvement at all (at least certainly not in a way that could be widespread and commonly used).

It's so bad you'd almost wish for a brand new wireless connectivity or wireless audio standard, or even resort to some proprietary 2.4 GHz nonsense, because it's genuinely so horrid. You could have the best most expensive headphones in the world, but because of Bluetooth and its ancient profiles and mic support it's gonna have baseline absolute garbage mic quality no matter what.
by user_7832 | 2026-03-14 15:27:25+00:00
Apart from the needless ableist/rude comment, no, they're not just popular because they're different. For many younger people (the iPhone-natives), wired is novel to them in some ways. Novel things always have some people adopting them. Except, wired actually does have advantages, meaning that some will continue using them for their benefits.

If it were purely "being different from status quo", everyone would be having a linux phone (like a pinephone).
by agentultra | 2026-03-14 15:27:57+00:00
100%.

There are cases where a unit test or a hundred aren’t sufficient to demonstrate a piece of code is correct. Most software developers don’t seem to know what is sufficient. Those heavily using vibe coding even get the machine to write their tests.

Then you get to systems design. What global safety and temporal invariants are necessary to ensure the design is correct? Most developers can’t do more than draw boxes and arrows and cite maxims and “best practices” in their reasoning.

Plus you have the Sussman effect: software is often more like a natural science than engineering. There are so many dependencies and layers involved that you spend more time making observations about behaviour than designing for correct behaviours.

There could be useful cases for using GenAI as a tool in some process for creating software systems… but I don’t think we should be taking off our thinking caps and letting these tools drive the entire process. They can’t tell you what to specify or what correct means.
by cc13cc13 | 2026-03-14 15:28:00+00:00
This is a great foundation—Project Naawi has a clear, provocative mission. To make this compelling for the Hacker News crowd, we need to lean into the technical "how" (the SDK-first and Compiler approach) while making the call for contributors feel like an invitation to join an elite R&D effort.
Show HN: Project Naawi – A Community-Driven "Compiler" for Intent-Driven Infra

We’re building Project Naawi, an open-source framework designed to replace the "YAML wall" with Intent-Driven Infrastructure (IDI). Instead of wrestling with rigid DSLs, we’re developing a system that translates natural language and high-level SDKs directly into cloud orchestration.

We’ve moved past the "vanity project" phase and are now entirely community-driven. We’re seeking contributors who are ready to stop managing configuration files and start building the logic that renders them obsolete.

Why contribute to Naawi?

Architect the "Infra-Compiler": Help us build the core logic that maps intent to infrastructure providers. If you have experience with LLM tool-calling or cloud SDKs, your input will shape the engine.

Kill the Boilerplate: We aren't just making YAML "better"—we're bypassing it. You’ll be working on the frontier of SRE and AI, defining how natural language becomes a deployment.

Build the SDK Primitives: We need engineers to help define the functional building blocks that make infrastructure "conversational" and reliable.

Real-World Stress Testing: No more building in a vacuum. Your contributions will be validated against actual platform bottlenecks that keep SREs up at night.

The Tech Stack:

Core: Intent-based orchestration logic.

Interface: Natural language processing paired with a robust SDK.

Goal: Moving from "How to deploy" to "What to deploy."

Get Involved:

Repo: github.com/nicksmoore/project-naawi

Explore the UI: project-naawi.lovable.app

If you’re tired of "configuration drift" and want to help build a more intuitive, intent-based way to deploy, check out our roadmap and open issues. We’d love to have you in the mix.
by ToucanLoucan | 2026-03-14 15:28:11+00:00
You know if we're gonna pass laws to make it illegal for the government to interfere with the Torment Nexus, the least they could do is not gaslight us with the fucking name of the law. Just tell us the billionaires get to fuck the planet in the eye and the rest of us have to deal with it, at least it's honest that way.
by dguest | 2026-03-14 15:28:13+00:00
First time I saw this hell was when a junior colleague convinced a rather senior one to use black. Of course senior went bumbling around black-ing every file he touched, including some random thousand-line files in long-lived forks of an established code base. Those files became essentially unmergable from then on.

It was a confluence of a lot of bad design features and blunders and I can't blame the formatter for the mess it caused. So I understand your point but, I'd amend it a bit: version control is the reason many projects require a specific formatting style.

In projects without an explicit style, the number one formatting rule is don't reformat code you didn't touch.
by amiga386 | 2026-03-14 15:28:14+00:00
My favourite ice-cream is rum and raisin, by the way...

I guess I'd say the thing to do is to measure harms with direct evidence (e.g. this many people get addicted to lootboxes, they spend this much of their money, etc.) rather than seek an imperfect analogy with an existing but different harm. Lootboxes and fake FOMO are both techniques used by video game producers to fatten their bottom lines by psychologically manipulating their playerbase, let's get that regulated and set controls on it (audience, age limits, frequency, openness, etc.) rather than argue where it lies in the games-of-chance spectrum.
by rdtsc | 2026-03-14 15:28:21+00:00
> But an escape hatch is still an escape hatch. These mechanisms bypass the process isolation model entirely. They are shared state outside the process model, accessible concurrently by any process, with no mailbox serialization, no message copying, no ownership semantics. And when you introduce shared state into a system built on the premise of having none, you reintroduce the bugs that premise was supposed to eliminate.

Not they are not. I don't know what "Technical Program Managers at Google" do but they don't seem to be using a lot of Erlang ;-) it seems. ETS tables can be modeled as a process which stores data and then replies to queries. Every update and read is equivalent to sending a message. The terms are still copied (see note * below). You're not going to read half a tuple and then it will mutate underneath as another process updates it. Traversing an ETS table is logically not that different than asking a process for individual kvs using regular message passing.

What is different is what these are optimized for. ETS tables are great for querying and looking up data. They even have a mini query language for it (https://www.erlang.org/doc/apps/stdlib/qlc.html). Persistent terms are great for configuration values. None of them break the isolated heap and immutable data paradigm, they just optimize for certain access patterns.

Even dictionary fields they mention, when a process reads another process' dictionary it's still a signal being sent to a process and a reply needing to be received.

* Immutable binary blocks >64B can be referenced, but they are referenced when sending data using explicit messages between processes anyway.
by xg15 | 2026-03-14 15:28:35+00:00
> Every few years a new tool appears and someone declares that the difficult parts of software engineering have finally been solved, or eliminated. To some it looks convincing. Productivity spikes. Demos look impressive. The industry congratulates itself on a breakthrough. Staff reductions kick in in the hopes that the market will respond positively.

As a software engineer, I'd love if the industry had an actual breakthrough, if we found a way to make the hard parts easier and prevent software projects from devolving into balls of chaos and complexity.

But not if the only reward for this would be to be laid off.

So, once again, the old question: If reducing jobs is the only goal, but people are also expected to have jobs to be able to pay for food and housing, what is the end goal here? What is the vision that those companies are trying to realize?
by janice1999 | 2026-03-14 15:28:48+00:00
The 2nd rule is clearly intended to be a shield and distraction. It's there to pretend the law serves the public, when in reality it's designed to defend datacenter builders from the public interest. Politicians can talk about meaningless sci-fi concepts like SkyNet and how it can defeat it with off switches, instead of real issues like noise pollution, tax giveaways, electricity prices and mass surveillance.
Show HN: Score any URL against a quality profile with one curl command
by onebit0fme | 2026-03-14 15:28:50+00:00
I've been building a quality scoring API for text content. The idea: instead of writing rules for what good looks like, each profile is trained from examples of great and not-so-great writing. The profile then scores anything you throw at it, with per-trait scores.

Two profiles live right now — compelling READMEs and technical writing. Happy to train more profiles on request. Try it:

curl -s https://qed.systems/p/qed.compelling-readme -H "Content-Type: application/json" -H "Accept: text/plain" -d '{"content":"https://github.com/astral-sh/uv"}'

Works with any public URL or raw text. No auth, no account. Also ships as an MCP server (claude mcp add --transport http qed https://qed.systems/mcp).
by embedding-shape | 2026-03-14 15:28:55+00:00
Slight adjustment, but I'd see "maintaining code" is the same as before, matters more the people and their experience and knowledge how to manage that. But agree that the literal typing was never the difficult part, knowing what code should and shouldn't be written was a hard part, and still remains a hard part.

Right now, "what code shouldn't be written" seems to have become an even more important part, as it's so easy to spit out huge amounts of code, but that's the lazy and easy way, not the one that let you slowly add in features across a decade, rather than getting stuck with a ball of spaghetti after a weekend of "agent go brrr".
by rchaud | 2026-03-14 15:29:10+00:00
I was a big user of Pocket between 2015-19, which also curated interesting long-form articles. The problem with that model was that paywalls were coming up everywhere, so the free articles that remained came from low-quality sites (Forbes, The Inc, FastCompany) full of long-form hustle culture or self-improvement stuff loaded with affiliate links. Maybe Digg v2 had the same issue.