Machine Learning For Engineers: Reading List 2
This is the second of a set of book reading lists written from the point of view of a software engineer who wants to develop a basic knowledge of machine learning. In Part 1, we looked at some introductory books to the discipline. Herein, we'll look at some more hands-on programming books.
Machine Learning For Engineers: Reading List 1
This is the first of a series of book reading lists written from the point of view of a software engineer who wants to develop a basic knowledge of machine learning fundamentals. In this part we'll look some introductory books and some background books for machine learning mathematics.
Thoughts for 2018
Herein some thoughts about software technology 2018. I won't call these predictions, more extrapolations of what's already happening and what the second order effects might be.
Some Books Were Read: 2017
A nice thing about 2017 was getting to read more books than previous years, with the aim of working my way back to an inveterate reader. Here are some notes on a few I enjoyed over the year.
Feature Flags: Smaller, Better, Faster Software Development
Feature flags let you work smaller, better, faster, with less risk. The leverage they provide makes them a first-class engineering and development approach.
Installing gRPC for Ruby on Mac OSX Yosemite
I've been looking at HTTP/2 recently along with the gRPC framework. One of the things I wanted to try out was cross language interchange. Herein some notes on getting things working for Java and Ruby on Mac OSX Yosemite, that might be of help to someone.
Board Games 2 - Strategy Games
This is the second of a series of posts about board games. In this post, I'll go through twelve strategy games that we've enjoyed.
Board Games 1: Family Games
I occasionally get asked to recommend a board game. Herein the first of a few posts about some games I've played and enjoyed with my family.
On Scala
This is one of a series of posts on languages, you can read more about that here.
Scala's blending of programming paradigms in a single language is impressive. It's fun to write code in and is a good language for leaning into the functional plus static typing paradigm. As much as I like the language, I usually qualify recommending it outright. Scala is the language I find myself most conflicted over - the part of me that likes programming loves it, the part of me that goes oncall has a doubt.
On Go
This is one of a series of posts on languages, you can read more about that here.
A grab bag of observations on the Go programming language, positive and negative. It bucks some orthodoxy on what a good effective language is supposed to look like. It makes sensible engineering decisions and is squarely in the category of languages I consider viable for server-side systems that you have to live with over time.
On Languages
I have been playing around with Erlang, Scala and Go more and more, to the point where I'm able to draw conclusions about them as production languages. I don't consider myself expert in any of them, but like most people in my line of work I have to be able to make judgments in advance of deep understanding. I've also spent time to a lesser extent with Rust, not enough to decide anything much. I've been foostering with Erlang and Scala on and off for years, Go and Rust are more recent.
Ubuntu Lucid 10.04 on Thinkpad W500
After over 3 years at 10 hours a day it was time to retire the thinkpad T60.