Non-empty Kotlin collections is something very obvious, something on the very tip of the tongue. This post describes one possible way to implement them.

#kotlin #collections

Esoteric programming languages are different. Some are frightening, like Madness. Some are funny, like FiM++. But I've never seen anything as disgusting as Folders. There are no source code files in Folders, just Windows folders hierarchy, and this hierarchy defines our program.

#humor #esoteric #language

A strange but rather entertaining post: proof that Vim keystrokes are Turing-complete.

#vim #cs

The idea to show explicitly in a return type that function can fail is not new, yet still not mainstream either. In this post author shows us how to implement such Result monad in Kotlin. The implementation itself is not perfect (in which universe val reason: String is enough to describe an error?), but good enough.

#fp #monad #kotlin

Fetching updated string resources without re-building the app is kind of an understandable desire. However, implementing this thing is surprisingly hard. Check out the frightening log of this journey in the post.

#strings #resources

.flatMap, .filter and .reduce are nothing new these days. In this post you'll learn the .traverse. All these functional thingies are always interesting and fancy, but do they make our code more readable? I'm not sure.

#fp

There are a lot of different open source licenses out there, and it's kinda important to understand them. This resource will help you with that. The author explains popular licenses line-by-line, so that even regular people could understand all the conditions.

#oss #license #law

A repo with a bunch of links that'll help you to understand how the Kotlin compiler works.

#kotlin #compiler

An old post which is best described by it's title: The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets. Enjoy!

#text #unicode #encoding

I've never had that need, but yes, we can use Glide to load images for our WebView. Author mentions that it significantly improves performance. I wouldn't take it for granted, but would try to measure it.

#webview #glide #image

I really enjoy posts like that: author spotted an unscramble-the-words task in a local newspaper and without hesitations implemented solvers for it in three languages.

#algorithm #just4fun

Check out this new experimental tool by Google. It helps to analyze dependencies of different open source libraries. Maven support is already there!

#google #oss #deps

This one is funny: "Drunk Post: Things I've learned as a Sr Engineer"

#software #developer

Interruptions are frustrating to developers, it's a fact. In this post you'll find some trivial tips on minimizing them, but you'll also find a somewhat beautiful analogy between building a picture of a piece of code in your head and building a card tower, really liked that one.

#focus #programming

That's an interesting move by Google: AppSearch alpha is out. It's kind of a document DB tailored for fast on-device full-text search.

#jetpack #library #appsearch

Well, this is huge! A number of severe vulnerabilities were discovered in apps pre-installed on Samsung devices. Possibilities are endless: from spying and reading any file to full control over the system.

#cybersec #samsung #vulnerability

@istima shared a totally insane link: this guy has decided to reach "complete electronic independence" and has built: custom assembly language, custom assembler and custom CPU scheme. Moreover, now he threatens to physically build that custom processor. JUST BECAUSE HE CAN

#talk #cpu #assembler

An entertaining talk with a brief history of different programming languages, a nice complement for your evening: "Why Isn't Functional Programming the Norm?"

#talk #fp #language

And again, a short and simple post with a speaking title: "What Every Programmer Should Know About SSDs".

#ssd #hardware

Good old Rich Hickey and his "Maybe Not" talk. He reflects on all these Optional<String> and String? thingies and comes up with a rather interesting solution for Clojure: we need to use the same User entity with optional fields in different contexts with different requirements - sometimes we want a firstName + lastName User, and sometimes we need only id + address.

#talk #clojure #optional