#and meticulously code my conditional formatting | Explore Tumblr posts and blogs

amadwinter · 1 year ago

Text

Making of Monday - Tracking Word Counts

On Making of Monday, we share behind the scenes of one of our works past, present, or future. All the little things that would fit into a DVD bonus content section: cut scenes, outlines, director's writer's commentary, or basically any thing that didn't make it into the final version. Send me an ask if you're interested in knowing little details about any particular fic!

This week, I decided to show my word count spreadsheet that I've been meticulously using and crafting for coming up on two years now. It wasn't built in a day, and I'm almost constantly tweaking it to make it look nice and functional as I keep writing.

Uh, fair warning. This is not a very exciting post. Unless you like numbers and data, like I do.

For the sake of my own sanity, I started a new Excel document for the new year. This is my Summary page for the year 2024. I have pages created already for each month but hide them when it isn't that month. I'll show the Overview page next after I've explained what you're looking at.

So what you see here is my monthly and annual writing totals. This only takes into account new words written, although the start number at the top of each yearly column includes my running word count. Each month's number is automatically updated from the corresponding month's page, and added up in the total column.

On the side, I have fun projections. So if I wanted to write x number of words per year, not counting the words I have already written, I would need to write y number of words per month with an average of z number of words per day. It's not something I pay too much attention to, just for fun. Below that is a projection of if I write the NaNoWriMo daily count (1667 words per day) or 1000 words per day, how much that would add up to at the end of the year.

This is the Overview page from last year (2023) plus December 2022 which is when I switched over from my previous Google Sheets document. Additionally at the bottom you can see the different monthly pages that are not hidden (I color coded them because I was bored one day).

This page keeps track of my daily totals in the form of a color gradient, linked to the monthly pages to get the totals.

Solid Red = 0

Solid Yellow = 1000

Solid Green = 1667 (NaNoWriMo Daily; 50,000 words in a 30 day month)

Originally, the idea was to be able to look at it and see if there were time periods that I wasn't writing as well due to being busy for various reasons, so I could be able to predict in the future what conditions weren't great for writing. But an interesting side effect is it's also able to track my good days and my bad days for health reasons.

That random number you see on the right side is my highest daily word count. I was curious about it, but I couldn't figure out a way to make it look pretty and fit in with everything else.

This is my month page, divided by each individual project. Y is series or event with multiple fics involved, Z is one-shots, two-shots, or very short fics. The greyed out ones at the top are ones I'm not actively working on, the ones in green are fics that I am either actively working on or trying to work on.

Also at the top are the new words added each month (which is the cell used in other pages to keep track of the monthly number), the total words in all my documents, and the daily average for the month.

The color gradient at the top for each day follows the same pattern as before; Solid Red = 0, Solid Yellow = 1000, Solid Green = 1667+

I keep track of the word count for each chapter, add the total, subtract it from the previous day, and boom, that's my daily total. If there are times where I delete things, I throw it into a document called "Binned" to balance the numbers. That way, I never subtract from the amount of words I've written, only add.

While it may look like a very simple sheet, it is very messy with formulas, conditional formatting, etc. If I were more skilled at Excel, I could probably improve it even more, but at this point, there's very little maintenance needed to keep it going and I can focus on actually writing.

In theory.

#making of monday #writing process #no i didn't almost forget to post this #what are you talking about?#this might only make sense in my own brain

8 notes · View notes

viswatechynology · 3 years ago

Text

Pseudocode

What is Pseudocode?

Pseudocode literally means ‘fake code’. It is an informal and contrived way of writing programs in which you represent the sequence of actions and instructions (aka algorithms) in a form that humans can easily understand.

You see, computers and human beings are quite different, and therein lies the problem.

The language of a computer is very rigid: you are not allowed to make any mistakes or deviate from the rules. Even with the invention of high-level, human-readable languages like JavaScript and Python, it’s still pretty hard for an average human developer to reason and program in those coding languages.

With pseudocode, however, it’s the exact opposite. You make the rules. It doesn’t matter what language you use to write your pseudocode. All that matters is comprehension.

In pseudocode, you don’t have to think about semi-colons, curly braces, the syntax for arrow functions, how to define promises, DOM methods and other core language principles. You just have to be able to explain what you’re thinking and doing.

Benefits of Writing Pseudocode

