284 stories
·
1 follower

‘Quiet on the Set’ Goes for Objects, Too

1 Comment

Unless you’re sonically savvy, trying to sleep, or simply on edge, you probably don’t realize just how noisy common items can be. Pretty much everything makes enough racket to ruin a sound man’s day, or at the very least, their chance of picking up the dialogue between two characters. What you need on a set are noiseless but realistic versions of common noisemakers like paper bags, ice cubes, and to a lesser extent, billiard balls.

If you’ve spent any time at all on Reddit, you’ve probably seen frustratingly short GIFs of [Tim Schultz] quickly explaining how this or that noiseless prop is made. Embedded below is a compendium of prop hacks with more information worked in along the way. Talk about dream job! Problem solving and then hacking together a solution for a living sounds terrifying and delightful all at once.

Speaking of terrifying and delightful hacks, there’s still plenty of time to enter our Halloween Hackfest contest, which runs through Monday, October 11th. Halloween is the best time to go all out, so show us what you can do!

Via adafruit

Read the whole story
GaryBIshop
15 days ago
reply
Wow. Super interesting video.
Share this story
Delete

My House

1 Comment

08-31-2021 Carl Riis

On the 19 of August 2019, I bought a house with a small garden. The house is what in English apparently is called an allotment. Basically, a small slot meant for vegetable gardening which sometimes has a house or shed. Not really meant for living in. But after nearly a year of work, I moved into mine. It's legal as long as I don't live there all year round (I skip out on the winters). Price for the slot was 5,500$ which for a 17-year old was a pretty big investment. The cost for all the materials needed to make it liveable was about the same.

alt Picture I took of the house the day I bought it

alt What the inside looked like

The first thing to do was to clean out all the junk and give the outside a paint job since the wood was slowly decaying in the elements.

alt A much needed paint job and clean out later

The first thing I started on was the electrical wiring. To actually supply the house with power I had to dig a 0.5 meter deep trench from the start of the garden to the house. I did it by hand with a shovel.

alt

Next thing to do was to insulate the walls. Here I used glass wool Blanket insulation which gave all the walls a 10 cm layer of insulation. After the insulation I put up two layers of drywall on the walls and one layer in the ceiling.

alt

After the walls and ceiling were painted I laid down the floor with vinyl click flooring.

alt

I then bought a bunch of second hand furniture and a kitchen. I realize I'm making it seem a lot easier than it was. It really was a ton of work. I also can't take all the credit since my parents helped me out a lot. But there you have it. The end result is a liveable (though slightly primitive) house which I absolutely love living in.

Here are some pictures of the end result.

alt

alt

alt


Check out my GitHub and my Twitter

Email me at:

c

a

r

l

t

h

e

p

e

r

s

o

n

_

p

r

o

t

o

n

m

a

i

l

:

c

o

m

Adblock test (Why?)

Read the whole story
GaryBIshop
19 days ago
reply
Wow! He did this at 17!
Share this story
Delete

The quest to recreate a lost and ‘terrifying’ medieval mead

1 Comment

It starts with a cauldron, an open flame, and a good measure of raw honey. Then—double, double, toil and trouble—stir constantly until the honey spits black steam at you. Add water and stand back as it erupts, volcano-like. Throw in some yeast and spices and, after it ages a bit, behold: bochet, a mysterious and lost style of mead.

My path to recreate this ancient and mysterious beverage would take me on a deep dive into the nitty-gritty of medieval yeast strains, and turn my tiny kitchen into a mad scientist’s lab. It would have me digging through scant archival records about obscure systems of measurement in 14th century France. This experiment would require my biggest stockpot—and nerves of steel.

“Caramelizing honey is kind of terrifying,” says Ontario microbiologist Bryan Heit, the brains behind popular homebrewing reference site Sui Generis Brewing. While Heit experiments mostly with beer, particularly traditional styles, he’s been intrigued by bochet for years.

“It truly is a lost style. It’s not a historical style that has survived into the modern era,” says Heit. “It’s literally something that disappeared.”

