MurphyA/hacker-news huggingface dataset:
by dalmo3 | 2026-03-04 13:33:28+00:00
Long rant, but the author never defines what he means by "simple". He heavily hints at smaller changeset == simpler.

Too often the smallest changeset is, yes, simple, but totally unaware of the surrounding context, breaks expectations and conventions, causes race conditions, etc.

The good bit in tfa is near the end:

> when someone asks “shouldn’t we future-proof this?”, don’t just cave and go add layers. Try: “Here’s what it would take to add that later if we need it, and here’s what it costs us to add it now. I think we wait.” You’re not pushing back, but showing you’ve done your homework. You considered the complexity and chose not to take it on.
by mikegchambers | 2026-03-04 13:33:33+00:00
Author here.

I started experimenting with this pattern after noticing how much better recent models have become at generating small pieces of working code on the fly.

The experiment is slow and messy, but it made me wonder what changes when the model stops being just another library and starts behaving more like the execution environment itself.

Curious how far people think this direction could go. In five years, how many applications might actually treat the model as part of, or all of, the runtime?
by zorked | 2026-03-04 13:33:41+00:00
They're fighting our datacenters. (...) A hyper-conservative regime like this will probably fare (at least in the long run) about as well as you would if you decide to nope out of society

You do know that Iran has technical universities, works on advanced weaponry, and the leader of their National Security council has a computer science degree?

It is important to at least look at things as they are, and not through the prism of orientalism.

