The Way I Code (and have been coding for 30 years)
Start with good decomposition. Then use encapsulation to create good abstractions. That's how I code. That's how I was taught to code 30 years ago. And it's still how I code today.
Creativity, curiosity, and code
Start with good decomposition. Then use encapsulation to create good abstractions. That's how I code. That's how I was taught to code 30 years ago. And it's still how I code today.
I started trying to explain what I was doing and why, and as I did so I realised all the many, many things you have to understand for this process to make sense.
If you're using a script that uses cookie authentication with the WordPress REST API then you may also need a nonce. Here's how to make this work!
I want to talk (again) about friction. Things that slow us down. How some friction is good, and some is bad.
A super simple asset-watching script and "LiveReload" functionality. All fitting with my values. Let's see what it looks like!
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!
This time it's a static-file-driven, mobile-app-like blog. And the tooling I made should be usable on any simple WordPress blog! But... WHY???
I now have a process that gets me small, fast, side-project websites for virtually zero cost. Let's see how it works...
The web used to be fun and simple and easy to get stuff done with. Now it's discovering that someone who doesn't know what they were doing used a div instead of a button and fixing it involves half a day of frustratedly poking around files that make no sense and fixing a broken build process.
The experimental "command center" is coming to WordPress core. What do I think of it? And what does it mean for my own "command palette" product, Turbo Admin?