Brian Conn

Building software and teams with agents and humans. Founder of Connsulting, co-host of Manager / Builder.

[Brian Conn @TheConn_Man]

Rebooting my X. Expect a lot of AI talk. Planning to discuss how and what I'm building these days.

[Manager x Builder @managerxbuilder]

We used to work together. One of us still manages. One went back to building. AI smashed those jobs into each other, so we started arguing in public.

Manager x Builder. Three episodes up.

[Brian Conn @TheConn_Man]

@housecor Behavior and tests are abstractions on top of the code. Code is and will always be all that matter. I do think we'll stop reading all the code, though. Abstractions allow humans to try to make sense of it at scale.

[Brian Conn @TheConn_Man]

@henrytdowling I cycle through Claude, Codex, and Grok. Any work a model is doing is instructed to get a review from one of the others. All based on how much usage I've got left for the week. I found even an Opencode Go subscription did a decent job pushing back on bad plans.

[Brian Conn @TheConn_Man]

@mollsack1 You know these tweets are public, right?

[Brian Conn @TheConn_Man]

@Patrick_Wyman This episode was great (they all are, though). Do you have any non-academic books you recommend around medieval economics? Anything that touches on the commercial revolution, double entry bookkeeping, and trade route development?

[Brian Conn @TheConn_Man]

@SirZach @Createors Doesn't work with pets. Literally unusable.

[Brian Conn @TheConn_Man]

@astroneergame Could you let us know how many people can play at once in 1.0? We need to know how many people to invite to the release parties.

[Brian Conn @TheConn_Man]

Balancing IC work with a "tour of duty" managing: https://t.co/27fg7n1NoT

[justice beaver @mollsack1]

There was a woman sitting in front of me and Emily on the plane who spent the entire plane ride writing out on her phone notepad how much hatred she had for the woman next to her eating cheddar popcorn. These are my favorite lines. These....are the cheddar chronicles.

[Brian Conn @TheConn_Man]

@QuinnyPig @copyconstruct Where does the cost usually come from? Bad reservations? High I/O? Too much data? Misunderstandings about serverless not being costless?

[Brian Conn @TheConn_Man]

@tpwky Just finished Gnarlypox. Have either of you seen https://t.co/ATxPJzxld3? It terrified me as a child.

[Eric Elliott @ericelliott_]

There are only two hard problems in distributed systems:
2. Exactly-once delivery
1. Guaranteed order of messages
2. Exactly-once delivery

[Brian Conn @TheConn_Man]

MRW I'm trying to get used to Gmail again instead of Inbox

[Brian Conn @TheConn_Man]

Today's the day I start transitioning back to Gmail off of Inbox 😢

[Brian Conn @TheConn_Man]

4PM: When you snooze all your Slack notifications until tomorrow.

[Charity Majors @mipsytipsy]

This is an excellent best practice for a number of reasons.

* time is consistently allocated to improving prod tooling
* keeps everyone practiced and fresh
* less context switching
* relieves pressure to ship while on call
* treats on call like real work

[My Public Apology @mypublicapology]

To My Cats https://t.co/I1osszc7w2

[Ben Grinnell @Ben_Grinnell]

“Every time you get paged you should have no idea what is wrong” @mipsytipsy #DOES18 predictable problems have all been automated out of existence