1. The more you fix the more you break. Whenever you change code you run the risk of altering its behavior. Unintendedly. The Mikado Method separates the process from the change itself. Thus shifting the cognitive power to where it belongs
Läs mer »
I often hear from people working with security that we can’t have both security AND privacy. That we have to sacrifice privacy in order to prevent crimes. This is simply not true. I have learned, by working with the DNS TAPIR team and development, that there are ways of doing both.
Läs mer »
As a programmer of passion, I think tools matter as much as people do.
Läs mer »Since I was a teenager I've been somewhat interested in dream interpretations. So, now and then I google a strong dream I've had
Läs mer »Highlander: A data oriented pattern for menus and things of which there should only be one opened at a time
Läs mer »Leveraging the `attr-map`, clojure-lsp and nREPL to avoid syncing the argument list/signature of Clojure functions
Läs mer »I don't like to wait minutes for PR feedback!
Läs mer »Throw out the waste. Keep the fun. Perhaps Clojure’s super power is Interactive Programming. I.e. using the REPL to connect to, inspect, and modify the running program as you are developing it. As a Clojure developer you can leverage this power for fun and for profit.
Läs mer »Did you know? VS Code has a command for stringing multiple commands together: runCommands.
Läs mer »It is mind boggling how much an AI can read out of a picture. At least if the picture has a lot to say.
Läs mer »