hello world ~ i'm a web developer from midwest, usa. it's been awhile since i worked on anything. since the i've been working my way up the ladder at a blue-collar job; i was promoted to team lead last week. but as i browse hacker news everyday, my cravings for web development increases.
Any conversation
ะฆะฒะตัะพะบ ัะพะทั ะฝะต ะธะทะดะฐะตั ะณะพะปะพัะฐ, ะฐ ะฑะปะฐะณะพัั
ะฐะฝะธะต ะตะณะพ ะดะฐะปะตะบะพ ัะฐัั
ะพะดะธััั ะผะพะปัะฐ; ัะฐะบ ะฝะฐะดะพ ะถะธัั ะธ ะฒัะตะผ ั
ัะธััะธะฐะฝะฐะผ.
โะกะฒััะธัะตะปั ะคะตะพัะฐะฝ ะะฐัะฒะพัะฝะธะบ
The rose flower makes no sound, but its fragrance spreads far and wide in silence; so should all Christians live.
โSt. Theophan the Recluse
one-point-five-shotted a local node app for creating social posts. drawing from static pages (hey this exists) or new blog posts (timely). with copy/paste to x, and one click post to bluesky and mastodon, tag manager and stale/archive/reject/refresh options. An idea and a solution in about 10 minutes. Madness.
Really glad to be using Haskell for work - especially in today's climate with agentic coding.
Our team uses containers to keep our development environment consistent across team members, though, and most agent sandbox approaches want to either offload your work fully to the cloud or they want to sandbox the agent harness process itself.
We're not ready for full cloud based development (yet?) and sandboxing just the agent doesn't work for us when the agent needs to run docker.
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.

