https://blog.davetcode.co.uk/post/21st-century-emulator/ · Implementing an 8080 emulator in a microservice architecture on top of kubernetes
https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/
https://juliareda.eu/2021/07/github-copilot-is-not-infringing-your-copyright/
https://www.getzola.org/ · Everything you need to make a static site engine in one binary.
https://copilot.github.com · AI that builds with you
https://www.youtube.com/watch?v=cApVVuuqLFY · Enjoy the videos and music that you love, upload original content and share it all with friends, family and the world on YouTube.
http://dtrace.org/blogs/bmc/2020/10/11/rust-after-the-honeymoon/ · Two years ago, I had a blog entry describing falling in love with Rust. Of course, a relationship with a technology is like any other relationship: as novelty and infatuation wears off, it can get on a longer term (and often more realistic and subdued) footing – or it can begin to fray. So well one might ask: how is Rust after the honeymoon? By way of answering that, I should note that about a year ago (and a year into my relationship with Rust) we started Oxide. On the one hand, the name was no accident – we saw Rust playing a large role in our future. But on the other, we hadn’t yet started to build in earnest, so it was really more pointed question than assertion: where might Rust fit in a stack that stretches from the bowels of firmware through a hypervisor and control plane and into the lofty heights of REST APIs?
https://thoughtbot.com/blog/alt-vs-figcaption · Describing images with the alt attribute and figcaption element.
https://minimaxir.com/2021/06/gpt-j-6b/ · At the least, AI-generated code is much more readable than the average human’s.
https://jakearchibald.com/2021/last-return-wins/ · An edge case has convinced me it's the 'last' return that always wins…