Fast Feedback Systems
Published 📅: ....
Last modified 📝: ....
Share this post on BlueskySee discussion on Bluesky
I've written a bit about developing within what I like to call "fast feedback systems". The core value proposition of these systems or tools is that I as an engineer should be able to take a problem statement and begin to better understand it by fast feedback loops of trial and error experimentation.
Usually these systems look a lot like sandboxes or not unlike CodeSandbox, the built-in Node.js REPL, or even the browser dev tools! I heavily use these tools on a day to day basis, they allow me to take a complex problem and better visualize it through code.
Tags:
Related Posts
micropost
Published: ....
Leveraging service monitors properly to improve service observability.
Published: ....
It's fine for a library to express some opinions about how it should be adopted and how the overall workflow/application in which it is adopted should function. However, it's false advertising to say that it is unopinionated.
Published: ....
No I don't mean those Milano cookies you keep taking from the office snack wall either (although you should probably stop snacking on those as often as well).
Published: ....
Low/no process workflow wasn't actually no process, it was only an "invisible" process. An implicit contract with everyone on the team to do that async workflow on their own time.