@@ -141,6 +141,7 @@ We’re currently subsidizing the ecosystem’s addiction to the public endpoint
...
@@ -141,6 +141,7 @@ We’re currently subsidizing the ecosystem’s addiction to the public endpoint
-**Don’t use free-tier infra internally.** We shouldn’t use the public endpoint for internal services for the same reasons the community shouldn’t. We should use a dedicated Alchemy key per service.
-**Don’t use free-tier infra internally.** We shouldn’t use the public endpoint for internal services for the same reasons the community shouldn’t. We should use a dedicated Alchemy key per service.
-**Lock down our launches.** On-chain activity is public, so whenever smart contracts are involved in a launch those contracts should be pause-able.
-**Lock down our launches.** On-chain activity is public, so whenever smart contracts are involved in a launch those contracts should be pause-able.
-**Don’t sacrifice quality for speed.** The claims backend was rushed, and had little oversight or review. We should put a cultural stake in the ground and clearly say that we won’t sacrifice that oversight in order to make a launch.
-**Don’t sacrifice quality for speed.** The claims backend was rushed, and had little oversight or review. We should put a cultural stake in the ground and clearly say that we won’t sacrifice that oversight in order to make a launch.
-**Minimize cross-team dependencies.** The OP Labs engineering team has historically been structured by function (e.g., "frontend team", "client team") and not by product. This has increased the need for cross-team communication and increased the overhead required to ship production-quality software. OP Labs is in the process of transitioning its engineering team into a product-oriented structure which should significantly reduce the number of cross-team dependencies and generally diffuse engineering knowledge across the entire organization.
