playtested my game at an event last night. so much fun to see people curiously prod at mysteries i constructed, and stubbornly battle its challenges. oh no i might actually have to finish this one
Any conversation
โฆ
NIH syndrome? I am guilty of it too. I love implementing things from scratch, you learn a lot by doing so and you get to own the codebase end-to-end, so no surprises and fighting around othersโ choices. It can get exhausting too though, in the end I succumb to using off-the-shelf components because my primary goals move at a higher level.
a kis laptopnak pedig nincs elรฉg memรณriรกja, szรณval ezt a fลterminรกlt eredetileg programozรกsra vettem, azt nem tudom mรกr, mit akartam programozni vele, de pont รบgy zรบg, mint egy adatkรถzpont, รฉs hogyha egy kicsit korszerลฑsรญtem, a Gemma 4 LLM รฉppen visรญtva el fog tudni futni rajta
and the little laptop doesn't have enough memory, so I originally bought this main terminal for programming, I don't know what I wanted to program with it anymore, but it hums like a data center, and if I upgrade it a little, the Gemma 4 LLM will be able to run on it screaming
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.

