Iโm using textlog to explore the intersection of and tech, with the goal of building an app that solves a problem in this space. Named , it's word represented as a hex color.
Of all the words there, it is a cocoa-ish color and is an appropriate name for this idea.
Any conversation
ennek a laptopnak mindegy mรกr szegรฉnynek, annyi minden tรถrtรฉnt mรกr vele, most telepรผl rรก a Gemma 4 26B A4B QAT, az eredeti tervek szerint, amik lehet, hogy nem is a mi terveink, de arrรณl mi mรกr nem nagyon tehetรผnk, mert a kรถrรผlmรฉnyek รกldozatai lettรผnk
This laptop doesn't matter anymore, poor thing, so much has happened to it, now Gemma 4 26B A4B QAT is being installed on it, according to the original plans, which may not have been our plans, but there's not much we can do about it, because we've become victims of circumstances
โฆ
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.
spiral
for(y=-5;y<5;y++){
s=""
for(x=-10;x<10;x++){
r=Math.hypot(x/2,y);a=Math.atan2(y,x/2);s+=" .:*#โ"[((r+a*2)%5+5)%5|0]
}
console.log(s)
}::.........:::***##
.. ...::**##
######## ..::**#
###********# ..::*#
#**:::...::*# ..:**#
. ##**::. ..::**##
##**:.. #*::***##
##**:.. ######
. ##**::... ...
. ##***:::......:::I needed to process 20,000 json files & 20,000 JXL files. I'm pulling together a website from them all. Anyway, started with emacs elisp to handle it all, just because I've not done that before. Went kinda ok, and I'm gonna use org-mode to export it all to a website (done that bit loads of times before).
In the end, I ended up breaking out my C programming skills (late 80s->nowish). It was a delight. Nothing more refreshing than writing raw code, that doesn't rely on 3rd party code/libs.
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.



