{
  "video_id": "reddit_1tlj7ou",
  "channel_slug": "singularity",
  "channel_handle": "r/singularity",
  "title": "coding is basically solved for the boring 90% of tasks",
  "url": "https://www.reddit.com/r/singularity/comments/1tlj7ou/coding_is_basically_solved_for_the_boring_90_of/",
  "external_url": null,
  "upload_date": "20260523",
  "published_at": "2026-05-23T15:16:40+00:00",
  "transcript": "just mass refactored a 120 file FastAPI service. 400 steps, 2M tokens, $3 total, zero human input. it confidently introduced a deadlock into my async event handler which was genuinely funny, so the hard 10% still needs opus.\n\nran deepseek v4 and Hunyuan Hy3 preview as the cheap workers. 21B active params, roughly $0.18 per million input tokens, about 80x cheaper than opus. Tencent reports 99.99% step success across 495 step production runs and that honestly tracked for routine refactors in my case. what caught me off guard was latency: the open weight tier responded faster than opus, so the 360 easy steps finished in under an hour while the 40 escalations took almost as long.\n\n\n\n--- Top Comments ---\n\n\n[131 upvotes] People may downvote it, but it is true. What people do not understand is:\n- average devs are crap\n- overall average human's work results are far from being perfect\n- people fail to squeeze out the AI models properly and fail at the setup (which leads to crap results later)\n\nI stand by the sentence: one senior dev with skills and experience can build things with AI within one month which are of the same quality as a project made by a team of 1 senior and 3 or more juniors without AI done within half a year. Sorry, but this is consistently being proven.\n\nIn fact, in most standard setups organization of the project is itself a bottleneck - you can finish tasks quicker than management can \"make decisions and plans\" which leads to a lot of time being wasted if you ask me. On the other hand, give AI to juniors and witness the apocalypse because they fail to set the harness properly, formulate the context and task goals and overall keep track of solutions.\n\n[118 upvotes] Share the code before and after. Talk is cheap \n\n[32 upvotes] in 2024 dario said coding would be solved by the end 2025, that was pretty much exactly true opus 4.5 was out the the public then and they were a bit ahead internally on tooling. for all the sceptics, watch the latest lectures on the claude channel and actually impliment htm in your project.\n\nIts pretty clear to me that if model progress stopped now and all we did was itterate on harnesses and tooling we'd have near fully automated software development from a code gen side of things, and models aren't stopping here. The next step is them iterating on their own ideas and a/b testing them at scale with near perfect analysis of uses actions at a level aggregate data couldn't show.\n\n",
  "transcript_chars": 2454,
  "ingested_at": "2026-05-24T01:30:40.299594+00:00",
  "source": "reddit",
  "yt_meta": {
    "score": 203,
    "upvote_ratio": 0.79,
    "num_comments": 89,
    "author": "Dramatic_Spirit_8436",
    "is_self": true
  }
}