My Latest LLM Workflow and Modern Engineering Values
The author reflects on the transformative impact of coding agents and LLMs on software development. They share their experiences of using AI to write code, fix bugs, and implement features at an unprecedented speed. This shift has allowed them to manage multiple projects simultaneously and improve the quality of their work significantly.
- ▪The author has transitioned from writing code by hand to relying on AI-generated code for most of their projects.
- ▪They have successfully used coding agents to fix bugs and add features to existing codebases, resulting in faster and more stable software.
- ▪The author prefers using the Codex CLI for its efficiency and ability to produce correct solutions quickly.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,266 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 | Cpojer |
| Canonical URL | https://cpojer.net/posts/modern-engineering-values |
| Publication time | Wed, 03 Jun 2026 14:09:55 +0000 |
| Retrieval time | 2026-06-03T14:27:09.556Z |
| Last seen | 2026-06-03T14:27:09.556Z |
| 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 | AfEFAc-sj6Cx |
| 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
‹ homeTable of Contents› How I use LLMs Now› Modern Engineering Values› Strong Ownership› Taste, Taste, Taste› Strict Guardrails & Fast Feedback Loops› Context in the Repo› Own your Stack› Option Value› On Management› How much faster?Modern Engineering ValuesPublished on June 3, 2026 14 minutes reading time, 2700 wordsAt the end of last year I shared my LLM workflow in You are absolutely right!?. I knew it would be outdated quickly, but I didn’t realize it would be outdated that quickly. I actually cannot believe that I rarely write code by hand anymore. Or rather, I cannot believe that I used to write code by hand! Programming has fundamentally changed and I’ve been wondering which engineering values still matter.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Cpojer.