Oliver Kennedy

124 Followers
199 Following
1.5K Posts

Oliver is a CSE Prof teaching databases and data structures. He enjoys HEMA, cooking, photography, home automation, and coding random stuff. He built a notebook for collaborative, reproducible data science called Vizier (https://vizierdb.info) and now works on scaling datalog on commodity hardware (https://git.odin.cse.buffalo.edu/Norn/Draupnir)

Expect posts here to be mostly about #draupnir, #vizier, bad puns, #photo graphy, and/or travel logs.

[He/Him]

Homehttps://odin.cse.buffalo.edu/people/oliver_kennedy.html
DBPL @ UBhttps://cse.buffalo.edu/dbpl/people/

@jonmsterling @pamorim @chrisamaphone Not PL, but one of my industry colleagues once described a heated discussion he had with a heavyweight in the database community. After discussing their respective approaches to a problem, he finally exclaimed "I understand now. Your idea is publishable, and my idea is implementable"

Humor aside, research publication requires novelty, not functionality... and complexity is an easy way to signal novelty to reviewers who are overworked, underpaid, and likely to be lacking at least some context. It's definitely an uphill battle when the novel element is in the approach's simplicity compared to prior work.

@dev Still looking? I'd be happy to write a letter.
@natefoster You need to adopt XML if you're going to get anywhere in today's fast paced data exchange. Not having a DTD is a one way ticket to being left behind.

SciEnCV now supports XML C&P uploads!

(/me detours into an hour of writing scripts to generate appropriately formatted XML)

@aud @jonny @lina @SnoopJ @ricci Goose-typed objects also tend to leave a bit of a mess... it's hell on the garbage collector.
@okennedy @jonny @lina @SnoopJ @ricci is goose typing where a variable bites you until you get its type right?
@aud @jonny @lina @SnoopJ @ricci False. Python is duck-typed, not goose-typed.

Refactoring #Draupnir 's scheduler, the power of reactive programming really came to the fore. We want a lot of expressiveness out of our workflows, and that forces the scheduler logic into a giant mess of dynamically interlocking state machines.

A recent refactor using a reactive programming paradigm led to much more readable "pull" style code, more visibility into current state, and far far less book-keeping logic and state. So much nicer!

@lindsey It's unfortunate that the student still hasn't found that sort of passion in their own lives yet. Ah well... they're young and (probably) have time.
For the causal separation diagram enjoyers: Harry Goldstein hacked together this "Lamport-CSD Explorer" https://harrisongoldste.in/lamport-to-csd/
Lamport-CSD Explorer