Posts

OK, you came to the conclusion that type-safety is good. It helps you get things
done in a safer manner, at least for whatever you’re working on at the moment.
So you started using types more than before to describe what a piece of code
does without the need to run. In another word, to bring forward unwanted errors.

Sometimes, we need to invoke our own brain to describe some facts about itself but in a more pleasant way to help ourselves move on. It’s not a bad thing at all, but I prefer to know the scientific facts, no matter what’s the cost.

SBT is the main build tool for Scala projects. It’s simply one of the most powerful build tools available. You’re not limited to a single method for doing a specific job and there is no predefined and restricted rules. You can automate things as much as you want. And the good news is that SBT tries to run the tasks in parallel as much as possible.

Choosing the best editor/IDE for your favorite programming language is not as easy as it seems to be. Obviously, that’s not the case if you work with the main-stream technologies or if you don’t consider yourself a geek programmer!

Right now, Scala is my favorite language and fortunately, contrary to what most developers think, there are a good number of available choices as editor/IDE. This post is about my experiences of using these tools.

Several month ago, I left Ubuntu for Arch. This post is about my experiences and the reasons that led me to move back to Ubuntu.

Update 2017-01-21: As the VirtualBox bug, which made me go back to Ubuntu, is resolved, I couldn’t resist going back to Arch. This time I tried i3 instead of a full fledged DE and I’m very happy so far.

I’m not sure if it’s a good name but as we inject types into our classes, type injection seems a good name. I used this technic in my latest project to build a database-agnostic data-access layer on top of Slick 3.

Default internationalization support in Play works with cookies which is not SEO-friendly. It would be very nice if it was possible to use route parameters instead of cookies but as Play routes are (nicely, truly and correctly) type-safe, this will come at some cost; verbosity. Albeit it’s not true for smart people who code in Scala :D

Multi-JVM tests are the default way of testing an Akka cluster sharding application. But sometimes you just need the sharding functionality where multi-JVM tests are just overkill. I didn’t find any sample or guide describing the best practices for this situation.