Discover and read the best of Twitter Threads about #kafkaSummit
Most recents (6)
1. Here’s a summary of my #kafkasummit talk for those who missed the live stream with links and pics of all the things we announced! 
2. This was probably the most new open source stuff, cool at-scale cloud details, and new Confluent features I’ve ever had in a keynote. But it was too exciting to leave anything out.
3. I gave an overview of the stack that is emerging around Kafka, the Data Streaming Platform. There are a couple of components to this. There’s Kafka of course, but increasingly the key other layers are the connectors, stream processing, and tools to govern streaming data.
For a conference about data, you'd rightly expect that we use data when evaluating sessions and building the program for #KafkaSummit and #Current22. It starts with the program committee (confluent.io/en-gb/blog/int…) reviewing all the submissions with this: en.wikipedia.org/wiki/Elo_ratin…
The output from the session reviews is a single score for each talk, which then forms the basis for the first pass of building the program. Some talks are obviously great … whilst others are obviously not
This is just the beginning of the process. If we built a program on abstract score alone it probably wouldn't be a very balanced program. There are many more factors to take into account.
The first #KafkaSummit CfP office hours is TODAY!
IST 21:30
MSK 19:00
CET 17:00
GMT 16:00
EST 11:00
PST 08:00
everytimezone.com/s/15d8846f
To participate, join our Slack group and head to the office hours channel: cnfl.io/slack
IST 21:30
MSK 19:00
CET 17:00
GMT 16:00
EST 11:00
PST 08:00
everytimezone.com/s/15d8846f
To participate, join our Slack group and head to the office hours channel: cnfl.io/slack
The CfP office hours is a chance for you, a prospective speaker at #KafkaSummit, to come along and chat with others familiar with the process.
Perhaps you've got an idea but you're not sure if it would be suitable, or maybe you've got your abstract drafted and would like someone to read it over and give feedback.
Getting ready for my "I don't always test my streams" session at #kafkasummit #streamingselfie #speakerselfie
💁♂️ There was a question during my #kafkasummit talk about how to test co-group in @kafkastreams.
Answer is always - there is #kafkatutorial for this
kafka-tutorials.confluent.io/cogrouping-str…
Answer is always - there is #kafkatutorial for this
kafka-tutorials.confluent.io/cogrouping-str…
Submitting an abstract for a conference? Remember the basics like paragraph breaks. If a reviewer finds it harder to read yours vs another, guess which one gets favoured?
A popular conference is going to have 100s of submissions, and little things like this matter, a lot.
A popular conference is going to have 100s of submissions, and little things like this matter, a lot.
It would be great to think that reviewers can telepathically discern your intent in an abstract by spending 20 minutes poring over the words, right? In practice, you're lucky to get 20 seconds. Layout, grammar, spelling, verbosity - all these matter!
Verbosity is an interesting one. Too verbose and you get marked down for being too unfocused, the concern being that if you can't pinpoint the purpose of your talk concisely in an abstract are you just going to waffle in your actual talk?