A sip of honey, caramel, and history in a glass of finished wild-ferment bochet.
A sip of honey, caramel, and history in a glass of finished wild-ferment bochet. Gemma Tarlach for Gastro Obscura

Bochet is mentioned, briefly, in French texts as early as 1292, according to research by independent scholar Susan Verberg, published in 2020 in ExArc Journal. The first and only complete recipe for the drink—and the primary source for modern recreations—turns up in 1393, in what might be considered a manual of mansplaining.

An anonymous French writer penned an exhaustive guide to etiquette, moral conduct, and the practical concerns of a young bride, from choosing servants to throwing feasts: Le Ménagier de Paris (The Good Wife’s Guide). “It’s a ridiculous book,” says Verberg. “It’s micromanagement. I would not have wanted to be his wife.” The book was known mostly in medievalist circles until 2009, when it was fully translated into modern English for the first time. And there, in between reminders of the need for wifely submission and tips on keeping fleas out of the bedclothes, was a curious recipe for something called bochet.

The recipe called for water and honey, plus “brewer’s yeast” and an assortment of spices, including ginger and cloves. That’s standard fare for medieval mead, as were the steps describing fermentation. But the very first few steps were unique: “Put it in a cauldron on the fire to boil” and stir until the honey blisters and bursts, “giving off a little blackish steam.” Unlike any other mead, which is based on raw or gently warmed honey, bochet requires the honey to be caramelized.

A preserved recipe for an extinct beverage is a rarity, and its unique method tantalized historic reenactors and homebrewers alike, including myself. While I’ve made small-batch meads in the past, they have all been based on modern ratios, and none involved a cauldron. Commercial meadmakers have been particularly intrigued by the idea of caramelization: The process offers new possibilities, unlocking “all those roasty, toasty, nutty flavors,” says Jen Otis of KVLT Mead in Tacoma.

Finding a vessel that’s big enough can be a challenge, however, particularly for commercial-scale bochet. “Honey can double, possibly triple, in volume when heated to certain temperatures. For safety, the vessel would have to be four times larger than what you think you would need,” says Ricky Klein, head meadmaker at Vermont’s Groennfell Meadery. He has made small-scale, experimental bochets, and has some words of wisdom. “There are two things I will always say about a bochet. One is, you have never been scalded like getting boiling honey on your skin. It is a second-degree burn, immediately. It can be a very, very nasty burn,” says Klein. “The second thing is, what I just said.”

For some homebrewers, the danger of recreating bochet may be the very thing that attracts them to it. “People who like rollercoasters and jumping off cliffs like bochet,” says Verberg with a laugh. “You can make a sugar volcano that will explode, violently.”

To recreate bochet—at least the version detailed in Le Ménagier, the only full recipe to survive—I started at the source. Most modern interpretations call for a ratio of 3–4 pounds of honey per gallon of water. Le Ménagier calls for one quart of honey (about 3 pounds) per septier, an antiquated measurement that varied from one region to the next. Digging through the scant historical records available online, I found that, in Paris, a septier equaled about four gallons. Modern versions use four times the honey, or more, as the 1393 version.

"The Beekeepers" by Pieter Bruegel, 1565, shows cone-shaped skeps, made of coiled hay or dried grass, used to house honey bees. Beekeepers often crushed the entire skep, bees and all, to harvest the honey.
“The Beekeepers” by Pieter Bruegel, 1565, shows cone-shaped skeps, made of coiled hay or dried grass, used to house honey bees. Beekeepers often crushed the entire skep, bees and all, to harvest the honey. The Print Collector/Getty Images

Then there’s the honey itself. “Honey as diverse as what they had access to then, when monoculture was not a thing, was very different,” says Verberg. Harvesting techniques have also changed: Today, commercial beekeepers and most hobbyists use extractors that pull honey out of the wax comb through centrifugal force. Back in medieval times, says Verberg, “They weren’t extracting the honey, they were crushing it.” In addition to bits of wax, the medieval meadmakers also had pollen and the occasional squished bee in their raw material—components missing from modern honey that would have added more flavor. For example, propolis, a sticky, antibacterial compound that bees produce for colony health, has a zingy taste, and beeswax itself can impart a fuller mouthfeel. “I found that that contamination is really good, and we’re really missing it,” says Verberg, a beekeeper who has made traditional meads.

