bahmanm

cross-posted from: https://lemmy.ml/post/18315517

I wanted to share a personal experience that might resonate with some of you. I've been diagnosed with ADD and major depressive syndrome, and for a long time, I struggled to enjoy over-the-board chess.

The fast pace and constant need for focus left me feeling drained and frustrated – blaming myself for not being able to concentrate.

Then, I discovered correspondence chess! This format allows for a much slower pace, giving me the time I need to analyze positions and make thoughtful moves. It's been a game-changer. No more pressure, just the joy of strategic thinking without the stress.

Do you ever feel like traditional chess isn't quite the right fit?

If you struggle with focus or find the fast pace overwhelming, correspondence chess could be for you! Here are a couple of options to get you started:

• ICCF.com (International Correspondence Chess Federation): This is the official platform for serious correspondence chess with tournaments and rankings.

• Daily Chess on chess.com: This is a more casual option where you can play correspondence games at your own pace.

Let me know in the comments if you've tried correspondence chess, or if you're interested in giving it a go!

I stumbled upon Opening Master the other day and am quite tempted to buy the Golem subscription and use it with Scid.

Have you ever used their databases? If yes, can you share your thoughts please?

In particular:

• How is the quality of the compilation?
• Are there any annotated games in the database (like ChessBase)?
• Is it as large as they claim it to be?
• Does it receive proper regular updates?

cross-posted from: https://lemmy.ml/post/17978313

Shameless plug: I am the author.

Shameless plug: I am the author.

cross-posted from: https://lemmy.ml/post/15607790

Just wanted to share some (exciting) news about my Common Lisp project, euler-cl. I finally got the time to sit down and integrate it with Codecov! This means a couple of cool things:

• 📈 Test Coverage Tracking: I can now see how well my code is tested over time, giving valuable insights into code quality.
• 🏅 Codecov Badge: euler-cl now sports a snazzy Codecov badge to show off!
• 📦 Reusable Setup: The code and setup process should be simple enough to be used as a reference to integrate Codecov (and potentially other services) into your own Common Lisp projects!

If you're interested this commit is almost all you need: https://github.com/bahmanm/euler-cl/commit/855b014

Let me know in the comments if you have any questions or want to chat about integrating Codecov into your own projects!

If you've found yourself manually crafting complex Docker images or repeatedly installing tools, I've got something for you 😁

Check out "fusions" in bdockerimg project (https://github.com/bahmanm/bdockerimg).

With fusions, you merge base images into powerful composite images.

Currently there are:

• sdkman.bmakelib
• quicklisp.bmakelib

Let me know what other fusions would make your Docker life easier 🙏

I've been working on a small project called bdockerimg.

It's a collection of pre-built Docker images for some less common development tools (currently bmakelib, QuickLisp, and SDKMAN).

The idea is to streamline setup, especially for CI/CD pipelines, where I found myself repeating the same Dockerfile steps a lot. Basic functionality tests are included for a bit of extra peace of mind.

👀 Here's the repo if you're interested: https://github.com/bahmanm/bdockerimg
🗣 And here's the the Matrix room: https://matrix.to/#/#bdockerimg:matrix.org

I'm curious:

• Does this seem like something you might find useful?
• Are there any specific tools you'd love to see as easy-to-use Docker images?

This project is still in its early stages, so any feedback or contributions are much appreciated 🙏

cross-posted from: https://lemmy.ml/post/8492082

bmakelib is a collection of useful targets, recipes and variables you can use to augment your Makefiles.

I just released bmakelib v0.6.0 w/ the main highlight being the ability to define enums and validate variable values against them.

➤ Makefile:

define-enum : bmakelib.enum.define( DEPLOY-ENV/dev,staging,prod )
include define-enum

deploy : bmakelib.enum.error-unless-member( DEPLOY-ENV,ENV )
deploy :
	@echo 🚀 Deploying to $(ENV)...

➤ Shell:

$ make ENV=local-laptop deploy
*** 'local-laptop' is not a member of enum 'DEPLOY-ENV'.  Stop.

$ make ENV=prod deploy
🚀 Deploying to prod...

lemmy-synapse is a light-weight observability and monitoring stack for Lemmy servers.

Using Prometheus and Grafana, it allows the admins to visualise and query the stats of their instance. v1.0.0 comes out of the box with 3 detailed dashboards:

• Host stats (CPU, RAM, disk, network, ...)
• PostgreSQL stats (connections, locks, transations, queries, ...)
• Docker stats (container CPU, RAM, disk, network, OOM signals, ...)

It runs as Docker compose cluster alongside the Lemmy cluster and does not require any changes to it in most cases. Uninstalling lemmy-synapse is as easy as tearing down its cluster and deleting its installation directory.

Got questions/feedback? Pray drop a line:

• #lemmy-synapse:matrix.org
• !lemmy_synapse@lemmy.ml

cross-posted from: https://lemmy.ml/post/6863402

Fed up w/ my ad-hoc scripts to display the targets and variables in a makefile(s), I've decided to write a reusable piece of code to do that: https://github.com/bahmanm/bmakelib/issues/81

The first step toward that would be to understand the common commenting styles. So far I have identified 4 patterns in the wild which you can find below.

Are there any style guides/conventions around this topic? Any references to well-written makefiles I can get inspiration from?

A

VAR1 = foo   ## short one-liner comment
my-target:   ## short one-liner comment 
	…

B

# longer comment which 
# may span
# several lines
VAR1 = foo

## comments can be prefixed w/ more than # 
## lorem ipsum dolor
my-target: 
	…

C

#####
# a comment block which is marked w/ several #s on
# an otherwise blank line
#####
VAR1 = foo

D

#####
#>    # heading 1
#     This is a variation to have markdown comments
#     inside makefile comments.
#
#     ## It's a made-up style!  
#     I came up w/ this style and used it to document `bmakelib`.
#     For example: https://is.gd/QtiqyA (opens github)
#<
#####
VAR1 = foo

cross-posted from: https://lemmy.ml/post/6856563

When writing a (GNU) Makefile, there are times when you need a particular target(s) to be run before anything else. That can be for example to check the environment, ensure variables are set or prepare a particular directory layout.

... take advantage of GNU Make's mechanism of includeing and makeing makefiles which is described in details in the manual:

I just stumbled upon a collection of bash completions which can be quite handy: https://github.com/perlpunk/shell-completions

I tried mojo, cpan and pip completions in a sandbox and they worked like a charm!

The only question I've got is, has anyone ever done a security audit of the repository? Anyone has taken the time to look at the code? I could try auditing but I'm not even sure what to look for.

I feel quite wary of letting an unknown source access to my bash session and what I type.