CodeShmode

Or you can have a conversation with an agent to build up a requirements/plan spec, asking it to analyse existing code patterns. When it seems like the agent has a good understanding of what needs to be done and how. Ask it to implement, keeping changes as a local spike.

Ask the agent questions about all the other teams' code, reaching out to them for questions it can't answer or clarification. With agent capabilities atm this is rare or can be done fairly async: "please confirm these things".

Maybe realise your code architecture is completely wrong. Manually code up some new abstractions that fit better, write the learnings into the spec plan. Strip out any implementation that largely doesn't fit your updated abstractions. Ask the agent to migrate the code to the new structure.

Repeat until spike is operational and you're happy with the abstractions used

Chat with the agent to create a Design Doc for the approach in the spike. Create a single JIRA ticket for "Productionise CodeShmode's spike". Get reviews and feedback from stakeholders.

Integrate feedback into your spike, or even the original spec document and regenerate the whole thing.

So much of the ritual you've outlined here is overhead from working in a large org where roles are siloed. When one person is empowered to do more then the actual work per person goes down and the overhead becomes the dominant. But that overhead isn't needed anymore because one person can now do many people's work.

I've whipped up spikes in a few days that would've been a month of work across a team multiple DDs and approvals. In the past this wasn't feasible so we would need to justify what those people would work on. Now you can whip it up, show a working demo and ask "should we productionise this"

The tax dollars can go to programs that support normal folk, when the vast majority of tax collected will not come from normal folk.

Canva proper is freemium, yet they continuously add more free features

The issue being they don’t give everything away for free?

The timer would not need to be onboard the spinning flywheel, it could be on an observing quasite orbiting higher. When it's time to launch it could shine a control laser at the flywheel, which is used to time the triggering of a cutting laser at the right position to slice the payload off at the correct angle.

One timer could be used to launch multiple flywheel payloads over time

They're forced to execute their options, not sell their shares.

There would be a lot of evidence of what happened after though

> Their influence still can override the mining process that’s supposed to be the final word on transactions.

Any attempted tampering would be highly visible and why would anyone with control of that much ETH risk loss of trust in their valuable asset?

If someone wants to kill themselves and is physically able I very much doubt that going through the legal process would be the easy way out.

The web was the killer app built on the infrastructure of the internet. The blockchain ecosystem is still building it's infrastructure.

There are many ways to launder money.

I'm surprised Kleros is missing from this list

> regular people don't want to manage their keys

They don't have to, but they can if they want to.

How is that any better than telling git to ignore them? Esp when they're tightly coupled translations