If you find these posts valuable, you can subscribe to the newsletter here!
Posts
-
When LLM-based agents overlap in scope, vending full-blown agents creates more problems than it solves.
-
Building with LLMs means running experiments, not guaranteeing outcomes.
-
Promotion beyond senior isn't about wisdom alone, focus on strategic work visibility.
-
Throttle at the entry to preserve useful work.
-
1 > 2 > 0. But man that 2 > 0 is painful.
-
Dedicate at least one engineer to paper cuts and small features. They ship quickly, boost customer satisfaction, and give engineers a fast path to earn trust.
-
Change minds in design reviews by restating their position, finding common ground, and asking genuine questions.
-
That message that bothered me for two days? I should have assumed good intent, responded privately, and suggested better wording instead of defending publicly.
-
Code that works but confuses you is worth refactoring.
-
Client-side platform tools let you start with simplicity and drop down to lower-level abstractions when you need more power.
-
We removed a huge dependency by duplicating 240 lines of code.
-
Good abstractions hide what's undesirable and expose what's powerful.
-
An example of George Pólya's problem solving method applied to a software project.
-
Lessons from junior to senior at Amazon.
-
Own your data types. Packages that expose external structs can't evolve without breaking changes, but owning your abstractions gives you room to grow.