Iran's regime is socially conservative. But so is the current US government. There is no sign that they are anti-technology or isolationist.
by aurareturn | 2026-03-04 13:33:47+00:00
Its worked before (see 1980s https://www.strausscenter.org/strait-of-hormuz-tanker-war/), and it'll probably work again. Especially as Iran has different values on loss.

One of the lessons learned:

The oil market is likely to adapt to disruption in the Strait of Hormuz. Initially, the Tanker War led to a 25 percent drop in commercial shipping and a sharp rise in the price of crude oil. But the Tanker War did not significantly disrupt oil shipments. In fact, Iran lowered the price of oil to offset higher insurance premiums on shipments, and the real global oil price steadily declined during the 1980s. Even at the its most intense point, the Tanker War failed to disrupt more than two percent of ships passing through the Persian Gulf.[x]

This seems relevant to the global stock/oil market overreaction.
by aenis | 2026-03-04 13:34:02+00:00
TBH, they are all rather useless at those sizes.

I used to run a lot of local models on my mbp - mainly stt, tts, embeddings and diffusion models - and small LLMs used for utility purposes - but stopped. It saves time in the long run to run those models on target architecture from the get go - which in most cases is nvidia/cuda - rather than test and tweak on metal, and then switch to cuda for prod - and experience weird and subtle differences and regressions. I don't think it makes much sense to develop anything (other than hobby projects for home use) on mlx atm.
by the_af | 2026-03-04 13:34:13+00:00
I don't see it.

Russia has their hands full with Ukraine and has failed in the past to protect other allies such as Syria.

China seems wise enough to provide some support to Iran while sitting out of direct involvement in the war. China has everything to lose with war and nothing to gain. If anything, they are signaling "stability" to the Global South -- something from which the US is increasingly drifting away -- and war is the opposite of stability.

> Meanwhile, the US is still carrying out precision attacks with expensive ordnance which they have limited supplies of.

I think they have more than enough, plus Iran faces an even worse situation. Limited stockpiles of their only effective weapons, missiles and drones, and quickly running out. What's worse, by not using those weapons in huge salvoes, they reduce their efficiency... they only work if they can overcome defenses, but if they spend them too fast they lose their only effective weapon.

I think the Islamic Republic will be overthrown, but this requires boots on the ground, and it'll become a quagmire like Iraq or Afghanistan. At some point the US will declare success and leave, and from the ashes of Iran countless warring factions will emerge, an endless insurgency, and possibly the next ISIS. We've seen this happen more than once, no reason to believe this will go a different way.

Russia and China cannot stop this.
by csmpltn | 2026-03-04 13:34:13+00:00
People always overcomplicate this. Companies want to get the most out of their employees, for the least amount of money paid.

Promotions are supposed to incentivise people to stay, rather than leave. If the company never promoted anyone, people would leave. So there needs to be a path for promoting people. But that process doesn’t have to be transparent, or consistent, or fair - in-fact it rarely is.

You promote people who consistently overdeliver, on time, at or below cost, who are a pleasure to work with, who would benefit the company long term, who would be a pain to lose. A key precondition is that such people consistently get more done compared to other people with equal pay, otherwise, they don’t stand out and they are not promotion material.

What counts as overdelivering will vary based on specific circumstances. It’s a subjective metric. Are you involved with a highly visible project, or are you working on some BS nobody would miss if it got axed? Are you part of a small team, or are you in a bloated, saturated org? Are you the go-to person when shit hits the fan, or are you a nobody people don’t talk to? Are you consistent, or are you vague and unpredictable? Does your work impact any relevant bottom lines, or are you just part of a cost centre? It really isn’t rocket science, for the most part.
by spwa4 | 2026-03-04 13:34:33+00:00
Why would anyone want any kind of non-politician-approved interaction? Are you a traitor or a paedophile? In fact give me all your chat history and let's go through it, because I have no idea what we'd even approve.

(dixit every European government)

https://fightchatcontrol.eu/

Oh and all your private photos too. Think of the children! (and let's NOT discuss that when it comes to child abuse in Europe BY FAR the biggest culprits are European government employees. School teachers, and people in youth services. That's >90% of all child abusers in the EU. The youth services part of that would be the EXACT individuals screaming about thinking of the children. Don't worry. They've put rules in the Chat Control legislation protecting themselves from ... well the law)
by randusername | 2026-03-04 13:34:36+00:00
Whatever is going on with each 'f' in this font is breaking my brain. Feels like the drunk goggles equivalent of dyslexia.

I don't think this phenomenon is unique to programming. My plumber was explaining how he put in a manifold and centralized whole-house off valve accessible indoors and I was like, okay, thanks? I can just turn it off at the street.

Only established professionals have the status and self-confidence to show restraint. I think that explains interviews.
by kevincox | 2026-03-04 13:34:37+00:00
Yeah, I would be fine with a different build stream. I do think it could be sufficiently secure in a single stream but it will always be increased attack surface so the safest option is to do separate builds.

I also don't include a root account in my container images, but you probably have a root account on the sever that runs them in case you need to debug something. But you can probably also build and deploy a new container. At the end of the day you almost always want some last-resort way to access the data stored in case something goes very wrong. Whether that is for backups, "hostile" data export or for other reasons it is important to me.
by rayiner | 2026-03-04 13:34:43+00:00
You’re overlooking the fundamental difference between Iranian society and Afghan society. In Afghanistan, the U.S. was trying to bomb a place that was always a collection of small feudal states into being a functioning country. In Iran, it’s trying to dislodge a theocracy that’s taken over a country that’s had orderly, centralized administration for almost two thousand years.

I wouldn’t bet on either approach working. But a good outcome in Afghanistan was always completely hopeless. A good outcome in Iran is merely unlikely.
by uyzstvqs | 2026-03-04 13:34:44+00:00
From the link:

> For anyone wondering how this happened, a bit lower in the comments OP says that this key was UPLOADED TO GITHUB, I mean, that should really be the end of the thread. It sucks that this happened, sucks even more that you have a personal card on file, but the fact that Google is even saying ‘shared responsibility’ after you uploaded it to GH is crazy, it is your responsibility.
by jvidalv | 2026-03-04 13:35:57+00:00
I work as a consultant so I navigate different codebases, old to new, typescript to javascript, massive to small, frontend only to full stack.

Claude Code experience is massively different depending on the codebase.

Good E2E strongly typed codebase? Can one shot any feature, some small QA, some polishing and it's usually good to ship.

Plain javascript? Object oriented? Injection? Overall magic? Claude can work there but is not a pleasant experience and I wouldn't say it accelerates you that much.
by fer | 2026-03-04 13:36:10+00:00
> It's not easy, but it's their work.

There's a significant asymmetry though, it's not just a bit more work. I'm a bit cynical here, but often it's easier to just overengineer and be safe than to defend a simple solution; obviously depending on the organization and its culture.

When you have a complex solution and an alternative is stacked up against it, everything usually boils down to a few tradeoffs. The simple solution is generally the one with the most tradeoffs to explain: why no HA, why no queuing, why no horizontally scalable, why no persistence, why no redundancy, why no retry, etc. Obviously not all of them will apply, but also obviously the optics of the extensive questioning will hinder any promotion even if you successfully justify everything.
by dzonga | 2026-03-04 13:36:44+00:00
Charlie Munger once said >>> Show me the incentive, I will show you the outcome

Problem is in big tech -- the incentives are all aligned towards complex stuff

you wanna get promoted - do complex stuff that doesn't make sense. If you get promoted, then it also boosts the performance of your manager.

the only way to escape this nonsense is to work at smaller companies

right now you've people advocating for A.I coded solutions yet never realizing that A.I solutions result in a convoluted mess since A.I never possesses the ART of software engineering i.e knowing what to cut out
by babuskov | 2026-03-04 13:36:52+00:00
+1 from me.

Motorola has such great quality/price ratio and the user experience is decent. There's still some nagging and such but overall it's much better than the competition.

But I still can't get over my old iPhone 6. That phone size was just perfect. Easy to hold and do everything with one hand, easy to fit into any pocket.

I really want an Android like that. I don't need 3 cameras and bunch of other nonsense.
by boondongle | 2026-03-04 13:36:57+00:00
I wouldn't say you're mistaken, but it's a simplification. In the network world, the capability exists to restrict what BGP advertisements are accepted via RPKI/a peer. Internet providers usually don't because the premium is placed on uptime/connectivity.

If tomorrow, everyone said "we don't want IP's from Frankfurt showing up somewhere in Dubai", you'd have a massive technical problem and rearranging to start with but once that was sorted you could geo-lock. IANA and Network providers simply haven't been doing that.

The reason it doesn't happen is Devs/Stakeholders want uptime from ISPs/Networks and not something they can't abstract. Basically its just a status quo much like the entire internet reverse-proxying through CDNs is a status quo. It wasn't always like that, and it may not always be like that in the future - just depends which way the winds blow over time.
by Cyph0n | 2026-03-04 13:37:09+00:00
You should sprinkle in a few other news sources because that’s not what is happening at all.

Iran also has further escalation paths it can take. So far, they have only been targeting US-affiliated targets in the Gulf. You can imagine what would happen if they decide to expand their target list. But I think this will only happen if GCC countries decide to participate.
by TwoFerMaggie | 2026-03-04 13:37:20+00:00
I watched the first video. One point they didn't mentioned is that their android example of the "last small flagship phone", asus zenfone 9/10, is about the same size as an iphone 12/13, not the mini.

Do regular iphones sell well? If so, the small flagship phones are not dead, because iphones are not dead. If iphones are not counted as small phones, then the small android flagship phones are dead long time ago.
by okanat | 2026-03-04 13:37:26+00:00
NFC is limited access for phones. You need to pay Google and Apple tax. Android does allow independent communication but it is not widespread and you'll lose a big chunk of Apple users. You basically tie yourself to a platform that way.

You can scan and add your QRs (or more correctly Aztec barcodes) in DB Navigator app already. If you bought it via your own account (instead of your company buying it), you don't even need to do it. The tickets automatically appear.

DB Navigator is one of the best transport apps and already implements some caching. However you're ultimately tied to cell network or WiFi in train for certain othet apps and the quality of implementation. PDFs don't expire.
by MartyMcBot | 2026-03-04 13:38:18+00:00
the .md scratch pad point is underrated, and the format matters more than people realize.

summaries ("tried X, tried Y, settled on Z") are better than nothing, but the next iteration can mostly reconstruct them from test results anyway. what's actually irreplaceable is the constraint log: "approach B rejected because latency spikes above N ms on target hardware" means the agent doesn't re-propose B the next session. without it, every iteration rediscovers the same dead ends.

ended up splitting it into decisions.md and rejections.md. counter-intuitively, rejections.md turned out to be the more useful file. the decisions are visible in the code. the rejections are invisible — and invisible constraints are exactly what agents repeatedly violate.
by palata | 2026-03-04 13:38:27+00:00
And I'm fine with you wanting root on the device you own. But you were implying that not having root means that you don't own your device. I disagree with that. You can totally own your device and not be root.

I think it is important, because I read a lot of comments that imply that "owning their device" means "owning the developers". And that's a wrong fight.

The real fight is that it should be illegal to prevent me from installing my preferred OS on a general-purpose computer.
by withinboredom | 2026-03-04 13:38:47+00:00
This is a really great test for vibe coding. This isn't easy, but it took me several hours to pass. Vibe coding the results is ... not exactly faster. Reminding it to output logs (I'm just doing this in chat and manually copy/pasting the code), it getting hung up on 'the maximum wait time' exactly equaling the challenge, etc. Opus was able to generate a passing implementation up to level 7 on the first level but can't seem to pass level 12. Sonnet, had to iterate on every level up to level 5, and couldn't pass that level.
by davexunit | 2026-03-04 13:38:49+00:00
Permissions can be handled with capability systems. Keyhive [0] is the furthest along on this. I've also made my own prototype showing how certificate capabilities can be composed with CRDTs.

