Archive for the ‘engineering notebook’ Category

In some programming languages there is an essential, powerful tension between two common pieces of advice: Don’t Repeat Yourself and Meaningful Names over Code Comments. Both are really good pieces of advice. “Don’t Repeat Yourself” (DRY) means that if you can find an abstraction that allows you to avoid repetition in your code, you can […]

I have a problem with the shiny. It’s the whole ADHD/Interictal thing interacting. There are so many things I want to learn and I haven’t got the time to learn all of them. Right now, I’m going back to a well I’ve gone to a number of times and dived deep into interpreters and… other […]

The second thing I’ve been reading about this week is OpenAPI, a way of specifying REST APIs. Well, a way of specifying the API for a server that defines its actions in terms of well-known endpoints and HTTP verbs like GET, PUT, POST, and DELETE. (As well as HEAD, OPTIONS, PATCH, but presumably not the […]

I’ve been doing poorly on my engineering notes recently, mostly because I haven’t been having many successes worth writing about. On the other hand, I did manage to get something working in Go. At work, we had a problem: We wanted to deploy CookieCutter, but we wanted it deployed as a service and we wanted […]

I’ve been reading about implementing advanced collections in Rust thanks to Alexis Beingessner’s wonderful, if perhaps excessively opinionated, lecture on “exceptional” collections1. Rust’s enforced memory correctness requires the programmer to make intelligent decisions about references and move semantics, stuff no one’s ever really had to think about in C or C++. I’m having a hard […]

Subscribe to Feed



July 2020
« Jun