Homepage
The Curious Case of Quentell
I go on a journey to learn about a man named Quentell, and discover unsettling things about the information landscape.
The Humble For Loop in Rust
Rust has some really nice functional programming facilities built in, all around an iterator concept. Rust being focused on performance and low level control makes it possible to use this without paying a performance cost. Sometimes I still prefer to use the humble for loop though. In quite a few cases, it combines high performance with high readability. I thought I'd motivate why. β¦
The Humble For Loop in JavaScript
I've seen some programmers try to avoid the humble for loop at all costs, in favor of more functional abstractions. I'm going to argue that the for loop is sometimes simply the best option. That doesn't mean you should always use it -- far from it -- but it does mean you should give it due consideration. The goal is to help develop some intuitions about this topic. I talk about readability of code in this post, but I also talk about performance. My argument will be that there are cases where the for loop combines readability with performance. I'm focusing on JavaScript as the example language, but it can stand in for many languages with similar characteristics like Python and Ruby. But the culture of JavaScript leans more towards functional programming patterns than these other languages, so I think it's the appropriate language to highlight. β¦
Question Best Practices
In software development we have best practices. These are the distilled wisdom of software engineering, and you should follow best practices to be a good software developer, and to develop good software. If someone points out you broke them, that should be sufficient to make you mend your ways. This is what the term "best practices" implies to me . There are different, more subtle interpretations, but I think this interpretation is a reasonable one and in actual usage. Let's go into its problems. β¦
I Was a 1980s Teenage Programmer Part 5: Achieving Assembly
Part five in a series about my teenage adventures learning about computers and programming in the 1980s: achieving assembly
I Was a 1980s Teenage Programmer Part 4: The Call of Assembly
Part four in a series about my teenage adventures learning about computers and programming in the 1980s: the call of assembly language.
The Tooling Shift
Tool maven versus language maven. Do modern development environments enable you to be both? How does this affect languages?
I Was a 1980s Teenage Programmer Part 3: MSX-2
Part three in a series about my teenage adventures learning about computers and programming in the 1980s: the MSX 2 computer.
JavaScript: when you need two ways to do it!
Wherein we discover JavaScript always gives you a choice.