[celdon25]

I actually had to use this about a year ago to build a SOAR system at a Fortune 500 company. The Tines team was pretty responsive to questions and requests for help, and they even sent me a nice box of swag. The box arrived after I resigned from that job, however.

No matter how many niceties you put on flow-based programming, the tools I had to use (all serverless) were the wrong ones for the job, and management was unreceptive to feedback (they wouldn't even give me a github repository).

I think Tines has potential but it's going to have to invest more into mitigating its shortcomings, not just further improvements on what it already does well. For example, as of March 2021, it was still far too easy to misclick and break something in production with no confirmation. You could export your setup as json, but IMO there was too much friction/manual work with that approach for it to be useful. To be fair, the company was pretty early stage at the time, maybe it's improved since then.

I don't blame Tines for what was the worst job I ever had (which I still have nightmares about to this day), but maybe someone else can be avoided the same fate with this feedback.

[thomasdub]

Thanks for the feedback! We've implemented a ton of features since then, most notably story history & versioning, annotations for documenntation, better alerting on changes (e.g. no event in 24 hours etc.), but recognise there's still a long way to go. I'd love to hear some more feedback if you want to DM me, it sounds like the project was a bit of a horror show!