[0] https://www.inkandswitch.com/keyhive/notebook/

[1] https://spritely.institute/news/composing-capability-securit...
by samiv | 2026-03-04 13:38:51+00:00
You're actually not necessarily right.

At this point here in the south of Germany not having DB would be an improvement.

Now it exists and you might even try to take it just to be delayed and disappointed. You'll lose your money and they behave in their arrogant manner with impunity.

Their customer "service" will definitely tell you how it's your own fault for having had the nerve to actually try to take their train. You might have even carried some dirt to the train for Christs sake!

So yeah. Not having it would already be an improvement. You'd just shrug and move on and take an alternative transport. Even horse and carriage would be better.
by HarHarVeryFunny | 2026-03-04 13:38:58+00:00
Agreed, although SpiNNaker really isn't much specialized for spiking NNs - it's really just a large ARM-base cluster specialized for fast message passing. The messages could be inter-neuron communications, or anything else, and it has been used for other purposes.

I really don't understand the thinking behind these hardware-based neuromorphic projects... as you say it would make more sense to prove ideas out in software first, especially for experimenting with more biologically accurate models of neurons.

It seems the time to commit to hardware would be if neuromorhic/spiking/asynchronous designs show worthwhile functional benefits, and need custom silicon for efficient implementation.
by zhebrak | 2026-03-04 13:39:13+00:00
Link: https://simulator.zhebrak.io?welcome

