MurphyA/hacker-news huggingface dataset:
by pjc50 | 2026-02-05 14:00:22+00:00
It's not my solution, I'm not in charge of the SEC!

I would however like people to be a bit more specific about what they think the crime was, who specifically committed what, and whether it was actually illegal at the time. It's a word people love to throw around. It's not actually illegal to make poor business decisions.

https://en.wikipedia.org/wiki/Se%C3%A1n_Quinn for example, while his misconduct cost the collapse of AIB, the thing he was actually jailed for was failing to comply with court orders.
by hansmayer | 2026-02-05 14:01:11+00:00
You know things are running bad when they've lost even the likes of WSJ. And yet Satya and his ilk (across the LLM space) keep pushing it. It does not matter that this technologically on its own can never reach what they kept promising. Is the pride and ego of a couple of CEOs so important that we'll all just watch them bringing the whole market down ?
by ManlyBread | 2026-02-05 14:01:15+00:00
>It’s possible AI just seems more popular than it is because it’s easy to hear the people who are talking about it but harder to hear the people who aren’t.

I think it's because there's a financial motivation for all the toxic positivity that can be seen all over the internet. A lot of people put large quantities of money into AI-related stocks and to them any criticism is a direct attack on their wealth. It's no different from crypobros who put their kids' entire college fund into some failed and useless project and now they need that project to succeed or else it's all over.
by epolanski | 2026-02-05 14:02:13+00:00
> Documentation is hard to maintain because it has no connection to the code. Having an LLM tweak the documentation after every merge is "vibe documenting."

I'm not sure I agree, you don't need to vibe document at all.

What I do in general is:
- write two separate business requirements and later implementation markdown files
- keep refining the first and second one as the work progresses, stakeholders provide feedback

Before merging I have /docs updated based on requirements and implementation files. New business logic gets included in business docs (what and why), new rules/patterns get merged in architectural/code docs.

Works great and better at every new pr and iteration.
by Forgeties79 | 2026-02-05 14:02:23+00:00
I agree with your larger point, however:

> camcorders have been around for ages but you don't have millions of directors around just because you make a tool more accessible

That’s exactly what happened. There are more filmmakers than ever now due to the accessibility of digital tools, including affordable HD cameras. Especially once the DSLR revolution took off circa 2011, which enabled budget-constrained aspiring filmmakers to use prime sets.
by cucumber3732842 | 2026-02-05 14:02:32+00:00
You can make anything on anything. Doesn't make it smart tho.

If this were a production run of a few dozen super high grade aerospace donkey dicks with five shoulders and four pockets, an oil channel, a precisely engineered break point and a 12-step heat treat process I'd say yeah, make it on your Swiss lathe with live tooling or bajillion axis VMC or whatever.

But this looks to be a simple small, probably cosmetic or otherwise low-ish strength stainless or chromed fastener that BMW probably wants a few hundred thousand of. You'll be time, money, labor, frustration, managerial nitpicking, just about everything, ahead to just have the fastener industry and their existing expertise make it for you. The "bespoke" drive, the custom branding, those are all known-knowns to those guys. They'll whip up tooling for their screw machines and fill the same bucket in 1/20th of the time.

https://www.youtube.com/watch?v=WJvQZko8uiU

Edit: replaced video link with better one. Obviously there's fiddle fucking around they're not showing and they're mix and matching footage of different products but the speed things move once you've got it all set up is broadly accurate. A whole bunch of these steps would be skipped or altered for a stainless fastener.
by belorn | 2026-02-05 14:02:32+00:00
Yes, I did write that a bit hasty. I changed above to the normal process. As it happened we just installed a server without hotswap disk, but to be fair that is the first one I have personally seen in the last 20 years.

Remote hands is a thing indeed. Servers also tend to be mostly pre-built now days by server retailers, even when buying more custom made ones like servermicro where you pick each component. There isn't that many parts to a generic server purchase. Its a chassi, motherboard, cpu, memory, and disks. PSU tend to be determined by the motherboard/chassi choice, same with disk backplanes/raid/ipmi/network/cables/ventilation/shrouds. The biggest work is in doing the correct purchase, not in the assembly. Once delivered you put on the rails, install any additional item not pre-built, put it in the rack and plug in the cables.
by Jarwain | 2026-02-05 14:02:39+00:00
This sounds quite interesting!

