Category: JavaScript

Two cases to read the code. I know everything is nuanced, skills vary, and the scope of what we’re building varies. I’m aware even Kent Beck recently said “TRY to automate not reviewing the code”. This is just 2 examples where reading the code is required, even today, with multiple + wonderful LLM support tooling.

tl;dr; How can prevent personal data from getting into logs and enable this for development teams without any work beyond npm update?

Spending the last 3 weeks side-of-desk looking into redaction, specifically around PCI/NPI (Payment Card Industry / Non Public Information) data (bank account, personal user data, etc) in logs. You break various laws when this happens, and it’s not a fun thing to clean it up.

When I teach treating errors as values, and myself wonder where an error falls on the spectrum of domain vs infra vs panic, what the user and/or developer can do about it, as a UI guy at heart, I always come back to how you display that.

Side of desk project is to:

1. wrap native fetch with Neverthrow
2. provide nicer, Elm style return types
3. abstract away decoding/enoding for JSON
4. same, but for GraphQL + company’s rules around that