When you’re writing code in a programming language, you’ll have to battle with strict syntax and rigid coding patterns. But you write pseudocode in a language or form with which you’re very familiar.

Since pseudocode is an informal method of program design, you don’t have to obey any set-out rules. You make the rules yourself.

Pseudocode acts as the bridge between your brain and computer’s code executor. It allows you to plan instructions which follow a logical pattern, without including all of the technical details.

Pseudocode is a great way of getting started with software programming as a beginner. You won’t have to overwhelm your brain with coding syntax.

In fact, many companies organize programming tests for their interviewees in pseudocode. This is because the importance of problem solving supersedes the ability to ‘hack’ computer code.

You can get quality code from many platforms online, but you have to learn problem solving and practice it a lot.

Planning computer algorithms with pseudocode makes you meticulous. It helps you explain exactly what each line in a software program should do. This is possible because you are in full control of everything, which is one of the great features of pseudocode.

Example of Pseudocode

Pseudocode is a very intuitive way to develop software programs. To illustrate this, I am going to refer back to a very simple program I wrote in my last article:

When a user fills in a form and clicks the submit button, execute a ValidateEmail function. What should the function do?

1. Derive an email regular expression (regex) to test the user’s email address against.

2. Access the user’s email from the DOM and store it in a variable. Find and use the right DOM method for that task.

3. With the email value now accessed and stored, create a conditional statement:

· If the email format doesn’t match the rule specified by the regex, access the element with the myAlert id attribute and pass in the “Invalid Email” message for the user to see.

· Else, if the above condition isn’t true and the email address format actually matches with the regex, check to see if the database already has such an email address. If it already does, access the element with the myAlert id attribute and pass in the “Email exists!” message for the user to see.

· Now, if both of these conditions aren’t met, (that is the email format matches the regex and the database doesn’t have such an email address stored yet), push the users email address into the database and pass in the “Successful!” message for the user to see.

All you have to do at this stage is find the programming language constructs that will help you achieve each of your steps. Noticed how seamless the transition from pseudocode to actual code became? That’s how effective writing pseudocode can be for program design.

Pseudocode is also a great way to solve programming-related problems when you’re struggling with them. For those practising programming in coding challenge platforms like CodeWars, pseudocode can be of immense help.

How to Solve Programming Problems with Pseudocode

Solving programming problems can be hard. Not only do you have the logical part to reckon with, but also the technical (code forming) part as well. I recently uncovered a brilliant and effective formula for solving tricky coding problems.

Here are the steps you can follow to solving programming problems with pseudocode:

Step 1: Understand what the function does

First, you need to understand that all a function does is (optionally) accept data as input, work on the data little by little, and finally return an output. The body of the function is what actually solves the problem and it does so line by line.

Step 2: Make sure you understand the question

Next, you need to read and understand the question properly. This is arguably the most important step in the process.

If you fail to properly understand the question, you won’t be able to work through the problem and figure out the possible steps to take. Once you identify the main problem to be solved you’ll be ready to tackle it.

Step 3: Break the problem down.

Now you need to break down the problem into smaller parts and sub-problems. With each smaller problem you solve, you’ll get closer to solving the main problem.

It helps to represent these problem solving steps in the clearest and most easily understandable way you can — which is psedocode!

· Start solving: open and use tools like Google, Stack Overflow, MDN, and of course freeCodeCamp! :)

· For every step of the problem that you solve, test the output to make sure you’re on the right path. Keep solving these small problems until you arrive at the final solution.

#Pseudocode #explain Pseudocode #what is Pseudocode

2 notes · View notes

rafaelafranzen · 6 years ago

Text

(This is entirely unrelated to Good Omens, so feel free to scroll on. But, I read @drawlight’s love songs to the two cities he’s lived in and the idea and format of serenading a city and place just clung to me and wouldn’t let go until I sat down with a word processor. I meant to write three shorter pieces - this one here, one about London, and another about a couple of coastal regions I’ve been to in the UK, but this one just kept going, so I’m saving the others for another day, mayhaps.)

A love song to Singapore (a city of “and yet”s, an acquiesced home)

I know you. You and your concrete and glass, you with your cutting edge. You with your perpetual summer. Your hot and wet. Your hot and dry. Your hot and hot. Your cool kiss of air-conditioning curling from the entryway of every mall, that permeates every office. Your pull of shade languid under each five-foot walkway, the never-quite escape from the stick of sweat that clings like a second skin. Your own personal welcome to an island two degrees north of the equator.

