Category: JavaScript

Michael Feathers released a whitepaper on learning a new & large code base. It provides 4 tactics in order you can use to better understand it quickly, and be productive and 3 tactics to start working. I’ve had this happen a lot, and in the past in consulting and freelance. I’ve tried a variety of techniques, so this paper is neat in that it’s way better than mine, organized, and has co-contributors.

I _do_ have a few thoughts on it as well based on using some of these.

https://communications.globant.com/public/wp/system-renewal-patterns/White_Paper-Patterns_of_Systems_Renewal-v4.pdf

If you like JavaScript’s Zod to validate your types at runtime, you’ll Valibot. Like Zod, however, you can also use it with TypeScript to get compiler help. Their current claim to fame is the Lodash style of “1 function per file” which makes it easier for bundlers to shrink the code down super small.

https://www.builder.io/blog/introducing-valibot

Gregor Hohpe discusses Domain Driven Design in Cloud, and hits 3 important topics:

1. How the words you use enable design, and indicate what type of work culture you’re in, and incentives to use better words.
2. How bad and difficult it is for Cloud providers to keep a consistent language, and to what degree they’ve created a decent set of words to describe their services, and how they could do better.
3. How most people do NOT get how to use AWS CDK.

Learning Test Driven Development (TDD) is hard. I have a decade+ of “Test Last” “Test After” content on my blog and YouTube, none of it “Test First” until much later in my career. So here’s a 3 phase process to ease into it. I’m assuming you already know how to setup unit testing frameworks (Jest/Vitest/Mocha/Jasmine, etc) and use assertions (expect, assert, etc).