effective▌

Apply best practices and conventions from the official Effective Go guide to write clean, idiomatic Go code.

Templates and guidance for writing READMEs matched to your project type and audience. \n \n Identifies four project types (Open Source, Personal, Internal, Config) with distinct audience needs and required sections \n Provides a structured three-step process: identify the task (creating, adding, updating, or reviewing), ask task-specific questions, then solicit final feedback \n Includes essential baseline sections for all READMEs: name, description, and usage with examples \n References support

Frameworks for running more effective meetings drawn from 40 product leaders. \n \n Separates meetings into strategic (open-ended discussion) and operational (structured updates) to prevent mixing incompatible formats \n Emphasizes that meetings should only host discussion; discovery and decision-making belong in async channels \n Provides structured closing questions (what was decided, who does what by when, who else needs to know) to ensure alignment and prevent re-meetings \n Includes guidanc

Frameworks for running productive one-on-one meetings drawn from seven product leaders. \n \n Emphasizes coaching over advising: shift to curiosity and empower reports to solve problems rather than providing immediate answers \n Recommends dedicated deep-dive conversations on past (life story), future (dreams), and present (career action plan) to build long-term development \n Includes monitoring for joy and recovery as performance indicators; treat lack of daily joy as a risk requiring interven

READMEs answer questions your audience will have. Different audiences need different information - a contributor to an OSS project needs different context than future-you opening a config folder.