Hacker Newsnew | past | comments | ask | show | jobs | submit | fathermarz's commentslogin

Second this

This is what life is about right here

When ChatGPT 3.5 dropped, I typed in. “Can you make me a Python script that tells me when the ISS passes over my house at <address>” and it one shotted it. I knew the world had changed forever.

I sincerely disagree that AI is worse than the crypto/NFT hype… pig butchering is one of the most disgusting practices imaginable and it was turned into a legitimate low effort vehicle for scammers due to web3 and the hype train.

AI is definitely on a scale of magnitude more but it has inherent value outside of “scarcity”. It’s actually quite the opposite with sheer supply/demand balance. Also investing in crypto made me less money than investing in myself by using AI to learn and challenge myself to think differently.


Excellent write up and inspired me for our next IA design run. After reading Fly’s Litestream work it makes me think this is a solid option.

I’m confused, isn’t this rewrite still unreleased as of today? Surely people understand that a simple, “do an audit for memory safety” will bring it up to par.


100% could not agree more. Was hired to fix a vibe coded app for a company that one of their people whipped up over five months. Tens of thousands of lines of code in a single file and no security whatsoever.

The guy uses Claude Code, same as me… it’s like a highly skilled mason with a chisel, against me with a chisel. I’m not going to produce the same masterpiece, because there is SME that underpins the accelerant.


The slot machine lever is my least favourite opinion on the subject.

Also, let’s not forget. The developer is rarely the person pitching the feature, and is normally given the constraints and the PRD…

Soooo people can keep tiptapping on the keyboard, but eventually they need to open their mind to the possibility that “the old way” is actually dead.


> The developer is rarely the person pitching the feature, and is normally given the constraints and the PRD

This heavily depends on the industry and company culture.

I've pitched plenty of features and I've basically never had a spec land on my desk ready to go. Part of my job as a SWE is to help product folks decide what to build.


Completely agree. This is a harness problem, not a model problem. The model is rarely the issue these days


I don't know. To me, this is a human problem. Not only has the model access to the production database, they have the backups online on the same volume, have an offline backup 3 month old. This is an accumulation of bad practices, all of them human design failures. Instead of sitting down and rethinking their entire backup strategy they go public on twitter and blame a probabilistic machine doing what is within its parameters to do. I bet, even that failure could have been avoided, were more care given to what they do.


No, this is a "being stupid enough to trust an LLM" problem. They are not trustworthy, and you must not ever let them take automated actions. Anyone who does that is irresponsible and will sooner or later learn the error of their ways, as this person did.


More-so an environment problem. An agent doing staging or development tasks should never be able to get access to prod API credentials, period. Agents which do have access to prod should have their every interaction with the outside world audited by a human.


I built a community tool for exactly this, based on privacy first principals but around the what. It’s workflow based and not “put your sensitive data into ChatGPT and hope it captures the right stuff”. Mostly built for security folks but anyone can use it

Check it out: https://redact.cabreza.com


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

Search: