Skip to main content

Functional and Idiomatic Kotlin

I've been programming in Kotlin for many months now, and there are a couple things I have noticed when working with others in a Kotlin-based project: 
  1. I greatly prefer Kotlin to Java. 
  2. Kotlin can quickly turn back into Java when people are not careful. 
I do not claim to be a Kotlin expert. I do know that Kotlin was designed to be both more functional and idiomatic than Java out of the box. Because of this, I've decided to spend some time reviewing the Kotlin documentation again. Now that I have spent a good amount of time working in Kotlin, I think the documentation can help me become better about writing idiomatic Kotlin in particular. I've already spent enough time becoming familiar with functional programming; I am comfortable with mapping, various kinds of reducing, etc. Kotlin's scope functions, however, remind me that functional is not just about basic tools; it is also about expression, keeping code ever more DRY, and idioms that help other developers understand intent.  I hope reviewing the documentation again will help me get better in these areas.

Comments

Popular posts from this blog

ANSI-92 SQL Syntax - aka "JOIN" me in software progress!

 I've run into several projects lately that don't use and/or refuse to use the JOIN keyword/syntax.  I've had conversations in these projects to help people understand that, but I wonder why this is not more common across SQL database projects.  This standard is not new, and it more easily defines the join section vs the WHERE/filter section, so it has good benefits.  So far, the only reason I have heard to not use it is "we just don't tend to do that here."  This makes me sad. I hope to continue evangelizing small changes like this in my projects, be it JOIN, use of functional programming, listening to IDE feedback (great static analysis checking... available before you ever even push!), etc.  There are so many small things that help make software easier for everyone, I think.

Spring Security - Authority vs Role

I have spent a lot of time recently trying to understand the difference between Authority and Role in Spring Security.  This is a brief review of what I found. When creating a UserDetailsService or overriding configure(AuthenticationManagerBuilder auth) in the security config class that extends WebSecurityConfigurerAdapter, I basically get complete control over what I populate inside of the UserDetails that is used/returned.  This is important because the UserDetails interface really only cares about how to return one thing: Collection<? extends GrantedAuthority> getAuthorities(); A GrantedAuthority just seems like a glorified String wrapper that names some thing.  The question is... what is that thing? This is where the subtle difference between Authority and Role comes into play. I think that Role is an older thought/construct that automatically gets plugged into Authority if we just create a user with a Role.  But completely forget about the code a...

Generating JKS Keystore for SSL/TLS

I have done this and forgotten how to do this too many times... so here are some quick references for myself.  https://stackoverflow.com/questions/11952274/how-can-i-create-keystore-from-an-existing-certificate-abc-crt-and-abc-key-fil or... this: openssl pkcs12 -export -in <CRT_FILE>.crt -inkey <KEY_FILE>.key -out <OUTPUT_P12_FILE>.p12   keytool -importkeystore -srckeystore <OUTPUT_P12_FILE_FROM_ABOVE>.p12 -srcstoretype PKCS12 -destkeystore <KEYSTORE_FILE_NAME>.jks -deststoretype JKS