As a beekeeper, I have access to raw honey produced from a wide range of flowers. Instead of using honey I’d extracted and strained the modern way, however, I crushed some comb taken from a colony that had unfortunately not survived winter—the bees’ lasting legacy would be to provide honey close to what was available in the 14th century, including the occasional stray leg or wing.

The bochet bubbling away as it ferments.
The bochet bubbling away as it ferments. Gemma Tarlach for Gastro Obscura

To avoid the chlorine, fluoride, and other additives found in modern tap water, I opted for distilled water. The spices called for in the Le Ménagier recipe include supermarket staples such as ginger and cloves, but also long pepper and grains of paradise. I used a pepper blend that included grains of paradise and added some cardamom, which, combined with black pepper, is often cited as a long pepper substitute.

The toughest thing to recreate from 1393 is the yeast, which, next to the caramelization of the honey, would have had the most impact on a bochet’s taste. Unlike medieval yeasts, which were not cultured in clean labs, modern commercial yeasts are typically single strains bred for reliability and characteristics specific to their use: A commercial wine yeast will perform very differently, and create different flavors, than bread yeast. While most modern bochet recipes use a wine or champagne-style yeast, Le Ménagier called for beer (or, in a pinch, bread) yeast. Heit, Verberg, and others who’ve dabbled in historic bochet suggested trying everything from English-style ale yeast to Norwegian Kveik, now commercially available after being used by farmhouse brewers “for over a thousand years,” says Heit. “It’s not the yeast historical to the France area, but it might be closer to what they had.”

To get as close as possible to a vintage 1393 bochet without investing in special equipment, and to learn how different yeasts might affect the final product, there seemed only one option: a controlled trial. I adapted Le Ménagier’s recipe for a smaller batch and then divided that into six micro-batches; only the yeast would be different.

The array of commercial yeasts I used. Not shown: wild yeast coaxed to participate in the experiment.
The array of commercial yeasts I used. Not shown: wild yeast coaxed to participate in the experiment. Gemma Tarlach for Gastro Obscura

I bought a few commercial ale-brewing strains other meadmakers had suggested, as well as a dry white wine variety often called for in online modern bochet recipes. I also reserved a little of the caramelized honey for a wild-ferment bochet: I would collect whatever yeast was in my environment, similar to how sourdough bread is traditionally made.

I also added a few organic raisins, which would help the yeast get started. The concept is the same as adding a lab-derived yeast nutrient powder, called for in many modern bochet recipes; the difference here is that medieval meadmakers would have had access to raisins or other dried fruit.

With a big enough pot, caramelization was a safe and stress-free process—though, full disclosure, I’ve worked as a pastry chef and this was not my first time to the sugar volcano rodeo. Once measured into their glass jars, each batch bubbled away happily for a month before being strained and moved into new, clean containers for the duration of fermentation.

While transferring them to new jars, I sampled the month-old batches. They were thinner in body and less sweet than other meads I’ve made, thanks to the lower ratio of honey-to-water. The different yeasts gave each micro-batch its own distinct character, from a bone-dry, astringent drink made with white wine yeast to the sweeter and smoother concoction that used English ale-style yeast. The Kveik’s dominant notes were bitter and medicinal—perhaps appropriate, since Verberg’s research suggests bochet may have been drunk to balance one’s humors. The wild yeast strain was milder overall, similar to the English ale–style but not as sweet.

My mad experiment.
My mad experiment. Gemma Tarlach for Gastro Obscura

“You have to do a decent amount of conjecture as you try to get close to what they did,” says Jereme Zimmerman, author of Make Mead Like a Viking. “In some cases, you really try to recreate what they did historically, and it doesn’t come out that great.”

The experiment was not a disappointment. Unlike many beers, meads are generally meant to be aged, and most don’t reach their potential for a year. So I’ll bottle these batches when they stop bubbling, and set them aside to see what develops. All of them taste of caramel, honey, and history.