You are the Compute Officer aboard a generation ship. Systems are failing, a signal arrives from deep space, and every mission is a real distributed ML problem — fix OOM errors, configure tensor parallelism, scale training across clusters, optimise inference throughput.

The game runs on a first-principles physics engine: FLOPs, memory bandwidth, collective communication, pipeline bubbles. Calibrated against published runs from Meta, DeepSeek, and NVIDIA within 1-2% MFU.

If you are not into the story, there's also a Learn mode with 60 tasks (from beginner to advanced) covering both training and inference, and a full simulator for exploration and planning. All client-side, no backend.

GitHub: https://github.com/zhebrak/llm-cluster-simulator
by Cyph0n | 2026-03-04 13:39:26+00:00
The beautiful irony is that Carney initially went all in supporting this illegal war of aggression. It seems he tempered his language a bit since then. Perhaps his team realized how hypocritical he sounds after that whole speech on Greenland.

https://x.com/markjcarney/status/2027721462233141679?s=46

Here is the walk back: https://x.com/harry__faulkner/status/2028950225683894395?s=4...
by chrismatic | 2026-03-04 13:39:29+00:00
While I agree with some of his sentiments the entire video reeks of half-baked conspiratorial thinking and shallow engagement with the facts.

A quick tell is that the video's title includes "Game Theory", while only referencing game-theoretical concepts twice in an off-hand comment. In both instances the usage is plainly wrong.

