Saying don't do it won't solve the problem unfortunately. Changing the review process so the session is tied to the code and the reviewer can ask the session/agent is the way, imo, and what we're doing at Chapter.
I took it to mean their process was more divergent than convergent. They explored some branches, felt one had life, or tension, and then unfolded from there.
Guys, this is super cool. As someone building a canvas product that also has a (prosemirror) notepad I am super inspired by this. The way you can flick from a canvas on the notepad, back to the notepad, and it doesn't feel like you're locked in to any block because you can still slightly see where you came from.. love it.
Excel is great but there’s a large audience who would benefit from something simpler and more intuitive. That’s what we are trying to build at Klaro (klaroapp.com)
We are building a collaborative workspace to help non-technical, non-financial people work with numbers. We have an ambitious goal and are looking for an equally ambitious engineer.
Key things you would be working on:
- Sync engine for local first experience.
- Building an innovative canvas experience on the frontend.
- Custom graph computation engine.
We are building a collaborative workspace to help non-technical, non-financial people work with numbers. We have an ambitious goal and are looking for an equally ambitious engineer.
Key things you would be working on:
- Sync engine for local first experience.
- Custom graph computation engine.
- Building a novel canvas experience on the frontend.
https://www.youtube.com/watch?v=dcolM6W5Odc
reply