Bochet

Adapted from Le Ménagier de Paris, 1393
Yields 1 gallon

Ingredients
1 pint (24 ounces by weight) good quality, raw honey, preferably local and multi-source, such as wildflower honey
1 gallon plus 1 pint water, distilled or spring (do not use tap water)
4 grams (about 1 rounded teaspoon) of commercial wine, beer, or bread dry yeast, either single-strain or a combination per preference (do not use rapid-rise bread yeast)
1 ounce (28 grams or about 3 tablespoons) organic raisins, chopped
6 grams (about one tablespoon) fresh ginger, skin on, chopped
4 cloves, whole
20 green cardamom pods, lightly crushed
8 grams (about one tablespoon) whole black peppercorns, or peppercorn blend (preferably including grains of paradise), lightly crushed

Step 1

The first step toward making bochet is the most important and potentially most dangerous: Caramelize the honey. Boiling honey, or any sugar, can be messy and, if done improperly, can cause severe burns (unlike water, boiling sugar adheres to the skin). Choose a tall pot at least three times larger than the volume of the honey.

Place the pot on stove and add one gallon of the water. Make a mental note of the waterline on the pot for later reference (if using a pot that has quarts and gallons marked on the side, skip this step). Pour the water out into another container but keep it within easy reach. Wipe the pot dry.

Turn the burner on medium-high heat and add the honey to the pot. Monitor the honey closely; when it starts to bubble, begin stirring it gently with a long-handled stainless steel or wood spoon, making sure that the spoon touches the bottom of the pot. Avoid sloshing or splattering honey up the sides of the pot, where it can burn. The edges of the honey will begin to darken when caramelization starts; the bubbling will then slow and the honey will take on a foamy appearance. The bubbles will start to pop and emit steam; to avoid scalding your eyeballs, do not lean over pot. If the honey begins to swell, lower the heat but do not stop stirring.

As the honey continues to darken, you can test its color by letting a drop of it fall from the spoon onto a plate, where it will quickly harden. Do not stick your finger in the boiling honey. Do not touch the drop of honey, which will remain hot for several minutes.

When the honey is a deep mahogany color (after 20–30 minutes, depending on the type of pot and burner setting), turn off the burner. Do not lean over the pot. Slowly pour in about two cups of the water while continuing to stir. The caramelized honey will swell dramatically and sputter intensely for a few seconds, shooting up a lot of steam. If you have chosen your pot wisely and are not leaning over it, you’ll be fine.

Continue stirring and gradually add the remaining water. Bring to a boil and reduce to the level noted earlier (or to the gallon mark on the inside of the pot). Turn off the burner and remove the pot from the heat. Let it cool to room temperature, which may take a few hours or even overnight. Do not refrigerate, since fermentation will only occur at or slightly above room temperature.

Step 2

While the caramelized honey syrup is cooling to room temperature, wash and sanitize the fermentation vessel and lid. To make a gallon batch of bochet without investing in specialized homebrewing equipment, use a wide-mouth gallon glass jar and a silicon fermentation lid. Be sure the jar and lid are dry before proceeding.

Prep the spice sachet by adding the spices to a square of cheesecloth, folding up the sides and tying it with kitchen twine to make a little bag.

Add about ¼ cup of distilled or spring water to your vessel. The water should be between room and body temperature, neither cool nor hot. Add the chopped raisins. Sprinkle the yeast into the water and let it sit for a few minutes until the yeast dissolves and the water looks cloudy.

The nice golden hue of a bubbling batch of bochet.
The nice golden hue of a bubbling batch of bochet. Gemma Tarlach for Gastro Obscura

Pour in the caramelized honey; you may strain it through cheesecloth if you wish but this is optional. Leave about an inch of space at the top of the jar. Place the spice sachet in the jar and then cover with the fermentation lid and outer ring. You want an airtight fit so that undesirable microbes can’t get in. Swirl gently and place it out of direct sunlight but somewhere you can keep an eye on it. Do not place the jar near a heat source. After an hour or two, you should start to see lots of tiny bubbles shooting up through the liquid. The top of the developing mead may foam or get scummy-looking. Just let it be. If liquid overflows through the fermentation lid’s one-way valve, wipe it with a clean cloth but do not open the jar. After two days, open the jar briefly just to remove the spice sachet, which you can toss or reuse if making another batch at the time.

