MurphyA/hacker-news huggingface dataset:
by prmph | 2025-06-03 00:51:23+00:00
Technology improving is not the issue.

1. LLM fanboy: "LLMs are awesome, they can do x, y, and z really well."

2. LLM skeptic: "OK, but I tried them and found them wanting for doing x, y, and z"

3. LLM fanboy: "You're doing it wrong. Do it this way ..."

4. The LLM skeptic goes to try it that way, still finds it unsatisfactory. A few months pass....

5. LLM fanboy: "Hey, have you tried model a.b.c-new? The problems with doing x, y, and z have now been fixed" (implicitly now agrees that the original complaints were valid)

6. LLM skeptic: "What the heck, I though you denied there were problems with LLMs doing x, y, and z? And I still have problems getting them to do it well"

7. Goto 3
by DarmokJalad1701 | 2025-06-03 00:51:34+00:00
> It took less time to hand-edit one based on reading the docs.

You can give it the docs as an "artifact" in a project - this feature has been available for almost one year now.

Or better yet, use the desktop version + a filesystem MCP server pointing to a folder containing your docs. Tell it to look at the docs and refactor as necessary. It is extremely effective at this. It might also work if you just give it a link to the docs.
by kasey_junk | 2025-06-03 00:51:49+00:00
When you wire them up to your cicd process with pull requests and the github gui as your interface, rather than sitting there passively riding along as it prompts you the changes it’s going to make.

With my async agent I do not care about how easy it is for me, it’s easier to tell the agent to do the workflow and comeback to it later when I’m ready to review it. If it’s a good change I approve the pr, if not I close it.
by killerstorm | 2025-06-03 00:52:32+00:00
Bullshit. We have absolute numbers, not just vibes.

The top of SWE-bench Verified leaderboard was at around 20% in mid-2024, i.e. AI was failing at most tasks.

Now it's at 70%.

Clearly it's objectively better at tackling typical development tasks.

And it's not like it went from 2% to 7%.
by timr | 2025-06-03 00:52:33+00:00
> Or for a lot of libraries you can dump the ENTIRE latest version into the prompt - I do this a lot with the Google Gemini 2.5 models since those can handle up to 1m tokens of input.

See, as someone who is actually receptive to the argument you are making, sometimes you tip your hand and say things that I know are not true. I work with Gemini 2.5 a lot, and while yeah, it theoretically has a large context window, it falls over pretty fast once you get past 2-3 pages of real-world context.

> "they fail at doing clean DRY practices" - tell them to DRY in your prompt.

Likewise here. Simply telling a model to be concise has some effect, to be sure, but it's not a panacea. I tell the latest models do do all sorts of obvious things, only to have them turn around and ignore me completely.

In short, you're exaggerating. I'm not sure why.
by runjake | 2025-06-03 00:52:51+00:00
You’re not providing a key piece of information to provide you with an answer: what were the prompts you used? You can share your sessions via URL.

A prompt like “Write a $x program that does $y” is generally going to produce some pretty poor code. You generally want to include a lot of details and desires in your prompt. And include something like “Ask clarifying questions until you can provide a good solution”.

A lot of the people who complain about poor code generation use poor prompting.
by consumer451 | 2025-06-03 00:53:21+00:00
I am just a muggle, but I have been using Windsurf for months and this is the only way for me to end up with working code.

A significant portion of my prompts are writing and reading from .md files, which plan and document the progress.

When I start a new feature, it begins with: We need to add a new feature X that does ABC, create a .md in /docs to plan this feature. Ask me questions to help scope the feature.

I then manually edit the feature-x.md file, and only then tell the tool to implement it.

Also, after any major change, I say: Add this to docs/current_app_understanding.md.

Every single chat starts with: Read docs/current_app_understanding.md to get up to speed.

The really cool side benefit here is that I end up with solid docs, which I admittedly would have never created in the past.
by fn-mote | 2025-06-03 00:54:05+00:00
Instead of just disagreeing, I find I actually agree! At least with the premise of the I/O bound system.

At some point I realized that linear writing (typing or writing on lined paper) does not have the flexibility to express the thought processes that I want to commit to writing.

Now I write on blank paper (or an iPad if the thinking needs to be active for a long period of time).

I might be I/O bound but at least this way I don't need Serializable thoughts.
by kcplate | 2025-06-03 00:54:21+00:00
I am aware of the history and used the term intentionally. Historically, one of the chief complaints from those English workers (along with their compensation concerns…but there are always compensation concerns when human labor is changed in any way) was how the automated machines would lower the quality of the textiles.

The commenter I was responding to was specifically speaking to code quality concerns generated by AI automation. While the modern usage of “Luddite” tends to generalize towards rejection of any new technology. When I mentioned “Luddite-like rejection of the technology because of some offended artistic notions” it was specific to the Luddite complain that the automation of would lower quality.

That might be a specific detail in the history that you may have missed, forgotten, or perhaps simply ignored—but it’s an important detail with a direct parallel in this conversation.
by leecarraher | 2025-06-03 00:56:18+00:00
It depends on what level of nuts you mean. Some are AGI skeptics about LLMs, theyre probably right, there is likely more breakthroughs required before true AGI. But AGI isn't required to completely disrupt a ton of good, well-paid professions. That is the more worrying scenario. AI is already widening the wealth gap irreparably and with more progress it will only continue.
by ketzo | 2025-06-03 00:56:35+00:00
I think it’s just fairly rare that formal verification is valuable to a business.

Obviously all software benefits from correctness — but we all know that software certainly doesn’t need to be bug-free to make money!

And if the benefits of formal verification don’t outweigh the (non-trivial!) costs — and critically, outweigh them in a business-person-legibile way — then people won’t put up the time and effort.
by Aurornis | 2025-06-03 00:56:47+00:00
> I'm going to go ahead and press (X) to doubt on this anecdote. You've had an issue for months and the logs were somehow so arcane, so dense, so unparseable, no one spotted these "metadata corruption issues?" I'm not going to accuse anyone of blatant fabrication, but this is very hard to swallow.

I have this problem with a lot of LLM miracle anecdotes. There’s an implication that the LLM did something that was eluding people for months, but when you read more closely they don’t actually say they were working on the problem for months. Just that they were complaining about it for months.
by roasbeef | 2025-06-03 00:57:53+00:00
Lightning Labs | Lightning Infrastructure Engineer, Protocol Engineer | San Francisco | Remote | Full-time

https://lightning.engineering/join-us/

https://github.com/lightninglabs

Lightning Labs is hiring! We’re looking to expand our team to build technology that'll bring Bitcoin to the next billion people. Our current focus is the development and deployment of the Lightning Network, an open blockchain scalability protocol. We push the edge of innovation with regard to blockchain scalability, privacy-preserving smart contracts, and cryptocurrency UX. If you’re interested in one of the positions below, please apply using our careers page: https://lightning.engineering/join-us. And if you know someone who might be a good fit, we'd very much appreciate any referrals.

{Lightning Infrastructure Engineer}:

