Andrew's Digital Garden
Topic - engineering
#todo - figure out what this topic is
#topic-page
Referred in
Owning projects like a senior engineer
Topic - principles
Topic - concepts
Prioritising design system work
Architecture Decision Record (ADR)
Pull requests should be atomic
The dangers of vibecoding
Code review
How I use Obsidian
Tips for auditing UI
Removing something is infinitely harder than adding something
The importance of alignment
The importance of agreement
Separating view from non-view in React
Loop engineering with AI
Slope intercept library design
Prioritisation using workarounds
How to ensure that 'urgent work' is truly urgent
Topic - writing
Creating helpful keyword bookmarks in Firefox
Responding to PR changes
Estimating timelines in software
Avoid catch-all buckets
"Getting things done in large tech companies"
How to give feedback
Plan first, code after
Limiting lines of code written
Juggling & context switching
Tech debt, and when to fix it
Open source licenses
Tech debt is a resource (or tool)
"Some mistakes I made as a new manager"
Developer marketing tips
Innersource
The Hot Potato process
Users don't care about code
Being a catalyst for change
20241108051310-continuous-discovery-builds-relationships
Being told what to do as a senior
Writing (early) saves time
Owning a platform vs a product
Write mostly integration tests
Software Development Life Cycle (SDLC)
Keeping things closer to the web platform
Situation-Behaviour-Impact Feedback
The great divide
What to do when you're stuck
Use post it notes when pair programming
What is a code smell?
Better engineers bring business value
LNO Effectiveness Framework
The flywheel effect
Five whys (5 whys)
Honesty & Pragmatism
Spec Driven Development
Three D's of Feature Leading
Writing tools with AI
A guide to problem solving at large
How to write good commits
The wrong abstraction
Building your career on dirty work
Software Delivery
Why senior engineers get nothing done
DORA metrics
Software Development loops with AI
Ideas
AI and the Software Development Lifecycle
Andy Hunt & Dave Thomas - Pragmatic programmer
Accuracy of estimates
Topic - product
Code review nitpicks
Writing tickets
Tech writing tips
The XY problem
Infrastructure as Code
Juniors and making decisions without rationale
Comprehension debt
Senior engineers and roadmaps
Definition of done
Request for Comments (RFC)
How to receive feedback
Good strategy / Bad strategy
Writing matters in remote work
Context switching takes time
Platforms are a reflection of values
Verifying AI code
Engineer manager pendulum
No feigning surprise
Dogmatic, idiomatic, and pragmatic
Make the change easy
Co-ordination cost grows faster than headcount
Documenting decisions
Tracer bullets
Existing code
Topic - engineering