After two to four weeks, you will notice the bubbles slow. Wash, sanitize, and dry another gallon jar and place a funnel with a double layer of cheesecloth in its mouth. Remove the fermentation lid and gently pour the liquid into its new home. Discard the semi-solid material in the original container. The liquid should appear clearer once transferred. Close the new container with the fermentation lid and store in a dark, cool place for at least a month, preferably three or more. You can transfer the liquid to a new vessel monthly for a clearer finished product, but this is optional.

To bottle the bochet, wash and sanitize flip-top beer bottles; be sure they are dry before using. Using a funnel and cheesecloth, gently pour the bochet into each bottle but do not fill completely. Leave at least two inches of space. Close using flip-top and store upright in a cold, dark place. Avoid shaking.

Excessive gas can build up in the bottle if you overfill it or bottle it before fermentation has finished. This may cause the bottle to explode. For this reason, I store my bottled mead and bochet in a large bin in the basement, with the bin lid weighted down so that, if it does explode, it won’t make too much of a mess. When opening a bottle of homemade bochet, do so outside or with the bottle in the kitchen sink, just in case built-up pressure causes a geyser-effect.

Gastro Obscura covers the world’s most wondrous food and drink.
Sign up for our email, delivered twice a week.

Adblock test (Why?)

Read the whole story
GaryBIshop
31 days ago
reply
Madness!
Share this story
Delete

Flying Home

1 Comment and 2 Shares

Flying Home

One of the most challenging things about being a cartoonist is making jokes when you don’t feel like it. But even when times are tough, I keep making comics, because that’s what I do… and I do find that humour helps me get through the tough times. And this summer, there have been some of the toughest of times.

You got to know my mother a bit through my recent Savage Family Moments comics – and those comics exist because I was making more regular visits to see her. Now that my family is getting together for a “Celebration of Life” party for Mom, I feel ready to make some comics about her life and our times together. I hope you like them. And I’ll still make a few jokes along the way, of course. 🙂

Read the whole story
GaryBIshop
32 days ago
reply
Share this story
Delete
1 public comment
jlvanderzwan
33 days ago
reply
I had this when we helped my uncle move out of my grandparents' house. He still lived there after they passed away for over a decade (he had lived with them his whole life) and he hadn't changed anything to the place.

It looked the same way as it did in my childhood, it smelled the same way as well. Their coats were still hanging on the coat rack. The whole place just felt like a home that was waiting for them to return. The realization that they never will was enough to make me burst out crying over their passing all over again.

If I try to remember what their home smelled like it still brings a feeling of grief to the point where it almost makes me cry. Somehow it really emphasizes that this is a memory of a former home and a childhood that is forever lost to the past.
ttencate
32 days ago
*hugs*

AG-Grid's simpleHttpRequest

1 Comment

We use AG-Grid at work for several of our projects. Earlier this week, I ran into an interesting issue in some code being used to load data into the grid. The call was very simple:

agGrid.simpleHttpRequest({url: theURLToLoad })
    .then(function(data) {
        gridOptions.api.setRowData(data);
    });

This asynchronous call was failing and no error was being thrown (as we typically do elsewhere in our code). In looking around, I couldn't determine where the simpleHttpRequest call was defined. The AG-Grid documentation, which is generally pretty good, had no mention of it, save for its use in a few examples. After half an hour of digging, I decided to actually poke around in the AG-Grid source code. There I found the function's definition:

function simpleHttpRequest(params) {
    return new _utils__WEBPACK_IMPORTED_MODULE_0__["Promise"](function (resolve) {
        var httpRequest = new XMLHttpRequest();
        httpRequest.open('GET', params.url);
        httpRequest.send();
        httpRequest.onreadystatechange = function () {
            if (httpRequest.readyState === 4 && httpRequest.status === 200) {
                resolve(JSON.parse(httpRequest.responseText));
            }
        };
    });
}

