Lachlan Donald

Co-founder, CTO @buildkite, Dad, Llama Aficionado (not the model). Previously @GroqInc @cashapp @99designs.

[Lachlan Donald @lox]

@jmvldz That is pretty different to "CI will die soon"

[Lachlan Donald @lox]

@Macfeecn @tonychang430 Yeah, I came here to say exactly this.

[Lachlan Donald @lox]

@ibuildthecloud Like nested virt?

[Lachlan Donald @lox]

@meetgranola might it be worth reconsidering the default sharing setting of "anyone with the link"? It's not super clear to many folks that this means all their meetings are available to anyone that can guess the meeting identifier. It's also a bad time with the rise of data breaches (which might contain granola links).

[Lachlan Donald @lox]

@joelhooks @daradoescode If it makes you feel any better, mine is $50k a month or so.

[Morgan Barrett @MorganBarrettX]

VC: this deal would go much more smoothly if you used our preferred lawyer

First time founder: yeah of course, let’s not rock the boat here. Grateful to have you aboard

VC: this deal would go much more smoothly if you -

2nd time founder: *unholstering gun*

[Lachlan Donald @lox]

@EVStraya Fascinating, mine does it constantly on everything > chill. I had three disengagements between Bright and Melbourne yesterday.

[Lachlan Donald @lox]

@ChristineMilne What is wrong with data centres?

[dex @dexhorthy]

signal is a great word for it. Recently I encouraged folks to stop thinking in terms of "loops" and more in terms of:

"forward pressure" - what causes work to start (crashes, bugs reports, performance issues, +100 things)

and

"backpressure" - how does an agent hill climb against an outcome (linters, tests, ai review/risk judge, canaries, feature flags, +100 things)

looping these toward a desired state rather than an outcome / artifact is a powerful mental model - forward pressure increases autonomy in what gets attention, backpressure increases autonomy in getting to a super high-quality solution

9 months ago, loops like ralph were primarily used to go from point A to point B in terms of functionality, but this is just one degenerate case of a more generic control loop:

- read desired state (e.g. no open bugs, or DB perf above X metric, OR "feature Y shipped", OR "all linter warnings resolved or explicity ignored")

- read state of the world (query systems, run linters, etc)

- decide if anything needs to be done (compare to policy / desired state)

(optional: approve decision)

- do the thing (code change, infra change, docs change, process change)

(optional: approval action)

- repeat

shouts out @0xblacklight for the original framing here at AIE back in june. same logic works for evolving the control loop itself

[tobi lutke @tobi]

A huge amount of the Anti-AI code sentiment massively overestimates the quality of human code outside of a very small set of open source and high quality company codebases. Human Slop is everywhere and can trivially be improved on by any opus level model.

[Karl Clement @karlclement]

Leaving Conductor? You can bring your chats to Amp.

1. Update Amp
2. Run this in your terminal:
`amp threads import conductor --all`

Using the Amp Mac app? Open Settings, go to Imports, and click Import.

Chats in Conductor Cloud: move them to your Mac first (right-click → Transfer to local) before Nov 20.

Once you're imported, use the following code to get 3 months Megawatt plan on us: https://t.co/oxIQ7VdSMR

[Lachlan Donald @lox]

@manny4c We use and love @AmpCode at @buildkite

[Lachlan Donald @lox]

@joshprice At this point I can’t even tell if folks are joking.

[Lachlan Donald @lox]

@dannolan 👋

[Lachlan Donald @lox]

@ItsCynnamoroll @droid It’s totally possible! General solutions vs codebase-specific or language/framework specific ones are much harder though.

[dax @thdxr]

i see people saying

they're moving to iac because agents
they're not using iac because agents
they're switching to a monorepos because agents
they're moving off monorepos because agents

you're all confused man everyone is doing random shit

[tobi lutke @tobi]

When I first told @MParakhin that we were planning to move to a monorepo he said wisely:

Moving to a Monorepo is an idea that every engineer absolutely hates, and that once its there, no engineer would ever want to work at a company that doesn't use one. We will definitely do it.

[dax @thdxr]

with current token prices i wouldn't really say "cost of software is going to zero"

our token cost is double our payroll which means even though we're 25 it's like we're 75

and i feel like our output is similar to a team of 75 pre-ai. we're just able to do it without all the downsides of a larger team

this is still a good thing. we couldn't hire 50 more people. so much overhead and impossible to retain a high bar