Typos in code and comments can be annoying. But they don’t have to be, with typos it is super easy to introduce automated typos checking (and fixing).

Some 10+ years ago on a job interview I was asked to query the database for the comments tree in a front-end friendly way, meaning no heavy processing/sorting to happen on the back-end. Turns out this question was to check if I knew about the Hierarchical Queries with Oracle (WITH RECURSIVE on other databases), which I did not back then.

TL/DR: read [1] and watch [2]:

1. Actor Model of Computation
2. The Actor Model (Hewitt, Meijer, Szyperski)

TL;DR: See sergey-melnychuk/project-one.

INFO: Optional fields missing from Cargo.toml: ‘description’, ‘repository’, and ‘license’. These are not necessary, but recommended INFO: ✨ Done in 2.43s INFO: 📦 Your wasm pkg is ready to publish at /home/work/Temp/project-one/build.

AWS Lambda shows memory peak-usage, but when memory usage hits the limit, breaking down where exactly too much memory is being used might be a very useful things. The runtime is kind of a black box (at least in my understanding), so any telemetry/measurements need to be baked into the function. For this example, I only describe an approach useful for Rust runtime.