Similar thoughts (btw I came here looking for your comment ha!).
I guess you had mentioned in one of the videos that at Fivetran, it is your responsibility to ensure data integrity across all of the sources/integrations, and has been since the early days. This led the customers to trust the product in the early days and the team to draw learnings from abstract patterns across sources.
Have come to believe that it is THE MOST important thing to have an explicit ownership for issues whenever there is physical movement of data across an org's ecosystem.
How do you determine this explicit ownership for issues? I've come across many governance problems linked to a lack of transparency in "bug ownership", but I've often failed to find a common ground for clients and third parties: who's responsible? Who should pay for it?
Quite often it's the one with the loudest mouth or the biggest sponsor who wins.
Yes, a mix of 1 & 2 possibly -- am trying not to think too much about the implementation at this stage tbh.
Problem statement remains that every major SaaS app has an API available - while that's good, an API is still an engineer's tool. These apps can't really expose SQL on the go on their apps given a. multi-tenant architectures b. transactional/nosql databases used.
However, an ideal solution does seem like a mix of 1&2 in my mind. An easy to use SDK (?) to make any SaaS app have the capabilities of Stripe Sigma.
If I am looking to build an MVP and assuming that I can learn both native and React/Flutter like frameworks -- which one would you suggest based on the learning curve in both?
Noticed a similar increasing trend for remote in the past few years. As someone who is not even in the US, even remote jobs do not add value since most don't provide VISA sponsorship.
Yes, if someone were to regularly post startup / smallCo / R&D job openings in more affordable locales than the usual megabuck cost of living megalopoli, I'd subscribe. Raptly.
Can you please post a reddit-AMA style proof to assure users that it really is you. It is unbelievable that you weren't aware of HN and that the profile was created just a few hours ago. Thanks. :)
I guess you had mentioned in one of the videos that at Fivetran, it is your responsibility to ensure data integrity across all of the sources/integrations, and has been since the early days. This led the customers to trust the product in the early days and the team to draw learnings from abstract patterns across sources.
Have come to believe that it is THE MOST important thing to have an explicit ownership for issues whenever there is physical movement of data across an org's ecosystem.