Archive
Introductory articles are all the same: here's the new shiny (used as a noun), it's really cool, please use it. Admittedly, this post is about my new library called Kapsule, but I want to first discuss the state of dependency injection in Kotlin and hence explain what drove me to create this library.
Because Kotlin has an abundance of features and it isn't too opinionated, oftentimes you find yourself wondering which is a better way to achieve the same result. Is there any difference in readability, performance or extendability? This happens with even the most basic things like for-loops.
When writing libraries in Java, it's not uncommon to create an abstract class with some basic functionality that the user would extend. But how do you ensure that the overridden methods call through to super?
Kotlin, a relatively new programming language running on the JVM, has been making headlines as the more elegant alternative to Java in any of its applications. One of them is Android development and this talk will explore the benefits that the language offers for everyday coding.
You can now write Gradle scripts in Kotlin. So what? This talk will show you how, why and when to do it. We'll cover basic syntax and review a few simple examples that you can use in your existing projects.
Looking at web development, Spring seems to be the star of most Kotlin articles and tutorials. This talk will explore an asynchronous alternative that is Vert.x and evaluate its production readiness. We'll do that by writing a simple (but working) web API, with some neat Kotlin features to boot, and figure out what the benefits of using this framework are.
Almost two years have passed since I started droning on about how awesome Kotlin is and how much better it makes Android development.
Unless your mobile app is completely self contained, it's likely to be using a server component in some shape or form. And when front-end features depend on their back-end implementations, the app teams are left waiting for their server counterparts, wasting time and money. Prototyping can be used to mitigate that.
Revisit of last year's talk about Kotlin and its application in Android development.Summary of the changes that took place since then, new features and feasibility for production usage as it stands.
Everyone uses libraries. They are your optional way to save time on writing boilerplate code. But when to use them is a debatable question. The unspoken rule is: keep writing custom code until you get the feeling that something is so common that there must be a standard way of doing it. But there are those who disagree: those who vowed to write everything from scratch and those who never write a line of code without checking GitHub for a ready solution.