MurphyA/hacker-news huggingface dataset:
by twodave | 2026-03-06 18:41:42+00:00
I am beginning to disagree with this, or at least I am beginning to question its universal truth. For instance, there are so many times when "learning" is an exercise at attempting to apply wrong advice many times until something finally succeeds.

For instance, retrieving the absolute path an Angular app is running at in a way that is safe both on the client and in SSR contexts has a very clear answer, but there are a myriad of wrong ways people accomplish that task before they stumble upon the Location injectable.

In cases like the above, the LLM is often able to tell you not only the correct answer the first time (which means a lot less "noise" in the process trying to teach you wrong things) but also is often able to explain how the answer applies in a way that teaches me something I'd never have learned otherwise.

We have spent the last 3 decades refining what it means to "learn" into buckets that held a lot of truth as long as the search engine was our interface to learning (and before that, reading textbooks). Some of this rhetoric begins to sound like "seniority" at a union job or some similar form of gatekeeping.

That said, there are also absolutely times (and sometimes it's not always clear that a particular example is one of those times!!) when learning something the "long" way builds our long term/muscle memory or expands our understanding in a valuable way.

And this is where using LLMs is still a difficult choice for me. I think it's less difficult a choice for those with more experience, since we can more confidently distinguish between the two, but I no longer think learning/accomplishing things via the LLM is always a self-damaging route.
by aquariusDue | 2026-03-06 18:41:47+00:00
Not OP and I won't dispute your point exactly but I'd like to point to a book called Pixel Logic wherein the author makes the same point regarding pixel art. Even though you'll be using stuff like the Lasso and Paint Bucket tools the big thing about pixel art is the manual control and precision of pixel placement (by hand) where you employ techniques like anti aliasing (again by hand). Advanced techniques like sub-pixeling when doing animation frames are another thing that makes sense only when you can place pixels one by one.
by xrd | 2026-03-06 18:41:54+00:00
Two reasons. One, they have already filled it internally but legally have to post the job. Two, they are gathering data on market trends and what salaries people will take, which is useful if they are considering firing people and rehiring with lower salaries.

I've applied for many jobs where I was perfectly qualified and got rejection notices immediately. I applied on a Sunday and got rejected on Sunday an hour later. No human reviewed that application I made, it was auto rejected, and if that's the case, what other explanation is there than "ghost jobs."
by WillMorr | 2026-03-06 18:42:17+00:00
I've been working on a surprisingly similar project for the last week: plants grow cells on a grid by executing a raw chunk of memory according to a simple instruction set. I'm aiming more for an evolution simulator, where each plant gets a 1kb brain that is randomized a little when a new plant is spawned.

Most plants right now settle into a simple goto loop that places the requisite cells to survive and then spam seeds until they die. I have seen some interesting variety in body plans emerge where plants sort into discrete species regionally. I'm hoping to eventually get decision making to emerge organically. If things go well this system is theoretically capable of sexual selection (and maybe fisherian runaway) but that's a pipe dream right now.

https://github.com/Will-Morr/PlantBrainGrid
by uqual | 2026-03-06 18:42:20+00:00
The CBP seems to be asserting that they lack the technical resources to issue the refunds in a timely fashion. Thus, when they finally comply, they (well, the US taxpayer) will end up paying more interest - probably around $20M/day (assuming 4% and $175B in illegal tariffs collected).

Perhaps this Administration should ask Musk to bring in a team to revamp the systems involved to get these refunds "in the mail" quickly. The DOGE team must be done with the Social Security system rewrite by now so may be available for this task. Maybe Big Balls is free this weekend to take care of this...
by hellojesus | 2026-03-06 18:42:33+00:00
Lol I remember back in the day when we used to replace the windows logo during boot with our own bitmaps (if I can appropriately remember the file format) at school. We showed kids and suddenly every computer was booting with unexpected media. Admins were not pleased.

But the real fun began when we showed people how to set bios passwords and that cascaded into kids rendering an entire classroom of computers unbootable.

And then there was the time I thought I was really clever because I realized I could open arbitrary files in notepad, so I attempted to edit save files for a learn-to-type program by replacing the score with my own. It seemed to work so I told my friends and then they started copying the same save file into their program files. I don't remember exactly what happened, but I do know the UI update did not propagate to the actual scores and also it introduced a bug into the prodgram which would cause it to crash at distant future epochs, so we destroyed the program for everyone, not just our user profiles. There was an investigation and I think they gave up because the same bad file somehow was on everyone's computer and everyone just told them they got the file from someone else and there was no root of the chain.

This is all to say, any bypass will be identified and implemented at the speed of virality.
by thighbaugh | 2026-03-06 18:42:46+00:00
Since these things can be made into forks with minor difference relatively easily, instead of playing along with this tech company + creepy government data grab because California says so

So much for privacy I guess, hence pulling out this protecting children BS that I saw too many kids at my urban CA highschool get stabbed to fall for. The fact these tactics still work, where we limit our toothless privacy protections that the firms that don't comply the state might eventually sue when someone with more money than I presses the Attorney General, but then dial it back marketing it as protecting children and people still buy it? Absurd these same people work at such bleeding edge tech firms but then again LLMs can do that busy work they actually are doing better most of the time....
by mushufasa | 2026-03-06 18:42:46+00:00
I spent time looking into this a couple years ago as a startup founder with this problem. We are in the finance space so I saw how bad the treasury options were with our bank, given their fee cut versus plain T-bonds at the time. I looked into which brokerages allowed us to setup self-directed accounts (many banks don't offer that for businesses at all). I found the "correct" approach. But then there would be more paperwork and back and forth to set up that new account, then manage transferring money around when we needed it, logging into a different system. On a ski trip a friend in finance told me "you're being dumb, if your bank offers you a treasury plan with a one click button, even if it's not perfect, click that button now!" So I did.

Then, the benefit of saving 1-2% extra versus spending my time trying to actually running the business and doing things with our money in the real world, has meant I have never looked back. 1-2% on millions of dollars is significant but it's not nearly as impactful as finding Product-Market-Fit in your actual business.

All this to say: I'd be in your target market but I'm simply not interested in a "marginally better" treasury system versus just going with my bank's options that make it easy for me.
300 Founders, 3M LOC, 0 engineers. Here's our workflow
by parsak | 2026-03-06 18:43:00+00:00
My co-founder Tyler Brown and I have been building our product for 6 months. The co-working space that Tyler founded that we work out of houses 300 founders that we've gleaned agentic coding tips and tricks from.

Neither of us came from traditional SWE backgrounds. Tyler was a film production major. I did informatics. Our codebase is a 300k line Next.js monorepo and at any given time we have 3-6 AI coding agents running in parallel across git worktrees.

Every feature follows the same four-phase pipeline, enforced with custom Claude Code slash commands:

1. /discussion - have an actual back-and-forth with the agent about the codebase. Spawns specialized subagents (codebase-explorer, pattern-finder) to map the territory. No suggestions, no critiques, just: what exists, where it lives, how it works. This is the rabbit hole loop. Each answer generates new questions until you actually understand what you're building on top of.

2. /plan - creates a structured plan with codebase analysis, external research, pseudocode, file references, task list. Then a plan-reviewer subagent auto-reviews it in a loop until suggestions become redundant. Rules: no backwards compatibility layers, no aspirations (only instructions), no open questions. We score every plan 1-10 for one-pass implementation confidence.

3. /implement - breaks the plan into parallelizable chunks, spawns implementer subagents. After initial implementation, Codex runs as a subagent inside Claude Code in a loop with 'codex review --branch main' until there are no bugs. Two models reviewing each other catches what self-review misses.

4. Human review. Single responsibility, proper scoping, no anti-patterns. Refactor commands score code against our actual codebase patterns (target: 9.8/10). If something's wrong, go back to /discussion, not /implement. Helps us find "hot spots", code smells, and general refactor opportunities.

The biggest lesson: the fix for bad AI-generated code is almost never "try implementing again." It's "we didn't understand something well enough." Go back to the discussion phase.

Wrote up the full workflow with details on the death loop, PR criteria, and tooling on my personal blog, can share if folks are interested.

All Claude Code commands and agents are open source: https://github.com/Dcouple-Inc/Pane/tree/main/.claude/commands

I built Pane using this workflow over the last month or so and started using it every day a little over a week ago. Each workspace gets its own worktree and session. Takes me less than 30s to go from idea -> discussion now. The repo link above takes you to it.

On a good day I merge 6-8 PRs. Happy to answer questions about the workflow, costs, or tooling for this volume of development.
by levkk | 2026-03-06 18:43:56+00:00
As the tool gets better, people trust it more. It's like Tesla's self-driving: "almost" works, and that's good enough for people to take their hands off the wheel, for better or for worse.

The "almost" part of automation is the issue + the marketing attached to it of course, to make it a product people want to buy. This is the expected outcome and is already priced in.
by phendrenad2 | 2026-03-06 18:44:03+00:00
> Top candidates are commanding higher salaries than ever

I haven't found that to be true. Unless by "top candidates" you mean people working at actual AI companies such as Alphabet/Meta/OpenAI/Anthropic. If you're an AI-user and not an AI scientist it's bad out there, even for senior+ developers who previously worked in "FAANG".
by forgotaccount3 | 2026-03-06 18:44:30+00:00
Yes, backups are great but a 'dumb robot' or a 'mistaken junior' shouldn't have access to prod.

And a sleep-deprived senior? Even then. They shouldn't have access to destructive effects on prod.

Maybe the senior can get broader access in a time-limited scope if senior management temporarily escalates the developers access to address a pressing production issue, but at that point the person addressing the issue shouldn't be fighting to stay awake nor lulled into a false sense of security as during day to day operations.

Otherwise it's only the release pipeline that should have permissions to take destructive actions on production and those actions should be released as part of a peer reviewed set of changes through the pipeline.
by BobaFloutist | 2026-03-06 18:44:33+00:00
>it is unthinkable for some professional with a master's degree to become a warehouse sorter.

I mean I think you do actually have a salient point, but I also think there's a material difference between telling someone that's maybe been paid not a lot for half a of labor that they need to change industries and someone who's tens of thousands of dollars into debt that the implied social contract encouraging that debt was a house of cards and they need to start from scratch with 0 experience even ever being employed.
by hellojesus | 2026-03-06 18:44:36+00:00
Agreed. Which is why I think the OS level is dumb. Kids can just live boot or launch a vm or keylog their parents' account.

If it's windows, they can just live boot into the OS and get access to pretty much all the files anyway, if the parent didn't encrypt things.

My point is, if the implementation is trivial to bypass, why do we need this legislation? Just let the parents use the existing tools we have and parent.
by arikrahman | 2026-03-06 18:44:50+00:00
The perception seems to be that AI is only causing security vulnerabilites (see: openclaw injection in npm (Clinejection)). But the article's optimistic tone much reflects my own, and if it were all bad, then nobody would be using AI. But it's mostly good, and with the benchmarks, it's a statistical fact that it helps more than it hurts. It's just math at a certain point.
by adrian_b | 2026-03-06 18:45:27+00:00
During the Paleogene, the terrestrial plants and animals were very different from those of today.

Now on all continents and islands most of the big animals and plants are humans, domestic animals and cultivated plants. The wild animals and plants, even if they are much more varied, with many thousands times more species than the domestic ones, are much smaller in quantities, with only a few kinds that are non-negligible, e.g. ants, termites, rodents.

So if we will return in a short time to the Paleogene climate, the main question is how this will affect the few dominant animal species, like chicken, humans, pigs, sheep, cattle, dogs and the main cultivated plants, all of which are not adapted to a Paleogene climate and which will not be able to adapt in such a short time.

It is likely that places like Canada, Alaska, Greenland, Siberia, Antarctica might become nicer places where to live and practice agriculture, but the few people who live now there would not welcome invaders coming from places that are no longer habitable.
by robocat | 2026-03-06 18:45:31+00:00
> Exactly - go give someone you love a hug, that's worth infinitely more than flexing an expensive watch.

Hugs are massive signals of status (who, where, initiator, awkwardness, yada yada).

My fascination with the politics of hugs might be called autistic by some.

I wonder whether my own status avoidance is on account of being bad at playing at ladders.
by es617 | 2026-03-06 18:45:37+00:00
That’s a really interesting way to frame it — showing the flow of prompts and responses rather than just the final result.

I’ve mostly been using it for demos and sharing sessions with teammates, but the training / best-practices angle is a great point.

On navigation: you can already step through turns with the arrow keys or jump around the timeline, so you don’t have to sit through long generations. But I agree that smarter defaults (skipping or collapsing long runs) could make it smoother.

And the Loom comparison is interesting — I hadn’t thought about the workspace/permission side yet since this started as a small CLI tool for sharing sessions, but that’s a good direction to think about.
by mrweasel | 2026-03-06 18:45:41+00:00
Maybe I'm reading the graph wrong, but the decrease comes after years on continuous growth, so total employment numbers in tech should still be absolutely massive, compared to 18 years ago?

If it continues, then yes it could be bad, but so far it seems like a correction for over-hiring in 2021 - 2023. Seems a little weird to be focusing on a decline in 2024 - 2026, without addressing the large increase right in the years before.
by taylorsatula | 2026-03-06 18:46:06+00:00
Most prompt engineering is done by changing words, running the model, and squinting at the output. Over the past few weeks I've built this toolkit which lets you measure what's actually happening inside the model instead.

You define regions of your prompt (instructions, examples, constraints, whatever), run the pipeline on any HuggingFace model, and get back per-layer attention heatmaps, cooking curves showing how attention to each region evolves through the network, and logit lens snapshots. Supports Llama, Qwen, Mistral, Gemma out of the box. Self-contained engine script you can scp to a GPU box and run with no dependencies beyond transformers. The repo is designed so that Claude can handle the whole pipeline end-to-end including interpreting results in a grounded domain-specific way.

I built it to tune system prompts for another project and realized the general approach was useful enough to extract. The "before and after" comparison tooling ended up being the part I use most.
by devin | 2026-03-06 18:46:10+00:00
My observation has been that there are a lot of personal styles to engaging with the LLMs that work, and "hold the hand" vs "in-depth plan" vs "combination" doesn't really matter. There is some minimum level of engagement required for non-trivial tasks, and whether that engagement comes mid-development, at the early design phase, or after isn't really that big of a deal. Eg; "Just enough planning" is a fine way of approaching the problem if you're going to be in the loop once the implementation starts.
Show HN: Mog, a programming language for AI agents
by belisarius222 | 2026-03-06 18:46:10+00:00
I wrote a programming language for extending AI agents, called Mog. It's like a statically typed Lua.

Most AI agents have trouble enforcing their normal permissions in plugins and hooks, since they're external scripts.

Mog's capability system gives the agent full control over I/O, so it can enforce whatever permissions it wants in the Mog code. This is even true if the plugin wants to run bash -- the agent can check each bash command the Mog code emits using the exact same predicate it uses for the LLM's direct bash tool.

Mog is a statically typed, compiled, memory-safe language, with native async support, minimal syntax, and its own compiler written in Rust and its own runtime, also written in Rust, with `extern "C"` so the runtime can easily be embedded in agents written in different languages.

It's designed to be written by LLMs. Its syntax is familiar, it minimizes foot-guns, and its full spec fits in a 3200-token file.

The language is quite new, so no hard security guarantees are claimed at present. Contributions welcome!
by krisoft | 2026-03-06 18:46:14+00:00
> If they had direct evidence that some author's instructions failed to ask for the case study to be fictionalized, I think they would have specifically said that.

Which they do. They specifically say that. “Neither the instructions for authors from 2010 — when Koren and his coauthor Michael Rieder would have written their article — nor the linked list of article types — state the cases are fictionalized, or fictional.”

“An archived version from September stated, ‘Each highlight is a teaching tool that presents a short clinical example, from one of the studies or one-time surveys,’ with no mention of fiction.”

These are direct quotes from the article. The exact kind you are asking for. With inline links to the archived documents. And yes it is very definitive.

> I'm pretty sure what happened here is that:

No need to speculate. Just read the article.

> 1) The journal always asked for […] fictionalized case studies.

This is false. As evidenced by the article.
by m727ichael | 2026-03-06 18:46:18+00:00
nformation architecture for AI reasoning. PromptOS structures rigorous thinking (7 or 8-step pipelines). HITL Context Engine manages cross-domain problems with human guidance. Both work with any model—Claude, GPT-4, Gemini. Copy, paste, use immediately. MIT licensed, freeware logic.
GitHub: m727ichael/context-engineering
by carderne | 2026-03-06 18:46:23+00:00
How does this work with self-hosting? Is the assumption that self-hosters won’t run into this problem?

For most use-cases I’d probably prefer to just delete the payloads some time after the job completes (persisting that data is business logic problem). And keep the benefits of “just use Postgres”, which you guys seem to have outgrown.
by renewiltord | 2026-03-06 18:46:33+00:00
I don’t use Terraform much anymore because don’t need it but that’s not how you use it.

Always forward evolve infra. Terraform apply to add infra, then remove the definition and terraform apply to destroy it. There’s no use in running terraform destroy directly on a routine basis.

Also, I assume you defined RDS snapshots also in the same state? This is clearly erroneous. It means a malformed apply human or agent results in snapshot deletion.

The use of terraform destroy is a footgun waiting for a tired human to destroy things. The lesson has nothing to do with agent.
by rconti | 2026-03-06 18:47:22+00:00
I don't visit Canada for the same reason I don't do a whole lot of touristy stuff here in the US: The travel costs aren't really _that_ much cheaper vs going somewhere more exotic like South America, Europe, Asia, etc, and it feels a bit too much like "home".

Living on the west coast, Vancouver's the easiest to get to -- I love Vancouver (and Victoria), and I've been both places several times, and I've gone to Whistler a handful of times as well, but, again, it's a lot like where I grew up in Seattle.

I really do want to visit Montreal sometime, but I also want to visit Chicago and Memphis and a lot of other "domestic" locations that I somehow never find the time for.

Also, when you grow up in a country you have a lot of local knowledge from culture, friends, television, education, so we just know a lot more about domestic places we haven't (yet) visited. Plus, a substantial number of people don't have passports. We used to be able to visit Canada easily without one, now we cannot.
by yesb | 2026-03-06 18:47:30+00:00
Relating it to performance is just silly. Most companies barely understand the performance of their employees much less candidates. The market has shrunk but not catastrophically so. Most people haven't been majorly affected but that doesn't mean they're automatically the most deserving or best performing.

People with experience and/or credentials desired by companies in areas of growth (i.e. AI) are always in high demand
by pm90 | 2026-03-06 18:47:43+00:00
I don’t believe this is true. There are plenty of roles that are happy to hire remotely. Sure, there is an in person requirement for many job listings but Ive found EMs/companies to be very flexible if they need to hire talent.

For people that can’t/dont want to move to the “hubs”, just know that there is absolutely still a career path. I will say though that you need to have above average communication skills and proactively build relationships during in person off-sites.
by 8note | 2026-03-06 18:47:46+00:00
ive had it write some good cdk, but only as a one off project. havent tried any maintenance, but the deployment of infrastructure should also go through CI/CD, so the only thing i could destroy is a local playground

i did have to fight it to build the right thing - it wanted to spend something like $100/month but what i had in mind should have been <1, and i eventually got it there.

something i found handy prompt wise was to keep asking claude to predict the monthly cost after builds