schmooser

I tried Elfeed2 immediately after the announcement, well, it's nowhere near the experience of elfeed in Emacs. Elfeed2 doesn't load content for most of my feeds, elfeed does. I also integrated elfeed-tube, which shows previews of videos and their transcripts, making it no-brainer to get a summary without watching the whole video.

Reaching RET to open a block is too far from the home row, very unpleasant. C-m (Control-M) is much better and supported by both vim and Emacs.

I keep weekly notes in my work Org Roam project, Week-N-of-2024.org, where I store all the current work. At the end of the week I carry on TODO/DOING/WAITING headings. Every heading usually references topical Org Roam notes, so checking backlinks I can trace the work progress.

To keep it public - I tag certain headings with :Priority: tag and then use Org-QL to find them, pretty-print (enrich with Story links , completion date), sort by priority, TODO state etc; then export to HTML and copy-paste into Confluence.

The trick is to balance between granularity of items. I definitely don’t want to make everything public, but I do want to have everything in my notes, and this method solved it - the best of all tried over 15 years.

My iPad crashed when I clicked to the video on the page.

Did you ask why does JetBrains have so many IDEs, each for different language? PyCharm, WebStorm, RubyMine, CLion, Idea.

Emacs has LSP client that works will all LSP servers. It's your responsibility to bring an LSP server or implement your own, not Emacs'.

Emacs 29 is bundled with version of modus-themes that doesn't include tinted variants, you need to install them from Elpa.

I used Echo for one of my projects few years ago. I don’t remember which version it was, but authors (Labstack) were releasing major versions like every year or so, after two migrations I found myself in need to migrate again. That project is in maintenance mode, so still uses old Echo, but if I ever need to migrate, that would be to Fiber.

Several big mainstream products are implemented in Scala, including Apache Spark and Akka. Clojure has nothing of comparable size.

I tried it, doesn’t work - Lambda resource needs hash sum to compare against previous deployment to trigger updates of the source bundle, and Terraform needs a file to be present during plan stage. With null_resource the file is created after plan, during apply. To workaround this I tried to provide something else to bundle hash sum (like hash sum of source files, not bundle), but the value that TF keeps in the state is the one returned from AWS Lambda API, not the one you supply it; so it causes resource update on every apply, this is not what I wanted.

Your comment made me think of trying to skip bothering with Lambda’ hash sums and use custom refresh triggers instead, initiated by null_resource. Will do after holidays.

I’m building data pipelines in AWS (s3/sqs/dynamo/api gw/lambda/batch) + Snowflake.

Earlier this year I tried to use Terraform for everything, using principle “everything is a resource” (everything in my case is AWS, Datadog and Snowflake), so adopted “terraform apply” as universal deployment interface. Like if we need a ECR task and a Docker image, build the image from within Terraform (using null_resource which runs “docker build”). This approach works for everything but Lambda as Terraform requires a pointer to source code bundle at the plan stage. After unsuccessful fights I gave up for Lambda, so I build bundles prior to “terraform apply” (using “make build”, where build target does its magic of zipping either Go binary or Babashka Clojure sources).

That approach scales well for already two dozens of Lambdas and counting. Ping me if you want more details.

——

I disagree with this tutorial about tendency to use Terraform modules per AWS service, hiding well-documented AWS resources behind the facade of module with custom parameters with long names.