MurphyA/hacker-news huggingface dataset:
by bdangubic | 2025-06-03 00:00:28+00:00
they can't be aware of the latest changes in the frameworks I use, and so force me to use older features, sometimes less efficient

of course they can, teach them / feed them latest changes or whatever you need (much like another developer unaware of the same thing)

they fail at doing clean DRY practices even though they are supposed to skim through the codebase much faster than me

tell them it is not DRY until they make it DRY. for some (several projects I’ve been involved with) DRY is generally anti-pattern when taken to extremes (abstraction gone awry etc…). instruct it what you expect and it and watch it deliver (much like you would another developer…)

they bait me into inexisting apis, or hallucinate solutions or issues

tell it when it hallucinates, it’ll correct itself

they cannot properly pick the context and the files to read in a mid-size app

provide it with context (you should always do this anyways)

they suggest to download some random packages, sometimes low quality ones, or unmaintained ones

tell it about it, it will correct itself
by pera | 2025-06-03 00:00:30+00:00
It's a bit more than a metaphor :) during the California gold rush there was this guy named Sam Brannan who sold shovels and other tools to miners, and made a fortune from it (he is often referred to as California's first millionaire). He also had a newspaper at the time, the California Star, which as you can imagine was used to promote the gold rush:

> The excitement and enthusiasm of Gold Washing still continues—increases. (1848)

https://sfmuseum.org/hist6/star.html

https://en.wikipedia.org/wiki/Samuel_Brannan
by sgammon | 2025-06-03 00:01:28+00:00
elide.dev | Multiple Roles | REMOTE OR OFFICE (US) | Full-time & Part-time | Kotlin + Rust

Elide, a new runtime built in Kotlin, and which runs JavaScript/TypeScript, Kotlin, Python, WASM, and soon Ruby.

https://elide.dev

https://github.com/elide-dev/elide

We are hiring for Kotlin and Rust. If you like things like Bun and are interested in the runtime space, reach out at sam@
by conception | 2025-06-03 00:01:38+00:00
I don’t think this is true actually. There was a huge shift of llm coding ability with the release of sonnet 2.5. That was a real shift in how people started using LMS for coding. Before that it was more of a novelty not something people used a lot for real work. As someone who is not a software engineer, as of about November 2024, I “write” hundreds of lines of code a day for meaningful work to get done.
by connivingbear | 2025-06-03 00:01:44+00:00
Location: NYC, Philly, Chicago, Boston, Preferred. Open to others

Remote: No, Hybrid/full time onsite preferred

Willing to relocate: Yes

Technologies: Java, Spring Boot, Bit of Angular and Go, ModSecurity WAF, F5 App Protect, Veracode, BurpSuite, Wireshark, Artifactory, K8s, Docker, Splunk, AWS Services, Terraform, Helm Charts, Git, and more.

Résumé/CV: Available Upon Request

Email: <HN Username> @ proton.me

Looking for security engineer roles. For the past 5 years I have been building security tooling that internal teams can make use of. I work closely with other teams to help improve the security posture of their apps. I help write documentation and host department wide presentations to educate others about web app security and steps they can take to make apps more secure. I took on the responsibility of managing our H1 Bug Bounty Program which previously was failing SLA targets by 10+ months and managed to bring it down to days. I have helped mentor interns and junior developer and also been active in conducting pair programming interviews for future candidates. What you get from me is a go-getter, self-motivated individual. I am always looking to improve not only myself but also my work.
by PantaloonFlames | 2025-06-03 00:02:28+00:00
> It, never has, in fact the opposite is true. Every type of automation has expanded the economic output so much that it created massive amounts of labor demand, …

This seems to be true, but there’s a second issue at work here, which that automation and progress in general can _disrupt_ the labor market. Sure there’s a net gain in labor demand, but there are people involved who are more than just “resources” who can easily be redeployed.

Progress is what built and then killed (injured?) cities and towns like, in the US, Detroit, or Gary, or Pittsburgh.

We want to promote progress and automation while at the same time protecting people who are inadvertently over-exposed to the downside. (Generally less educated people or people with less agency).
by moron4hire | 2025-06-03 00:02:39+00:00
I think I figured out a big problem I have with AI, and that is that I just hate using other people's software. The vast majority of software is just garbage. It all tries to take way too much of my attention. It doesn't help that all these AI tools are new, so they are inextricably linked to some SV startup that wants to be the next unicorn, so they have some bullshit account-generation/data-retention/terms-of-service/acceptable-use-policy/remarketing-email-campaing song and dance that is all stuff I have to pay attention to. All I really want to do is sit down and think on my own. I'm constantly inundated with distractions at work, so when I get a few minutes to myself, I sure as hell don't want an AI bot messaging me about reviewing its PR. I don't even want to review the human-written PRs; just push your code already, if it breaks you get to fix it. I certainly don't want a 500th unread email in my inbox.

You know what doesn't constantly nag for my attention? Dead text files on disk. They just sit there, waiting for me to grace them with my presence. That's the way it should be. Computers serve me, not the other way around.
by orsorna | 2025-06-03 00:03:10+00:00
If you are resource constrained this article will make you sad.

I do not have unlimited funds to plug in some token and burn a bunch of money when writing code.

I am gpu poor. I'm lucky that 8gb vram can run the smallest models. But the output is so poor that I lose out to anyone using a hosted service.

If anything this article shows that building great programs is less democratized than it once was.
by CobrastanJorji | 2025-06-03 00:03:47+00:00
This reminds me of Isaac Asimov's "Profession" short story. Most people receive their ability (and their matching assigned profession, thus the name) from a computer. They then are able to do the necessary tasks for their job, but they can't advance the art in any way. A few people aren't compatible with this technology, and they instead learn to do things themselves, which is fortunate because it's the only way to advance the arts.
by Jtsummers | 2025-06-03 00:04:13+00:00
I agree, using tools more in line with your language is better but I believe the knowledge from learning Dafny ought to transfer well to other systems. And Dafny seems better as a pedagogical system than what I've seen and used for other languages.

I'm exploring it now as a way to ease colleagues into SPARK. A lot of the material appears to transfer over and the book Program Proofs seems better to me than what I found for SPARK. I probably wouldn't have colleagues work through the book themselves so much as run a series of tutorials. We've done this often in the past when trying to bring everyone up to speed on some new skillset or tooling, if someone already knows it (or has the initiative to learn ahead of time) then they run tutorial sessions every week or so for the team.
by Mofpofjis | 2025-06-03 00:04:31+00:00
> I got into programming because I like programming, not because I like asking others to write code on my behalf and review what they come up with

oh finally someone else who didn't enter programming because, as 7-10 year old child, they were into SOLVING PRACTICAL PROBLEMS FOR PEOPLE.

> But the last fucking thing I want to do is delegate all the code writing to someone or something else

Thank God there is at least one other person that understands that the ratio between creative and reactive work is crucial for wellbeing at the job.

For crying out loud.

> but if I ever get to the point that I feel like I spend my entire day in virtual meetings with AI agents, then I'm changing careers

so am I.

> but at least I guess I got a couple of good decades out of it

Thanks for this perspective. Yes, at least we've got our memories, and the code locations and commits we recall from memory, from a distance of 10 or more years.

>. If this is what the job turns into, I'll have to find something else to do with my remaining years

Me too.
by 0x000xca0xfe | 2025-06-03 00:05:03+00:00
And who can push new code after the manufacturer's bankruptcy? I've worked in IoT and I'd say the biggest security problems are in this order:

- Devices requiring Internet access for functionality that could have been done locally

- Hardware SDKs which are basically abandoned forks by manufacturers so IoT companies ship stone-age kernels and device drivers

- The usual stuff: too much complexity, lack of tests, bad documentation, meaning old parts of the software get forgotten (but remain exploitable)

Theoretical waxing about trusted computing and remote attestation does seem disingenuous when problems with non-certified firmware is probably not even in the top 10 in the real world. Notice how the article author mentions some scary attacks but conveniently omits how the attackers actually gained access?
by metalman | 2025-06-03 00:05:31+00:00
you forgot to add in ,zero land costs, and a certainty that the solar coridor will intersect transmission lines.also it is a fact that agriculture is now useing water at non sustainable rates, so every drop saved is significant, and I would not be surprised if they are evaluating, "curtaining" the remaining air gaps and attempting to elliminate evaporative loses. As far as "complexity" goes, I take that you mean in comparison to perfectly flat level ground, that is cheap, and located next to transmission lines, and markets, in an area with easy permiting requirements.Here's the rub though, any large scale mega project is a beast to spool up, but once it get's moving it becomes routine and if the quality of engineering and management is up to it, then efficencys of scale will tend to zero out minor quirks.
by al11588 | 2025-06-03 00:05:43+00:00
Location:New York but open to remote

