This article explains Reed-Solomon erasure codes and the problems they solve in gory detail, with the aim of providing enough background to understand how the PAR1 and PAR2 file formats work, the details of which will be covered in future articles.

I’m assuming that the reader is familiar with programming, but has not had much exposure to coding theory or linear algebra. Thus, I’ll review the basics and treat the results we need as a “black box”, stating them and moving on. However, I’ll give self-contained proofs of those results in a companion article.

So let’s start with the problem we’re trying to solve! Let’s say you have n files of roughly the same size, and you want to guard against m of them being lost or corrupted. To do so, you generate m parity files ahead of time, and if in the future you lose up to m of the data files, you can use an equal number of parity files to recover the lost data files.

Most people are familiar with white noise, that static sound of an air conditioner that lulls us to sleep by drowning out any background noise.

Except technically, the whirl of a fan or hum of the AC isn’t white noise at all. Many of the sounds we associate with white noise are actually pink noise, or brown, or green, or blue. In audio engineering, there’s a whole rainbow of noise colors, each with its own unique properties, that are used to produce music, help relaxation, and describe natural rhythms like the human heartbeat. If you know what to look for, you can start to notice the colors of the noise that make up the soundscape around us.

I’ve never stepped into a leadership role without it quickly becoming clear why a new leader was needed. I think it’s normal for companies to hire new leaders when there are problems that need to be addressed. So I suspect that as the congratulations die down, it’s also normal to look at the set of problems that surround you and ask, “Where do I begin?” (also normal: “What have I done?!”). I suggest instead starting with these two questions:

• How do I create clarity?
• How do I create capacity?

When I started using qjackctl I couldn't understand the difference between the patchbay and the connections window. They both seemed to show the same information and the patchbay was not very useful. Now, thanks to various hints on the linuxaudio mailing list, I think I understand how it should work and how useful it could really be. This document is my attempt to share that understanding with those in the same position as I was.

CSS Grids have been around a long time. Often they come bundled in frameworks such as Bootstrap. I'm not a Bootstrap hater, but sometimes using a framework is overkill if all you really need is a grid. Here's how to make your own CSS Grids from scratch.

There are four related issues here. First, how did "begging the question" come to be a technical term for (a certain kind of) circular reasoning? Second, do people really need a way to talk about circular reasoning, anyway? Third, why did "begging the question" get re-purposed in common usage to mean "dodging the question" or "raising the question", rather than simply subsiding, along with the rest of the terminology of medieval logic, into the midden heap of obsolete idioms? And fourth, should you go with the flow and use "beg the question" to mean "raise the question", or should you fight for the traditional usage, or what? I'll take up these issues one at a time.

Sommartid ger möjligheter till en bättre mobilitet genom att hyra bil. Men det finns en hel del att tänka på vid hyra av bil för att inte ledigheten i efterhand ska solkas av tvister med biluthyraren om pengar.

Giving and receiving whether it’s objects or favors is a bit more complicated in Japanese because you need to be aware of the social status between the giver and the receiver. Basically, there are two words for giving and one word for receiving listed below.

The goal of this project is to create a universal database of disallowed usernames for web applications. This repository contains a list of keywords that should be banned/disallowed to prevent users from registering with, on your software projects and apps to prevent impersonation and phishing on your platform.

The goal of this article is to provide a historical context of how JavaScript tools have evolved to what they are today in 2017. We’ll start from the beginning and build an example website like the dinosaurs did — no tools, just plain HTML and JavaScript. Then we’ll introduce different tools incrementally to see the problems that they solve one at a time. With this historical context, you’ll be better able to learn and adapt to the ever-changing JavaScript landscape going forward. Let’s get started!