Programming is a delight for me. I feel myself fulfilled when I am creating new worlds.
-
Testing the Behavior of a GraphQL Schema
I submit a PR that adds a new resolver to my GraphQL schema. My teammate tells me they’ve merged and deployed it. But when I try to access the new resolver, it isn’t reachable, and I can’t figure out why. I check the infrastructure test and see that the schema has changed - but my resolver is missing. I start losing my mind.
-
Test-Driven Education
In a recent discussion with one of my mentors in full-stack web development, I was explaining how I learned certain frameworks and libraries. After seeing my approach, he remarked, “This looks like… Test-Driven Education.”
-
Overcoming the Struggles of Naming Variables
While contributing to the obsidian-tasks project with Clare Macrae, I was introduced to two powerful concepts that helped me tackle one of the hardest problems in programming - naming variables.
-
Data flow approach to full stack web-development
The way I am developing features for full stack applications has a pattern. I’m pretty sure that I’m not inventing anything new, this is more of an exercise for me to bring clarity to myself first, but maybe someone can find this helpful too.
-
Automated and versioned type importing from GraphQL schema
While recently working on a GraphQL project I had a task where the schema (part of the Infrastructure-as-Code) had to be exported to the frontend and the backend in TypeScript.
-
Testing Svelte reactivity with a wrapper
In an open-source project that I’m co-developing with Clare Macrae, we had to TDD some functionality in a Svelte component, but first we had to cover the behaviour of the existing component with tests looking like “The user has done this, test that the component has behaved like that”.