You are so good at hardware. You bend metal and glass and concrete into seagoing sails a-billow, into dry docked boats marooned atop three towering plinths, into spiked fruit with a thousand panes of refraction. Between and beside tembusus, and angsanas and sagas take root, so people have to guess which came first, the garden or the city. (The answer is yes.) You’ve carved forests and waterfalls inside of these bodies of concrete and glass. Filled our airport with the flutter of butterflies by the hundred. Stuck them side-by-side with Muji, Shake Shack and Vans to keep us guessing.

You’re all very well. Yes, all shiny and new. You never let anyone see the bits that aren’t. (Until someone published a book about the bits we’ve tuned out. The bits that fell through the cracks. A national bestseller. Over 20,000 copies in less than a year). Your blueprints are meticulous, but your software development chugs, always a revision behind. This code that lives between pages, proclaimed from black-box stages, left held between sealed lips and balanced on tips of tongues. The wary voices that quiet when The One speaks for the people. Saying we are not ready. (If so, riddle me this – when, how, if, will we ever be ready?). These bits and bytes that live sight unseen, the sparkling spirits shrouded amongst the pack-huddled ghosts, moving as one. Don’t you want them to shine too?

And yet I’ve kicked ping pong balls along your corridors when we were too little and too poor for soccer balls (not even plastic ones). You’ve never let me worry about lounging or leaving the house with naught but a t-shirt, shorts and a pair of flip flops no matter the time of year with a promise of nothing worse than a bit of sunlick and a pinch of damp. Your ports are my gateway to Asia, and my runway to places yet further-flung. Your stage is the one I strode across in robes of navy and crimson, and your institutions were the ones who armed me with tools enough to set out upon the wide world.

And yet you are the harbor to which the world comes. These docked boats from far-flung seas with their cargo of wonders. The flock of violins that have come to roost, bowing in time to the trill of woodwinds, the rosewood-deep vibrato of the Chinese pipa’s steel strings, and sharp resounding patter and thwack of the Indian tabla, all singing under the same roof. These migratory birds that have settled and bade us speak in a language of four tongues picked apart and mashed into an arrangement that could only be yours. Your gravitational pull that’s brought everyone from the Wooster Group, to Andrew Lloyd Webber, the Bolshoi Ballet, U2, Carol Ann Duffy and Neil Gaiman to visit our shores, so we can, for a space of time, bask in the light of something other than the sun.

And yet you’re a mecca of $2 Michelin starred soy chicken noodles. Morning coconut-jam butter toast with runny eggs swirled into a mess of brown and yellow, slurped from the steel of a teaspoon. Steamed rice cake topped with radish relish. Carrot cake, fried in a wok, with no carrots of which to speak, garnished with spring onions and eaten with chopsticks. Yellow egg noodles in sweet potato, peanut, shrimp and curry gravy. Ghee griddled flatbreads with curry and sugar. Cantonese Dim Sum, Japanese Tonkatsu and Italian Antipasti side-by-side, take-your-pick. If you could measure the yearning of being away in raised chopsticks and waiting spoons, we are some of the most homesick people in the world.

And yet you are the city where I know every street and shore. Where the river always flows. Where it’s a place that will stay within me wherever I choose to go.

This is why: And yet (despite the heat, and the concrete and software too) you are home.

(with lines from the last couple of paragraphs from Dick Lee’s Home, a popular national song. I did not mean, in using it, to come off as patriotic by any stretch of the imagination, but the words fit, somehow, as this country has come to fit within me, with all it’s jags and anxiety beneath it’s polished surface).

Several landmarks are mentioned here, each wonders of architecture, if you’re so inclined to look: The Sail, Marina Bay Sands, Esplanade - Theatres on the Bay, Jewel @ Changi Airport.

#personal #my writing #i got really inspired and just wanted to try it and the words just kept coming #which is unusual because I never ever write in this format #but it felt right and fresh #of all the gripes I have with the place I live #and no matter how much I dream of other spaces to call home #this one stays with me whether I want it or not #and I don't suppose it's a bad thing after all #that saying its a super fun format #it should be a thing! love songs to cities #i'd read it if anyone else wrote these #so I can see places through your eyes

5 notes · View notes

viswatech · 3 years ago

Text

PSEUDOCODE

What is Pseudocode?

