Last week I encouraged a friend to give a conference talk about some tooling he had built, but was met with mild protest.
This is the follow up post in to my explanation of
Monads for Scala developers. Read part one here.
Scala developers love to discuss Monads, their metaphors, and their many use cases.
There was a gem of “practical computing” advice nested in the comments of a Fred Wilson blog post today. I’m including this here for ease of reference, since I get asked for information sources like this often. Full credit to signmaalgebra for this comprehensive overview, included in full below. (Original comment)
I created a base Scala application repository so that I didn’t have to do it every time I started a new project.
Maybe you’ll find it useful too!
It’s pretty easy to host a static site on Amazon, all you have to do is copy files to an S3 bucket, update a couple of properties on the bucket, and voila! You can upload files via the GUI, but it’s relatively time consuming and definitely repetitive. Naturally there is an easier way.
Migrating this site from ~5 static pages to a static site generator took some time, but it will provide enough convenience for updating that it was worth it. This site is now generated using Jekyll, a Ruby project that takes a handful of text files and transforms them into a fully functioning blog or site without requiring a server to back it up.
In my programming career so far, I’ve spent most of my time lurking behind the scenes - working with data, APIs, and infrastructure. Very little of my time has been dedicated to making websites look the way they do. Before this week I didn’t know the difference between a CSS class and id selector.