any · textlog

500 chars / 20 lines max · use #hashtags, @mentions and more

😀😃😄😁😆😅😂🤣😊😇🙂🙃😉😌😍🥰😘😋😛😜🤪🤨🧐🤓😎🤩🥳😏😒😞😔😟😕🙁☹️😣😖😫😩🥺😢😭😤😠😡🤬🤯😳🥵🥶😱😨😰😥😓🤗🤔🫣🤭🫢🤫🤥😶😐😑😬🙄😯😦😧😮😲🥱😴🤤😪😵🤐🥴🤢🤮🤧😷🤒🤕🤑🤠😈👿👻💀☠️👽🤖🎃😺😸😹😻😼😽🙀😿😾❤️🧡💛💚💙💜🖤🤍🤎💔❣️💕💞💓💗💖💘💝💟👍👎👌🤌✌️🤞🤟🤘🤙👈👉👆👇☝️✋🤚🖐️🖖👋🤝👏🙌🫶👐🤲🙏✍️💪👀👁️🧠🫀🫁🌱🌿☘️🍀🌸🌺🌻🌞🌙⭐✨⚡🔥🌈☀️☁️❄️☕🍕🍎🎉🎊🎈🎁🎵🎶🎨📚💡✅❌⚠️🚀🌍💻📱🔒🔑

example.com or https://example.com
Regular links: [title](example.com) or [title](https://example.com)
Markdown links: ~text~ or ~~text~~
Strikethrough: *text* or **text**
Bold: _text_ or __text__
Underline: /text/
Italics: > text
Quote: :smile
Emoji autocomplete: 1. first 2. second 3. third
Numbered lists: - first - second - third
Bulleted lists: Name | Status | Count ----- | :----- | ----: notes | ready | 3
Tables: |redacted|
Redacted: `code`
Inline code: ```…```
Code fences: $inline$
Inline LaTeX: $$block$$
Block LaTeX

Which one? #poll First option Second option
PollsUse 2–8 unique options.: Which one? #quiz Wrong answer > Correct answer Explanation revealed after answering
QuizzesMark exactly one of 2–8 unique answers with >. Text after a blank line is revealed after answering.: Visible text #spoiler Hidden text
SpoilersText after #spoiler is hidden until revealed. Aliases: #tldr, #sensitive, #contentwarning, #cw, and #triggerwarning.: Going hiking #map Kallikratis, Crete
MapsShows a map preview for the first location line. Alias: #location.: #flying Heraklion to Berlin
FlightsHover over the itinerary to see a map connecting the airports. The next three words form the itinerary: airport, to (or → or ->), airport. Use single-word airport names or IATA/ICAO codes.: Today #todo [ ] First task [x] Finished task
TodosOnly [ ] and [x] lines become items. Click your items to toggle them.: Run this #exec ```js console.log(6 * 7) ```
Executable codeRuns the next language-tagged code fence and shows its output beneath the note.: Keep this visible #pin
Pinned notesYour latest #pin is shown first on your profile, independently for notes and replies.: No more replies #lock
Locked conversationsPrevents new replies to this note and every reply beneath it.: About textlog #meta
Meta conversationsKeeps this note and its replies out of public discovery feeds. Aliases: #tlog and #textlog.: Continue quietly #whisper
Whisper conversationsKeeps the branch out of all and hot. Participants, mentions, and tag followers can receive it in my feed. It remains public elsewhere.: For @someone and @another #private
Private conversationsOnly the author and mentioned users can read this branch.: Answer before reading #HiddenReplies
Hidden repliesHides all replies until you reply.

moreless

wrote:

I'm doing experiments with short attention-span students and code. Starting with python, and, oddly, now working in BASIC. As a C programmer of 40+ years, I find this aesthetically and pedagogically displeasing, but I am delighted to see them getting fully absorbed in writing 130 PRINT "You have been eaten by a bear!" : GOTO 900. Yes there is spaghetti, but it's their spaghetti and they seem to take delight in debugging it. Python will come later.

(deleted post)

replied to(deleted account):

I was talking about this with some alumni students, specifically their experience learning python with us a few years earlier (these are college students who are not really using python any more). What it seems to boil down to is that with python you have the feeling that there is this huge forest of solutions to any problem you are having -- but you will never know the whole forest. BASIC feels like you "know" it after a day or two of playing around, evidently.

wrote:

hi :3

replied to:

wrote:

Why was the math textbook sad? revealBecause it had too many problems.

wrote:

my today’s list:

wake up

make coffee

work

and possibly later:

contemplate existence

wrote:

Sunk cost fallacy is no longer applicable in the age of . Now you can do broad changes without second thought, u can always revert back, without incurring the cost of doing so, since it’s all done so quickly and effortlessly.

replied to:

I think it will still apply, just perhaps to a lesser degree. Kind of related to I wrote recently (not to shamelessly plug my stuff 🫣)

…

replied to:

Nice read! Thanks for sharing!

replied to:

My biggest problem nowadays is realizing that the coding was never the real problem, it was always lack of domain knowledge, lack of specs or just conflicting visions.

wrote:

és így nem kell egy ilyen zöld modulba applikált, baszott nagy integrált chipet venni hozzá, pedig nem is néz ki rosszul, de jól sem

and that way you don't have to buy a fucking big integrated chip applied to a green module, even though it doesn't look bad, but it doesn't look good either

wrote:

Wow show code

n=42
print(n)

42

wrote:

there's so much room for activities!

wrote:

Anyone here using NixOS? How long did it take for you to learn it and completely set it up? My current distro is Arch (btw)

wrote:

replied to:

hi there ;) welcome

