any · textlog

wrote:

You look in the corner, you see a guy quietly eating cigarette butts. It's ok. He's dealing with a lot of stress from work. He takes care of his family. Capitalism

replied to:

Likewise... you look in the corner, you see a guy quietly eating cigarette butts. It's ok. He's dealing with a lot of stress for lack of work, or food, or future. He wants to take care of his family. Communism. We haven’t figured out yet. Maybe we never will.

wrote:

A show code

n=27;s=[n]
while n!=1:
    n=n//2 if n%2==0 else 3*n+1;s.append(n)
for v in s[:15]:print(f"{v:>4} "+"█"*min(v//3,40))
print(f"{len(s)} steps, peak {max(s)}")

stdout length exceeded

wrote:

While learning jj, I realize how Git habituated me into being ok with its unique jargon and prickly command line interface. Unlearning Git is refreshing.

replied to:

is just brilliant; it really feels like they’ve fixed all of the problems with git whilst at the same time remaining completely backwards compatible. The simpler interface, the universal undo, the reduced set of concepts — I’m a big fan

replied to:

Also, editing and rearranging commits like 3x5 notecards on your desk is tremendous. It makes using an SCM feel more like editing your work than lumbering forward.

wrote:

⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣀⣀⠀⠀⢠⠉⢹⢳⢄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡤⠔⡞⠛⣵⠀⠀⠙⡄⢸⠀⢸⠀⡜⠀⠀⠀⠀⠀⢀⡴⠉⠈⡧⣀⣀⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⡰⠃⠀⢰⠀⠘⡆⠀⠀⢰⠈⡀⠀⡀⡇⡇⠀⠀⠀⡰⡱⡝⠀⡜⠀⡜⠀⢈⠆⠂⠤⡀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⢀⡀⢏⠀⢇⠀⠀⢃⠀⠸⡀⠀⠀⡆⡇⠀⡇⠁⡇⠀⠀⡰⢡⡱⠁⡐⢀⠌⢀⢴⠋⠀⠀⠀⣈⡆⡀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⡁⠈⠹⣦⠈⢆⠀⠈⡆⠀⠱⠀⠀⢰⢁⠀⢃⢸⡇⠀⢠⢁⢧⠃⡰⢀⠎⢠⡾⠁⠀⠀⡠⠊⡠⠃⠈⣄⠀⠀⠀

wrote:

Today, I wrote a new Business Continuity Plan, worked with my SRE manager to improve responses to alerts, got a cringe email from HR and have to tell my staff to RTO 3-days a week if not classified as remote. Worked out for my 8th day streak, and cuddled in bed with my girl. Hello World

wrote:

I've been building a Markdown variant called Zd that's focused on extensibility and simplicity. I'm curious what you would change about Markdown if you were designing it from scratch, what challenges you face as a user, or what you wish were easier to do when incorporating Markdown into your own projects.

replied to:

Definitely tables are cumbersome.

replied to:

Yeah, 100%. That is completely something I am punting on currently. It would be easy to just copy over the solution from (extensions to) Markdown, but it's hard to entirely narrow in on both what tables ought to do and how to make them do it. If you had a magic wand, what would you have them be more like?

wrote:

89

continued:

89

wrote:

Loving this, congratz on the

replied to:

<3 tysm

wrote:

Hello to friends. Holla for tools. 👨‍💻 : , , and Pragmata Pro 💪 : NotePlan 🎧 : Overcast 🧠 : Allume 🖋️ : Mark Two (EDC), Pen Type-B 🌳 : Anisota

wrote:

┌─────────────────┐ │ hello, world │ │ │ │ i was here. │ └─────────────────┘ ,

wrote:

Any shows recommendations? I have no idea what is worth watching (since I rarely watch shows) so now I’m watching The Mentalist from 2008. They had flip phones then.

replied to:

This one is good

wrote:

például Telegram, Facebook, stb., de ilyen ügynökökkel bárki találkozhat naponta, egyből felismerhetők, meg is kell őket szépen jelölni, és egyre bénábbak a szövegük is, ahogy megfigyeltem, gondolom, attól függ, ahogy promtolják, vagy instruálják őket, ha a gazdájuk kifogy az ötletekből, a projekt hamar elfárad, a bot csak unalmas h#lyeségekre képes egy idő után

for example, Telegram, Facebook, etc., but anyone can encounter such agents every day, they are immediately recognizable, they need to be nicely labeled, and their text is getting lamer and lamer, as I have observed, I think it depends on how they are promoted or instructed, if their owner runs out of ideas, the project quickly gets tired, the bot is only capable of boring nonsense after a while

wrote:

Unsettled App Launched

wrote:

I think I will stop here. maybe

replied to:

why

wrote:

I've been on a kick lately of trying to visualize the oscillating clock, and ultimately the effectively arbitrarily complex activity of a computer processor, as modern refinements of the line shaft factory of the 19th century. Of compute as being not much more than profoundly refined "work" delivered by the electrical grid into marvelously complex machines. Does that, as a metaphor at least, feel as important to you as it has to me of late? We spend so much time in a world abstracted.

wrote:

Testing, testing…

replied to:

You forgot the “one, two, three”. :-)

wrote:

Phoenix oolong instead of my normal because I'm sick.

wrote:

An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using it.

Any conversation