Hi, I'm Eric.
I’m an avid world traveler, photographer, software developer, and digital storyteller.
I help implement the Content Authenticity Initiative at Adobe.
Hi, I'm Eric.
I’m an avid world traveler, photographer, software developer, and digital storyteller.
I help implement the Content Authenticity Initiative at Adobe.
Rachel Laycock argues that experienced developers’ hesitancy about coding agents isn’t nostalgia for writing code or fear for their jobs — it’s hard-won knowledge that “built” and “works in production” are very different things. The questions she lists (Are these the right boundaries? Will we be able to evolve it? What happens when something breaks?) are exactly the ones that agentic workflows tend to gloss over.
Roman Kashitsyn lays out a set of goals for designing error types in Rust libraries: prefer specific enums over catch-all types, reserve panics for genuine bugs, lift input validation out of fallible calls, and embed rather than wrap underlying errors. The unifying theme is empathy — design the error type you’d want to handle as a caller.
via a co-worker: VitePress: Vite & Vue Powered Static Site Generator
via a co-worker: proptest: Hypothesis-like-property-based testing and shrinking.
Subscribe to my free and occasional (never more than weekly) e-mail newsletter with my latest travel and other stories:
Or follow me on one or more of the socials: