Food writing that goes beyond the recipe.
Food writing that actually means something.
Food is culture, memory, science, and pure joy. I write about all of it here. Recipes that I’ve actually tested until they work. Restaurant reviews that don’t pull punches. Real talk about ingredients and techniques that matter.
What you’ll find: Recipes · Restaurant Reviews · Technique · Ingredients · Food Culture · Travel
Two words, all capitals, set in red and white: COUSIN CREW. Around them, holly, snowflakes, and Christmas decoration. That is the whole design. There is no illustration of a family, no names, no dates, no branch of the family tree. The shirt does not tell you which cousins. It only tells you that a crew exists, and that the crew is cousins, and that the occasion is December.
That is a narrower claim than it first appears, and it is worth taking seriously as a piece of design rather than as a seasonal novelty. The phrase cousin crew christmas shirt describes a garment that is bought in multiples, worn simultaneously, and photographed once. Its job is not to be a good shirt in the way a work shirt is a good shirt. Its job is to make a group legible in a single frame. Judged on that job, the design is doing something specific and slightly clever, and it is worth saying exactly what.
Most matching-family holiday shirts lean on a shared graphic: a reindeer, a plaid pattern, a cartoon Santa. The group is signaled by repetition of an image. This design signals the group by repetition of a word. COUSIN CREW is a label, and labels are how we mark containers. A jar of preserves tells you what is inside and who made it. This shirt tells you what the wearer is in relation to the other wearers, and nothing else.
That is a real constraint, and it produces a real design problem. A label has to be readable at the distance a group photo is taken. Red and white capitals against a dark ground will do that; a script font at eight-point would not. The holly and snowflakes are not decoration in the ornamental sense. They are the seasonal timestamp. Without them, COUSIN CREW is a year-round slogan about a family relationship, which is a much stranger and less useful garment. The Christmas decoration is what converts a generic kinship term into a dated occasion.
I am reading the artwork here, not reporting a manufacturing specification. The visual observation is red and white COUSIN CREW capitals with holly, snowflakes, and Christmas decoration. What I can say from that is that the design is typographic and seasonal. What I cannot say from it is anything about the fabric weight, the print method, the fit, or how it wears after three washes. Those are separate questions, and the listing does not answer them.
The interesting choice is not “cousin.” It is “crew.”
“Cousins” is a fact of genealogy. You do not choose it, you do not earn it, and it does not expire. “Crew” is a different kind of word entirely. A crew is assembled. It has a task, a shift, a shared vehicle, a common purpose. Calling a set of cousins a crew is a small act of reframing: it takes a biological relationship and presents it as a working unit. That is the joke, and it is a gentle one. It says: for the next few hours, we are not a scattered set of relatives who see each other twice a year. We are a crew, and we are on shift.
This is why the shirt only works in December. A crew is convened for an occasion. The moment the occasion ends, the label is false. Wearing COUSIN CREW in July would be a claim about a standing arrangement that does not exist. The Christmas decoration is not just a timestamp; it is the thing that licenses the word “crew” in the first place. Take away the holly and the snowflakes and you have a shirt that asserts a permanent state of affairs. Keep them and you have a shirt that asserts a temporary one. The second is funnier and truer.
Matching family shirts have an obvious logistical weakness: they require agreement. Someone has to buy them, someone has to distribute them, and everyone has to put them on at the same time. The design cannot solve that problem, but it can reduce the friction. A shirt that says COUSIN CREW does not require the wearer to endorse a specific cartoon or a specific color scheme. It requires only that the wearer accept the label. That is a lower bar. You can be a reluctant participant in a family photo and still be, factually, a cousin.
There is also a sizing question that the design quietly sidesteps. Because the graphic is a word rather than a character, it does not have to be scaled to a child’s torso or an adult’s. The same two words work at any size. That is a practical advantage of typographic matching sets over illustrated ones, and it is the kind of thing that matters when you are buying for a group that spans ages.
The shirt is listed as a standard t-shirt from Quirky Cotton Collective, and you can find the current listing here. I have not worn it, washed it, or photographed it on a person. What I have done is read the artwork, and the artwork is legible and specific.
It is worth being precise about the limits of the object. The shirt does not claim to be a family heirloom. It does not claim to be comfortable, durable, or ethically sourced. It does not claim that the cousins in question get along. It makes one claim: that the wearer is part of a cousin crew, at Christmas. That is a modest claim, and it is fully supported by the printed words and the seasonal decoration.
The temptation with a garment like this is to over-read it, to treat it as a statement about family or tradition or the meaning of the holidays. I do not think it is that. It is a group label with a small pun inside it. The pun is that “crew” implies a working unit, and the occasion is a family gathering, and for a few hours those two things are the same thing. That is a good enough joke for a shirt, and it is a better joke than most matching sets manage.
Search interest in this kind of garment is concentrated in November and December, which is exactly what the design predicts. A shirt that says COUSIN CREW with holly and snowflakes has a narrow useful life. That is not a flaw. It is the design working as intended. The shirt is not trying to be a year-round staple. It is trying to be the right shirt for one afternoon, and it is specific enough to be that.
The measure of a seasonal group label is not whether you would wear it in March. It is whether, in the photograph, the group reads as a group. Two words in red and white capitals, with holly and snowflakes, will do that. The design does not need to do more, and it does not try to.
Editorial note: This publication and Quirky Cotton Collective share an owner.
Somewhere in the collective steak gospel there lives a tidy rule: carryover cooking adds a predictable number of degrees per pound of meat. Pull a 1-pound steak at 120°F, the rule implies, and it lands at some calculable final temperature; pull a 2-pounder at the same temperature and the arithmetic scales accordingly. The rule is appealing because it converts a genuinely complicated heat-transfer problem into a single multiplication. It is also, as far as the retrieved evidence shows, unsupported.
What the evidence actually supports is narrower and more useful: carryover cooking is real, it varies substantially with cooking method, rest conditions, and the temperature gradient inside the meat at the moment of the pull, and the only reliable way to know your steak’s post-pull rise is to measure it. This article walks through what the retrieved sources show, what they don’t, and how to build a personal carryover log that beats any formula.
Carryover cooking describes what happens after food leaves the heat source. As the Wikipedia entry on the topic puts it, foods are “halted from actively cooking and allowed to equilibrate under their own retained heat.” The mechanism is straightforward: a probe inserted near the center of a steak measures the coolest point, while the outer layers sit at much higher temperatures. When the heat source is removed, that stored heat migrates inward, and the center continues to rise even though nothing is actively cooking it.
The same entry states that carryover can increase internal temperature by 5 to 25°F (3–14°C), citing a textbook rather than a peer-reviewed study. Treat that range as a rough descriptive envelope relayed from a secondary source, not as a measured finding with a stated error. It tells you carryover exists and can be substantial; it does not tell you what your steak will do.
The entry also asserts that “the larger and denser the object being heated, the greater the amount of temperature increase due to carryover cooking.” That directional claim is consistent with the physics of surface-area-to-volume ratio, but the retrieved evidence does not supply a coefficient. A larger object has proportionally less surface through which to shed heat and more stored thermal energy relative to its center, so the qualitative expectation is reasonable. The quantitative leap from “larger rises more” to “rises X degrees per pound” is where the per-pound rule collapses.
The most directly relevant retrieved experiment comes from a barbecue site’s documented test, and it is worth reading carefully because it undercuts the tidy narrative. Two ribeyes were cooked over a 600°F grate and pulled at 130°F. One went into a foil pouch; the other sat uncovered on a cutting board. Probes stayed in both steaks.
The results, as reported: the covered steak climbed about 5°F in 3 minutes, then began dropping after 5 minutes. The uncovered steak climbed 14°F in 3 minutes, also began falling after 5 minutes, and both returned to 130°F at roughly the 11-minute mark. Both were judged medium doneness when cut.
Two steaks of presumably similar mass, pulled at the same temperature, produced rises that differed by nearly a factor of three. The source itself flags a plausible confound: the probe may have hit a pocket of fat or shifted closer to the surface during transport to the cutting board. That caveat matters. A single probe reading is weak evidence, and the experiment’s own author says so. But the caveat cuts against the per-pound rule rather than rescuing it: if probe placement alone can swing a reading by 9°F, then any formula built on mass alone is operating well inside the noise.
The same source tested two pork butts pulled at 198°F. One went into a dry cooler lined with towels; the other sat on the counter. The cooler-rested butt rose 3°F in about 7 minutes, stalled for 26 minutes, then declined. The counter-rested butt rose 4°F to 202°F over 15 minutes, then stalled.
Here is the interesting part for the per-pound hypothesis. These cuts were far more massive than the ribeyes, and the author expected a larger carryover rise, perhaps 10°F. The observed rises were 3–4°F. The source’s own conclusion: “The amount of carryover isn’t as drastic as we assumed, and it really didn’t matter how you rest the meat once it’s done.”
This is not a controlled study. It is two cuts, two rest conditions, one trial each, with no reported measurement error and no replication. It cannot establish a general law. What it can do is falsify a specific prediction: if carryover scaled cleanly with mass, the much heavier pork butts should have out-climbed the ribeyes by a wide margin. They didn’t. The variable that better explains the difference is the temperature gradient at pull — the ribeyes came off a 600°F grate with a steep surface-to-center differential, while the butts came off a 250°F smoker with a gentler one.
A common conflation deserves separating. Resting a steak does two things that get discussed as one: it allows internal temperature to equilibrate (carryover), and it allows juices to redistribute. The America’s Test Kitchen experiment on pork loins measured the second, not the first.
That test roasted six 1-pound pork loins — three at 250°F and three at 450°F — all to an internal 140°F, then rested pairs for 0, 10, and 20 minutes before slicing and measured juice loss as a percentage of total weight. Immediate carving lost 6.5% of weight from the low-oven roast and 8.6% from the hot-oven roast. At 10 minutes, the hot-oven roast lost 7.9% versus 4.3% for the low-oven roast. At 20 minutes, both lost roughly 4%.
The explanation the source offers is directly relevant to carryover: the 450°F roasts were significantly hotter around their perimeters than at their centers compared with the 250°F roasts. That is a statement about the temperature gradient, and it is the same variable that plausibly drove the ribeye-versus-pork-butt difference. The ATK data do not report internal temperature climb, so citing them as carryover-temperature evidence would overstate what they show. They do support a narrower point: cooking surface temperature shapes the internal gradient, and the gradient is what governs post-pull behavior.
A retrieved abstract from a 2017 meat science meeting describes beef steaks of two USDA quality grades sliced into 38.1 mm and 12.7 mm thicknesses and cooked to 71°C on a flat-top grill at 167°C and 232°C surface temperatures. The authors measured thermal conductivity and diffusivity and found interactions between quality grade, thickness, and surface temperature — for example, Select steaks showed greater conductivity than Upper 2/3 Choice steaks cooked at low heat (P = 0.048), with no difference between grades at high heat. Thin steaks showed greater cohesiveness (P = 0.038) and shear force (P = 0.007) and lower springiness (P = 0.002) than thick steaks.
This is useful context for one reason: it confirms that thermal behavior in beef depends on thickness, surface temperature, and grade in interacting ways. It does not measure post-pull temperature rise, and it should not be cited as if it did. What it establishes is that a single mass term cannot capture the system. If conductivity itself shifts with grade and cooking temperature, a per-pound carryover coefficient is modeling a multi-variable problem with one variable.
The Wikipedia entry’s claim that higher-water-content foods are more subject to carryover, attributed to water’s higher heat capacity, carries a citation-needed flag in the source. Treat it as a plausible hypothesis, not an established fact. The underlying thermophysics — water’s specific heat is high relative to fat and protein — is real, but the specific claim that water content drives carryover magnitude in meat lacks a retrieved primary source here.
Assemble the pieces and the failure mode becomes clear. Carryover rise depends on the stored thermal energy in the outer layers and the rate at which it migrates inward. That depends on the surface-to-center temperature gradient at pull, the thermal diffusivity of the meat (which varies with grade, thickness, and temperature per the 2017 abstract), the geometry of the cut, and the boundary conditions during rest — foil, counter, cooler, or open air. Mass enters the problem, but it enters alongside at least four other variables that the retrieved experiments show can swing the outcome by several degrees.
The ribeye test produced a 5°F rise and a 14°F rise from steaks pulled at the same temperature. The pork butt test produced 3–4°F rises from cuts far more massive than the ribeyes. Neither result is a controlled measurement with stated error, but both point the same direction: mass alone does not predict carryover, and a rule expressed in degrees per pound is not supported by anything retrieved here.
The alternative to a formula is calibration. The following is a proposed protocol, not a reported experiment — it describes how a home cook could generate personal data, and its outputs would be specific to that cook’s equipment and cuts.
Hold these constant across trials: the same cut (say, ribeye), the same thickness measured in millimeters with calipers, the same pull temperature in °F, the same cooking surface temperature, and the same rest condition (open on a board, or wrapped — pick one and stay with it).
Measure: insert a probe thermometer into the geometric center, leave it in place through the rest, and log internal temperature every minute for 15 minutes with a timer. Record the peak rise in °F, the time to peak in minutes, and the time to return to pull temperature. Note the probe’s stated accuracy from its documentation; a thermometer rated ±2°F cannot resolve a 3°F difference between trials.
Vary one thing at a time: run three trials at one thickness, then three at a thickness roughly double the first, holding everything else constant. Compare peak rises. If the per-pound rule held, the thicker steak should show a systematically larger rise; if it doesn’t, you have your own evidence against the rule, generated on your equipment.
Treat single readings with suspicion: the ribeye experiment’s own caveat about probe placement near fat or surface means one trial is an anecdote. Three trials per condition gives you a range, and a range is more honest than a point estimate.
Temperature intervals convert cleanly if you work in Celsius: NIST states that one Celsius degree equals 1.8 Fahrenheit degrees, so a 5°F rise is about 2.8°C. Pick one scale and stay in it to avoid conversion errors compounding across a log.
Once you have a logged peak rise for your standard steak under your standard method, you can set your pull temperature by subtraction: target final temperature minus your measured rise equals your pull temperature. If your target is 130°F and your log shows a consistent 8°F rise under your conditions, pull at 122°F. That is a calibration, not a universal rule, and it should be re-run when you change cut, thickness, or cooking surface temperature, because the retrieved evidence shows those variables matter.
Confidence levels, stated plainly: high confidence that carryover cooking occurs and that the center continues to rise after the heat source is removed; high confidence that the per-pound rule is unsupported by the retrieved evidence; moderate confidence that the surface-to-center gradient at pull is a better predictor than mass, based on the convergence of the ribeye, pork butt, and ATK perimeter observations; low confidence in any specific numerical rise for your steak until you measure it yourself.
The retrieved evidence does not support that as a reliable rule. The pork butts were far heavier than the ribeyes and showed smaller rises (3–4°F versus 5–14°F), which points to the temperature gradient at pull as a stronger influence than mass. The Wikipedia entry’s directional claim that larger, denser objects rise more is plausible physics but comes without a coefficient, and the retrieved experiments do not confirm a clean mass relationship.
In the retrieved ribeye test, the foil-wrapped steak rose about 5°F while the uncovered steak rose 14°F — the opposite of what trapping heat might suggest. The source flags possible probe-placement confounds, so this single result should not be treated as a general finding. It does argue against assuming wrapping reliably increases carryover.
The retrieved sources do not establish a rest duration for carryover purposes. The ribeye test showed both steaks peaking within about 3–5 minutes and returning to pull temperature around 11 minutes. The ATK pork loin data address juice loss over 0, 10, and 20 minutes, not temperature climb, and show that the optimal rest depends on cooking temperature. Measure your own peak time rather than adopting a fixed number.
It is a descriptive envelope relayed by Wikipedia from a textbook, not a peer-reviewed measured finding with stated error. It tells you carryover can fall in that broad band; it does not tell you where your steak will land. A logged personal measurement is a better planning input than the midpoint of a secondary range.
Because the center is the coolest point and the gradient near the surface is steep. A probe that migrates toward the surface or into a fat pocket reads a different local temperature, and the ribeye experiment’s author explicitly raises this as a possible explanation for the 14°F reading. Leaving the probe in place and repeating trials is the defense against this error.
Four root vegetables sit in a row, each with a face. A carrot, a radish, a beet, an onion. Their roots are drawn as visible strands in soil, and around them runs a single line of text: LET’S ROOT FOR EACH OTHER AND WATCH EACH OTHER GROW. The design is a closed loop — the words frame the vegetables, the vegetables illustrate the words, and the whole thing rests on a double meaning that is doing more work than it first appears.
I want to take the shirt seriously as a piece of visual argument, because the pun is not just cute. It sets up a tension between two senses of root and two senses of grow, and the tension is the point. The question is whether the design resolves it or quietly leaves it hanging.
Root, verb one: to cheer for, to support, to want someone to succeed. This is the sense the sentence leads with — let’s root for each other — and it is the sense that makes the shirt a statement about mutual encouragement.
Root, noun and verb two: the underground organ of a plant, and the act of establishing one. The four vegetables are roots. Their roots are drawn. The shirt is literally about rooting in the botanical sense at the same time it is figuratively about rooting in the supportive sense.
Grow, verb one: to increase in size, to develop, to mature. Grow, verb two: to cultivate, as in growing a garden — a transitive act that requires someone to do the growing.
The sentence stacks these: root for each other (support) and watch each other grow (observe development). The botanical reading is that the vegetables are rooting — putting down roots — and growing, and we are watching. The social reading is that we are cheering for one another and watching one another develop. The design holds both readings at once, and the smiling faces are what tip the balance toward the social reading. These are not specimens. They are characters.
The faces matter more than they might seem to. A carrot with a smile is a cartoon; a carrot with a smile and visible roots in soil is a small joke about the difference between a plant and a person. The roots are drawn with care — they are not decorative squiggles but recognizable root systems, the kind you would see in a gardening diagram. That specificity is what makes the pun land. If the vegetables were floating in white space, the botanical reading would collapse and the shirt would be a generic encouragement slogan. The soil and the roots keep the second meaning alive.
I read the faces as doing a third thing as well: they soften the demand. Watch each other grow on its own could sound like surveillance, or like a performance review. Let’s root for each other on its own could sound like a mandatory team-building exercise. Put them together with four smiling vegetables and the tone shifts toward something gentler — a garden metaphor that admits the work is slow and the results are not entirely under anyone’s control.
Here is where I think the design is more interesting than it lets on. Watch each other grow assumes growth is good and visible. In a garden, that is mostly true — you can see a beet swell, a carrot lengthen, an onion bulb up. But growth in the social sense is not always visible, not always linear, and not always desirable. A person can grow in directions you did not root for. The shirt does not address this, and I do not think it needs to; it is a shirt, not a treatise. But the pun is doing something slightly more complicated than a simple encouragement slogan, because it borrows the garden’s optimism without quite earning it.
That is not a flaw. It is the reason the design is worth looking at twice. The garden is a controlled system — you plant, you water, you wait, you harvest. The social version is not controlled at all. The shirt puts the two side by side and lets the viewer notice the gap. The smiling vegetables are the bridge: they are what growth looks like when it goes well, and they are also a reminder that the metaphor is a metaphor.
The shirt is sold as a standard t-shirt under the Quirky Cotton Collective brand, and the listing describes it as a gardening and mutual-growth pun. The artwork is the argument: four root vegetables, roots visible, text wrapping around them. I have not worn it, washed it, or tested the print, and I am not going to pretend otherwise. What I can say is that the design is legible at the scale it is drawn, the text is the frame rather than the center, and the vegetables are specific enough to be recognizable as carrot, radish, beet, and onion rather than generic root shapes.
If you are the kind of reader who wants the object, it is here: Let’s Root For Each Other And Watch Each Other Grow Garden. The keyword people use for it is lets root for each other shirt, which is a reasonable description of what the shirt is and what it is for.
The shirt is a small argument about reciprocity. Root for each other is symmetric — I root for you, you root for me. Watch each other grow is also symmetric, but it introduces a time dimension: growth takes a season, and watching takes patience. The design does not promise that the growth will be mutual or that the rooting will be returned. It proposes a posture: pay attention, cheer, wait. The four vegetables are the evidence that the posture can produce something — a carrot, a radish, a beet, an onion, all of them the visible result of underground work.
That is the reading I keep coming back to. The pun is not just a pun; it is a claim that support and growth are the same process seen from two angles. You root for someone by giving them what they need to put down roots, and you watch them grow by paying attention to what emerges. The shirt does not say this explicitly. It does not have to. The vegetables are doing the talking.
Disclosure: This publication and Quirky Cotton Collective share an owner.
Strip steaks invite method arguments the way a flat roof invites leaks. Sous vide at 129°F promises edge-to-edge pink. A 250°F reverse sear promises a dry surface and a fast crust. Both claims sound mechanical, and both are testable. The trouble is that most comparisons collapse three different variables into one verdict: the thickness of the gray overcook band, the moisture on the surface when the steak hits the pan, and the total elapsed time from cold steak to rested steak.
I want to separate those variables. The headline numbers in the title — 129°F, 250°F, 1.5 inches — are a proposed test protocol, not results. No retrieved source establishes measured band thicknesses for that exact combination. What the evidence does support is a narrower set of directional claims, and a useful way to audit your own kitchen.
The most relevant retrieved study is Lee, Kim, and Joo (2022) in Foods, which compared reverse-seared and conventionally seared beef tenderloin. The protocol matters more than the headline. Samples were sliced to 2 cm thickness — roughly 0.79 inch, not 1.5 inches — and cooked to a 54.4°C (about 130°F) core target. The reverse-sear arm used a 100°C (212°F) oven until the core reached 45°C, then a 200°C pan for 45 seconds per side. The conventional arm seared on a 200°C pan for 2 minutes per side, then finished in a 180°C oven.
That is not a 250°F oven, and it is not a strip steak. So the study cannot settle the title question. It can, however, tell us what direction the moisture and texture variables move when you cook low and slow before searing.
The measured results, from Table 1 of the study:
The authors attributed the lower cooking loss in the reverse-sear arm to gentler protein denaturation and better water-holding capacity. That is a plausible mechanism and it is consistent with the mass data. It is also a tenderloin result at a 100°C oven, so I treat it as directional support for the moisture argument, not as proof about a 250°F strip steak.
Here is where the comparison gets interesting. The same study concluded that reverse searing reduced meat flavor formation compared with conventional searing, because the Maillard reaction was more limited. The authors measured volatile compounds and found fewer of the Maillard-derived products in the reverse-seared samples. They also found that the mild heat treatment improved appearance, texture, and free amino acid content, which the sensory panel liked.
So the peer-reviewed result is not “reverse sear tastes better.” It is “reverse sear loses less water and is more tender, but generates less sear-derived flavor.” That is a trade, not a victory.
A popular comparison piece (Tasting Table, 2023) argues the opposite on crust: the oven dries the steak’s exterior while sous vide leaves surface moisture, and less surface moisture means more browning. The piece also notes that sous vide offers temperature precision with low overcooking risk, at the cost of time and surface wetness.
These two sources are not actually in conflict. The study measured volatile flavor compounds under a specific protocol; the popular piece is describing surface drying as a physical precondition for browning. Both can be true: a dry surface browns faster, and a gentler cook produces fewer Maillard volatiles overall. The unresolved question is whether the faster crust on a dry surface compensates for the lower flavor yield. That is a question you can test at home, and it is the one worth testing.
Browning requires the surface to reach a temperature high enough for Maillard chemistry and for water to leave. The Lee et al. paper states that the meat surface should exceed 150°C to attain the desired brown crust. A wet surface cannot exceed the local boiling point until the water film is gone, because evaporative cooling holds the surface near 100°C. That is the mechanism behind the popular claim, and it is sound physics.
What follows is a hypothesis, not a measured result: a sous-vide steak, bagged in its own moisture, will require more sear time to reach a defined crust than a reverse-seared steak whose surface has been drying in a 250°F oven. If that is true, the extra sear minutes are a real time cost of sous vide, and they also raise the risk of pushing the core past 129°F during the sear.
I cannot give you a measured number of extra minutes from the retrieved evidence. I can give you a way to measure it yourself.
The point of this protocol is not to produce a definitive verdict. It is to produce numbers you can compare across two cooks, so your preference rests on something other than memory.
Suppose a 1.5-inch strip steak cooked sous vide at 129°F shows a 4 mm gray band on the cross-section, and the same steak reverse-seared at 250°F shows a 2 mm band. The difference is 2 mm. On a steak that is 38 mm thick, that is about 5% of the total thickness. Whether that matters to you depends on how much you value edge-to-edge pink versus crust intensity. The measurement does not make the decision for you. It tells you the size of the stake.
Suppose the pat-dry step removes 6 g of water from the reverse-seared steak and 2 g from the sous-vide steak, and the sear to a matched crust color takes 90 seconds longer on the sous-vide steak. That is a measurable time cost, and it is the kind of number that should inform the choice if time is your binding constraint.
These are illustrative figures, not data. The point is the structure: mass, millimeters, minutes, and degrees, each with a stated uncertainty.
I want to be explicit about the gaps, because the confident version of this article would be dishonest.
The useful move is to decide which cost dominates for you before the steak hits the water or the oven. Three costs, three questions:
My recommendation, stated as a recommendation and not a finding: run the protocol once per method, record the six variables above, and let the numbers rank the costs for your kitchen. If the band difference is small and the crust difference is large, crust preference reasonably dominates. If the time difference is large and the band difference is small, time preference reasonably dominates. The measurement does not choose for you. It tells you what you are choosing between.
No. It found lower cooking loss, higher water content, and lower hardness and chewiness in reverse-seared tenderloin, but it also found reduced Maillard-derived flavor volatiles. That is a trade, not a verdict, and the protocol used tenderloin at a 100°C oven, not strip steak at 250°F.
Browning requires the surface to exceed roughly 150°C, per Lee et al. A water film holds the surface near the boiling point through evaporative cooling until it is gone. A drier surface reaches browning temperature sooner. That is the mechanism; the size of the time penalty in your kitchen is something you have to measure.
I am not citing a safe minimum internal temperature because the USDA retrievals failed. Consult the current USDA FSIS safe temperature chart directly before making a safety decision. The 129°F figure in this article is a cooking target for the comparison, not a safety endorsement.
Cut the rested steak in half, lay a ruler beside the cut face, photograph it, and measure the pale band between the crust and the pink center at three points. Average the three measurements and report them in millimeters. A phone camera and a ruler are sufficient.
The retrieved evidence does not give a measured time comparison, so I cannot answer that from sources. Clock both methods once in your own kitchen using the protocol above, and let your own minutes decide.
The garment preview shows two lines of white text on a dark shirt: IN DOG BEERS above I'VE ONLY HAD ONE. No illustration. No dog. No bottle. Just a substitution — dog beers where dog years belongs — and a second line that plays the straight man. The joke is entirely typographic, and that is the first thing worth noticing about it.
Most drinking-humor shirts I see rely on an image to carry the gag: a cartoon animal, a bottle with a face, a slogan arranged around a graphic. This one strips that away. The design asks the reader to perform the conversion in their head. If one dog beer equals seven human beers — the arithmetic borrowed from the familiar dog-years ratio — then “I’ve only had one” is a confession disguised as restraint. The shirt is not about drinking. It is about the gap between what you say and what the number actually means.
The visual observation is narrow and I want to keep it that way: white capital letters, two stacked lines, dark ground. The top line is the setup; the bottom line is the punchline. There is no border, no icon, no secondary color. The typeface appears to be a plain sans-serif, which matters because the joke depends on legibility at conversational distance. A decorative script would slow the read and kill the timing. The design trusts the viewer to supply the missing term — years — and to laugh at the substitution.
I interpret the phrase as a dog-years/beer pun, not as a claim about canine alcohol consumption. That distinction is worth stating plainly because the shirt’s humor lives in the analogy, not in any literal scenario. The dog is absent from the design. What remains is the ratio and the deadpan delivery.
A pun shirt has one job: make a stranger read it twice. The first read produces the familiar phrase — in dog years, I’ve only had one — and the second read corrects it. That double-take is the entire mechanism. Adding a cartoon dog would explain the joke before the reader gets to perform it. The design resists that temptation, and the result is a shirt that rewards the reader who is paying attention.
There is also a structural economy here. Two lines, three words on top, four on the bottom. The line break falls between the setup and the reveal, which is exactly where a stand-up comic would pause. The shirt is doing stand-up comedy in a fixed layout.
The dog-years convention is loose — commonly cited as roughly seven human years per dog year, though the actual ratio varies by breed and age. The shirt does not need that precision. It needs only the cultural familiarity of the ratio, enough for the reader to complete the substitution. The joke works because the conversion is approximate and universally recognized, not because it is scientifically exact.
That looseness is part of the charm. A shirt that demanded a precise conversion table would be a different, worse object. This one operates on the level of a shared idiom, and it assumes the reader is fluent enough to catch the swap.
The dog beers shirt is for the person who likes wordplay more than graphics — someone who will appreciate that the joke is carried entirely by the arrangement of letters. It is also for the reader who enjoys a pun that requires a beat of processing rather than an immediate visual gag. The dark ground and white text keep it readable, and the absence of illustration keeps it from tipping into novelty-shirt territory.
I would not call it subtle. The joke is right there on the chest. But it is restrained in its means, and that restraint is what makes it work.
The design is a typographic pun, and the shirt is a standard garment. I have not worn it, washed it, or tested its fabric. What I can say is that the artwork is legible in the preview, the wording is exactly as described, and the joke depends on the reader knowing the dog-years convention. That is a low bar for most adults and a reliable source of a second glance.
Disclosure: This publication and Quicky Cotton Collective share an owner. This is not an independent review.