Why all of the security articles lately? Don't know, just been feeling them. In this one, Samuel Groß summarizes the fruits of reverse engineering iOS 14 to look for any signs of previous vulnerabilities to "memory corruption based 0-click exploits".

"Inheritance is a useful but controversial technique in C++". Basically it's easy to use incorrectly, but it's fairly useful in certain circumstances. Everything in moderation, right? Jonathan Boccara's article takes a look at a technique byPavel Novikov for using inheritance in C++ without pesky pointers to complicate implementation.

Although the complexity of modern computers is great, in that it allows to to quickly build wonderful applications that would've previously taken 1000x the resources, one downside is that it becomes really easy to miss out on all of the details of what your computer is actually doing. Justine Tunney's Blinkenlights is a neat binary emulator that allows you to watch under the hood of your computer when running an executable.

Injecting code into remote processes isn't the safest thing to do, and is actually a common way for malicious actors to get existing processes to run code that the actor has written. Nonetheless, it's interesting to know how it's done. In this informative article, Vladimir takes "a running Node.js HTTP server and, from another local Node.js process, [injects] a script into it to make it log all incoming HTTP requests".

It's not a bad ideas to get to know how SQL databases work. A lot of projects use them. In this article of an extensive series, Pamela Mooney breaks down how the SQL sserver works and how to tune queries.

When creating websites or webapps, you conventionally had two major options for rendering; you could either do it client-side, or server-side. Well in this article, Nethmi Wijesinghe presents a third option (to be fair, it's more of an alternative of the second option), which involes progressively loading server-side rendered content. Faster rendering = more conversions, or just less frustration.

If you're using TypeScript, you mgiht sometimes be tempted to take the easy way out and slap the any type on something you can't be bothered to type. Well in this article, Alejandro Dustet and Wil Hall discuss the intricacies of why if you use the any type in TypeScript, you're gunna have a bad time mmkay?

Await/async are my go to in most JavaScript programming, since I personally think it makes code much more readable and easier to reason about. Unfortunately, not all JavaScript code has caught up (or shares the same opinion), and often times you might have to work with callbacks. In that case, Tamás Sallai has written an article where you can learn how to switch between the two, reimplementing any legacy (or poorly written code) into your perferred solution.

More security related than programming, but this in this article, Adam Weidemann brings to light how a "government-backed entity based in North Korea" is up to some shady shenanigans, in an attempt to build credibility with the CompSec community. Stay vigilant, stay safe.

In this first part of what looks to be a promising series, Oren Eini goes over some of Twitter's stats (in regards to user activity and posts), then outlines some specifications for the social media platform he intends to design from scratch.

Data as code is a common theme in Lisp languages, and is in general a good idea to wrap your head around. Veit Heller's article focuses on implementing quasi-quoting, which marks the part of the code that should be considered dynamic.

Although this article is from 2016, containers are more relevant than ever. Most cloud providers offer containerized systems that are deployable at the click of a button, and running processes in clean environments on a dev machine has never been easier. In this article, Julian Friedman implements a container in Golang and describes what every line of code does.

Joachim Breitner talks about how "CPS-conversion and defunctionalization can help you to come up with a constant-stack algorithm".

Brent Ozar discusses "when you need to do writes, but you want your query to get along with others in high concurrency environments, without creating a blocking firestorm" with MySQL.

"This booklet walks you through building the editor in 184 steps" in C.