it is 19.45. i am still working
Any conversation
I find myself building bespoke tooling for my own and workflows these days, not only because of the obvious reason of software being so much cheaper to build, but also because there are SO MANY options for solving any given problem that it feels impossible to evaluate all of them.
If it's not a crucial piece of tech for a work problem then it often feels like paving my own way is both cheaper mentally (kind of amazing that's true these days) and probably a better fit.
signals. thinking about shifting my mental framework to identify signals instead of waiting for concepts to be assembled. exploring the amount of energy and opportunities for distractions through the operations of processing what just happened and what is happening to short circuit latent and unnecessary systems. cut through the assembly processes and identify the raw signals. recognizing that naming these "raw signals" is misleading. maybe, shifting observability lower in the stack.
Ikea has rules for naming products (so in theory, you could figure out what it is from the name) -> www.ikea.com/โฆ/6f564c4d-2ccc-46de-โฆ545a3948dc79.html