You see, computers and human beings are quite different, and therein lies the problem.

With pseudocode, however, it’s the exact opposite. You make the rules. It doesn’t matter what language you use to write your pseudocode. All that matters is comprehension.

In pseudocode, you don't have to think about semi-colons, curly braces, the syntax for arrow functions, how to define promises, DOM methods and other core language principles. You just have to be able to explain what you're thinking and doing.

Benefits of Writing Pseudocode

When you're writing code in a programming language, you’ll have to battle with strict syntax and rigid coding patterns. But you write pseudocode in a language or form with which you're very familiar.

Since pseudocode is an informal method of program design, you don’t have to obey any set-out rules. You make the rules yourself.

Pseudocode acts as the bridge between your brain and computer’s code executor. It allows you to plan instructions which follow a logical pattern, without including all of the technical details.

Pseudocode is a great way of getting started with software programming as a beginner. You won’t have to overwhelm your brain with coding syntax.

In fact, many companies organize programming tests for their interviewees in pseudocode. This is because the importance of problem solving supersedes the ability to ‘hack’ computer code.

You can get quality code from many platforms online, but you have to learn problem solving and practice it a lot.

Example of Pseudocode

Pseudocode is a very intuitive way to develop software programs. To illustrate this, I am going to refer back to a very simple program I wrote in my last article:

When a user fills in a form and clicks the submit button, execute a ValidateEmail function. What should the function do?

1. Derive an email regular expression (regex) to test the user's email address against.

2. Access the user's email from the DOM and store it in a variable. Find and use the right DOM method for that task.

3. With the email value now accessed and stored, create a conditional statement:

· If the email format doesn’t match the rule specified by the regex, access the element with the myAlert id attribute and pass in the “Invalid Email” message for the user to see.

Pseudocode is also a great way to solve programming-related problems when you're struggling with them. For those practising programming in coding challenge platforms like CodeWars, pseudocode can be of immense help.

How to Solve Programming Problems with Pseudocode

Here are the steps you can follow to solving programming problems with pseudocode:

Step 1: Understand what the function does

Step 2: Make sure you understand the question

Next, you need to read and understand the question properly. This is arguably the most important step in the process.

Step 3: Break the problem down.

Now you need to break down the problem into smaller parts and sub-problems. With each smaller problem you solve, you'll get closer to solving the main problem.

It helps to represent these problem solving steps in the clearest and most easily understandable way you can – which is psedocode!

· Start solving: open and use tools like Google, Stack Overflow, MDN, and of course freeCodeCamp! :)

· For every step of the problem that you solve, test the output to make sure you’re on the right path. Keep solving these small problems until you arrive at the final solution.

#explain psedocode whatispsedocode psedocode

0 notes

johnboothus · 4 years ago

Text

Wine 101: Cap vs. Cork

This episode of “Wine 101” is sponsored by Talbott Vineyards. At Talbott Vineyards, we focus on crafting estate-grown Chardonnay and Pinot Noir in Monterey County’s Santa Lucia Highlands. Our celebrated Sleepy Hollow vineyard is located in one of the coldest grape-growing climates in California, ideal for these two varieties. Here, the brisk wind and fog rolling off Monterey Bay create a long growing season, producing fruit-forward wines with spectacular acidity. Building on a nearly 40-year legacy of meticulous craftsmanship, Talbott continues to produce highly acclaimed wines of distinction.

Click the link below to discover and purchase wine brands discussed on the “Wine 101” podcast series. Get 15% OFF of your purchase of $75 or more when you use the coupon code ‘wine15’ at checkout. https://www.thebarrelroom.com/discover.html?src=vinepair

In this episode of “Wine 101,” VinePair tastings director Keith Beavers discusses the difference between the two most popular wine closures: corks and screw caps. Beavers details the brief history of corks, which were originally popularized in the 17th century.

Though the screw cap was initially used for spirits and liqueurs, Australian winemakers began experimenting with screw caps in the ‘70s in an effort to avoid TCA, or cork taint. The screw caps have since taken off worldwide and are even used for sparkling and age-worthy wines.

Tune in to learn more about the debate between corks and screw caps.

Listen Online

Listen on Apple Podcasts

Listen on Spotify

Or Check out the Conversation Here

Keith Beavers: My name is Keith Beavers and is cold soup considered a meal, or is it an appetizer? Or is it just a snack?