All this function is an incredibly light-weight wrapper around XMLHttpRequest. It provides absolutely no support for error handling, and is missing all the other hooks one would need to take full control over the request and its response. It frustrates me when packages do stuff like this. If you're going to show how to fetch remote data for your package, use the vanilla JavaScript features that are industry standard, not some custom wrapper.

Read the whole story
GaryBIshop
47 days ago
reply
Use fetch, much nicer api.
jgbishop
47 days ago
I've typically been using jQuery's ajax() call (we still use jQuery for a fair bit of our stuff). This was also in code that a colleague wrote. I love debugging other people's problems...
Share this story
Delete

New in Git: switch and restore

1 Comment

"When I see a door with a push sign, I pull first to avoid conflicts" - anonymous

For those that work with git for some time, it is not often that you get to discover new things about it. That is if you exclude the plumbing commands which probably most of us don't know by heart and most likely that's for the better. To my surprise, I recently found out about 2 new additions to the list of high-level commands:

  • git restore
  • git switch

To understand why they came to be, let's first visit our old friend git checkout.

alt

git checkout is one of the many reasons why newcomers find git confusing. And that is because its effect is context-dependent.
The way most people use it is to switch the active branch in their local repo. More exactly, to switch the branch to which HEAD points. For example, you can switch to the develop branch if you are on the main branch:

git checkout develop

You can also make your HEAD pointer reference a specific commit instead of a branch(reaching the so-called detached HEAD state):

git checkout f8c540805b7e16753c65619ca3d7514178353f39

Where things get tricky is that if you provide a file as an argument instead of a branch or commit, it will discard your local changes to that file and restore it to the branch state.
For example, if you checked out the develop branch and you made some changes to the test.txt file, then you can restore the file as it is in the latest commit of your branch with:

git checkout -- test.txt

A method to the madness

If you first look at these two behaviors you might think that it doesn't make any sense, why have one command do 2 different actions? Well, things are a little more subtle than that. If we look at the git documentation, we can see that the command has an extra argument that is usually omitted:

git checkout <tree-ish> -- <pathspec>

What is <tree-ish> ? It can mean a lot of different things, but most commonly it means a commit hash or a branch name. By default that is taken to be the current branch, but it can be any other branch or commit. So for example if we are in the develop branch and want to change your test.txt file to be the version from the main branch you can do it like this:

git checkout main -- test.txt

With this in mind, maybe things start to make sense. When you provide just a branch or commit as an argument for git checkout, then it will change all your files to their version in the corresponding revision, but if you also specify a filename, it will only change the state of that file to match the specified revision.

alt

So even if things may start to make sense after reading the previous paragraphs, we must admit that it is still confusing especially for newcomers. That's why in version 2.23 of git, two new commands have been introduced to replace the old git checkout(git checkout is still available, but people new to git should start with these ones preferably). As you would expect, they basically each implement one of the two behaviors described previously, splitting git checkout in two.

Switch

This one implements the behavior of git checkout when running it only against a branch name. So you can use it to switch between branches or commits.

git switch develop

While with git checkout you can switch to a commit and transition into a detached HEAD state, by default git switch does not allow that. You need to provide the -d flag:

git switch -d f8c540805b7e16753c65619ca3d7514178353f39

Another difference is that with git checkout you can create and switch to the new branch in one command using the -b flag:
git checkout -b new_branch

You can do the same with the new one, but the flag is -c:
git switch -c new_branch

Restore

This one implements the behavior of git when running it against a file. You can restore, as the name suggests, the state of a file to a specified git revision(the current branch by default)

git restore -- test.txt

These methods are still marked experimental, but for all intents and purposes they are here to stay so by all means I encourage everyone to start using them since they will probably make a lot more sense in your head and also it will make git just a little bit less confusing to new users.

More details about the two commands can be found in their git documentation:

Adblock test (Why?)

Read the whole story
GaryBIshop
50 days ago
reply
A useful change.
Share this story
Delete
Next Page of Stories