ishmaelsamuel

3 ms·

1. 1.▲
   by ishmaelsamuel 6y ago

   Thank you! We built it ourselves in React, though we used the styled-components and react-beautiful-dnd packages for building the components and helping with the dragging functionality. - https://styled-components.com - https:&
2. 2.▲
   by ishmaelsamuel 6y ago

   Ahh, gotchya. We're not using Kafka or any tools for code gen / boilerplating code.
3. 3.▲
   by ishmaelsamuel 6y ago

   ( ͡° ͜ʖ ͡°)
4. 4.▲
   by ishmaelsamuel 6y ago

   Heya! We have given some thought to implementing CI, reviews, and a sandbox environment. We've built out some testing functionality that allows users to test their workflows and steps, and we're going to continue down this road to
5. 5.▲
   by ishmaelsamuel 6y ago

   Writing the code yourself is always going to give you the most flexibility. This comes at the cost of complexity and domain expertise. If you wanted to run something like this on a schedule, monitor execution results step by step, ensure yo
6. 6.▲
   by ishmaelsamuel 6y ago

   Noted, adding your use case to our internal board
7. 7.▲
   by ishmaelsamuel 6y ago

   Thank you!
8. 8.▲
   by ishmaelsamuel 6y ago

   Thank you! Our cofounder @fooly_wk did it himself. We've built everything in house.
9. 9.▲
   by ishmaelsamuel 6y ago

   Hey! We're not exposing anything like Kafka to our end users. We think all of the underlying technical infrastructure should be abstracted so the users can focus on their core logic. We're also not currently exposing any external