News for hackers. Stuff that matters.
Re:Vote on which of Hacker News' challenges for AI have been... by tripleee on Thursday October 01, 2026 @02:25PM (#49925253)
> An LLM today sure can do many many many business-speak conversion tasks

Not reliably, and not without supervision. That's the main point. I'm trying really hard to figure out a workflow that doesn't require me to review the code and I just don't see how it's possible (yet)

You either need a comprehensive test suite (which requires understanding the code in order to create) or you need to review the actual implementation code to make sure it does the right thing

Re:Vote on which of Hacker News' challenges for AI have been... by FabCH on Thursday October 01, 2026 @03:50PM (#49926260)
Code is a tiny part of "business".

Most business is correspondence with people who want money from you and people you want money from.

Re:Vote on which of Hacker News' challenges for AI have been... by rstuart4133 on Friday October 02, 2026 @12:12AM (#49929762)
[delayed]
Re:Vote on which of Hacker News' challenges for AI have been... by sokoloff on Friday October 02, 2026 @06:00AM (#49931741)
People who demand risks to be lowered to once-a-millennium are not the type to go start or even run businesses.

There’s nothing wrong with that, but starting a business means fading several once-a-year risks of failure and running even an established one means facing several once-a-century risks every year.

Re:Vote on which of Hacker News' challenges for AI have been... by user43928 on Friday October 02, 2026 @04:25AM (#49931166)
No, you don't.

I've stopped reviewing the code in my mobile app project months ago. I now only look at files changed and lines count in MRs. Functionality is best verified via manual QA testing.

I know that people here are going to doubt the quality of my project and say that it is impossible, but they are clueless and have evidently not build a project in this way. Experiences from eg. corporate backend work are hardly relevant.

It is clear to me that the fewer consequential mistakes people find during code review, their attention to code reviews is going to go down, to the point of also skipping them.

I expect that for most development, not reviewing the code will be the standard by March of next year. Only critical code like authentication will be reviewed.

Re:Vote on which of Hacker News' challenges for AI have been... by suddenlybananas on Friday October 02, 2026 @04:41AM (#49931243)
What's the app?
Re:Vote on which of Hacker News' challenges for AI have been... by user43928 on Friday October 02, 2026 @05:56AM (#49931724)
Not public.

It's a paid app, and after 6 months of work I expect to publish it this month.

In other words, you will have to take my word for its quality.

Re:Vote on which of Hacker News' challenges for AI have been... by tripleee on Friday October 02, 2026 @10:48AM (#49934131)
what do your prompts / your workflow look like?
Re:Vote on which of Hacker News' challenges for AI have been... by user43928 on Friday October 02, 2026 @05:07PM (#49938618)
Nothing special at all, it just works.

One thing that I do is have each change reviewed by another model. If I implement with Codex, I would have Claude do the review, or the other way around.

I did not benchmark this against a review from a subagent with the same model, so I don't know if that in particular helps.

Re:Vote on which of Hacker News' challenges for AI have been... by sokoloff on Friday October 02, 2026 @05:55AM (#49931716)
I have a task that I do once per year for a robotics team that I mentor: Roughly,

Take this calendar of events and rank your preferences for the event lottery. Events are spread across 5 weeks, some are 20 minutes away, some are 4.5 hours away, some are Friday/Saturday, some are Saturday/Sunday, some are historically extremely competitive, some fill up in round 1, others don’t even fill after round 2. For the last two years, I’d written some scripts to scrape the event sites, find the addresses, ask Google Maps to give me driving distances and times, scrape prior year registration information to find which teams went and the strength of those teams, etc. It was several hours of effort.

This year, ChatGPT was capable of doing almost all of that basic research and data conversion, filling out our internal spreadsheet. It probably still took 4 hours on the wall clock, but at 2% attention (5 minutes of human toil).

I doubt I go a single workday without some kind of “I have an idea and I know there are disparate data sources out there; go find those and cross-correlate or extract the relevant data points.” question that is now 10-50x more efficient than 2 years ago.