Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AI, Tools and Transformation

ben-evans.com

Post reply on HN
Print view View original

81–86 of 86 posts

Re: AI, Tools and Transformation

#81

Post by Kuyawa »

saulpw wrote: post #77
Kuyawa wrote: post #46

> It’s very tempting to imagine that AI turns everyone into a tool-builder It is not imagination, it is the undeniable truth. The quality of the tool is proportional to the competency of the builder, it always has been that way, AI makes the building process shorter by a magnitude

I have a friend who writes, she has certain needs, I've shown her how to start building tools, she has no interest in building tools. She's focused on writing and does not think about her personal process that way. Not every is a tool-builder, in fact most aren't!

Let me correct myself, every PROGRAMMER is a tool builder. I thought HN was a Hacker News site, sorry about my intrusion in this forum

Re: AI, Tools and Transformation

#82

Post by pydry »

a2ff6eeb0 wrote: post #80
pydry wrote: post #79

Earlier quoted context omitted.

At some point it will become a strong competitive advantage to zag where others zig. If you understand the codebase deeply and have trust in it can roll out changes quickly without manual testing you can run circles around the people scratching their heads wondering if this vibe coded 2,500 pull request is going to be the one that takes down the system for a day.

Have you ever written significant changes by hand without testing?

Ive written many significant changes without manual testing by leaning heavily on well crafted automated tests, carefully honed type systems and clean architecture. These foundations serve as the bedrock of high quality applications I can move fast on.

IME vibe coding isnt just not capable of building these foundations, it actively chips away at them where they already exist. shrug

Re: AI, Tools and Transformation

#83

Post by a2ff6eeb0 »

pydry wrote: post #82
a2ff6eeb0 wrote: post #80

Earlier quoted context omitted.

Have you ever written significant changes by hand without testing?

Ive written many significant changes without manual testing by leaning heavily on well crafted automated tests, carefully honed type systems and clean architecture. These foundations serve as the bedrock of high quality applications I can move fast on. IME vibe coding isnt just not capable of building these foundations, it actively chips away at them where they already exist. shrug

You can ask for tests.

Re: AI, Tools and Transformation

#84

Post by pydry »

a2ff6eeb0 wrote: post #83
pydry wrote: post #82

Earlier quoted context omitted.

Ive written many significant changes without manual testing by leaning heavily on well crafted automated tests, carefully honed type systems and clean architecture. These foundations serve as the bedrock of high quality applications I can move fast on. IME vibe coding isnt just not capable of building these foundations, it actively chips away at them where they already exist. shrug

You can ask for tests.

sure i can get all sorts of very poor quality tests by asking for them

Re: AI, Tools and Transformation

#86

Post by ryuuseijin »

simianwords wrote: post #36
ryuuseijin wrote: post #2

> You need audit, security, maintenance and accountability. I think this is where the role of humans will move towards in the future. Things like accountability can't really be outsourced to AI. This relates to solving the alignment problem: if you give the AI a specific goal and it has to plan sub-goals, how can you be sure the sub-goals align with your interests. For tasks in an isloated environment, this doesn't r…

False. Accountability is the result of difficulty of things. As things get easier you need fewer accountable people. Like, you need a guy who understands Linux and be accountable for Linux working well in your company. But if Linux does a good job that doesn’t leak, you don’t need a Linux guy.

Agreed, as things get easier you need fewer accountable people. Organisations will shrink, people will be more accountable by themselves for things they ask the agent to do instead of having an accountable person do it for them.

On the other hand, I think for complicated software there is such a long tail of things that can go wrong, and in your linux example with disastrous consequences, people will pay good money for a long time to have someone who they can call if there is a problem. In the business they have the term indemnification - that's what companies like redhat provide for linux for example and it's probably a big part of what makes them a billion dollar business.

Post reply on HN