Remote:Yes Willing to relocate:No

Technologies:Python, Java, Swift, .Net, JavaScript

Résumé/CV:https://www.linkedin.com/in/alvin-lawson-b8300635

Email:al11588@gmail.com

My name is Alvin. I am looking for a developer advocate role, Developer relations, Support engineer role, Backend engineer role, Systems engineer role, DevOps role.
by simonw | 2025-06-03 00:06:23+00:00
tptacek is using Zed, which I've not tried myself.

I actually do most of my "agentic coding" (not a fan of the term, but whatever) in ChatGPT Code Interpreter, which hasn't changed much in two years other than massive upgrades to the model it uses - I run that mainly via o4-mini-high or o3 these days.

OpenAI's Codex is a leading new thing, but only if you pay $200/month for it. Google's equivalent https://jules.google/ is currently free.

GitHub Copilot gained an "agent mode" recently: https://github.blog/ai-and-ml/github-copilot/agent-mode-101-...

There's also Copilot Coding Agent, which is confusingly an entirely different product: https://github.blog/changelog/2025-05-19-github-copilot-codi...
by NeutralCrane | 2025-06-03 00:06:27+00:00
> Question: If everyone uses AI to code, how does someone become an expert capable of carefully reading and understanding code and acting as an editor to an AI?

LLMs are very much like pair programmers in my experience. For the junior engineer, they are excellent resources for learning, the way a senior engineer might be. Not only can they code what the junior can’t, they can explain questions the junior has about the code and why it’s doing what it’s doing.

For senior devs, it is a competent pair programmers, acting as an excellent resource for bouncing ideas off of, rubber ducking, writing boilerplate, and conducting code reviews.

For expert devs, it is a junior/senior dev you can offload all the trivial tasks to so you can focus on the 10% of the project that is difficult enough to require your expertise. Like a junior dev, you will need to verify what it puts together, but it’s still a huge amount of time saved.

For junior devs specifically, if they are not curious and have no interest in actually learning, they will just stop at the generated code and call it a day. That’s not an issue with the tool, it’s an issue with the dev. For competent individuals with a desire to learn and grow, LLMs represent one of the single best resources to do so. In that sense, I think that junior devs are at a greater advantage than ever before.
by CrimsonCape | 2025-06-03 00:06:44+00:00
I put 3 sugar cubes in my coffee every day. So I divide the weight of the box of sugar cubes and it results in 1 sugar cube = 3.5 grams. Thats 10.8 grams per 12 oz of coffee.

A 12oz can of Dr. Pepper soda has 40 grams of sugar. Divided by my aforementioned mass per cube, it yields 11 sugar cubes.

Either I messed up the math or soda is crazy; i can't imagine munching down 11 sugar cubes in one sitting.

TLDR:

12oz coffee: 10.8 g sugar, 3 cubes

12oz soda: 40g sugar, 11 cubes
by mrbungie | 2025-06-03 00:06:56+00:00
> Their data teams are too big, ours are the right size.

Come on dude, tech we can discuss a lot and there is no totally correct objective response. Irresponsible financials are an entirely different beast. A proportionally big data team in a non-data focused / non-tech company is a low-key red flag, and that's what I'm referring to (i.e. >10% of headcount). CFOs don't (and should not talk) in relatives, like "us vs them".

> Fwiw, I use Kafka regardless of scale. It's the only mainstream system out there that doesn't encourage throwing away your receipts. It's the programming equivalent of "accountants don't use erasers".

About Kafka, as far as I've experienced it and also read about, it is mostly safe if you are paying for managed solutions like Confluent or heavily investing on infra for covering for ordering and other issues. But Kafka is as good a technology as it is recognizedly messy, up to a point where I've seen people loving it and then hating it months-years down the line.