What’s going on, wine lovers? Welcome to Episode 26 of VinePair’s “Wine 101” podcast. My name is Keith Beavers, and I am the tastings director of VinePair. It’s Season 2, and how are you doing?

Screw caps. Corks. Or should I say screw caps versus corks? No, no, no, no, no, these are two different things. We are going to talk about the two of them and we’re going to get rid of some myths. We’re going to get into it.

I’m having a little bit of an issue on how to begin this episode because with the amount of time I’ve been in the wine industry, I was a witness to not the introduction of the screw cap, but the implementation and the evolution of its technology and its acceptance in wine culture. I don’t know where you are in your wine journey, but you could say, “Keith, I remember that. That was tough. We’ve come a long way.” Or you could say, “What’s the problem? I drink wine with a screw cap all the time. What happened?”

Well, let me tell you the story of these two wine closures, because that’s really what they are, wine bottle closures. We’ll get a sense of where we’re at with the debate because if you don’t know, it was a debate. It’s still going on, but kinda not. Let’s get into it.

A cork for wine is a small piece of bark, basically, from a tree. That tree is part of the oak family — the same family that makes barrels, just a different species. The thing about this particular species of oak is that it has a very finicky environmental preference, if you will. It grows best in sandy soils free of any chalk. It prefers an annual rainfall between 15 and 30 inches, and it would really like temperatures never to fall below 23 degrees Fahrenheit. We would like to have our elevation between 300 and 1,000 feet above sea level, thank you very much.

With those nature demands, man, the oak tree for cork oak really can only thrive in the western Mediterranean. Even there, specifically in Portugal, parts of Spain, and maybe North Africa — but it’s really centered in Portugal, specifically in the Alentejo region, which we talked about in the Portugal episode. Here, they have almost 2 million acres of cork trees, which represents about 34 percent of the world’s cork trees. That’s a lot, and they also produce half of the world’s corks. Wow.

When these trees turn 25, they are ready to yield commercially useful cork for the industry. Every nine years in the summer — this is according to Portuguese law — a cork tree is stripped of its bark. A hectare is a little over three, almost three and a half acres. The average hectare of a cork forest can yield 500 pounds of cork. It’s all science, but this particular cork is special because it has a specific cell structure that brings the corking material to life.

What they do is they take this cork and they actually boil it for, I think, 90 minutes to make it flexible, but also to kill a bunch of molds and bacterias. The wood is then rested, sorted, and cut into the corks, and then those corks are polished on each end. At this point, they used to bleach the corks to sanitize them, but recently, they found that bleach or chlorine can actually increase the likelihood of TCA being formed in the cork, which we talked about in the Wine Faults episode.

Actually, today it’s more common to use hydrogen peroxide, which I think we all know is used for cuts and bruises. Then, they’re graded for aesthetic, basically, for the visual quality of the cork. The more natural markings on the cork, the lower the grade. The fewer the markings, the higher the grade. Here is where if the cork needs to be branded for a winery, it’s done. Then, the cork is coated with a silicon film to help make it easier to get out of the bottle. They’re then put into bags dosed with wine’s protector, S02 as an antibacterial agent, and they need to be stored in an odor-free environment with a temperature not going above 68 degrees F and for the humidity to not exceed 70 percent. Just like the shock of S02, these conditions are helping to prevent the formation of TCA. They really don’t want this stuff to form.

Corks range between 1 and 2.3 inches. The longer corks are meant for bottles that are going to age for a long time, which makes sense. They’re going to hold up for a longer period of time. For well over two centuries, this has been the primary closure for wine bottles. It’s been around much longer than that. There is evidence that the ancient Greeks and Egyptians both used not only amphora for closures onto the amphoras vessels, but they also used large cork covered with pitch to actually close those amphora vessels. Yet, it was in the 17th century where if you look at some of the art back then, you can see that wine was basically still stored and served in barrels.

However, also in the 17th century was the innovation of glass. As glass became more popular, glass decanters became popular as somewhere to put your wine in. Then, of course, there were stoppers for those decanters so it would not oxidize or flies wouldn’t get in. They were glass stoppers that were formed to fit specific decanters, and then they were threaded. Also, in this century it was realized how expensive glass was, so the use of cork became more common.

The thing is, during the Middle Ages, cork wasn’t really used that much because the Moors had control and conquered the land where cork trees were and they didn’t drink wine. This was a comeback. The cork came back in the 17th century to become one of the primary closures of wine bottles, but this was before the corkscrew was invented. What would happen is corks would be put halfway into bottles so you could get them out. Of course, then the corkscrew was invented, and everything changed.

So, cork is popular. It’s the No. 1 way to close your wine bottles. There is this running thought that the cork is porous. Therefore, the small amounts of oxygen and gas exchange that happens between the outside and inside of that bottle help a wine age. There is a debate there, and we’re going to get into it in a second, because as modern technology became more available, there was a heightened awareness to the extent to which how many wines were actually corked at any given time. It was a little bit alarming. Also, there is more communication in modern times, so there was more understanding of bottle variability, but the big deal was TCA, cork taint. That was the enemy.

As Jancis Robinson puts it in the “Oxford Wine Companion,” it’s because of cork that we actually do age wine today. It was the thing that allowed us to do that, even though it has issues. If it wasn’t for the cork in its natural state, we wouldn’t actually have wines that evolve. If you were worried about cork taint and you wanted to create a different closure for wine, you would have to check all the boxes that you liked for cork. The seal would have to be reliable. The substance would have to be inert in that if the wine came into contact with it, no crazy reactions would happen. The ergonomics would have to be sound. Easy to open, easy to close. Easy to insert and put back in. It would also be nice if it was relatively inexpensive to produce. And of course, the big deal, it can’t have the ability to form TCA.

In the late ’50s, there was a French company that had a screw cap called the Stelcap Vin. It was used primarily as a closure for spirits. Always forward-thinking, the Australians. In 1973, a company called Australian Consolidated Industries bought the rights to this specific closure. They were worried about cork taint, so they renamed it the Stelvin cap, and they began to experiment with this new technology.

A screw cap is basically two components. It’s an aluminum alloy, metal cap attached to a sleeve. The second component, which is a very important component, is the plastic wadding on the inside of the cap. This is called the liner. It usually contains a layer of tinfoil that acts as a barrier for gas exchange. This is the thing that doesn’t allow oxygen to get into the wine. Over the tinfoil is a layer of thermoplastic and this is the inert surface the wine can interact with.

As we learned in the Sulfites episode, aluminum and wine interaction can get a little stinky. In the early ‘70s, Australian Consolidated Industries experimented with this thing called the Stelvin cap. In 1976, they published the results of their study. What they showed was that the screw cap is actually ideal for sealing wine bottles if the wadding material is satisfactory. They had four reds and four whites with a screw cap, one with a cork for comparison. Each screw cap had a different wadding in it, so they were just trying to figure out how it would work. It came to the conclusion that when the wadding is right, the wine is sound. Of course, this was very exciting so Australia was going to focus on corks.

They started moving towards this as being the standard closure for their wines. There was a big push for it, but it didn’t work because TCA still wasn’t fully understood and there wasn’t much consumer acceptance because people liked the romance of a cork. There were people in the industry asking, “Wait, corks help wine age. Why would you put a screw cap?” It wasn’t really until 2000, when a group of winemakers in the Clare Valley of Australia, known for its Riesling, had enough.

Their wines are very susceptible to the lack of aromas that cork taint produces. They got together and produced a vintage, but with a screw cap. The problem was those bottles and those caps are not available in Australia yet, so they actually had to get everyone together and buy 250,000 bottles from a company in France. They made a big to-do about this. It made headlines, and everything gained momentum. I actually read that six years later, some of those wines were uncapped or unscrewed, if you will, and they’re aging just fine. This actually prompted the island a few thousand miles away, New Zealand, to create the New Zealand Screw Cap initiative in 2001.

By 2004, around 70 percent of the wines in New Zealand were under screw cap — up from only 1 percent three years before. Something’s working. By 2014, 95 percent, and 80 percent in Australia. An entire country is primarily under screw cap with their wines — and the wines are good, or sound, I should say. There’s no cork taint, and the screw cap isn’t just like screwed onto the bottle after it’s filled, the sleeve is held down tight on top of the bottle of the machine. Then, these pressurized rollers come and they mold the sleeve or the cap to the ridges on the outside or the top portion of the bottleneck where the little threading is.

