topic: software development

Everything I’ve written on the subject, from the beginning of this version of the site.

I may also have written on this on earlier versions of my website:

  1. 2006 – 2011 (link coming soon!)
  2. did not have a blog!
  3. 2012 – 2013 (link coming soon!)
  4. 2014 – 2019
  • 2020

    • Feb

      • 29

        • 16:41 ⚓︎ — NOTES

          I really, really wish GitHub had a slightly lower entry point for Teams/Organizations. I’d like to do everything for rewrite in a single organization on GitHub, rather than all under … but $25/month is frankly kind of steep for one developer. I’d be happy paying $10/month for just organization management, with the jump to $25 for supporting multiple developers. As is, though… GitLab looks appealing, whatever its other weaknesses.

    • Mar

      • 05

        • 14:35 ⚓︎ — NOTES

          One of the critical things Jira gets wrong — besides just generally having pretty bad information architecture — is that it treats issues as a tree instead of a graph. But that’s often not how projects and tasks actually relate to each other!

      • 08

        • 16:13 ⚓︎ — NOTES

          Quick Git tip: if you’ve manually edited your Git configuration file and removed a given remote, you may find yourself in a spot where you now have a bunch of branches associated with that remote… which you cannot delete. The only way (I could find) out of this problem was to re-add the remote, and then run git remote rm <the name of the remote>. That deleted the remote and all the references to its branches

        • 19:42 ⚓︎ — NOTES

          Status: working on figuring out how to wire up Elm and Rust-via-WebAssembly using webpack. I’ve spent the last four years in Ember and before that I was wiring up Gulp. So this is new. 😅

    • Apr

    • May

      • 03

      • 04

      • 08

      • 12

        • 10:15 ⚓︎ — NOTES

          TypeScript: it’s regularly absurd or weird, and I am frustrated regularly by so many things about the type system… but nearly all of them come down in practice to this works this way because JavaScript and JavaScript developers.”

      • 13

        • 08:11 ⚓︎ — NOTES

          Last night I threw away almost all the build config I’d been blinded by this spring while working on rewrite: webpack config, TypeScript integration, you name it. What I have left: a simple bunch of npm scripts that I can run in parallel in different terminal sessions:

          {
            "scripts": {
              "clean": "rm -rf dist/*",
              "build:static": "cp static/* dist",
              "build:css": "sass --load-path=./node_modules src/style.scss dist/style.css",
              "watch:css": "sass --watch --load-path=./node_modules src/style.scss dist/style.css",
              "build:elm": "elm make src/Main.elm --output dist/app.js",
              "watch:elm": "watchexec -w src 'elm make src/Main.elm --output dist/app.js'"
            }
          }
          

          It’s not fancy, but it gets the job done just fine for the things I’m actually working on — rather than things I’ll need eventually — and that’s exacty the right balance at this point.

        • mut (and set) and auto-tracking in Ember Octane  — JOURNAL

          Understanding a surprising behavior — and fixing a refactoring hazard.

      • 15

      • 24