GitHub’s Post

This is a handy guide if you are new to GitHub.

Fun little detail. When you initialize a Python-Rust project with Maturin you'll also get a neat Github Actions file that checks that it can build on all sorts of operating systems/architectures.

typical JIT interpreter compiler for WebAssembly byte code :) https://lnkd.in/gDAX3UDu

My Stack DS Based on Dynamic Array Implementation, C Lang.

Automated Rust Compiler Image Build Automation that downloads the latest Rust compiler and sets up the environment in a Docker image. It detects new compiler releases and creates automatically a new release for the automation repository. The image will then be tagged and publish on the GitHub container registry. All images tags can be found at: https://lnkd.in/e4GnfyFw Regularly the automation is launched and discovers new releases and adds them to the registry and the repository.

Learn about the performance findings from months of repo build testing and tips we learned along the way.

Lifehack: If you have any file that gets corrupted (like an ML model) in you project, Simply go to the git root directory, add *.<your file extension> <binary> in .gitattributes file. This will make your your files gets uploaded as a binary without any compression, which will prevent it from getting corrupted. Something like this:

tired: i'll do a git diff between my prompt versions and track changes manually wired: i'll just click "Update" on Portkey's prompt playground and get accurate diff summaries 💆

A simple application for recording data that can be used as a base example for an even larger system. Feel free to give your suggestions for improvement. Remembering that I am still an intermediate level programmer, I have a lot to learn. The application is still under development. I'm slowly implementing more functions and fixing some annoying bugs.

This is a wonderful blog post about different ways of implementing context switching within a single-threaded application (examples are in C). Nicely written. One thing I'll poke at about C (the author points out a particular bug) is just how easy it is to mess up your memory ownership and management to overwrite the stack. Keep it in mind. https://lnkd.in/gDWy4MpF