I once worked as a part of a company with four employees, all of us programmers. We formed a sort of daughter company with a bigger—though still modest-sized—company that handled our payroll and whatnot. Our work directly helped the parent company, but we were organizationally independent development-wise. I really liked working with that small team: we had a one-hour meeting each week to plan out our work, and a short, casual stand-up each morning to get things rolling. Almost all my time was spent building features and squishing bugs. I got a lot of really good feedback on all my pull-requests, as everyone there really cared about making a good-quality product.
...
23 Jan 2023
Background
#
This is a question I’ve been wrestling with for a little bit. My first experience with a type system was with Java, and I didn’t like it. It just felt like an annoying constraint on the kinds of programs I could write. I was coming from Perl, which sports weak dynamic typing, so Java’s rigidity came as a bit of a shock.
After Java I learned some C, which too has types. C’s types are different from Java’s in a big way: in C they’re really just directives to the compiler on how to interpret some bytes. “Everything is just void *
” is kind of true. In C, bytes can be interpreted however you wish.
...
27 Dec 2022
Are you tired of having a particular buffer pop open in the wrong direction? Do you wish, for example, that the Racket REPL buffer showed up on the right in a vertical split, rather than below in a horizontal one? Look no further. I give you, display-buffer-alist
:
(add-to-list 'display-buffer-alist
'("\\*Racket REPL </>\\*"
(display-buffer-in-direction)
(direction . right)))
That little snippet will make sure when you hit C-c C-k
inside of a racket-mode
buffer, a REPL will pop up on the right-side instead of on the bottom. I find that much more comfortable to use.
...
5 Dec 2022
I'm well aware that I may have a bit of an obsession with fonts. I don't think that's too unusual for someone who works in tech, however. Sites like Programming Fonts exist to let people test drive and compare a bunch of different fonts. Just for fun, I thought I'd write up some of the features I look for in a programming font that I've come to deliberately pick out.
Critical letter forms: i
, I
, l
, 1
; o
, O
, 0
These are probably the most important letters to get write in any font that's meant to be hyper-legible: lowercase l
must be easily distinguishable from an uppercase I
or the number 1
, and the lowercase i
should stand out nicely as well.
...