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
Tips for auditing UI
Separating view from non-view in React
Slope intercept library design
Prioritisation using workarounds
How to ensure that 'urgent work' is truly urgent
Topic - writing
Responding to PR changes
Estimating timelines in software
Avoid catch-all buckets
How to give feedback
Ideas
Keeping things closer to the web platform
Juggling
Open source licenses
Tech debt is a resource (or tool)
How I use Obsidian
Developer marketing tips
Innersource
The Hot Potato process
Being a catalyst for change
20241108051310-continuous-discovery-builds-relationships
Being told what to do as a senior
Writing (early) saves time
Write mostly integration tests
Software Development Life Cycle (SDLC)
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
Tech debt, and when to fix it
The flywheel effect
Three D's of Feature Leading
How to write good commits
The wrong abstraction
Building your career on dirty work
Software Delivery
Why senior engineers get nothing done
Andy Hunt & Dave Thomas - Pragmatic programmer
Write small PRs
Accuracy of estimates
Topic - product
Tech writing tips
Infrastructure as Code
Senior engineers and roadmaps
How to receive feedback
Good strategy / Bad strategy
Writing matters in remote work
Context switching takes time
Engineer manager pendulum
No feigning surprise
Dogmatic, idiomatic, and pragmatic
Make the change easy
Documenting decisions
Tracer bullets
Existing code
Topic - engineering