Programming
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
I've always wanted to write a chess engine.
I might steal that idea
There's a great book on it. Old, but very well explained. You wont make stockfish, but hey.
There's a bunch more ideas just like it! All you have to do is ACTUALLY OPEN THE POST'S LINK.
Going for that Futurama Lucy Liu vibe.
There is the excellent chess programming wiki, but unfortunately it does error 503 for me right now.
Here is the archive: https://web.archive.org/web/20250302091125/https://www.chessprogramming.org/Main_Page
Main site: https://www.chessprogramming.org/Main_Page
It has some pretty good resources to get started, and all the techniques being used.
EDIT: It's back!!! And Lichess is doing the hosting.
If visual explanations help you then I can highly recommend Sebastian Lague's video series on chess engines where he iteratively builds one himself and finally ends up organizing a tournament.
His other content is top notch as well.
I love this site !!
I have always wanted to make something but its just so time consuming. I also dont have ideas for something that isnt complex. ...and I refuse to use an llm to do it, for me thats fake and not real learning.
Upvote for recommendation to make a GBA game. GBA is seriously a joy to dev for.
I always write toy software. I derive joy from writing in G'MIC.
I would post a "Wait... I know you" picture with the ordered dithering filter used if forced .webp conversion didn't muddy the edges/colors further.
Aggressively avoid over-engineering, restrict yourself to only whatever code is necessary to achieve your goal.
I have to repeatedly tell myself this when building out prototypes. It's surprisingly difficult to not get lost in the weeds doing something not immediately necessary like setting up CI/CD or modularizing components.
I guess, this is different from automating a part of your workflow every so often, in that you don't yet know the surrounding context. It is the point to just dick around with some new context for a bit.
And if you get bored of it, i.e. you've learned enough about the new context, then you can just archive the repo and move on, because you don't actually need it as a solution.