Creativity, curiosity, and code
Previous Tip: Don’t inline everything! This is a little naming convention that I find really helpful. If a variable is Boolean type, or if a function returns a Boolean type, then consider if you can name it with an “is” or “has” prefix (or somewhere in the name). Because in many cases, not doing this […]
I want to talk (again) about friction. Things that slow us down. How some friction is good, and some is bad.
I made a server-less Scrabble clone that saves data in URLs. This post explains why and how, including a primer on binary data representations, and a little JavaScript library to help do this using BigInts!
There is a balance to be found between "inlining" multiple expressions, and using temporary variables. You may also learn about short-circuit evaluation here!
Refactoring complex conditions to make them more readable and easier to work with.
You kinda have a relationship with code from your projects. You probably have feelings about it. As I've been thinking about code style, I've also been thinking about how it's important to build up trust in a code base.
Poor code readability slows us down. So I'm going to post some of my code-readability tips! This is an introduction with the ideas behind it and all the caveats.
A super simple asset-watching script and "LiveReload" functionality. All fitting with my values. Let's see what it looks like!
I used some hacky JavaScript to scrape my friends birthdays from Facebook so that I can put them in my actual calendar.
I can't use any of my favourite note-taking apps at work. But I can use a web browser and I can write JavaScript. The logical conclusion is, of course, that I should build my own!