In general, he loves making big assertions without backing them up with evidence or explanations that go beyond hand-wavy examples.
by CloakHQ | 2026-03-04 13:39:37+00:00
the full-session evaluation framing resonates a lot. we've been running browser automation agents and the exact same problem shows up: individual actions pass, session fails. a click works, a form fill works, but the session gets flagged or blocked 8 turns in because something earlier created a signal that compounded.

one failure mode that's specific to browser agents and doesn't get much attention: the test environment is too clean. when you run simulations against a controlled setup, the agent never encounters the friction that real sessions do - bot detection challenges, CAPTCHAs, dynamic content that loads differently, fingerprinting checks mid-session. so you end up with agents that pass your test suite but fail in the wild, and the gap is in the environmental assumptions not the agent logic.

the mock tool platform approach is interesting precisely because it sidesteps this - you're testing the agent's decision-making in isolation from the messy runtime. that's valid for catching logic regressions. but i'd be curious how you handle cases where the tool call itself triggers secondary effects in the environment (e.g. the API call changes session state in ways that affect what the agent sees next).

also, does your session-level judge handle cases where the correct behavior is adaptive - where the agent should change strategy mid-session based on what it encountered? that feels like a harder eval problem than a fixed expected outcome.
by textadept-thrwy | 2026-03-04 13:39:45+00:00
I developed some plugins for Textadept some time ago. It's very lightweight and mature, but its dependence on different backends on different platforms introduced some frictions (QT vs. GTK etc.). We had a working Mermaid and image viewer plugin. It's really extensible. Never upstreamed them though.

It uses Lua LPEG lexers, which are extremely easy way to de develop syntax parsers/LSPs for new or unsupported languages.

Eventually our project moved to Pragtical, which has SDL as a cross-platform backend and uses the more modern meson as the build system, which made developing for it much easier.
by jghn | 2026-03-04 13:39:46+00:00
I also will rewrite both text and code created by Gen AI. I've found the best workflow for me is not to refine what I've written, but instead to use it to help me get over humps and/or crank through some of the drudgery. And then I go back and edit, fixing any issues I spot and to reshape it to be in my own voice.

I do this with code too.
Just got approved on the Apple App Store – launching our digital rehab startup
by spenzev | 2026-03-04 13:39:48+00:00
Excited to share that our startup VITA325 has officially been approved by the Apple App Store.
We’re building a smartphone-based gait analysis and digital rehabilitation platform — no wearables required. The app uses built-in motion sensors and AI to generate personalized insights and progress tracking.
It’s been a journey from idea → prototype → validation → App Store approval.
Would love advice on:
• Early traction strategies
• HealthTech distribution channels
• Scaling in regulated environments
by ocivelek | 2026-03-04 13:39:51+00:00
Most AI adoption advice optimises the existing process. Tickets, standups, code review, documentation — these didn't emerge from first principles. They evolved as workarounds for human limitations: forgetting, context loss, blind spots, communication bandwidth. AI doesn't share most of those constraints. Embedding it into workflows designed around human limitations means asking it to operate inside constraints built for a problem it doesn't have. The argument here is that the failure mode isn't tooling or team readiness — it's that the process itself was always the bottleneck.