Developer turned Evangelist @ Pusher
🇪🇺 afficionado. Lover of everything hoppy">
I speak to people about things on occasion. I am available for speaking at conferences, meetups - either technical or keynote / motivational, as well as appearing on or moderating panel discussions, podcasts, or serving on CFP reviewing committees. If you'd like me to come and speak at your event please contact me.
I prefer the topics that spark my interest. These days that's mostly Kotlin, Serverless, SDK development, and API design, and in the past it's been Android and testing related topics, as well as a pinch of public policy. Besides that, I'm always interested how great products are made, how teams work together, and how developer communities function.
We all know that Kotlin is a flexible language - it’s part of the appeal! It’s actually so adaptable it gives us powerful tools to create a mini-language on top of it (a DSL - or a Domain-Specific Language), that is better suited for a specific task at hand. Think about Anko, or Kotlinx.html - they are both DSLs.
In my talk I will take you through the process of designing and building a simple DSL in Kotlin. I will explore the common use-cases, and what features make Kotlin especially well suited for the task. It will involve live coding.
Few technologies allow us to interact with our app users when our apps aren’t in the foreground. Notifications, and Push Notifications systems allow us to do just that. They are also almost universally hated by users, because most notifications just plain suck.
In my talk I’ll be exploring the reasons why that is the case and why you should be designing your notification experience to be relevant first and foremost.
This goes from knowing who to notify, when to notify them, and what is the correct amount of information to serve. (No easyJet, your SALE NOW ON notification is not that). The iOS and Android platforms are mostly equivalent in what they allow us to do, but still have a few important distinctions.
In early 2018 I ran a survey of the global Kotlin ecosystem. My goal was to learn how developers use and adopt Kotlin - either in work or side projects, or just for playing around, and what are some of the most popular resources for learning it. The survey was a great success, and gained over 2000 responses in total! The results are meant to become a resource for the Kotlin community. Something we can all look at for interesting insights that will also help drive adoption of Kotlin in our teams and organisations.
To give you a taster, here’s a few questions I asked in the survey: How big is Android as a proportion of all Kotlin developers Are people happy naming libraries and tooling with K What are the favourite features of the language What kind of DSLs are people building with Kotlin and for what use-cases
In my talk will answer all these questions, and more. But be warned, some answers might surprise you.