hackeryarn

Thanks! And it looks like such a beautiful setup.

What keyboard is that?

I feel like this is a trend with dynamic languages that have a REPL. I’ve done a lot of Common Lisp in the past, and had the same feeling.

The best way to get over this is to pop open the python REPL and start playing around with the options and functions. It takes very little ceremony to get a nice example rolling.

https://realpython.com/python-repl/ has some nice advice and tips on extra things you can do in the REPL.

I am happy about this change. I wanted some extra damage out of the spell, but instead it just got mobbed and lucky if it got a turn.

If I just wanted a distraction, minor illusion doesn’t use a spell slot.

Alacritty is also the terminal that feels small and focused enough for me. Too many other terminals try to do everything like session management, etc.

You could also run Gentoo on it. Quite a few people are running it successfully: https://wiki.gentoo.org/wiki/User:Jared/Gentoo_On_An_M1_Mac

So flameshot lets you edit the images as you take them. I never used it to edit post screen shot. It also needs some additional configuration on most WMs, so that could be part of the problem. Their wiki has some suggested setup steps that you might need to make.

This look amazing. Seeing lots of examples like this is really helpful for internalizing all the uses of a command.

Well that’s a very clickbaity title. It’s primarily talking about office real estate, which is a lot less surprising of a fall.

It's really about making a conscious choice about which part of your application to keep "humid". Because you will have repetition somewhere no matter how good your abstractions are. I am advocating for a "humid" top layer and DRY lower levels.

The approach I see too often with overuse of DRY is creating a lot of small functions that only slightly differ in the steps they take. Then you end up searing through those functions, creating new ones, creating duplicates, or using the wrong one. I think it's easier to maintain a well named, straightforward list of steps.

Yeah, this definitely went deeper. I was really tempted to change the title to be honest. The article started out of a frustration of a code base that was too DRY, and kind of grew into a more general how to create abstractions. The original title just stuck around.