Who am I?

Axel, a 36 years old man. Since I discovered programming I have obsessive interests in how computers work and how we use them today. It translated into projects like image encoding, UI immediate mode, creating my own file format for note taking (which I rely heavily on), floating point representation in JS, HTML parsing, file uploading and more. When time allows me to be less busy, I will add articles on specific things I can confidently write about.

Why not share source code?

Some of my projects are possible future products or are used in my clients' codebases, so these will not be shared. However, some of them, which I do not mind sharing, could be. Sadly, GitHub and other source code platforms do not care about us anymore and allow AI to train on source codes (a lot of bad ones), making money from it in a way. There are more reasons for not sharing my code there, but I will not go into them here. The solution would be to allow sharing them here on my website. For that, I am not sure yet whether I want to use a full version control interface like Gitea or simply share the source code as it is at a given time. Without much thought, Gitea seems a bit overkill for me.

What comes next?

For now, this website is (very) limited. It is primarily used to test the IDK to HTML conversion. However, in the future, it will feature articles that I think could be of interest to others, as well as a global search through my own notes written in the IDK file format. The first article will attempt to represent programming as a whole: all related fields, their specificities, accompanied by links on ressources I think may be useful. This is important to me because, from my programming journey, I found that understand what I wanted/needed to learn to be a good programmer was unexpectedly hard. However, as soon as I got a clear image of where/how programming is used in our modern world and how it looks, it became much easier, without mentioning the ability to filter bad ressources, which is just as important. Shortening that time allows one to become a better programmer with the same amount of time. Programming is already hard (impossible?) to master, so you want to cut unnecessary time wherever you can, because as humans, we are not eternal.

What am I programming? (updated regularly)

1. A content management system interface on the client side as well as its server logic: calendar management, image upload, video player, payment. The goal is to allow the lowest cost possible, enabling me to offer competitive pricing.
2. IDK file format parser. The parser was working (the website's pages are constructed using it) but the architecture had to be modified in order to have more flexibility. Because the IDK file format design will be updated very frequently, I needed it to be simpler and more resilient. Implementing regex-like features enables me to translate the design logic into a compressed representation (the regex string) with no performance cost (the regex is multi-thread-capable with a light footprint).
3. Netcode for video game, using UDP. A simple and performant way to handle online video game world updates, mostly because networking is a field that interests me, but also because I found job postings wanting someone implementing netcode.

What will I program? (updated regularly)

1. A crappy sound player. File formats are something I love to learn about, maybe because I am designing one myself. The player must be able to read (I am not saying it will produce sound) mp3, flac, and, as a last resort, use libraries if the compression algorithm complexity is too hard or time-consuming.
2. IDK's UI. Currently, the IDK parser is CLI only, but the future of IDK is a self-contained program with advanced features easy to use. I must implement the UI architecture, which will be immediate mode.

Contact

You can reach me on @AxelDaguerre.