The cap itself is still attached to the sleeve, but with those little perforated bridges. When you open it up and it cracks and the wad releases, you hear a little pop, and oxygen rushes into the bottle. Now, the thing is chemistry and the aging of wine is still somewhat of a mystery. I find this so awesome. I mean, it’s frustrating, but you cannot do a scientific experiment with a compromised subject. This means that the second you either penetrate a cork or open a bottle of wine or even put a syringe down into the cork, oxygen is affecting the wine. The only way to really know how wine ages is to age the wine. Isn’t that crazy?

There’s a debate about screw caps versus cork and how wines age. This is a discussion that’s going to be going on for quite some time, until somebody figures it out. According to the “Oxford Wine Companion,” science tends to lean towards the idea that wine is always in a reductive state because it needs the absence of oxygen to reduce — which basically means to evolve. Others believe the porous nature of the cork allows for tiny amounts of oxygen, which I mentioned before, to allow the minor oxidation of wine, and that ages the wine. Both of these things could be true.

Actually, if you take the thin tin foil layer out of a screw cap during production, that actually allows for gas exchange very similar to a cork. Now, what’s frustrating and beautiful about wine is we may not know for some years until we taste wines that have aged how they do compare them both. Either way, though, today the screw cap is the No. 1 alternative to the cork. It has a reliable seal. It has an inert substance. It’s easy to remove and insert. And it’s a pretty relatively low cost closure. Think of a cork as a dollar. A screw cap is 70 cents. The only big cost would be smaller wineries that don’t often have the ability to buy the components that add on to the bottling systems, and they have to pay. In the end, it’s less expensive. There are other corks out there, synthetic corks and plastic corks. There is something called agglomerated cork, which is a bunch of cork pieces and dust glued together that was invented in the United States. There are glass corks. Again, these are glass closures they actually have a little suction cup around them. They can be fragile and expensive.

Honestly, a screw cap is a way to go if you’re not doing cork. It was such a big deal. There is a pretty famous winemaker in the United States named Randall Grahm who has a winery called Bonny Doon. I don’t remember the year — maybe 1999 — but he actually had a funeral for the cork. He took his entire line of wines, got rid of the cork, and only uses, to this day, a screw cap. It was a big to-do. He did a funeral procession down 5th Avenue in Manhattan. It’s crazy.

I don’t know where everybody’s at with their mind and screw caps, but the thing to really know is that they both do the thing. Cork is a good closure. Screw caps are good closures. Scientifically and technologically, they’re great. The only thing is, cork has this thing called TCA that can form and just straight-up ruin a wine. The only way that a screw cap wine can be ruined is not with TCA, but if the bottling system is not sanitary. For example, if there’s anything on the lip of the glass bottle before the sleeve goes down, you’re compromising the wine, so it has to be very clean.

Today, there are screw caps that are used for sparkling wine. I’ve had them, and it’s awesome. It’s not necessarily for Champagne. I don’t know if it’s a pressure thing, but I’ve had Prosecco under the screw cap. It’s just cool. It doesn’t come down to which one is better than the other, like screw cap versus cork. Each one has its benefits. Some winemakers, like Randall Grahm, are just going all-in on the screw caps. Some winemakers use screw caps for their entry-level wines and reserve corks for their age-worthy wines. Some winemakers are aging wine under screw cap. Some winemakers are doing both.

These humans that make this stuff called wine every decade and every generation, something changes and they figure something else out. The screw cap is just one of them. I mean, the screw cap was meant for spirits and liqueur. Now, it’s the No. 1 closure for wine. It’s just part of the evolution of what we understand in wine. We’re just going to keep on evolving. We are going to keep on understanding, and it’s going to get better and better.

@VinePairKeith is my Insta. Rate and review this podcast wherever you get your podcast from. It really helps get the word out there. And now for some totally awesome credits.

“Wine 101” was produced, recorded, and edited by yours truly, Keith Beavers, at the VinePair headquarters in New York City. I want to give a big ol’ shout-out to co-founders Adam Teeter and Josh Malin for creating VinePair. And I mean, a big shout-out to Danielle Grinberg, the art director of VinePair, for creating the most awesome logo for this podcast. Also, Darbi Cicci for the theme song. Listen to this. And I want to thank the entire VinePair staff for helping me learn something new every day. See you next week.

Ed. note: This episode has been edited for length and clarity.

The article Wine 101: Cap vs. Cork appeared first on VinePair.

Via https://vinepair.com/articles/wine-101-cap-vs-cork/

source https://vinology1.weebly.com/blog/wine-101-cap-vs-cork

0 notes