I would stick with batch processing if I don't care for receipts. You need to take care for them? Cool, then take charge but if not then don't tackle complexity your business don't/won't need. That's the point, even big banks have survived without taking care about the receipts.
by nickperry12 | 2025-06-03 00:07:01+00:00
Location: Vancouver, BC, Canada

Remote: Preferred, but open to hybrid and on-site as well

Willing to relocate: For the right opportunity

Technologies: JavaScript, TypeScript, Ruby, Python, React, Kotlin, AWS, Docker, Terraform, Kafka, Debezium, PostgreSQL, MongoDB

Résumé/CV: Available upon request

Email: nick.perry604@gmail.com

Hi, I'm Nick! I'm a software engineer with 3+ years experience developing fullstack web applications. Most recently I worked on Tumbleweed (https://tumbleweed-cdc.github.io/), an open-source framework for creating Change Data Capture pipelines, streaming captured data changes from a connected Postgres database to microservice consumers in real-time. I'm passionate about collaborating with others to tackle complex engineering problems and create impactful software. I'd love to work on a team that sets their egos aside so we can accomplish our goals, and really value great communication and empathy. If this sounds like a good fit, I'd love to hear from you!
by think_or_swim | 2025-06-03 00:07:06+00:00
Bun (YC S19) | https://bun.sh | San Francisco, CA; on-site | Visa sponsorship available | Full-time

Bun is an incredibly fast all-in-one toolkit for building, installing, running, and testing JavaScript and TypeScript. We were born out of frustration with the fragmented, slow JavaScript ecosystem and are on a mission to make JavaScript development faster and more productive.

We are looking to fulfill the following roles:

- Software (Product) Engineer - (email me: conner@bun.sh, help us build our first product. Looking for someone with great design and DX taste; javascript/typescript experience)

- Senior Systems Engineer: https://apply.workable.com/bun/j/A7A1388873/

- Head of Propaganda (DevRel): https://apply.workable.com/bun/j/FAD66BC1D1/

- Engineering Manager: https://apply.workable.com/bun/j/A3EC729D81/

- Systems Engineer - Developer Productivity: https://apply.workable.com/bun/j/09C6A4C166/
by mlsu | 2025-06-03 00:07:17+00:00
I tried the agent thing on:

- Large C codebase (new feature and bugfix)

- Small rust codebase (new feature)

- Brand new greenfield frontend for an in-spec and documented openAPI API

- Small fixes to an existing frontend

It failed _dramatically_ in all cases. Maybe I'm using this thing wrong but it is devin-level fail. Gets diffs wrong. Passes phantom arguments to tools. Screws up basic features. Pulls in hundreds of line changes on unrelated files to refactor. Refactors again and again, over itself, partially, so that the uncompleted boneyard of an old refactor sits in the codebase like a skeleton (those tokens are also sent up to the model).

It genuinely makes an insane, horrible, spaghetti MESS of the codebase. Any codebase. I expected it to be good at svelte and solidJS since those are popular javascript frameworks with lots of training data. Nope, it's bad. This was a few days ago, Claude 4. Seriously, seriously people what am I missing here with this agents thing. They are such gluttonous eaters of tokens that I'm beginning to think these agent posts are paid advertising.
by ugh123 | 2025-06-03 00:07:19+00:00
>So we replace the task of writing tedious boilerplate with the task of reading the AI's tedious boilerplate. Which takes just as long. And leaves you with less understanding. And is more boring.

These all sound like your projected assumptions. No, it generally does not take longer to review sizable code changes than it does to write it. This is further alleviated if the code passes tests, either existing or new ones created by the ai.
by srhtftw | 2025-06-03 00:07:29+00:00
> It took a few days to produce this library -- it would almost certainly have taken me weeks to write it myself.

As mentioned in another comment https://news.ycombinator.com/item?id=44162965 I think this "few days" is unrealistic given the commit history. I think it would be more accurate to say it allowed you to do something in under one month that may have have taken two. A definite improvement, but not a reduction of weeks to days.

Or is that history inaccurate?
by mike_d | 2025-06-03 00:07:30+00:00
> United States v. Causby (1946) sets the precedent that property owners own the airspace above their property to (at least) 83 feet.

Probably one of the most misunderstood cases ever. Causby's complaint was that his chickens were dying as a result of the stress from low altitude military flights over his property. The Supreme Court ruled this was a violation of his fifth amendment rights because the government was taking something from him (chickens) without compensation.

83 feet was simply the lowest recorded flight. People took that to be some sort of magical barrier, but would only be relevant if your issue was also with chicken deaths.

Even if you take it to apply to drones, it would only apply to government drones that in some way cause you real and demonstrable financial loss.
by bananapub | 2025-06-03 00:08:40+00:00
the FAANG-esque process is extremely stupid, but it is entirely dependent on 1) getting a referral / passing a phone screen and then 2) passing the dumb interview process on the day, and perhaps some story about why you don't have a degree from a university the American elite thinks is elite enough.

