Please don't pay me.
Yeah, you read that right - don't pay for the Primer. Everything in the Primer is free of charge, and I want it to stay that way. I want it to reach the broadest possible audience and don't want any part of it to be exclusive, live behind a paywall, or be dependent on any kind of contribution. I don't want to feel pressure to produce, and I only want to write when I have something of value to say, not because I feel an obligation to deliver to my supporters.
I wrote the Primer because I wanted to give everyone with an internet connection the ability to learn what I learned. I was, and am, obsessed with explaining things in a way that clicks, instead of reusing explanations that can be found elsewhere. One of the most challenging chapters to write was the one about generic variance - a subject that has been explained time and again for decades and could easily have been delegated to a different resource. But I was not satisfied with other resources - they didn't make it click. I felt like it could be done better, and I agonized for days before finally arriving at an explanation that felt right. I want this to continue to be the only reason I create content, and I want that bar of quality to stay exactly where it is.
That being said, there's honestly nothing more heartwarming than finding out somebody read the Primer, and it impacted them enough that they wanted to give something back in return. If - and only if - you're so delighted by what the Primer has to offer that you feel a simple "thank you" doesn't cut it - only then should you consider Buying Me a Coffee. The gesture means more than all the cash in the world.
Recent supporters
Hey Trondkla, thank you so much! I'm happy you enjoyed the parts about Result, and if you're interested, I actually gave a talk about error handling not long ago that you might find interesting. Near the end, there's some code demonstration, and if you look carefully, you'll see that it's exactly the same type of problems that you encounter with Result, but from a different point of view. You might also want to give Arrow.kt a look. https://www.youtube.com/watch?v=7NQC4WBKfQk Have a great day!
Thanks! I'll certainly check both out!
nikita ha offerto un coffee .
Hey Nikita, thank you so much for the support and gesture. How are you finding the Primer so far? I'd be delighted to hear any feedback you have.
Hi Gabriel, thank you so much for such a great source of information!I've been using Kotlin for the last few years at work but have not felt very comfortable with the language. The Primer, I think, provided me with the missing information, provided me with a sane structure, and highlighted things from a different perspective.One of the issues I had when I started with Kotlin was that it felt like Java with a nicer syntax, especially when working in teams with mainly Java people. Primer resolved that conflict, and now I have a good understanding of doing things the Kotlin way and why it's better than in Java.In addition, just a few more points that I especially liked:- tagging each article with an icon, so I knew what to expect and how to prioritize reading- presented FP concepts in a very approachable and practical way- nailed down scope-functions. I think I finally got them- delegation finally clicked- ...There are more points; just don't want to repeat the book structure :)And thx for the exercises!