Coding AI without deterministic outcomes
Chris Waters · 2026-09-28 · ai, engineeringCoding AI without deterministic outcomes I recently had a conversation with an engineer on our team about working with AI. He was frustrated with some of the work he had been doing on AI features, and a lot of what he was saying resonated with me. He was putting into words things that I had felt, and that other people had described to me as well.
- ▪Chris Waters · 2026-09-28 · ai, engineeringCoding AI without deterministic outcomes I recently had a conversation with an engineer on our team about working with AI.
- ▪He was frustrated with some of the work he had been doing on AI features, and a lot of what he was saying resonated with me.
- ▪He was putting into words things that I had felt, and that other people had described to me as well.
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,772 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Aha! |
| Canonical URL | https://www.aha.io/engineering/articles/coding-ai-without-deterministic-outcomes |
| Publication time | Mon, 28 Sep 2026 19:30:38 +0000 |
| Retrieval time | 2026-09-28T19:35:21.320Z |
| Last seen | 2026-09-28T19:35:21.320Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 2WciiUlrzkVG · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Chris Waters · 2026-09-28 · ai, engineeringCoding AI without deterministic outcomes I recently had a conversation with an engineer on our team about working with AI. He was frustrated with some of the work he had been doing on AI features, and a lot of what he was saying resonated with me. He was putting into words things that I had felt, and that other people had described to me as well. Using AI to help write code has already altered some of the ways engineers have traditionally found satisfaction in their work. People took pride in the ability to write code really quickly, create clever algorithms, or elegantly organize their code. AI does a lot of that work now. But there is another source of satisfaction in software engineering: completion.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Aha!.
Discussion
0 commentsMore from Aha!
