3 ms·
”54% of developers find that “Waiting on answers to questions often causes interruptions and disrupts my workflow.”” Isn’t this ironic? We are not allowed inte
by Too 2y ago
”54% of developers find that “Waiting on answers to questions often causes interruptions and disrupts my workflow.””
Isn’t this ironic? We are not allowed interrupt for questions, yet we find that the delay of waiting causes other interruptions.
Designing systems and documentation to avoid question thus becomes a double win-win.
- Aeolun 2y agoI’m sure I’ve read this as one of the success metrics in the Phoenix Project. Every time a ticket needs to go back to the original owner is a failure.
- TeMPOraL 2y agoThis explains the success of StackOverflow: don't have to wait on your colleagues or even your own investigative work, the answer is usually a Google query away. This also explains the success of ChatGPT in dev work: StackOverflow is still too much bullshit to deal with. LLMs strip that all away. It's such a big difference it's worth risking being led astray by hallucinations.
- fragmede 2y agoFor coding, if the LLM hallucinates, you feed the error message into the LLM and it apologises and corrects itself. For bonus points, you can tell it to run the code until it works.