this post was submitted on 29 Sep 2025
55 points (98.2% liked)
Programming
23242 readers
234 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I find myself developing random programs that fills my very small niche. Like a program that displays KeepassXC unlock popup on the workspace I am currently on because it doesn't work as expected when done with window rules. Or a program that displays the status of multiple services in a single table. I feel like I took customisation stuff too far.
Interesting that you make those very small programs in Rust which feels like a huge overhead, but at the same time I feel this would be a way to get into Rust, every time I try something it's so overwhelming because I'm trying to solve a too big of a problem while learning Rust so I just give up on it.
They surprisingly were. Originally I went with Rust because writing them in bash script would be very inefficient in terms of the number of programs I need to invoke to fulfil the function. Then I ended up learning some systemd basics.
The first chapter of the Rust-CLI book is IMHO a very good place to start for just learning how to build something useful. Of course, it does not replace building a project of your own, but might give you enough of a framework to fit your own ideas into.