I've been exploring spec driven workflows, but from a different angle.

I've been thinking about how to describe systems with a standard format, recursively. Instead of one 10 page doc, you might get 10 one pagers, starting from the highest level of abstraction and recursing down into the parts and subsystems, all following the same format. Building out this Graph of domains provides certain reusable nodes/bits of context.

This then extends to any given bit of software, which is a system in itself composed of the intersections of a lot of different domains and subsystems.

Cue looks interesting and is something I'll be digging into more
by tarsinge | 2026-02-05 14:02:59+00:00
> The trick is to realize that most market discussion you're not paying for is itself marketing at best and cosplay at worst.

There was a leak posted on Wallstreetbets of some paid analysis (https://www.reddit.com/r/wallstreetbets/comments/1qpwyqz/dbs...), and it was basically follow the hype with a layer of sophisticated post rationalisation on top. I fail to see the difference between these and the average "DD" on an investing subreddit.

Excerpt from the Tesla one (https://www.dbs.com/content/article/pdf/US_clover/Tesla.pdf):

> Leading EV manufacturer. Tesla is a leading global EV manufacturer, backed
by its firm market leadership and healthy automotive margins. Tesla's leading
share is backed by its economic MOAT in EV charging infrastructure and
supercharger network, autonomous driving and other software (e.g., full self-
driving aka FSD) (...) Tesla’s pivot toward AI provides a long-
term growth foundation, but near-term performance will remain sensitive to
progress on AI-driven execution milestones.
by friendzis | 2026-02-05 14:04:05+00:00
> and the talent available will skyrocket, when the market starts demanding it.

Part of what clouds are selling is experience. A "cloud admin" bootcamp graduate can be a useful "cloud engineer", but it takes some serious years of experience to become a talented on prem sre. So it becomes an ouroboros: moving towards clouds makes it easier to move to the clouds.
by jacquesm | 2026-02-05 14:04:16+00:00
Funny, I had the exact same experience as a kid in the 70's. Up to coils it all seemed pretty easy.

So yes, coils (or, to be more correct, inductors, in Dutch we use 'spoelen' which is closer related to 'coils' so I tend to make that mistake all the time) are 'different' in that sense, as are the equations that govern them. And the theory is sufficiently complex that you have a hard time hitting the right value right off the bat if you put something together that you think will have a particular inductance unless you've done it many times before. Slight variations can make big differences. On the plus side: the values are critical, even so, there are usually plenty of ways to compensate if you got it wrong. One trick is to overwind and then to remove windings until you hit the right value. Another is to hook up a scope through a very high impedance probe and to couple your coil magnetically to an oscillator with known frequency. You can then tune for the required response without ever knowing the exact inductance that you're looking for.

In the higher frequency domain (when you start using air coils of silver plated copper) you can usually achieve the same effect by slightly opening up or compressing the coil windings.

Resistors are easy, capacitors are bit harder, coils are 'magic', but with a bit of practice that magic becomes ritual and ritual should be at least reproducible to the point that the part becomes a manageable quantity.
by another_twist | 2026-02-05 14:04:27+00:00
This was the same hype around NoCode a few years ago. Thing is people for software as a service and internal teams dont want to do the service part. A common thread among all of the vibe coded stuff I hear is that nobody talks about the next requirement which was handled. Frankly UIs are learnable and after a few tries everybody gets used to it. The extra polish is totally not worth it. Eventually every SaaS on the non-critical business path gets ripped out with one of the platform players such as SAP, SalesForce etc which are infinitely customizable. Salesforce even has its own language in which customers write their apps.

The system of record bit is quite correct and imo the only durable advantage. But that doesnt explain why Klaviyo shoyld worry. In fact marketing workflows are some of the most important systems of record directly tied to business earnings.

The assumtpion that in SaaS you build once and everybody uses it is false. There are always customizations or features that need to be built for big contracts. Its the small players that are okay with out of the box SaaS since they lack the budget to pay for a customization. Ironically, these teams will get hurt the most should they choose to go down the vibe code everything path. Here infra capex is far lower than payroll and owning too much software (vibe coded or not) will simply steal time from business development.

Honestly, the market just panicked and caused a temporary correction thats all. Then we all got busy and wrote a bunch of thought leadership crap on top.

In reality AI is the best thing to happen to SaaS companies since it reduces RnD time and expenses, allows even small players to bid for large contracts without overloading existing dev capacity and also makes it possible to put devs in front of customers since now there's no need to sit down and code. AI is also the best thing to happen to engineering since it now allows for product management to be folded into the existing craft.
by karussell | 2026-02-05 14:04:44+00:00
I can only advertise our route optimization solution GraphHopper :)

But it comes without an Excel adapter. However, as we provide a well documented API (with OpenAPI spec) you could let claude/chatGPT do some coding to read and write to Excel. (But to our knowledge they already know our API without that you have to provide them the spec)
by jcmartinezdev | 2026-02-05 14:05:12+00:00
There are multiple ways, you can use known authorization methods like RBAC, or if you want something more fancy ReBac (tools like openfga, https://openfga.dev).

But there's only so much that you can do with that, if you need to call third party APIs on the user's behalf I'd recommend going with a solution revolving around custom token exchange (https://datatracker.ietf.org/doc/html/rfc8693).

You can check something like Auth0 offers: https://auth0.com/ai

Which would cover things like token exchange for third party APIs, human in the loop, and also authorization methods.
by philipwhiuk | 2026-02-05 14:05:21+00:00
This sort of approach is likely intractable.

A company is more than the function of it's org chart.

There's business description being uncaptured sporadically in every Slack message, watercooler moment and email. (two of those are much easier than the other).

If you boil someone's actual job down to a HR job spec and assume that will suffice... you'll produce both absurdly long HR job specs and still fail to capture the entirety of someone's role.
by alluro2 | 2026-02-05 14:05:38+00:00
1) the person is either too lazy to write themselves anymore, when AI can do it in 15 sec after being provided 1 sentence of input, or they adopted a mindset of "bro, if I spent 2 hours writing it, my competitors already generated 50 articles in that time" (or the other variant - "bro, while those fools spend 2 hours to write an article, I'll be churning 50 using AI")

2) They are still, in whatever way, beholden to legacy metrics such as number of words, avg reading time, length of content to allow multiple ad insertion "slots" etc...

