Taco Steemers

A personal blog.
  1. Some files and information should not be in source control

    Which are they, what should we do with them instead, and how can we avoid mistakes?

  2. Dark and light web themes: consider using a hybrid CSS/JS implementation

    Instead of using either CSS media queries for operating system theme preferences or a Javacript-based theme selector we can use both. An automatic CSS-based switching and JS-based switching where the user can choose.

  3. Git: how can we squash (flatten) commits

    In this article I explain two ways in which we can squash commits.

  4. The Twitter share button does not need javascript

    When we let Twitter generate a 'tweet this button' for our website, Twitter includes a javascript file. We don't need to include this javascript file. The share button can be just a hyperlink. Twitter uses the referrer header to determine which URL the user wants to tweet about.

    The javascript …

  5. Git pull without merge

    Applying remote changes to our local branch without an additional merge commit

  6. When (not) to squash commits

    In this article I want to talk about squashing (flattening) a series of commits in to one commit. Squashing is a good tool to have, but not everything should be squashed away. Intermediate commit history can have value.

  7. Please use root relative URLs

    Resources with URLs that do not specify the root will not be loaded if the user visits a subpage directly.

  8. Creating a new website without breaking search engine results and bookmarks

    When moving our website to a different CMS or framework we might end up with a different URL structure. This is bad for search engine rankings and people's bookmarks. To avoid problems we can use rewrite rules and redirect rules.

  9. Notes on making drag-and-drop functionality with Javascript

    When I wanted to make drag and drop functionality I found there were plenty of tutorials out there. I am adding a few more words on the topic because I had to find workarounds for issues that I didn't find mentioned elsewhere.

  10. Why can the data we just stored on disk not be read?

    Data that our code writes to a file may not be accessible immediately after writing. One reason is that some output stream implementations use buffers, and prefer to write out their whole buffer in one go. In these situations, if we want to be sure the data can be read …