#jeRecrute Pas moi mais c'est un poste de développeur à Paris pour écrire du bas niveau en #Zig

Apparemment, il faut un compte Twitter pour répondre "Do you want to write NVIDIA and AMD kernels? In Zig? In beautiful Paris?"
https://x.com/RetiredSyre/status/2028195608562126892

- switching between #Zig versions, I liked it more than the dedicated anyzig
- #Python venv activation – it's silly but feels so good, and collaborates with uv
- ensuring I have the right language server and formatter for a project, be it #Lua, #TypeScript, and trying out various options for Python
- setting LANG="C.UTF-8" only in the specific project folder because #Ansible refused to work with Polish...

The final boss was getting a really comfortable Tree-sitter setup: get the #Rust CLI, write grammar in #JavaScript, re-generate and run tests on source change as a mise Task. And then I only cloned the repo on another machine and was ready to go!

This post was written as a more cultured outlet for my excitement instead of aggresively committing mise.toml into every repository I touch

It was the talk "How to Build Software From Source" from @andrewrk@mastodon.social where someone taught me what build prefix is. I think that's an example of why hanging around #zig language is so beneficial – it also taught me a lot more about building C and libc than any other tool. Many layers of dirt and rust (pun intended) are washed away and you see the basic systems that were under there all the time.