dev diary: block theme essentials
There are essentials that describe the minimum number of files you need to make a “valid” block theme. Then there are the essentials of a good block theme. These are the templates, settings, and styles for block themes that are simply non-negotiable at this point. templates You can get by with the one index.html template, more or less like you could with a classic theme, but I also know you can do better than that.dev diary update
After three years I’m resurrecting this idea. More determined than ever after having built at least two block themes privately. My experience applying for jobs has made me have to confront something a bit depressing, too; I don’t have a lot to show for all the work I’ve done. As much as I understand what I’m doing and the “best practices” of this profession, my GitHub profile doesn’t really reflect that.automated testing for starters
I’m overwhelming myself again - I do it often, I have it down to a science. This time it’s with Test Driven Development. Did you know there are some zealots who say that you shouldn’t write a single line of production code unless you have written test coverage for it already? 😓 That’s intimidating! Even if you know how to write tests, there can be a few things that hold you back from writing them first.
graphql for rest dummies
If you come from the world of REST, things in GraphQL are going to look very strange at first. They only use POST requests. There is only one endpoint. What in the heavens??
dev diary
I find myself getting caught in a cycle, where I really want to write for a brief period of time because it helps me consolidate my learning, and I do, and then I get salty at the idea of spending time writing when no one’s reading, and then a few months down the line feeling bad again that I didn’t write anything about what I had been working on and being right back where I started.
I’ve resolved to break this habit by writing a developer diary, while I work to write and release a Gutenberg compatible WordPress theme.
finding and fixing issues with "stuck" scrolling in mobile safari
I recently had the “pleasure” of having to figure out why a user on one of our websites would get “stuck” trying to scroll near certain elements. Turns out one of the execs uses an iPad Pro in landscape mode exclusively, so it’s often the case that the site is being viewed by someone using a desktop sized viewport but a touchscreen for interaction.
copypasta allows bugs (and more) to creep into production code
I’m writing an Express app. I care about infosec. Naturally I went a-Googling to learn methods to harden Express apps. At some point I came across micaksica’s article, Your Node.js authentication tutorial is (probably) wrong.
The gold nugget quote comes right in the opening paragraph,
Thousands of front-end developers being thrown into the server-side JS maelstrom are trying to piece together actionable knowledge from these tutorials, either by cargo-cult-copypasta or gratuitous use of npm install as they scramble frantically to meet the deadlines set for them by outsourcing managers or ad agency creative directors.
Would you like some crippling performance issues to go with your copypasta? My next step found an illustrative example.