Railslove readings #6
  • 15. September 2017
  • 2 min read
Carl cerstrand 127444
More inspirational input: Read what our team is reading to improve their skills, discover new tools or technologies and because they love the things they do. Serious insights – into our industry and into our team.


Here's what you should read:


Johannes (RIP – he left us to achieve the mastery of the universe elsewhere) found an article about serverless architetures built using Raspberrys.

Your Serverless Raspberry Pi cluster with Docker
This blog post will show you how to create your own Serverless Raspberry Pi cluster with Docker and the OpenFaaS framework.


Does the blockchain need Design? Liane discovered a piece advocating just that point.

Why Blockchain Needs Design
As blockchain makes its way into the mainstream, it will be up to designers to temper its technical complexity with usability–in short, blockchain will need interfaces. IBM is in the early stages of creating them.


Brace Yourself: $h!tloads of things you shoud know as a dev incoming. Thanks Bumi.

Every Programmer Should Know 🤔
A collection of (mostly) technical things every software developer should know. ☝️ These are resources I can recommend to every programmer regardless of their skill level or tech stack


From Timo with love:

The React license for founders and CTOs
A startup founder and ex-Facebook engineer’s story of the BSD+Patents license. Disclaimer: I’m not a lawyer, nor is this legal advice.


Chris is into tools. Literally.

CSS in JS is like replacing a broken screwdriver with your favorite hammer.
There is a real problem here to be solved - it is entirely possible to create terrible, unmaintainable, disastrous CSS. In fact, it's extremely common to do so!


Want to design architectural diagrams? Marco's resource will clear things up.

The Art of Crafting Architectural Diagrams
At some point in time, in every software project we are involved in, there might be a need to create architectural diagrams. Whether we are following a formal architectural model or not, there is a need to document some parts of the application by creating diagrams.