any · textlog

Am in a beautiful national park right now, drinking with elks, but the lack of strong internet makes me nervous :(

Theory reuse > code reuse almost every time.

Found out about plain text accounting recently, and set up a journal. It was a bit tricky to understand at first, but I think I am getting better at it... will see if it helps me to analyze my monthly spendings...

wrote:

hey guys ☺️

replied to:

Hi lacie

wrote:

will go to university

wrote:

HelloWorld show code

from datetime import datetime
now = datetime.now()
formatted_time = now.strftime("%Y-%m-%d %H:%M:%S")
print("Formatted:", formatted_time)

Wow

Formatted: 2026-08-28 07:22:42

wrote:

Sharing your work with others is a hard computer science problem in 2026, the Year of our Lord. You either here the sound of chirping crickets or the sound of "AI Slop" yells.

replied to:

My past 3 projects went viral. I didn’t write a single line of code in any of them. But I still feel I engineered them. There were a few people that noticed but the majority didn’t see an issue.

replied to:

You're fortunate in that you've genuinely captured something that people clearly want with textlog. No one wants another static site generator or coding harness. Ideas that resonate are pretty few and far between now.

…

replied to:

I should have said past 4 projects went viral but the other one I did a lot of coding too, so wasn’t entirely “AI slop”. In all cases though, I made something I wanted to see. It just happened to resonate with others. Still, none of them extremely popular yet. All <500 users.

wrote:

Trying tsoding/tatr idea for task tracking in the project. Instead of his C implementation asked CC to implement tatr.el. I do similar thing with vulpea, even my org notes have timestamp ids. Tatr tasks live in the repo, which is good.

wrote:

Using deep research for trip planning and visualising it with coding agent is fun.

wrote:

thinking on deploying excalidraw on my homeserver, so I can store drawings without bothering with export/import. Yes, excalidraw+ for $7/mo; but nowadays I pay only one sub - for Claude; everything else is personal software.

continued:

Well, done, Claude did while I drove a car. It even added save/open file from the server (stored in SQLite). Deployed on my homelab server.

wrote:

Genuinely needed strace and got sMACed across my face.

wrote:

One idea that I've been thinking about is an or where it is a app so you get a new file everyday right except the app keeps track of all the files for you. the idea is that anytime you type anything it it basically makes a commit and use so anytime you type something it commits automatically after a quick pause after you stop typing.

replied to:

That sounds ! Could also create summary titles with for the filenames in addition to their date so you can find what you were writing about easily. Also full text search.

replied to:

Yes! Great idea. Not sure how I would implement it but the main idea is that you should feel free to delete text through out the day because everything is tracked in a git repo. 🫣

wrote:

been discovering random peoples indie websites and blogs on . takes me back! the internet lost so much charm when everything became coorporate. convenience can come at a big cost

replied to:

neocities is such a gem!

wrote:

This #tome about #Tcl/Tk has me re-evaluating my plans to move to the woods to be a carpenter hermit. Now I want to move to the woods and be a programmer hermit.

wrote:

Bonnie Raitt stuck in my head, who, by some definition, is a nepo baby, but well before the term was coined. I think the problem is obv not family businesses, but a shrinking pool of opportunities for those without a prebuilt network to inherit (or buy).

continued:

This is another way to describe "increasing wealth inequality".

wrote:

@@@@@@@ @@@@@@@@ @@@ @@@ @@@@@@@ @@@ @@@@@@ @@@@@@@ @@! @@! @@! !@@ @@! @@! @@! @@@ !@@ @!! @!!!:! !@@!@! @!! @!! @!@ !@! !@! @!@!@ !!: !!: !: :!! !!: !!: !!: !!! :!! !!: : : :: ::: ::: ::: : : ::.: : : :. : :: :: :

wrote:

& ˢ ᵖ ᵃ ᶜ ⁱ ⁿ ᵍ ~ ELDER FUTHARK: ᚠ ᚢ ᚦ ᚨ ᚱ ᚲ ᚷ ᚹ ᚺ ᚾ ᛁ ᛃ ᛇ ᛈ ᛉ ᛊ ᛏ ᛒ ᛖ ᛗ ᛚ ᛜ ᛞ ᛟ

replied to:

i perfer anglosaxon runes but thanks

wrote:

I noticed today that I'm an idiot. I built a static site generator with NO DATA MODEL. Beginning to fix it now, but my god how embarrassing. Hobbyist less than amateur...wow. Good thing my day job isn't at stake.

wrote:

replied to:

_ _ __ ___.--’_`. .'_`--.___ __ ( _`.'. - 'o` ) ( ‘o` - .`.’_ ) _\.’_’ _.-’ `-._ `_`./_ ( \`. ) //\` /\\ ( .'/ ) \_`-’`---'\\__, ,__//`---’`-'_/ \` `-\ /-' '/

replied to:

Noice Froggos make everything better.

wrote:

ai coding feels like it has reached diminishing returns for me. luna is my default orchestrator, routing work by complexity. in practice, usage lands around 16% luna, 48% sol, 30% astra, and 6% terra. at this point, i care less about each new frontier release. the system already finds a capable model for the job. the frontier is moving beyond my day-to-day work, so i’m happy to settle into predictable models for a while.

replied to:

I’ve found the same, albeit with Opus — it’s hard to find uses for Fable. I don’t need a model that works for longer or works on harder problems, I need one that consistently produces simple, easy to understand, code; which at this point none of them do.

replied to:

I've been there since I settled on a combination of GLM, DeepSeek and MiMo for planning, implementation, and verification flows. I'm a lot more interested at this point in having cheaper models that can consistently do the work I need. It's been a while that I hanven't noticed any improvement when I try new frontier models. I only notice they are very expensive.

…

replied to:

same here, for almost an year. At this point, I could easily live with models that were released 6-12 months ago and continue doing so. also possibly the reason why the current focus has been around agentic workflows or agentic anything, than the model capabilities.

replied to:

Coding probably yeah, but still they are bad at generating novel information, new ideas and such. They’re also not very good at seeing the bigger picture, they will narrowly perform the task but they’re not taking into account future revisions, which ends up in refactor after refactor in order to move forward.

Any conversation