Big Map of Content

🗺️ This big map of content lists every note in the Brainforest. Choose a link that takes your fancy and explore from there!

• A User Story is a placeholder for a conversation
• A commitment is a promise
• A poor metaphor dilutes the mental model
• A second brain is closer to a GPU than a CPU
• A shared document is not shared understanding
• A unit isn't a fixed size
• Agile Industrial Complex
• Agile in Name Only
• Agile is a perspective not a process
• Agile is a philosophy
• Agile is not the goal
• Agile
• Agility is a business capability
• Align system boundaries to business domains
• Allow architecture to evolve
• Allow ideas to emerge
• Always Take Meeting Notes
• Amplifying positives surfaces what's working
• An Option is freedom of choice
• An evergreen note is a unit of knowledge
• Analogies For Linked Thinking
• Architectural decisions must be made respecting the operating context
• Assume Positive Intent
• Attempt to push back the time to make a decision
• Autonomy requires Accountability
• Avoid Premature Optimization
• Avoid Targets Derived from Measures
• Backlinks
• Be aligned to values
• Block out focus time to reduce interruptions
• Branches are cheap in Git
• Buffer meetings with breathing space
• Building high-trust environments
• Can you consider a backlog as a portfolio of options
• Capital Expenditure
• Card, Conversation, Confirmation
• Clarify intent to align understanding
• Coaching
• Compensate for informal learning with support groups
• Consider alternative communications before booking a meeting
• Continuous Integration
• Continuous integration optimises team flow
• Conway's Law
• Culture is values plus behaviour
• Culture
• Curating a Digital Garden
• Curation of ideas broadens horizons and helps draw patterns
• Cynefin
• Decompose problems to manage complexity
• Deliberate practice
• Derive Booleans from state
• Derive documentation from source control
• Design NoSQL schema around data access
• Design objects to make invalid state impossible
• Differences Between Agile and Taylorism
• Digital Toolbelt
• Digital gardens promote knowledge accumulation
• Do not book more meeting time than is needed
• Do not conflate performance with presence
• Docker runs as root
• Effective remote working requires trust
• Estimates Reveal Options
• Estimates aren't quotes
• Evergreen notes are never finished
• Evergreen notes mature into a narrative structure
• Evergreen notes
• Example Mapping for Discovering Unknown Unknowns
• Examples clarify a rule
• Exercise an option to realise its value
• Expectations are premeditated resentments
• Experiment towards a Goal
• Experiments must be safe to fail
• Fast feedback improves quality
• Feature Injection
• Feature toggles enable small increments
• Finishing before starting new work
• Fordism
• Fragile Tests Restrict the Ability for Code to Change
• Future Work is an Option
• Gathering information reveals more options
• Give audio only breaks when not actively participating
• Goals tell us the ends not the means
• Good architecture only exists relative to a specific context
• HTML Data Attributes
• How does hypertext shape writing
• How to take notes from literature
• Hybrid meetings become necessary with flexible working
• Hybrid working promotes diversity and inclusion
• Hyperlinks are the fundamental unit of Hypertext
• Hyperlinks invite curiosity by blending form and content
• Hypertext embraces nonlinear exploration
• Hypertext
• Implicit backlinks identify unrealised associations
• Inclusivity benefits everyone
• Indirection without Abstraction is Waste
• Integrated Thinking Environment
• Interrupt Knowledge Workers as a Last Resort
• Invalidating an Assumption Generates Learning
• Iron Triangle as a Commitment Model
• Is Agile a Cult
• Is software a production line
• Journey Before Destination
• Knowledge Working
• Lean
• Learn Along the Way
• Let go of high standards to generate better ideas
• Link evergreen notes by contextual association
• Linked Thinking
• Listen to feedback from tests
• Local Maxima
• Look for new options
• Map of Content
• Mark up content semantically
• Markdown is a local maxima
• Markdown
• Measures as vectors
• Metrics are a tool for a conversation
• Microfrontend architectures compose UI at runtime
• Microfrontend architectures
• Microfrontends are a technical and a team choice
• Microfrontends enable team autonomy
• Minimise distractions to focus attention
• Never commit early unless you know why
• Not everything should be considered an option
• Not my circus not my monkeys
• Notice feelings without endorsing them
• OOP needs a Procedural Boundary
• Object-Oriented Programming
• Offices as spaces for collaboration
• One concern per test
• Operational Expenditure
• Optimise for Culture Add, not Culture Fit
• Optimise for Flow, not Resource Capacity
• Optimise workflows for the type of work
• Options expire
• Options have value
• Options reduce risk for an uncertain future
• Outcomes over output
• Overmocking Creates Alternative Facts
• People prefer to be certain and wrong over being uncertain
• Poor implementations of hybrid working strengthens presenteeism
• Prefer organic structure to hierarchical structure
• Present an Overview of Feature Toggling
• Primarily talk to the camera lens
• Product over Project Operating Model
• Promote calendar transparency
• Pull Requests can be Psychologically Unsafe
• Pull Requests can hinder Continuous Integration
• Pull Requests encourage rework
• QA as Validation
• Questions
• Real Options
• Record - Elaborate - Integrate
• Remote Workers are not Second-Class Citizens
• Remote Working is Here to Stay
• Remote working can be isolating and lonely
• Role-Playing Games
• Rules are requirements
• Second Brain
• Separate deployment from release
• Set Meeting Agendas in Advance
• Set boundaries and routines to support wellbeing
• Simple Rules Scale to Complex Behaviour
• Small improvements compound over time
• Small increments act as save points
• Software Development
• Software Economics
• Speed is a byproduct of quality
• Take Smart Notes
• Take thoughtful notes
• Target CSS By Data Attribute Value for Customisations
• Taylorism
• Technical Debt
• Tell Don't Ask
• Test Behaviour not Implementation
• Test from the outside-in
• Test-Driven Development
• Testing is clarifying misunderstandings
• Tests are Production Code
• Tests demonstrate intent
• Thank People to Amplify Positives
• The driving force rightwards on a Wardley Map is energy
• The graph of notes identifies unrealised associations
• The map is not the territory
• The medium shapes the message
• The quality of conversations drives the quality of the product
• The three types of decision outcomes
• Theory crystallises the practice
• These notes are for me
• Top of my Mind
• Transition between combat turns using narrative to maintain immersion
• Treat hybrid meetings as remote-first
• Use the language of the domain
• Use the platform
• User Stories Are Options, Not Futures
• User Stories
• User Story Cards as Vacation Photos
• User stories are told, not written
• Values are not nouns
• Vanilla JS
• Vary intensity to avoid audience exhaustion
• Video Call Fatigue is Operator Error
• Waterfall is the application of manufacturing thinking to software
• We all learn in a different order
• We can only be certain about now
• Web Components
• Web content is componentised
• What am I looking to achieve with my digital garden
• What's the difference between digital gardening and blogging
• Where does Markdown fall short
• Why Did Agile Win Over XP
• Why do I make my notes public
• Work at a sustainable pace
• Writing is Thinking
• XP
• You're Done When A Need Is Met
• About Me
• Big Map of Content
• Welcome to the Brainforest