Do we need a whole new “Ekosystem”?

There’s a joke that if you ask a developer to code a program to process widgets, they’d rather build a domain specific language and tool stack first to make life easier for when they might one day build the software that does the actual work.

A lot of development effort is under way to build a true Kotlin ecosystem, but I don’t think it’s all good news. Read more in my latest post for NLKUG.

Coding like Gaston Lagaffe

My favourite comic hero is Gaston Lagaffe by André Franquin. The series ran from 1957 till the early eighties and has been re-issued to the present day.

At the fictional offices of the Dupuis publishing house Gaston’s job was responsible to sort the incoming mail, but instead he wreaked havoc with his irresponsible fascination for the applied sciences. Everything Gaston touched resulted in a hefty bill from the real professionals and often a quick trip to the emergency room for him and his colleagues. Gaston was impulsive, reckless, without care or a shred of actual know-how, and occasionally brilliant. Granted, he was also an animal lover and never meant any harm. He was drawn most to mechanics and electronics, but also concocted a soap that ate through six floors like the blood of the Alien.
Continue reading “Coding like Gaston Lagaffe”

Kotlin’s invoke: it looks like a duck, quacks like a duck, but isn’t a duck

SUMMARY: Kotlin has given us a fresh perspective on some very ingrained OO-habits, particularly the pervasive use of nouns for objects that have only one public method.

Speaking like a native

Pronouncing a foreign language so convincingly that you can pass for a native speaker is one of the hardest tricks to pull off. While it comes natural to young children it is something that very few adults ever master. That is because our ears have become attuned to the speech habits of our native language and we interpret every foreign language according to these patterns. Continue reading “Kotlin’s invoke: it looks like a duck, quacks like a duck, but isn’t a duck”

Acting the part

It’s not a open to debate that English is the lingua franca of programming and that it’s good practice to use English in your code. It’s equally true that a sizeable majority of developers are non-native speakers of English, many of whom work on products intended for an exclusively local domain. By this I mean software that is used within a single country, like bespoke software for the Dutch tax office. Since English is not an official language in our country, are we allowed to use these Dutch domain concepts in our code or should we translate them? Continue reading “Acting the part”