afk

Topics in the source

• AFK
• Hours of wide exploration
• Better for the people who use it
• Sometimes out of the box
• Match the repository
• Stay reversible
• Notes that outlive the conversation
• 1. Check the tools before they leave

This skill spends the time you're gone making one project better. It gathers evidence, generates ideas widely, builds the best of them on a local branch and leaves a report you can read in two minutes. Reviewing an interface is better-interface, reviewing a diff is interface-review, exploring alternatives for one component is variant and stress testing one is break. A run is meant to last hours. A run that ends after three commits and twenty minutes wasted the time the person left for it. When a batch is built and has survived Try to reject it, take the next idea from the list. When the list runs dry, return to Gather evidence for a part of the project not yet read. This is exploration, so go wide before going deep. Read every area of the product, from its busiest pages to its settings, docs and tooling. Ideas clustered around one page or one file mean the exploration stopped early. Polishing one change past good enough costs breadth, so move on. Proving a change broke nothing is not polish, and no change skips it. A request that names a focus changes what wide means. Given one page, one feature or a piece of work in progress, explore every angle of it and leave the rest of the pro

This is an excerpt. Refer to the complete source and its current requirements.