Oceans of Wisdom

1. dev team chat (this one) 2. ideas and feedback for site/tech etc (open to all) 3. the once a day autoposted summary of the items pushed, 4. general commentary

in fact you could imagine all of the following being "subwaves"?

where someone sees something wants to share an idea, we can chat with them etc etc

and the other is a public chat in parallel

one is like this

so something like two areas - i dunno which one is wave/parent/sub

because we will inevitably then move our chat private again

but also we probably don't want a full free for all in our dev chat

and not somewhere else in brain

but it is possible that they have ideas that they want to share broadly "in this wave" whatever that means

and I think it is useful that people can read our chat

which is that this is a useful build in public wave

well we should check a real use case here

so how can we use subwaves here @[simo] so we can have our chat here but others can also chat?

but in any case, we cannot let the unmerged PRs list grow and grow :)

in parallel, we should prepare for allowing the bots to merge and deploy to staging

in the immediate term it should be: - merge and deploy all the easy/medium ones - take a very hard, deep, full team look at the 2 FE x 2 BE ones that change IPFS/Arweave handling and wallet/security handling. these need your brains engaged!

something like this is the world we are going to

so one ship with 25 people can carry across the world what used to take 2,000,000 horses and the associated riders etc

which is like 2M horse-loads

150,000 tons on the ship

they are absurdly efficient

a large container ship runs with 25-30 crew members

we are not going to be doing manual coding, 1 human per PR at a time, any more than we use camel trains, donkeys and horses to transport goods around the world and instead use container ships

but anyway it is a 1-way street

this will take a bit more work

what is it that you are supposed to be doing

how you see your role

so the issue is just identity

and accelerate from here

in our effectiveness and I think this is only going to continue

so I have done the work, taken the pain of how the tooling can support a step up

I laugh and say "wait, don't you realize that this is how all you are too?" :)

so when I see the dev teams get all worked up when 2-3-4 agents go and do conflicting things

I already have to deal with "coordination problems" and "competence problems" and "communication problems" and "people not doing what I thought I told them to do problems"

I already cannot "do all the work myself" or "check all the work myself"

I have to manage not 10, not 20, but thousands of humans already

I am obviously a worse software developer than anyone on either team, but I am simultaneously a vastly better manager than any developer on either team

because I have gone through cycle of psychological identity change with the other team, I have a sense of how it will play out

I do think the largest mental leap for @[simo] @[GelatoGenesis] @[prxt0] @[ragne] is a change in "identity" you cannot think of yourselves of a software developer any more. that job is anyway RIP. the job of engineering manager however is alive and well and very valuable. You have all been promoted to be in charge of a team! so you need to think "we each have 10 people reporting to us, how do we manage them"

and implement them in a mix of tools, scripts, bots, reports, management practices and so on

so we will steal / copy the systems of large human engineering organizations

is that you personally review each PR? probably not!

so if you are the CTO of Microsoft, how to you keep the 20,000 people pushing to the Windows monorepo effective?

There are companies that have had 30 developers and 300 developers and 3000 developers and in some cases even 30,000 developers for decades now

Fortunately , we do not need to invent this from scratch

- we did a nextgen and raise $10M to accelerate development - we hired 30 developers to help you - how do you make them effective - it certainly is not "you are going to sit with each one of them and work with them on each PR" because if you do that we will have the same outcomes as if we have 4 developers, in fact, worse outcomes

your mental model conceptually is something like this

yes and with increasingly powerful tooling to make this process better

so there needs to be regularly schedueld deployment bus service