Closed zliu41 closed 2 weeks ago
I appreciate the goal of fostering a deeper understanding of the product domain among our engineers. Personally I'd be happy to explore the ecosystem and learn from it.
However, I'd also like to highlight the importance of not overdoing this activity, the same way it doesn't make much sense for a product role to go and invest more time learning engineering, except maybe some low hanging low investment opportunities which deliver useful high-level insights / learnings.
I appreciate the goal of fostering a deeper understanding of the product domain among our engineers. Personally I'd be happy to explore the ecosystem and learn from it.
However, I'd also like to highlight the importance of not overdoing this activity, the same way it doesn't make much sense for a product role to go and invest more time learning engineering, except maybe some low hanging low investment opportunities which deliver useful high-level insights / learnings.
Regardless of whether anyone decides to spend the time on Midgard or not, I think it would be helpful if during those three days you could pair-program with an experienced smart contract developer. Many of these developers would benefit greatly from the plutus core team being empathetic to the pains of production smart contract development on Cardano, and as such have a big incentive to offer to pair (myself included). I can recommend a number of such developers who would be willing to do such a pairing, and personally I would be happy to.
If anyone wants to spend their three working days in the sprint working with Plutarch on a smart contract protocol that is pushing the absolute limits of PlutusCore and practical design patterns on Cardano, than please feel free to reach out.
The project is Midgard, an optimistic rollup scaling solution where the state of the layer 2 lives in a smart contract on the Cardano L1, and a very, very large number of validators collectively ensure the correctness of the transitions of the L2 state data.