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.
Any conversation
Last year I wasn't feeling too good.
I turned forty, waited for surgery, and was hurt by my own colleagues. So I dealt with things. Maybe not so well, but to the best of my ability.
One of the consequences was that I got a bit heavy. My body changed, and I didn't feel like myself. It was a problem for future me. So now I am here with this little belly of mine. We're not enemies, but I decided it's time to part ways.
So I count calories. Maybe not so well, but to the best of my ability.
we also launched Norma! :)
It checks AI-generated code for security, quality and maintainability while the agent is still working, rather than after a pull request opens. The output is deterministic. Here the demo link: portal.qualityclouds.ai/demo
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.



