Here’s some common things to do when you first setup a Pi.
Type classes provide ad-hoc inheritance which means that we can use them to create polymorphic functions that can be applied to arguments of different types. This is a fancy way of saying that we can create common behaviour for classes without resorting to traditional (
From the Neophytes Guide, Daniel Westheide describes type classes, slightly paraphrased, as follows.
Using a Raspberry Pi Zero, some cheap components and some custom software, you can build a data logger to track ambient temperature in your home for around £10. Track days, weeks and months worth of temperature data and display some pretty graphs via the web.
Pi specific instructions to disable the LED on the Edimax EW-7811UN USB wireless adapter.
Without an ethernet port, the Pi Zero doesn’t lend itself to being setup without a monitor and keyboard. This post shows how to configure your wifi using the Adafruit console lead without having to plug in a monitor or keyboard.
The Adafruit Console Lead uses the PL2303TA (a USB-to-serial/parallel converter chip) to talk to the Pi over GPIO pins 8 and 10 via USB. You can use this kind of USB to serial communication on plenty of devices but with the Pi, it’s handy to use the
screen application to effectively open a “telnet-like” terminal to your Pi.
Either when looking for work or looking to recruit, I’ve been doing pair tests in one form or another since 2008. I’ve only recently come to the conclusion that they just don’t work. At least not reliably.
I’m left wondering why we still use “pair tests” for recruitment. Is it to see how candidates problem solve? How they’d be to work with? The only way to assess these things is actually to do them. Pair tests are a poor simulation. If you want to see how someone works, work with them. Don’t pretend to work with them.
I have several versions of Java installed on my Mac. Trouble is, I can never remember where any of them are. So switching Java versions using the
JAVA_HOME environment variable was always a pain. Then I discovered the handy
It shows the Java versions are available and where there are. For example, on my machine, the output looks like this.
In the previous post, we looked at implicit parameters; parameters that will be automatically passed values annotated as
implicit. In this post, we’ll take a look at implicit functions and how they can be useful to convert things of one type to things of another.
Scala “implicits” allow you to omit calling methods or referencing variables directly but instead rely on the compiler to make the connections for you. For example, you could write a function to convert from and
Int to a
String and rather than call that function explicitly, you can ask the compiler to do it for you, implicitly.
In the next few posts, we’ll look at the different types of implicit bindings Scala offers and show some examples of when they can be useful.
An abbreviated set of JMock examples with their Scalamock equivalents.