Dumpster diving the Go garbage collector

Diving Deep: implied bounds and variance

Measuring Technical Debt

{{PreviewText}} 

Howdy Hope you all had a lovely weekend. If anyone has any good technical blogs or writers they want to share, feel free to reply to this email! I'm always on the lookout for good sites to source material from. Also this weekend I started working on the web development course I mentioned a while back. It's not really a course though. It's basically an opinionated how-to guide of getting a custom website live as fast as possible using modern tooling (svelte, postgres, graphql, nginx, let's encrypt, pm2, and docker to name a few) for people who already know how to code and want to build something as a hobby/side gig. Can all of the information already be found online? Sure, but you'll probably have to sift through a bunch of SEO garbage articles before you find it. Websites have a TON of moving parts, and my aim is to give you a step-by-step breakdown of implementation with best practices and nuggets of wisdom from building complex custom websites for several of my own startups. If you might be interested, or know someone who is, let me know! If this goes well, I can potentially get away from doing any ads in the newsletter. Anyway, sorry about the lengthy self-plug. Here's the issue. ==================================================================== Dumpster diving the Go garbage collector Published: 2 February 2022 Tags: go Natalie Serrino traces the Go garbage collector's low-level behavior on a live application using eBPF uprobes. ==================================================================== Diving Deep: implied bounds and variance Published: 5 February 2022 Tags: rust lcnr presents an unsound issue in Rust where a function can arbitrarily transmute lifetimes, causing a segmentation fault, and explores possible solutions. ==================================================================== Measuring Technical Debt Published: 27 January 2022 Tags: philosophy Sean Mack takes a thorough look at technical debt; its history, the different forms it comes in, and ultimately how it can be measured/calculated. Want to help? Thank you for reading! If you enjoy the newsletter, I would really appreciate you helping me spread the word by forwarding this to your friends and colleagues! If you want to discuss or comment on this issue, head on over to this page at A Byte of Coding. You can also subscribe there if you're new! Have comments or feedback? Just reply to this email or hit me up on Twitter @AByteOfCoding. Email landed in your promotions tab? Please move it over to primary so you don't miss the latest issues in the future. Thanks for your Support!  Thanks to sponsors and supporters like Євген Грицай, Scott Munro, zturak, pek, Emil Hannesbo, Joe Hill, and Astrid Sapphire this newsletter is provided to you for free. If you'd like to also show your support and buy me a monthly meal, you can donate on the Patreon page. It's not necessary, but it lets me know that I'm doing a good job and that you're finding value in the content.

Previous

Back to Issues

Next