Tags→#management
A draft for AI hygiene
Humans own the merge, bots look like bots, agents live in code. Then a small fleet: reviewer, bug hunter, security, developer, community.
Joel on Software
Assign responsibilities to someONE. Prioritise PRs > Bugs > Features, in that order.
Speed is not velocity
A good leader points clearly in an ambitious direction and helps people separate activity from progression. Confusing the two is how you get exhaustion and burnout.
AI: Think of them as a summer intern
Stop treating coding models as a tool on your machine. Encode the company and give always-on AI a job.
Postpone getting a board
Early startups need speed, and a board can be a big slowdown. Alignment inside the team already eats enough time. Want input? Coffee. Want names on the website? Call them an advisory board.
Become a generalist now
IC work is the new career flex elenaverna.com The rise of the High-impact Individual Contributor (HI-C!)Becoming a skilled individual contributor is the next thing, as AI lets one person ship end-to-end. This shift increases the value of a self-propelled coder who also understands strategy, sales and operations.
Give feedback on either Speed, Quality OR Priority
Don't call the work good or bad. Name whether you need speed, quality, or alignment right now, and own the tradeoff.
Managers should be careful worrying about dev speed
When a manager worries about speed, the real topic is trust. Grunt work is not how software actually moves. Instead, think of how priorities should change.
The effective engineer 👍
Keep leverage in the back of your mind: value produced over time invested. Read this if you ship digital products.
Blitzscaling pt. 2: Management
How a company feels as it grows from 10 to 100, and the odd rules that keep it from falling apart.