wrote:

Nudged by an interesting read about time perception to try reclaim moments where I can deliberately feel bored again.

wrote:

vibing

replied to:

same

wrote:

echo “films” >> .textlog echo “books” >> .textlog echo “games” >> .textlog sudo rm -rf /etc

wrote:

I like this concept

wrote:

Finally got around to setting up Remux on my phone so I can connect to tmux sessions when I'm not at my laptop. Even just for around the house, this seems like it'll be super useful.

replied to:

Tell us more! What apps are you operating?

replied to:

This is for monitoring/poking agentic coding sessions while I'm not at my computer. So, typically Claude, Emacs, and an overmind process running my app locally in different panes of a tmux window.

continued:

Call me old fashioned, but instead of adopting one of the "agentic coding orchestration frameworks" that seem to basically be reinventions of tmux, I've been tweaking my tried-and-true tmux-oriented workflow to incorporate agentic coding harnesses in an ergonomic way. I'm currently still using Claude Code, but getting Pi-curious as local models advance.

replied to:

I will be dead, and many years will pass after that, before local models are capable to match those of the big companies, unless their intended use is banal.

…

replied to:

It seems like we've reached a point where mid-grade frontier models like Sonnet are good enough for most day-to-day tasks. And Sonnet-grade models are already runnable on the higher end of consumer hardware. In which case, I can imagine a workflow where local models serve as workhorses for implementing plans that you may bump up to e.g. Opus or Sol to produce.

wrote:

“Every problem that is interesting is also soluble.” - David Deutsch

wrote:

Hey hola, aquí un hispanohablante que ingresó por curiosidad. No creo pasarme mucho por aquí pero igual aquí andamos por ahora.

Hey, hi! This is a Spanish speaker who joined out of curiosity. I don't think I'll be around much, but I'm here for now.

wrote:

One day I would like to see Thailand. That would be nice.

…

wrote:

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.

replied to:

I don't see much point in trying to build software at a "higher level", like whole products and services. I'm going to go down low and train myself on the fundamentals. Hopefully in time I'll be able to contribute to the foundational bits. You're right, it does get exhausting. At some point you just want to rebuild everything, which is not possible.

replied to:

I'm going to go down low and train myself on the fundamentals. When I wrote an HTTP sever (albeit HTTP/1.1), I learned how primitive the HTTP protocol its magic became a skill. It is freeing understanding how things work and allows me to choose where to spend time with more intention.

Any conversation