If You are Asking for Human Attention, Demonstrate Human Effort | Tom Bedor's Blog
An ever-increasing volume of debug investigations, document writing, and code is written by robots. This has created a new etiquette question when working with a team - when is it OK to forward the output of an AI to another human to read?
An ever-increasing volume of debug investigations, document writing, and code is written by robots. This has created a new etiquette question when working with a team - when is it OK to forward the output of an AI to another human to read? On one hand, an AI with robust integration to internal code bases and documentation often produces genuinely1 useful output. On the other, as an increasing amount of a software engineer's day is spent reading AI text, a fatigue sets in. If I can have a robot say something, so can you. It reads as inconsiderate to post un-digested AI output as though it's…
saved by
related reading
- The Human-in-the-Loop is Tiredpydantic.dev
- No Man Is an Islandborretti.me
- AI is removing the middle class of software engineeringblog.florianherrengt.com
- Cognitive load is what mattersminds.md
- Your job is to deliver code you have proven to worksimonwillison.net
- Leading Effective Engineering Teams in the Age of GenAIaddyo.substack.com
- Software Engineering in the Age of AIadiamond.me
- AI fatigue is real and nobody talks about it · Siddhant Kharesiddhantkhare.com
- After Automation | Everyevery.to
- It's rude to show AI output to people | Alex Martsinovichdistantprovince.by
- Growing as an engineer in a world of AInlopes.dev
- Prevent cognitive debt by manually retyping LLM-generated code — Ankur Sethi's Lab Notebookankursethi.com