otherwise we have a situation where anyone starting a ticket now
Shit Punk Says
Oceans of Wisdom
19,550
matching drops
#1511708
2026-10-12 06:03
and then the human part should be checking the deployments before taking to production
we should let the bots go all the way to deploying and doing their own testing on staging
i am almost certain this is not the answer
random idea for starting, ai loop what can order them logically? ones what are not affecting each other and can be done parallel + then ordering confliced ones in good order
bc valued Human Team Members (tm) have to sleep, eat, etc
there is no reason to stop them working and iterating
they can do that on staging
the bots are pretty capable at E2E testing
but they go through, merge, deploy on staging, and we hold them there
which that holding point should not be at "raised a PR"
but my guess is that the stable case is to actually use staging for what it is meant for
we can discuss at the end of the day
and it is going to cause conflicts down the line
we are going to have lots of parallel branches stuck in review
which they are going to get jammed on review
but I think I know the outcome what is going to happen
I am going to give you all a couple of days
now back to the PRs
ok lets try this
we can try
it is an interesting quesiton
I guess that is something like a detailed full daily summary of what happened
and then we would make something else that is a wave
but we can think about it
i dunno if it shoudl be everyone
ofc in that case we might want to loosen up the posting rules
we have the automations but we also discussion our BOD, EOD anything that is not a sensitive topic can move here
so anything we would previously do in our dev way, can just move to here
we cover new PRs, merges and we move our dev chat here effectively
ok so I think this can be then "everything"
that is somewhere else
maybe a detailed daily summary
and then we need something else I think that is more summary
which is interesting in a different way
unless if we are basically making this our coordination area for dev-ing and we are just dev-ing in public
is there any need to show twice?
is there any need to show twice?
do we need to show on both? I was thinking just to show on merge
@[punk6529] just to be clear. you want to summarise at the time of merge not at the time of creating the pull request, right? I think this makes sense because only at the time of merge we'll have the full context. This would mean that we'll leave the not so human friendly current PR trigger messages and we would add a new hook when PR actually would be merged to main which would have nice summary, what got merged.
and we have to speak to them in "their" language
because there are like 100 people here and 8 billion people not here
but making it useble, legible, comprehensible both to the people who are here but even more importantly, all the people who are not here!
and the work is not just "shipping it to main and deploying"
that will allow us with a small team to do the work that previously would have required a much larger team
so we can think about this not as some weird one-off, but as a repeating pattern
between:
a) @[prxt0] will get a new role as personal wallet consolidation concierge and
b) the bots will help you
the answer will be b) over and over again
"consolidating your wallets is a UX nightmare"?
almost every other "previously unsolvable" UX problem of this type is going to be solved in this way
and to be clear so we get everyone aligned with my way of thinking
quite the opposite
we do not have to fight about about the scarce resources of "this is the title of the PR" and unfortunately we are out of characters and out of pixels and we cannot (sadly) communicate to our friends and colleagues what we are doing because pixels and characters have been rationed!
but fortunately now we do not have to make hard tradeoffs, hard decision