Massimiliano Mirra

Notes

Expressive components in vanilla React, part 2: IO objects A(nother) library-free technique to make components easier to maintain and reason about
react
Expressive components in vanilla React, part 1: TypeStates A library-free technique to make components easier to maintain and reason about
react
Faster, simpler tests with explicit IO channels Not everything is an argument
testing
The process.env frontend time bomb (plus: a sustainable definition of “fixed”) From fragility in spite of effort to robustness by design
reacttypescript
Test-driven development of NextJS API routes NextJS's conventions are not TDD-friendly, but with some work and a little structure we can enjoy a smooth red-green ride.
nextjstesting
How two lines of TypeScript can make a bug go from “undetected in production” to “impossible to introduce” Notes from 2022/11/16 DevCafe
devcafeqatypescript
“I never did any formal design, where can I start?” Notes from 2022/10/21 DevCafe
architecturecodedevcafe
Emacs package quickstart with Eldev Notes on creating a basic package with tests and managing it with Eldev
emacs
“I’ve got a React codebase, I want to introduce tests, where do I start?” Notes from 2022/10/21 DevCafe
codedevcafeqareacttesting
TDD and (vs?) testing Notes from 2022/10/21 DevCafe
codedevcafeqatesting
Four patterns for developer-friendly, production-grade NodeJS services Originally written for collaborators on a project, to explain why services are structured the way they are, and to provide a set of reasoned guidelines
codecollaboration
Comment the code that is not there So your coworkers don't have to find out the hard way
codecollaboration
Mocking window.ethereum in Playwright for end-to-end dApp testing A short note on getting web3-mock to work in Playwright tests
playwrightqatesting
[draft] Structuring projects to guide and inform (for React applications) A project's structure speaks. Does yours say useful things?
collaborationreact
Bi-dimensional commit messages The useful dimensions of a change, at a glance
collaboration
Faster interactive development in Storybook Tweaking Webpack for responsiveness, or hacking Snowpack in
react
Data that grows together, goes together If it's conceptually interdependent, make it programmatically interdependent
codetyped languages
Lightweight external command integration in Emacs via compilation mode Doing more without leaving Emacs
emacs
The dangers of greedy functions Functions that ask for more than they need trick into writing risky code
codetyped languages

Tagged “notebook_practices”

Expressive components in vanilla React, part 2: IO objects A(nother) library-free technique to make components easier to maintain and reason about
react
Expressive components in vanilla React, part 1: TypeStates A library-free technique to make components easier to maintain and reason about
react
Faster, simpler tests with explicit IO channels Not everything is an argument
testing
The process.env frontend time bomb (plus: a sustainable definition of “fixed”) From fragility in spite of effort to robustness by design
reacttypescript
Test-driven development of NextJS API routes NextJS's conventions are not TDD-friendly, but with some work and a little structure we can enjoy a smooth red-green ride.
nextjstesting
How two lines of TypeScript can make a bug go from “undetected in production” to “impossible to introduce” Notes from 2022/11/16 DevCafe
devcafeqatypescript
“I never did any formal design, where can I start?” Notes from 2022/10/21 DevCafe
architecturecodedevcafe
“I’ve got a React codebase, I want to introduce tests, where do I start?” Notes from 2022/10/21 DevCafe
codedevcafeqareacttesting
TDD and (vs?) testing Notes from 2022/10/21 DevCafe
codedevcafeqatesting
Four patterns for developer-friendly, production-grade NodeJS services Originally written for collaborators on a project, to explain why services are structured the way they are, and to provide a set of reasoned guidelines
codecollaboration
Comment the code that is not there So your coworkers don't have to find out the hard way
codecollaboration
[draft] Structuring projects to guide and inform (for React applications) A project's structure speaks. Does yours say useful things?
collaborationreact
Bi-dimensional commit messages The useful dimensions of a change, at a glance
collaboration
Data that grows together, goes together If it's conceptually interdependent, make it programmatically interdependent
codetyped languages
The dangers of greedy functions Functions that ask for more than they need trick into writing risky code
codetyped languages