We're looking for a systems-oriented engineer who will design and build out key components to support the growth of the Lightning Network. These tools will lower the barrier to entry for operating Lightning nodes and enable existing node operators to more effectively manage their infrastructure. You'll work on products such as Lightning Pool (https://lightning.engineering/pool/), as well as other Bitcoin-based backend systems to make Lightning more useable, and secure.

{Protocol Engineer}:

Experienced systems software engineer versed in applied cryptography, peer-to-peer networks, distributed systems, open source software, and cryptocurrency protocols to design and implement core protocol and algorithmic components of the Lightning Network as well as the Bitcoin Network. Solid programming skills, experience with Go, C, or C++. Prior contributions to crypto protocols and open source software collaboration preferred.
by cookiengineer | 2025-06-03 00:58:23+00:00
Seeing everything these days being about vibe coding, I feel a little old with my VIM setup and my LSP servers who I already thought were a nice productivity increase.

The problems I have with the stuff relating to MCP is that the tech around it is developing so fast that it's hard for outsiders to catch up with what the best working setup is, for example.

What would you do, for example, if you want to selfhost this?

- which models (qwen ai coder?)

- which api (with ollama? Bolt? Aider? Etc)

- how to integrate PRs with a local gitlab/gogs/forgejo instance? Do you need another MCP agent for git that does that?

- which hardware dependencies to run it?

I am currently trying to figure out how to implement a practical workflow for this. So far I'm using still a synchronous MCP agent setup where it basically runs on another machine in the network because I have a too unperformant laptop to work with.

But how would I get to the point of async MCP agents that can work on multiple things in my Go codebases in parallel? With the mentioned PR workflows so that I can modify/edit/rework before the merges?

The author makes a lot of claims and talks always about that their opponents in the argument are not talking about the same thing. But what exactly is the same thing, which is reproducible locally for everyone?
by Verdex | 2025-06-03 00:58:24+00:00
Hundreds of comments. Some say LLMs are the future. Others say they don't work today and they won't work tomorrow.

Videogame speed running has this problem solved. Livestream your 10x engineer LLM usage, a git commit annotated with it's prompt per change. Then everyone will see the result.

This doesn't seem like an area of debate. No complicated diagrams required. Just run the experiment and show the result.
by gerdesj | 2025-06-03 00:58:40+00:00
Try getting your fav LLM to do something useful with PowerCLI. That's the VMware PowerShell thing. It is quite popular but not enough, so that most prompts will end up with bollocks, masquerading as code.

When a LLM has been tamed to the point that I can define and request a PowerCLI programme, I can be fairly sure that AI is a solved thing.
by Dracophoenix | 2025-06-03 00:58:45+00:00
And in turn, Star Wars was inspired by the film-work of Akira Kurosawa. Kurosawa's film noir period dramas are different in tone and scope from Toriyama's action-comedy flare and they both differ in subject matter and characterization from Star Wars. For Star Wars, going too far in the pursuit of cool overpowered characters creates difficulties for meaningful plot resolution.
by rudimentary_phy | 2025-06-03 00:59:18+00:00
I type (mostly) correct, but this is true. I'm still using one of the first keyboards I ever bought and the f and j keys have become worn down, so I seem to have learned ways similar to what you're describing.

Different keyboards with macros or weirdly formatted buttons throw me for a loop with this method though, while the f and j keys guarantee correct positioning.
by goosedragons | 2025-06-03 01:00:58+00:00
What 2010 reader did you have? The $140 6" Kobo Clara BW for example is far far better than original $150 6" Kobo of 2010. Screen is much sharper and higher contrast, supports touch, it's way faster, has WiFi, front light, software does more, 16 times the storage. Only thing it lost is SD card support and the shitty dpad and I guess Blackberry integration.

Kindle is a similar story, although some value the physical keyboard and 3G.

And what smaller models? Most eReaders have been 6" since the days of the Sony Librie. Recently we have had explosion of larger readers too.

Now granted, the color models don't have the best contrast, but I'm pretty sure a modern Carta 1300 BW reader will be superior to your what 8 year old Carta HD reader, even with extra layers.
by rbitar | 2025-06-03 01:01:06+00:00
Frontend.co | REMOTE | Full-time & Part-time | https://www.frontend.co

Frontend is building an AI-powered Shopify development platform. We use AI to generate full-stack application built using Next.js / Tailwind for Shopify-connected storefronts.

Experience: 7-10+ years as a full-stack experience with recent experience using TypeScript, Next.js, Tailwindcss, Postgres, and Ruby on Rails. E-commerce development using Shopify GraphQL APIs is a plus. Our tech stack is:

- Next.js - Supabase / Postgres - TypeScript - Tailwind - Ruby on Rails - Shopify Storefront + Admin GraphQL APIs

Send us a note at: info[plus]hn@frontend.co
by 0xbadcafebee | 2025-06-03 01:01:45+00:00
Keep in mind Yakisugi ("shou sugi ban" is a Western misinterpretation circa ~1995) is traditionally performed on wood which is already weather resistant, particularly Japanese Cedar ("sugi" is cryptomeria japonica, a type of cypress endemic to Japan). Even then they still treat it with oil regularly to improve its longevity. So I wouldn't char some white pine and stick it outside and expect it to last.
by ggm | 2025-06-03 01:02:05+00:00
On the whole I dislike "shoot the messenger" but given Bjorn Lomborg is who he is, this is a very one-eyed take on things, and I think demands balance from some other points of view.

I would suggest that we collect them, and then have a fine old discussion about which ones we like and why.

Here's some:

https://reneweconomy.com.au/south-australia-to-spain-does-bl...

https://reneweconomy.com.au/no-batteries-no-flexibility-spai...

https://reneweconomy.com.au/spains-blackout-has-already-trig...
Show HN: Apollo Scraper – Extract and Export Apollo B2B Leads
by qwikhost | 2025-06-03 01:02:23+00:00
Scrape B2B leads from Apollo.io with verified emails, phone numbers & company data. Fast, accurate prospecting.

Unlock Unlimited B2B Lead Generation with Apollo Scraper for Apollo.io Apollo Scraper is a powerful Chrome extension that transforms how you collect and manage leads from Apollo.io. Whether you’re a sales professional, startup founder, recruiter, or B2B marketer, this tool helps you extract verified contacts and company data in bulk — with zero manual effort and no limits.
by tptacek | 2025-06-03 01:02:32+00:00
They are not engagement bait. That argument, in particular, survived multiple rounds of reviews with friends outside my team who do not fully agree with me about this stuff. It's a deeply sincere, and, I would say for myself, earned take on this.

A lot of people are misunderstanding the goal of the post, which is not necessarily to persuade them, but rather to disrupt a static, unproductive equilibrium of uninformed arguments about how this stuff works. The commentary I've read today has to my mind vindicated that premise.
by colesantiago | 2025-06-03 01:02:32+00:00
Here is the pattern of what YC looks for in startups and founders (but they don't tell you):

1. Young 18-24 year olds, (anything beyond this age bracket is suspect to them and highly frowned upon)

2. Stanford, Harvard, MIT, Ivy League, Oxbridge, Ex-FAANG, Ex-Goldman/JPM, Ex-Bain/Bridgewater, Ex-Jane Street/Citadel, etc.

3. New Hyped Industries, (AI, Crypto, Web3, SaaS)

4. Anything on Request For Startups (RFS)

My guess is that YC selected BeerMe because the founders hit all these points and believed they that could pivot beyond the initial pitch of BeerMe.

Most investors now don't invest in the company but in the founders and their ability to pivot or expand their TAM once they capture initial growth and eventually to become revenue generating.

It doesn't look like BeerMe took off as they hoped (AI is the new hotness now not much about crypto) so it looks like they stalled and probably failed in the trough of disillusionment.
by adamjroth | 2025-06-03 01:03:03+00:00
Location: Connecticut, USA

Remote: Yes (20 years experience, efficient, productive, and highly available)

Willing to relocate: For the right position; remote with occasional travel much preferred

---

Seeking part-time or full-time work in development, source code audits, or reworking codebases left in poor shape. Specializes in Ruby, Rails, React Native, Node, React, and Javascript. Experienced in all phases of software development, including architecting solutions from the ground up, reworking/rebuilding/refactoring existing projects, and contributing to modern codebases. Focuses on React Native (core contributor), React, Ruby on Rails, and Javascript/Ruby.

---

Technologies: React Native (core contributor), React, Ruby, Ruby on Rails, JavaScript, Perl, Objective-C, Java, Swift, C, C#, Python, Node.js, Express, PHP, GraphQL (Apollo), Mobile Development (Native: iOS/Xcode, Android/Android Studio, Hybrid: Cordova/Ionic, HTML5/Canvas, CreateJS/ImpactJS/Phaser, Flux (Redux, Alt.js, Mobx)), MySQL, PostgreSQL, MongoDB, Firebase, RSpec, Cucumber, Selenium, Mocha, Jasmine, Sphinx, Solr, Lucene, Elastic Search, AWS (S3, EC2, Lambda, Amplify, RDS, etc), Linux, Apache, Git/GitHub workflow, DevOps, Heroku, JIRA, Confluence, BitBucket, MongoDB, Web3, Crypto, NestJS, TypeScript

Resume: https://docs.google.com/document/d/1kQ6wp-hvewB-fGRNEVnywVpL...

Email: adamjroth@gmail.com
by adamjroth | 2025-06-03 01:03:09+00:00
Location: Connecticut, USA

Remote: Yes (20 years experience, efficient, productive, and highly available)

Willing to relocate: For the right position; remote with occasional travel much preferred

---

Seeking part-time or full-time work in development, source code audits, or reworking codebases left in poor shape. Specializes in Ruby, Rails, React Native, Node, React, and Javascript. Experienced in all phases of software development, including architecting solutions from the ground up, reworking/rebuilding/refactoring existing projects, and contributing to modern codebases. Focuses on React Native (core contributor), React, Ruby on Rails, and Javascript/Ruby.

---

Technologies: React Native (core contributor), React, Ruby, Ruby on Rails, JavaScript, Perl, Objective-C, Java, Swift, C, C#, Python, Node.js, Express, PHP, GraphQL (Apollo), Mobile Development (Native: iOS/Xcode, Android/Android Studio, Hybrid: Cordova/Ionic, HTML5/Canvas, CreateJS/ImpactJS/Phaser, Flux (Redux, Alt.js, Mobx)), MySQL, PostgreSQL, MongoDB, Firebase, RSpec, Cucumber, Selenium, Mocha, Jasmine, Sphinx, Solr, Lucene, Elastic Search, AWS (S3, EC2, Lambda, Amplify, RDS, etc), Linux, Apache, Git/GitHub workflow, DevOps, Heroku, JIRA, Confluence, BitBucket, MongoDB, Web3, Crypto, NestJS, TypeScript

Resume: https://docs.google.com/document/d/1kQ6wp-hvewB-fGRNEVnywVpL...

Email: adamjroth@gmail.com
by skydhash | 2025-06-03 01:04:05+00:00
A small change around 50 lines is the size of an advent of code solution (the hardest part). Most of the code you write around that is for defensive coding (error handling, malformed input, expected output,…) which is the other hard part. Then you connect these cores to form a system and that’s another tough problem. And it needs to evolve to.

We’ve built tools to help us with the first part, framework with the second, architecture principles with the third and software engineering techniques for the fourth. Where do LLMs help?
by fuziontech | 2025-06-03 01:04:07+00:00
lol cheeky reply aside (I lead the ClickHouse team here at PostHog). We have two of the largest self hosted ClickHouse clusters out there (and growing rapidly) each with Petabytes of data. We are working on really interesting solutions to problems that we would love to open source for the broader CH ecosystem:

- Declarative, cluster aware migrations

- Iceberg and S3 backed merge tree's on ClickHouse (as performant as local MergeTrees)

- ClickHouse on K8s, but on Metal instances w/ NVMe used for caching and compaction.

- Load shedding query scheduler and eventually query optimizer

We have a broad charter when it comes to ClickHouse. It's one of the things that enables us to build so many products that share the same underlying data and context. Our goal is to enable all developers at PostHog to continue building these products quickly as the team and user-base scales.

It's honestly an exciting time to be working at this company and on the beating heart of what drives it. Chat with me if you have any questions!
by Brian_K_White | 2025-06-03 01:04:31+00:00
Because projectiles don't stop at any particular distance and can reach vehicles with humans which are flying over other humans, all of which were innocent of any spying, and most people are complete shit at judging size and distance when looking at objects in the air. (lots of great examples of this with the mystery drones in nj a while back)

I would like to shoot them down too but then I became 12 and a half years old instead of just 12.

As a policy that has to just apply across the board by default, of course the rule has to simply be be that you can not shoot at things in the air. I have no idea how bird hunting is handled but I bet it simply fails a logic test and shouldn't be allowed for the exact same reasons.

Now a tazer or a net or harpoon, all with physically limited tethers... Well there can be no safety argument about whacking something with a baseball bat, and anything with a tether that isn't rocket powered with 1000 feet of range is basically as safe for legit aircraft as a kid with a bat. IE it doesn't matter how inept the yahoo is, their capacity for harm to others is limited to a few people physically very near them, which is the same danger evrryone is to everyone else all the time.
by blibble | 2025-06-03 01:05:37+00:00
> You may be right. The author of this one even says if you spend time prettying your code you should stop yak shaving. They apparently don't care about code quality.

brought to you by fly.io, where the corporate blog literally tells you to shove your concerns up your ass:

> Cut me a little slack as I ask you to shove this concern up your ass.
by LoganDark | 2025-06-03 01:05:51+00:00
> This is super interesting - I have typed "wrong" since the time I first picked up a keyboard, 6 or 7 years old, back in an age where typing was not taught in school or an expected skill everyone was just automatically meant to know. As such, I developed my own "style" which looks a lot like "pecking" a lot of beginners will do, but has adapted over the decades to something that is my own.

Hey, me too: https://vxtwitter.com/LoganDark/status/1919146616763617342

(I usually type with more than two pointers, that post was just to prove a point that you don't need more than two fingers to type quickly. You probably don't even necessarily need two, though I couldn't go nearly that fast with only one.)