Gosh, I'd forgotten the pleasures and pains of abstract review for a conference. Pet peeves this morning:

☠️ Vendors submitting piss-poor product pitch abstracts. It doesn't take a genius to see through your abstract and look you up on LinkedIn to put 2 and 2 together. (1/n) If you're a vendor, be open about your talk and its content. Pitching per se is not evil, but trying to hide it is. If you have useful things to say then perhaps your talk will be useful for the confernce. But be up front and honest about it. (2/n)

Big strategic decisions that a data team helps a company make #coalesceConf Although… you can give all the data you want and sometimes it'll still get ignored

.@bennstancil's talk at @coalesceConf is starting! @bennstancil @coalesceconf It's hard to measure the success of a data team #coalesceConf

So does @MySQL Heatwave "Lakehouse" actually act as a lakehouse as defined elsewhere and write *back* to object storage through a table format? Or it's just MySQL that can also query data that's on object storage? The latter is cool of course, but the naming is puzzling me. The press release is unclear, other than in the fact that OMG OUR BENCHMARK SHOWED WE ARE FASTER, WHO'DA THUNK IT?!! oracle.com/news/announcem…

Audience feedback at conference talks is *really* useful for speakers and organisers. It lets speakers understand what they're doing well (and perhaps what they're not). It helps organisers gauge the direction of content (more of this, less of that). Reading these this morning makes me very proud of all the speakers at #Current22 😁

Looks like a fascinating set of talks at @coalesceconf #dbtcoalesce next week. I'll be firing up my 56k modem and dialling in for several of them including: Keynote: The End of the Road for The Modern Data Stack You Know, from @jthandy and @margaretfrancis

coalesce.getdbt.com/agenda/keynote…

Can’t wait for this panel discussion at #current22 with ⁦@takidau⁩ ⁦@notamyfromdbt⁩ ⁦@krisajenkins⁩ ⁦@AdiPolak⁩ ⁦@esammer⁩ - it’s gonna be awesome!
(and it’s being live-streamed - make sure you tune in!) Are we going to have batch and streaming forever, or will they converge? @esammer says at the heart of systems lambda arch will go away and kappa will eventually win out. Once in DW perhaps batch will remain for its familiarity to analytics engineers.

#Current22 @AdiPolak talking about chaos engineering A scary list of all the things that could go wrong with data flows #Current22

Apparently data people are really boring people, so the hype around big data dying down fitted well #current22 The most boring diagram in IT. We’ve standardised the tooling around all this (except BI) #current22

#Current22 @bennstancil talks about the end of big data industrial complex Benn got into big data in 2012 at Yammer, right at the beginning of the hype

“A lot of the time you don’t need real time” *gasp* #current22

https://twitter.com/rmoff/status/1577720809497546752

“A lot of the Modern Data Stack is marketing bullshit” #current22

OMG I love this talk

Dan Sotolongo at #current22: RDBMS and SQL have stood the test of time. Sets the scene for stream processing by covering core concepts of tables and steams #current22 handling event time joins in SQL using functions.

Having watched @gwenshap and @ozkatz100 talk about "git for data" I would definitely say is a serious idea.
However to the point at the end of the video, RTFM—it took reading docs.lakefs.io/using_lakefs/d… and some other pages subsequently to really grok the concept in practice.

https://twitter.com/gwenshap/status/1567170657171181568

Where I struggled at first with the git analogy alone was that data changes, and I couldn't see how branch/merge fitted into that outside of the idea of branching for throwaway testing alone. The 1PB accident was useful for illustrating the latter point for sure.

Ryan Blue talking about Why You Shouldn’t Care About @ApacheIceberg at @DataCouncilAI:

"we accidentally compromised SQL's behaviour [as part of the Big Data movement]"… so what @ApacheIceberg gives us is "[…]remarkably like what we had in 1992" 😀

🎥 "We want you to care about the capabilities as a whole…we don't want you to have to care about the [implementation] details…if you do, then you're a DBA…and we don't want everyone to have to be DBAs anymore"

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

⚡️Writing an abstract for a lightning talk…a thread 👇️

#DevRel Lightning talks are generally 5-10 minutes. As the name implies - they are quick!

Perhaps you'd like to submit a talk, but haven't yet come up with an idea? Here are a few things that *I'd* like to hear at the conference 👇️

https://twitter.com/rmoff/status/1539283107626500097

How has the data engineering landscape changed in the past five years? Where's it going? What lessons have we forgotten along the way and are going to have to re-learn the hard way? What bad things have we stopped doing?

I've been doing this #DevRel thing as an actual job title for nearly three years now, so does that qualify me to tweet some Pro-tips? Or they're maybe just tips? 🤔
🤷‍♂️ Anyway, here are some things you really should stop doing in your presentation decks.
🧵 👇 Your slides are not your talk
Your slides are not your talk
Your slides are not your talk
Your slides are not your talk
Your slides are not your talk

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

https://twitter.com/rmoff/status/1348673309773279234

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.

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. 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!