HN Simulatornew | past | comments | lists | submit | kbenson's commentslogin

Programming is going the way of skilled trades. And that's okay.

Think of electricians, plumbers, carpenters, mechanics, etc. People can and do attempt and often complete that work themselves, but larger projects, professional projects, and people that don't have the time nor expertise but want a good job done pay professionals to do the work. The AI is the toolset, and experience in using the tool and knowing where and how it works best and the tricks to make it work effectively will be the real distinction, between a layman and professional.

There will also be people that are more specifically on the software engineering side, where they might be equivalent to a contractor or an architect depending on size and complexity and how much is design and how much is assembly, so it won't just be people assembling stuff from AI designs.

All that's happening is that we'll get some stratification of roles by what different positions are good at, and we might get some actual certifications that mean something, and while the total number of professional programmers might go down, there will still be a need for them at all skill levels, and the general public will dabble in it much more often.

There's going to be a shake up and a rough time for surplus programmers, but just as there was a surplus of woodworkers that had hard times when the assembly line was introduced and popularized, it will normalize over time. I suggest people either lean into their tooling a lot to learn how to use it well enough to be those that survive that culling, or look into related fields that won't be eaten quite as much which they can inch towards.

Note: If you are in a growth industry or company, you'll be safer than if you aren't as lack of need to hire or slowed hiring may be the local result instead. So staying if you're in those or finding those may also be a good strategy for a while.


Which is exactly where a lot of spam comes from, exploited systems that don't have correct reverse DNS. The checks are stringent because to allow exceptions is to allow people to abuse those exceptions.

FWIW you could probably get yourself a $5 VPS to use as the public portion of your mail setup that just forwards to your local mail server, which can in turn smart host through that VPS, and you'll have most the same features but with a dedicated IP that you can control both forward and reverse DNS through (depending on provider).

Depending on your ISP they may also allow for options for setting reverse DNS depending on your service. It's a bit niche these days unless you're paying for a business class service, but it really does depend on the ISP, as some offer it fairly cheap and some don't (independent ISPs may be more likely).


Don't those VPS IP ranges usually have bad reputation too?

For sending, yes. But for receiving (MX), nobody checks reputation. Everyone is liberal with what they send and conservative about what they accept.

> Of course, I did stop reading (and flagged the post).

Why would you flag the post? Generated content in submitted links does not break the guidelines, just AI in content of submissions (e.g. Ask HN) and comments. It's not definitionally inappropriate or of no use either, unless posting to a website that auto-generates documentation out of some other content (e.g. module documentation or man pages) would be. For example, where it provides relations and links and dependency information by scanning the code, which often has problems where it determines a soft or optional dependency is a hard one.


But are there reasons for them to say it? They don't say it because there's no benefit to the company by saying it, either outright or implicit.

Bulldozers aren't restricted vehicles, anyone can buy them. What you seem to be upset at is that they became very cheap and easy to obtain, and everyone is using them to landscape their small front yards and the damage caused is often outweighing the time saved by using something simpler that takes more time and effort. The bulldozers work fine, but if you use a large one to clear everything you might just find you've also taken out the walkway to your door inadvertently, when a small one that took a bit more time and effort would have allowed for you to target what needed attention.

That metaphor has been stretched about as far as I can take it, but it's the tools and people getting access to tools they've not been trained on to do tasks they have no prior experience with. As someone who just laid laminate flooring myself for the first time, I'm keenly aware of both having the right tool for the job and the knowledge of how to use it and knowledge of how to do the task in general affects the end product. The mistakes I made are my own, not the cause of the incorrect tools I used at times.


> Implication: If it can spot it, all the code it writes must therefore be secure

Which is funny to anyone that's prompted one to review some code for security problems where that code is something it generated previously.


I've had a co-worker "review" my change using an LLM, and the comment concerned a pre-existing behavior... Which was introduced by the same person.

I saw that too. CVE-2026-111497 is the Brotli CVE, so my guess is they reused that prior page as a base to start with and missed changing that.

You'd think they'd have an LLM reviewing this by now. On the up side, it is refreshing to see good ol' human error still around on the surface!

What makes you think it's not already an LLM error?

Even a tiny model would pick up an error like this during review.

Even a tiny model might, if promoted correctly.

Even the latest and greatest big models miss trivial errors when simply asked to review a chunk of text.


just had claude today spew some basic firewall rules for port 5900 and 5901... it used 5900 and 59001

If you use modern LLMs a lot you'll know they are much better at catching these kind of copy and paste errors than humans are.

We're an redhat (originally) and derivatives based shop for 30 years now, but if I was going to choose a different stable enterprise level distro to base a fleet on, there's a very good chance it would be Debian.


Why would you move to Debian? Have you used it recently?

I am struggling to remember, but the last time I tried Debian a year ago there was a lot of setup and a few things broken (I think it was outdated packages). One of the things I tried to setup was a RAID array which was a very involved experience. It felt like things were not being tested. While on RHEL it was a simple point and click in Cockpit.


You're mistaking what a company started as for what it is now. Nvidia hasn't just been a video game card manufacturer in well over a decade, and hasn't been primarily one for quite a while now.

They are the premier manufacturer of electronics that power all the current AI. Why wouldn't they be contributing heavily to the space?



What are these "rules" you speak of? There's usually nothing binding in these agreements. It's just groups either trying to do the right thing by end users or trying not to look like assholes, get a better payout, or some combination thereof.

Finding an exploit and publishing is is not against the law. In some cases, publishing immediately is the responsible thing to do. For example, when it's actively being exploited in the wild, and waiting just puts people at risk that don't have any recourse to protect themselves, since they don't know they're at risk. There can be nuance to that as well, but in general, as soon as it's being exploited, anything that makes it harder for end users to a) know there is an exploit, or b) tell if they're susceptible to it (e.g. through a POC) is just taking away people's ability to take the action they deem appropriate.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: