kt.academy Logo
Jordan profile

Jordan

I have been developing on and off since I was 10. I started developing full time since I graduated from the University of Utah. I started evaluating Kotlin as a viable language since version 0.6 and have been using it as my primary language since version 0.8. I was part of an influential team that brought Kotlin to my entire organization. I love playing table top games with my family.

Reviewed articles

Effective Kotlin Item 10: Design for readability
10/24/2022
Marcin Moskała
Marcin Moskała

Effective Kotlin Item 10: Design for readability

Do we really want out applications concise, or do we rather want them readable?

Learn morelearn more icon
Effective Kotlin Item 7: Prefer a nullable or Result result type when the lack of a result is possible
10/19/2022
Marcin Moskała
Marcin Moskała

Effective Kotlin Item 7: Prefer a nullable or Result result type when the lack of a result is possible

Why should we prefer to avoid throwing exceptions and using types to our advantage.

Learn morelearn more icon
Effective Kotlin Item 5: Specify your expectations for arguments and state
10/12/2022
Marcin Moskała
Marcin Moskała

Effective Kotlin Item 5: Specify your expectations for arguments and state

How do we specify requirements and expectations in Kotlin.

Learn morelearn more icon
Effective Kotlin Item 1: Limit mutability
9/28/2022
Marcin Moskała
Marcin Moskała

Effective Kotlin Item 1: Limit mutability

Why it is so important to limit mutability, and how Kotlin supports it.

Learn morelearn more icon
Effective Kotlin Item 32: Consider factory functions instead of secondary constructors
7/25/2021
Marcin Moskała
Marcin Moskała

Effective Kotlin Item 32: Consider factory functions instead of secondary constructors

What factory functions are and why they are so important patterns for object creation.

Learn morelearn more icon
Effective Kotlin Item 36: Prefer composition over inheritance
4/25/2021
Marcin Moskała
Marcin Moskała

Effective Kotlin Item 36: Prefer composition over inheritance

Years of OOP made us overuse inheritance. Instead, we should more often use a composition that is safer and more explicit. More often, but not always...

Learn morelearn more icon