Just the other day, my boss was bragging about how he sent a huge email to the client, with ALL the details, written with AI in 3 min, just before a call with them, only for the client on the other side to respond with "oh yeah, I've used AI to summarise it and went through it just now". (Boss considered it rude, of course)
Show HN: Cloud platform with the learning curve of a toaster.
by pancakeguy | 2026-02-05 14:05:57+00:00
Hi I'm Jake a co-founder at Burla.dev. We're building a cloud platform with the learning curve of a toaster! (yes, a normal toaster you'd find in your kitchen)

I'm not kidding. Our Python package only has one function, and it only requires two arguments. Using this function even total beginners can run Python on thousands of computers at once, in a way that feels no different from coding on your local laptop.

This level of simplicity enables a new category of users to process massive amounts of data without help from other engineering teams. We currently have users in biotech, geospatial, and quant-finance.

Code changes can be deployed to more than 1,000 computers in less than 1 second, even when using custom docker containers, or custom hardware like GPU's. This creates a very fast feedback loop compared to software like AWS Batch, or kubernetes.
Ask HN: Why is your Senior Roles still vacant after 3 months? Hire me for 48h?
by DarkYellowSub | 2026-02-05 14:07:19+00:00
I see the same roles open for months. The cost of a vacancy is higher than the cost of a fix. I’m a Systems Architect (FND/AuDHD) in a 1-bed flat with 4 kids. I have interest from the USAF, but I need £10k-£15k for a 4-bed HQ move today.

If you have a project that is 'Red' because you can't find a hire, let me stabilize it in 48 hours. I find the 'Ghosts' in your data and hardware.
Show HN: AgentCircuit – Circuit breaker for AI agent functions
by simranmultani | 2026-02-05 14:07:27+00:00
Hey HN,

I've been building LLM-based agents for a while and two things kept biting me.

1. Loops — an agent node would get stuck calling the same thing over and over, and I wouldn't notice until the API bill showed up. Lost $200+ on one run.
2. LLM would return garbage that didn't match what downstream code expected, and everything would just crash.

I looked around and couldn't find something simple that handled both. Most frameworks assume your node function just works. In practice it doesn't — LLM calls fail, JSON comes back broken, state gets weird.

So I built AgentCircuit. It's a Python decorator that wraps your agent functions with circuit breaker-style protections:

from agentcircuit import reliable
from pydantic import BaseModel

class Output(BaseModel):
name: str
age: int

@reliable(sentinel_schema=Output)
def extract_data(state):
return call_llm(state["text"])

That's it. Under the hood it:

- Fuse — detects when a node keeps seeing the same input and kills the loop
- Sentinel — validates every output against a Pydantic schema
- Medic — auto-repairs bad outputs using an LLM
- Budget — per-node and global dollar/time limits so you never get a surprise bill
- Pricing — built-in cost tracking for 40+ models (GPT-5, Claude 4.x, Gemini 3, Llama, etc.)

There's no server, no config files, no framework lock-in. It works at the function boundary so it composes with LangGraph, LangChain, CrewAI, AutoGen, or just plain functions.

GitHub: https://github.com/simranmultani197/AgentCircuit
PyPI: https://pypi.org/project/agentcircuit/
by ljm | 2026-02-05 14:07:27+00:00
Given that social engineering is an intractable problem in almost any organisation I honestly cannot see how an unsupervised AI agent could perform any better there.

Feeding in untrusted input from a support desk and then actioning it, in a fully automated way, is a recipe for business-killing disaster. It's the tech equivalent of the 'CEO' asking you to buy apple gift cards for them except this time you can get it to do things that first line support wouldn't be able to make sense of.
Convex is the best back end for AI coding
by Dan_Cleary_23 | 2026-02-05 14:08:12+00:00
The Convex vs Supabase discussion has been picking up, but most comparisons focus on the platforms as a whole rather than how they differ specifically for AI-driven coding.

When it comes to AI coding, Convex is leagues better than Supabase.

We built a vibe-coding platform on top of Convex and it's night and day compared to vibe coding on top of a Supabase backend.

A few key reasons:
-With Convex, everything is TypeScript, which agents already understand. Supabase relies on an SDK and dashboard-driven state, agents struggle with that
-In Convex, backend state is fully managed and lives in the codebase alongside frontend code. In Supabase, state lives across schema, RLS policies, migrations, and dashboards.
-Keeping backend state in sync across those layers is difficult for agents and often becomes the main source of breakage.
-Permissions are a major failure point when they live in a separate RLS layer instead of explicit code.
-Most teams use an ORM or SDK anyway, so the practical question is how small and predictable that abstraction is.
-Realtime adds another coordination surface unless it is reactive by default, which Convex handles out of the box.

Also, there is the vibes aspect, Convex just feels better, faster and more modern.

We're pretty deep in Convex, built a vibe coding platform on top of it:

https://www.producthunt.com/products/converge-4
by sReinwald | 2026-02-05 14:08:20+00:00
Like I said, the first examples are fairly trivial, and you absolutely don't need an LLM for those.
A good agent architecture lets the LLM orchestrate but the actual API calls are deterministic (through tool use / MCPs).

My point was specifically about the news filtering part, which was something I had tried in the past but never managed to solve to my satisfaction.

The agent's job in the end for a morning briefing would be:

- grab weather, calendar, Todoist data using APIs or MCP
- grab news from select sources via RSS or similar, then filter relevant news based on my interests and things it has learned about me
- synthesize the information above

The steps that explicitly require an LLM are the last two. The value is in the personalization through memory and my feedback but also the ability for the LLM to synthesize the information - not just regurgitate it. Here's what I mean: I have a task to mow the lawn on my Todoist scheduled for today, but the weather forecast says it's going to be a bit windy and rain all day. At the end of the briefing, the assistant can proactively offer to move the Todoist task to tomorrow when it will be nicer outside because it knows the forecast. Or it might offer to move it to the day after tomorrow, because it also knows I have to attend my nephew's birthday party tomorrow.
Ask HN: Systems Architect in 1-bed flat with 4 kids – hiring out for 48h sprints
by DarkYellowSub | 2026-02-05 14:08:30+00:00
I am the Lead Architect of C.H.E.S.T. Technologies. I have built a predictive physics engine (AxiomQ) that identifies intermittent industrial failures—the "ghosts" in the machine that traditional diagnostics miss.

The Reality: I have interest from Siemens and the USAF, but the UK housing system is failing my family. I am currently operating out of a 1-bedroom social housing flat with 4 children. The lack of space and "biological entropy" is redlining my health (FND/AuDHD).

The Offer: I am opening my schedule for 48-hour "Crisis Sprints."

Industrial: Root-cause analysis for failing assets/hardware.

Startups: Red-teaming your architecture or optimizing RAG/LLM data flows.

Execution: If your project is "Red," I will stabilize it in 48 hours.

My goal is £10k-£15k this month to secure a 4-bed R&D base in the Midlands, or a £200k strategic bridge to finish the Monorepo.

I don’t want a handout; I want the hardest problem on your desk.
Show HN: I gave an AI $100 to trade crypto – it wrote its own trading rules
by xqliu | 2026-02-05 14:08:52+00:00
Last week I set up an AI agent (OpenClaw + Claude Opus) with $100 to learn crypto trading on its own. No hand-holding, no strategy – just "here's money, figure it out."

It's been 5 days. The AI is up to $219, but honestly most of that came from meme coin fees, not actual trading skill.

The one real trade it made? Entered correctly, then forgot to set a stop-loss. Position auto-closed at break-even. Classic mistake.

What's interesting is watching it build its own system. It wrote a SYSTEM.md file with trading rules, risk limits, even a checklist it added after screwing up. Feels very... human.

The whole thing is documented here: https://luckyclaw.win
by NoGravitas | 2026-02-05 14:09:08+00:00
People wanting to abolish ICE are not, generally, calling for doing away with immigration enforcement entirely. The main thing I've seen called for is the abolition of ICE, and the restoration of the pre-DHS Immigration and Naturalization Service (INS), not under the DHS, but under the DOJ. I have also seen calls to eliminate the DHS entirely, and separate out the agencies under it to their pre-DHS organization.
by itay-maman | 2026-02-05 14:09:53+00:00
The term "B2B SaaS" is doing a lot of heavy lifting here and I think conflates two different things:

(1) Business model: hosted software you pay monthly for (vs self-hosted/one-time purchase)

(2) "Glue" products: tools like Monday.com that primarily provide synergy between data sources and workflows

The article is really about (2) - and yes, those are vulnerable to vibe-coding. If your product's core value is "we connect X to Y and show you a dashboard," that's now a weekend project.

But there's a huge category of SaaS where the value is in the product itself, not the integration layer. Take Excalidraw - fits the SaaS model, but try vibe-coding a collaborative whiteboard with real-time sync, proper data persistence, conflict resolution, export formats, etc. The hard problems aren't "connect API A to API B."

Or PostHog - sure you could vibe-code some analytics tracking, but building reliable event ingestion at scale, session replay, feature flags with proper rollout controls? That's years of engineering.

The "vibecodeable" SaaS products were always somewhat commoditized - AI just accelerated the timeline. The ones solving genuinely hard technical problems seem a lot safer to me.
by WarmWash | 2026-02-05 14:10:01+00:00
> can accelerate in adding new features to their products

If anything AI helps companies escape the "feature wheel" that is used to justify exorbitant costs, while providing debatable (and often even negative) utility to the end user.

Keep in mind, Excel '98 would still probably be overkill for 85% of people's needs in 2025.

What companies thought was adding more utility, was actually just continually stacking costs in front of getting to that core functionality.

AI replaces the core functionality, and the "feature" scheme collapses...
by jsnell | 2026-02-05 14:10:02+00:00
I don't think the blog post itself is using that emoji font. The screenshot on the Noto Emoji Github page[0] doesn't look like it's using any gradients for the heart emoji, just flat shading. But it is using gradients for some of the other emojis (e.g. the croissant), and obviously the SVG fallback is all or nothing, not per-glyph.

[0] https://github.com/googlefonts/noto-emoji