while i’m bummed my name is no longer on this early release of the optimizing iceberg book, i’m happy to report it is all my content
Tag Archives: career
chasing new cheese (my cheese moved)
things never stay the same and i’m trying to adapt to change quickly as the quicker you let go of the old cheese, the sooner you can enjoy the new cheese
my iceberg book (early release 1)
super stoked to announce the first early release of my upcoming o’reilly book, optimizing your apache iceberg lakehouse, has been published — pull down the pdf and let me know what you think
optionality and common sense (why i returned to starburst)
i’m so excited to have returned to starburst and be focused on rebooting the devrel function, not to mention staying active in the trino and iceberg communities — long live the icehouse
my shortest gig ever (but what a ride)
wait… what??? you started evangelizing datavolo as a developer advocate and then 4 months later they were acquired by one of the biggest tech companies out there? well, yes… yes i did and i’m ready to do it again
what i do at starburst (educational engineer)
i came to starburst just over two years ago for the framework’s focus on optionality; i’ve stayed for the opportunities that have been presented to me (i’m proud to be an all-star and glad to talk about open opportunities with you)
workplace diversity (embrace it)
a short-n-sweet post reminding all of us that diversity is not a issue, but that diversity is simply an attribute of being human (and some cute graphics!)
why i joined starburst (optionality and common sense)
i’m just so excited to be working at starburst and I want to share why and to encourage others to consider joining us as we grow, grow, grow
wrapping up my 8 year hortonworks – cloudera adventure (best job ever)
what an amazing eight years at hortonworks/cloudera — the technology, the focus, the use cases, the domains, the FUN and most importantly, the PEOPLE, made this the best job of my entire career and make it super hard to say goodbye to this role
give as few orders as possible (encourage autonomy and responsibility)
micro-prioritizing can hurt your team’s ability to be autonomous and create a lack of ownership in their work