I made a thing:
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.
a Windows 11 รบjabb meglepetรฉse: amellett, hogy a kezelลfelรผlete sokkal gรกnyabb, mint a Windows 10-รฉ, รกllรญtรณlag most 10 napot kellene vรกrnom addig, ameddig az elลzล rendszer tรถrli magรกt a gรฉprลl
Another surprise from Windows 11: in addition to the fact that its interface is much more annoying than Windows 10's, I now supposedly have to wait 10 days for the previous system to delete itself from the computer
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.