that feels very different from Mark requiring your high school maths grades.
by rainsford | 2025-06-03 00:08:52+00:00
But how important is the core knowledge if it isn't necessary to achieve the outcomes people actually value? People only cared about map reading skills to the extent that it got them where they want to go. Once GPS became a thing, especially GPS on mobile phones, getting them where they want to go via map reading became irrelevant. Yes, there are corner cases where map reading or general direction finding skills are useful, but GPS does a vastly better and quicker job in the large majority of cases so our general way-finding experience has improved.

This is especially true because the general past alternative to using GPS to find some new unfamiliar place wasn't "read a map" it was "don't go there in favor of going some place you already knew" in a lot of cases. I remember the pre-GPS era, and my experience in finding new stuff is significantly better today than it was back then.
by baobun | 2025-06-03 00:09:06+00:00
Am I right in assuming that running Linux (or anything else than macOS) on the MacStudio is experimental at best?

I'd be looking for something that can run offline and receive system updates from an internal mirror on the airgapped network. Needing to tie an AppleID to the machine and allow it internet access for OS updates is a hard sell. Am I wrong in thinking that keeping an airgapped macOS installation up to date would additional infrastructure that requires some enterprise contract with Apple?
by sho_hn | 2025-06-03 00:09:07+00:00
ST: TNG had an episode that played a big role in me wanting to become a software engineer focused on HMI stuff.

It's the relatively crummy season 4 episode Identity Crisis, in which the Enterprise arrives at a planet to check up on an away team containing a college friend of Geordi's, only to find the place deserted. All they have to go on is a bodycam video from one of the away team members.

The centerpiece of the episode is an extended sequence of Geordi working in close collaboration with the Enterprise computer to analyze the footage and figure out what happened, which takes him from a touchscreen-and-keyboard workstation (where he interacts by voice, touch and typing) to the holodeck, where the interaction continues seamlessly. Eventually he and the computer figure out there's a seemingly invisible object casting a shadow in the reconstructed 3D scene and back-project a humanoid form and they figure out everyone's still around, just diseased and ... invisible.

I immediately loved that entire sequence as a child, it was so engrossingly geeky. I kept thinking about how the mixed-mode interaction would work, how to package and take all that state between different workstations and rooms, have it all go from 2D to 3D, etc. Great stuff.
by Mofpofjis | 2025-06-03 00:09:33+00:00
Agreed. Smartphones are portable, mobile computers that suck at every single aspect of being, and working as, a computer, except for mobility. They are not powerful, they are not general purpose, they are not ergonimic, they do not respect user freedom or privacy. Use such a mobile device only when you can't avoid it (i.e., when you are on the road -- when mobility is the single most important priority), and at no other time.
by mikepurvis | 2025-06-03 00:09:33+00:00
The Nix world is not a huge place. I was largely self taught for about a year and then heavily influenced by working with Numtide, so a bunch of my tools experience comes from them.

And I actually landed a minor contribution to nix2container, which was nice to do: https://github.com/nlewo/nix2container/pull/77
by cmdli | 2025-06-03 00:10:27+00:00
> tptacek wasn't making this argument six months ago.

Yes, but other smart people were making this argument six months ago. Why should we trust the smart person we don't know now if we (looking back) shouldn't have trusted the smart person before?

Part of evaluating a claim is evaluating the source of the claim. For basically everybody, the source of these claim is always "the AI crowd", because those outside the AI space have no way of telling who is trustworthy and who isn't.