Working theory, observations, and stuff I've read

At any given time, the highest priority is to eliminate bugs before writing any new code.

Will Larson on Migrations, from the book Elegant Puzzle

Another excerpt from a chat with Ibra & Victor.

Excerpt from a chat with Ibra & Vic

I’ve routinely seen team morale at its highest when everyone is focused on the same goal. One task, one feature For an extended period of time Extended period of time allows people to learn each others’ rhythms. That’s not something you can speed run unless you have very self aware, or very experienced people who can also communicate well The shared context makes for reduced overheads of coordination & communication cross teams This also goes hand in hand with autonomy.…

Reminder to self - I am my main audience.

Chasing quality over quick and frequent releases

Indecision can be more costly than making the wrong decision.

Exploring how writing is a tactical and strategic skill for developers to hone.

Something to think about when engineering solutions.

Answering the question "Why does this site exist?"

An actionable map to help you get started with writing

highlights, quotes, & other interesting bits from Developer Hegemony

I read shape up a year or two ago, and I'm applying some of the principles taught when managing my own workload. I only work on 1 'other' project at a time, outside of my daily work commitments

Some Paul Graham essays & videos

You might find this podcast useful👇

Audio mastering learning resources

You might find this podcast useful👇

How I freelance & contract

A list of companies that follow principles from Basecamp's Shape up

random links from the web I don't want to lose

You might find this podcast useful👇

I recently had a chat with my BK about his experience with outsourcing portions of his freelance work. a few things he said stood out to me, & that's what I'll highlight.