Useful Slick Implicits
I have used slick successfully in many projects. It offers some type safety while still allowing a great deal of control over the executed SQL code.
I have used slick successfully in many projects. It offers some type safety while still allowing a great deal of control over the executed SQL code.
When using Java libraries from Scala, if the library provides some
sort of async interface you often need to instantiate a Java class
that acts as listener. This is a bit cumbersome when working in Scala,
you would expect the external library method call to return a
Future[T] so you can use idiomatic monadic operations in your Scala
code.
One annoyance I have when using Java libraries from Scala is the need to explicitly create an anonymous class every time we need to pass a callback function.
Deploying a Scala app is not simple. One solution is to build a
big fat jar with all the dependencies using sbt-assembly, or just
run the app with sbt in production.
While writing some Akka code I eventually got to a point where I
needed to test that a child actor received a message from the actor I
am testing, which I will call Manuel in this post.
When writing ruby code, you need a tool to manage your ruby versions as well all the gem you need to have installed. In this post I'll show you some of the advantages of using rbenv if you are using emacs.
Don't you hate when and elsif??
If you ever worked with a big enough distributed system, you know that at some point you need to test how the system works with a large amount of traffic before deploying it to production.
MDUnify produces a single unified and beautiful HTML document from a Markdown file.
Backbone.persistence is a simple adapter to use Backbone.js without using the REST persistence layer.