Shahir Daya (@shahirdaya) 's Twitter Profile
Shahir Daya

@shahirdaya

CTO at Zafin | Former IBM Distinguished Engineer - My Tweets are my own.

ID: 1077418874

calendar_today10-01-2013 19:03:09

1,1K Tweet

393 Takipçi

1,1K Takip Edilen

Shahir Daya (@shahirdaya) 's Twitter Profile Photo

This is a great read. I couldn't agree more on data sovereignty. This is so important. Thanks 🕹️ Alexander Gallego ⚡️ for writing this blog. redpanda.com/blog/kafka-red…

Shahir Daya (@shahirdaya) 's Twitter Profile Photo

Couldn’t agree more. Early in the life of the platform we try not to say No but than end up adding capabilities that no one else needs. So I think asking if the use case is strategic, do others want it i.e. will it be reused, etc. are important to ask before saying Yes. Thoughts?

Shahir Daya (@shahirdaya) 's Twitter Profile Photo

This is way cool 🕹️ Alexander Gallego ⚡️! We are doing some research in this space as well to leverage OpenAI for code generation. And yes some focused on Redpanda. Let's talk more on this next week.

Shahir Daya (@shahirdaya) 's Twitter Profile Photo

Excited to join Bill Borden in co-hosting the Financial Services Executive Luncheon on May 18th in NYC. Let's dive into core modernization together. ⁦zafin⁩ ⁦Microsoft⁩ #financialservices #coremodernization #innovation linkedin.com/posts/william-…

🕺💃🤟 Alexander Gallego (@emaxerrno) 's Twitter Profile Photo

Regardless of the replication mechanism you must fsync() your data to prevent global data loss in non-Byzantine protocols. Here is a reproducible data loss on your laptop redpanda.com/blog/why-fsync… multi-az is not enough as advertised.

Shahir Daya (@shahirdaya) 's Twitter Profile Photo

We’re excited to share the prelude to our new monthly blog series on Core Modernization, “Empowering Banking Systems for the Future: Unraveling shaping forces and core system change” zafin.com/insights/thoug… zafin #coremodernization

Jean-Michel Lemieux (@jmwind) 's Twitter Profile Photo

I’ve retired from software… process. No scrum, dds, tdd, stand ups, devops, sre, micro services, retrospectives, pre and post mortems… Instead, we just build and run software together. We do use an issue tracker and a good readme. Everyone posts an eod update to our group