RefBan

Referral Banners

Wednesday, April 3, 2013

Former Friend of Michael Arrington Says He's Heard Abuse Allegations Before: 'It's Been The Worst Kept Rumor In The Valley for Years'

April 3rd, 2013Top Story

Former Friend of Michael Arrington Says He's Heard Abuse Allegations Before: 'It's Been The Worst Kept Rumor In The Valley for Years'

By Adrian Chen

Former Friend of Michael Arrington Says He's Heard Abuse Allegations Before: 'It's Been The Worst Kept Rumor In The Valley for Years' The Silicon Valley tech press has been largely silent on the serious allegations of rape and physical abuse leveled against TechCrunch founder Mike Arrington by his ex-girlfriend Jenn Allen. But a former friend of Arrington's, is now speaking out to say he believes Allen's story and has heard similar ones before.

This comes as Arrington's former business partner, the entrepreneur Jason Calacanis, said he'd heard the stories too. "Story after horrific story of unimaginable behavior were told to me in private," he wrote.

The tech blogger Loren Feldman, a former good friend of Arrington's, goes further in a video posted to YouTube today. "I think he did it," Feldman says. "Personally, I think he did it. I think he did all the things that woman spoke about." Feldman also airs the fact that rumors that Arrington has been abusive towards woman have swirled long since Jenn Allen took to Facebook.

"It's been the worst kept rumor in the valley for years," Feldman says. Feldman also claims he knows of other women who Arrington allegedly beat as well.

The fact is, among tech insiders, rumors that Arrington has been abusive towards women have circled for years. I personally know of two journalists who chased these rumors, to no avail. They ran into the same problem that is responsible for the silence of the tech blogosphere today: People are scared of Mike Arrington. He is an incredibly powerful player with an unpredictable mean streak and deep connections to most of the major tech media outlets. He's an investor in former TechCrunch editor Sarah Lacy's new start-up PandoDaily, and of course still a contributor at TechCrunch. Gabe Rivera launched tech news aggregator Techmeme, which functions as sort of the front page of the Silicon Valley and largely sets the pace of the news cycle, out of Arrington's home. Unsurprisingly, news of the Arrington allegations have been missing from all three.

Feldman, however, is a longtime character in the tech industry, known for speaking uncomfortable truths.

"The things he says are things that many would love to say but they have to live here," wrote the tech journalist Tom Foremski in 2010.

He's best known as a prickly blogger who earned a reputation as the "Court Jester" of Silicon Valley for his YouTube videos in which he parodied members of the tech elite through puppet performances. In the late 2000s, he became close with Arrington, who found his videos highly amusing. Here's a picture of the two together at a tech conference. Arrington even invited Feldman to film a series of Mike Arrington puppet videos in his home. Arrington considered Feldman a "good friend", until the two had a falling out in late 2009, which Feldman said was because of the rumors. (Feldman was also the center of a controversy himself when he made an offensive comedy video called "TechNigga" back in 2007.)

Arrington still has yet to weigh in on the allegations.

Number of comments

5 Cooking Mistakes We All Make, and How to Fix Them

April 3rd, 2013Top Story

5 Cooking Mistakes We All Make, and How to Fix Them

By Alan Henry

5 Cooking Mistakes We All Make, and How to Fix Them Cleaning your cast iron with soap and water? Squeezing every last bit of ground beef into that pan? Even if you know your way around the kitchen, there are a few mistakes nearly all of us make in the kitchen. Let's take a look at some common kitchen errors that may plague your cooking, and why they're bad for your food.

5 Cooking Mistakes We All Make, and How to Fix Them

You're Cleaning Cast Iron Pans with Soap and Water

The Problem: You've just finished dinner, and the cast iron pans you used to cook with are full of oil and stuck-on food. It's time to clean them, and you know cast iron pans require special treatment, but ain't nobody got time for that. You give them a quick scrub with a sponge and soapy water, rinse with hot water, and a dry them with a paper towel. You might think that a light scrub can't possibly hurt too much, but the moment that hot soapy water touched your pan, it started to destroy the "seasoning" on the pan, or the layer of fat and oil that's been cooked onto the iron itself over regular use. Photo by Ross Catrow.

It's that season that makes cooking with cast iron so great. Not only does it protect the iron of the pan from rust, it also provides a cooking surface that's non-stick, naturally oiling, and keeps your food from interacting with the oil of the pan. Some people even say the season imparts flavor. Here's the problem: since the season is all polymerized oil, hitting it with dish soap, and then scrubbing at it with a sponge and rinsing it with hot water causes those oils to break down and float away—taking that protective coating and washing it very literally down the drain. It may be easy, but it's destructive.

The Solution: Instead of using soap and water, try Alton Brown's method (seen in the video to the right). When you're finished cooking, pour a little oil into the pan (if there isn't any left from cooking), dump in a handful of kosher salt, and then just scrub the salt around the pan with an old rag or some wadded up paper towels. The salt will get dirty, and the pan will get clean. Dump out the salt, wipe the pan clean, and put it away. We've discussed this method before too, and it works brilliantly. This is the real beauty of cast iron: You don't actually have to wash it.

If your pan has started to lose its season, it's not too late: try re-seasoning your pan with flax seed oil (read here for more on why this method works), and toss it in the oven while you're baking to season and save time. Check our recent CrowdHacker guide for more tips.

You Thaw Meat at Room Temperature

5 Cooking Mistakes We All Make, and How to Fix Them The Problem: You need to figure out dinner tonight, but you forgot to pull something out of the freezer to thaw slowly in the fridge. You only have a few hours to thaw the steaks or chops you'll wind up cooking tonight, so you take them out of the fridge and put them right into the sink. Maybe you just leave them on the countertop—that'll thaw them out quickly, right? Perhaps, but you're risking your safety and the safety of your dinner guests in the process. Photo by Taryn.

Remember, the "danger zone" for bacterial growth in food is between 40°F and 140°F (5°C and 60°C), and sitting right in the middle of that is "room temperature," around 68°-70°F (20°-22°C). A couple of hours at room temperature will certainly make sure that the meat is thawed, but it's a field day for bacterial growth as well, especially as the deeper parts of your cut begin to come up to temp while the outsides have been room temperature for hours.

"But surely," you're asking, "It'll all come up to temp when I cook it, right?" Maybe, assuming you're sure to cook your meat until the core is minimum safe temperature for what you're making, but it's an incredible risk, and it doesn't take much E.Coli or Salmonella to make you really regret the way you thawed those porkchops or chicken thighs.

5 Cooking Mistakes We All Make, and How to Fix Them The Solution: Use a cold water bath to thaw your meats. It's fast, safe, and by far the easiest. It requires a little more attention than some other safe methods of quick-thawing, but it works the best. Just take your meat and put it in a sealed bag (if it's not already in one) and submerge it in a bowl of cold water. You'll need to change the water out every half-hour or so (so the water doesn't come to room temp and bacteria start growing) but I've found after a half-hour or so, the meat is thawed and ready to cook. Photo by Waifer X.

If you don't like that method, there are other ways to thaw meat quickly that are easy and safe. Both StillTasty and The USDA recommend one of three methods: In cold water like we described, in the fridge until the meat is properly thawed (since your fridge keeps food below the danger zone), and in the microwave (because some parts of the meat may be warmer than others or cook in the microwave when you do this, the USDA says you should cook the meat immediately after microwaving.) We've also mentioned a hot water method if you're in a hurry, but note: it only works with thin cuts of meat.

You're Overcrowding Your Pan, Baking Dish, Cookie Sheet, Etc.

5 Cooking Mistakes We All Make, and How to Fix Them The Problem: If you've ever baked cookies only to have them all stuck to one another, or sauteed meat or veggies in a pan only to have them take forever to cook through, the problem may be that you're overcrowding your pan. Perfect example: you're cooking up a batch of ground beef or turkey in the pan, and while everything seems great at first, over time the meat starts to get kind of gray and bubbly, releasing a ton of moisture that takes forever to cook away. Your meat isn't getting the delicious brown you'd hoped for. Sound familiar? You should have cooked it in batches. Photo by ilovebutter.

The same problem occurs in baking. If you've ever put meat in the oven only to take it out while it's swimming in its own bubbling juices, or baked french fries or veggies without making sure they're spread out evenly, you know what I'm talking about. Thankfully, it's an easy problem to fix.

The Solution: Separate your cooking into batches. It's simple, but that's all it takes. Resist the urge to try and get everything done in one go. Overcrowding your pan actually slows down the cooking process. If you're satueeing veggies, all of the moisture released as they cook stays in the pan and steams them, which gives you a mushy, wet mess, instead of the crisp, firm texture you're looking for.

With meat, large, cold cuts rob the pan of heat every time you put one in, so overcrowding the pan actually lowers the temperature of the whole cooking surface. This increases the overall cooking time, and in the worst case brings the temperature of the pan down below the threshold required for the Maillard reaction to take place (approx 300°F/150°C). Even worse, the pan may linger above the boiling point of water (212°F/100°C), which means you're essentially steaming your meat, and that's no good. Give your food plenty of room to move around in the pan, and let them cook in a single layer.

You're Cooking at the Wrong Temperature

5 Cooking Mistakes We All Make, and How to Fix Them The Problem: Speaking of cooking temperatures, even the most seasoned home cook can catch themselves cooking either entirely too hot or too cold. Usually this applies to on-stove cooking, so sauteing, frying, and stir-frying are the big problems. Here are the symptoms:

  • When you're cooking too hot: You tossed those chicken breasts into a pan, and while the outside is cooked well, the inside is next to raw. Your scrambled eggs are brown and firm on the outside but still runny and liquidy on the inside. You can't seem to cook anything without setting off the smoke alarm? Sound familiar? Listen, every beginning cook has trouble controlling heat, but you don't need to fry everything to a crisp. The problem here is self-evident: Food isn't evenly cooked (which can lead to undercooked and dangerous-to-eat insides) at best, or completely burned and overdone at worst. Photo by normanack.
  • When you're cooking too cold: The opposite problem doesn't happen as often, but it's still an issue. Cooking with the heat down too low may get your dish done, but avoiding higher heat will keep liquids from simmering, herbs from wilting, flavors from developing, and aromas from opening up fully. It'll keep that delicious sear and browning action we just discussed from taking place on steaks and chops, and of course, you also run the risk of underdone food. Veggies and other foods where texture is important run the risk of being a bland mush that's been cooked down too far, too long.

5 Cooking Mistakes We All Make, and How to Fix Them The Solution: Get to know your stove or oven, and stop cooking everything on high heat. Here are a few quick ways:

  • Try all of your burners and watch them heat up. If you have an electric range, see how long each one takes to heat up. If you use gas, tweak the control knob to see the level of fine control you have over the flame intensity. With luck, you'll have great control over the level of heat your stove puts out. Sadly, not all stovetops really know the difference between "medium" and "medium high," and testing the burners is the only way to find out. Photo by Steven Depolo.
  • Use more than one burner. If your stovetop doesn't give you the control you need, don't just use a different burner—a smaller burner turned down may be the equivalent of "medium" of your large one. You'd be surprised how few home cooks really learn the difference between "medium high" and "high," or how many kitchens I've visited where the large front-corner burner is the only one anyone ever uses.
  • Make a heat map of your oven. Most commercial ovens have hot and cold spots. They can be hard to identify, but once you make a heat map with a cookie sheet and a few slices of bread, you'll see your oven's hot and cold spots.

You're Cooking with the Wrong Oils

5 Cooking Mistakes We All Make, and How to Fix Them The Problem: You probably already know that heating oil until it smokes is a very bad thing, and keeping multiple oils around for different purposes is a good idea. Still, frying everything with extra virgin olive oil is a surefire way to set off the smoke alarm every time you sautee, and baking with an extremely flavorful oil like sesame or coconut will certainly introduce flavors to your dish that you may not expect. Even though we talked about smoke points and which oils work best for which cooking methods, going just by smoke point (or by someone's diet book) isn't the best way to pick an oil. Photo by Arthur Caranta.

The Solution: Choose your oils not just for their smoke points, but for whether or not their flavor works with the type of food that you like to cook. If you like asian flavors, sesame oil is a great staple to keep around. If you prefer your oil also add its own savory, fatty flavor, consider cooking with more butter, lard, or ghee (clarified butter). Coconut oil is great for a number of reasons, but it can impart a nutty, rich flavor to lighter dishes you may not want.

Also, consider neutral oils that let the flavor of your dish shine through without adding their own. Safflower oil, for example, is completely neutral, and has a high smoke point. Grapeseed oil has a very light flavor that you may not even notice in your dishes, and is also well suited to high-temperature cooking. Don't just assume that you can do everything with olive oil or "vegetable oil," which is usually either a mix of oils or (more often) store-shelf code for "soybean oil."


These five are just the tip of the iceberg. There are plenty of other common cooking mistakes many of us make all the time, and sometimes even knowing better doesn't stop us. The key is to remember why they're dangerous, cost us money, or make our food taste terrible: That's the key to putting an end to them for good.

Title photo made using Corey Seeman, Boring Soap, Consumatron, Biswarup Ganguly, and Juan de Vojníkov.

Number of comments

Slatest PM: North Korea's Threats and What the U.S. Will Do About Them

Trouble viewing this email? View these recent stories in your browser.
 
 
header
Wednesday, April 03, 2013

Stories from Slate and The Slatest, your daily news companion with @JoshVoorhees.

Blog | Josh Voorhees
Slatest PM: North Korea's Threats and What the U.S. Will Do About Them
Wednesday, April 03, 2013, at 4:51 PM EDT

 
Blog | Josh Voorhees
Did the Aryan Brotherhood of Texas Just Scare a U.S. Attorney Into Quitting a Major Case?
Wednesday, April 03, 2013, at 1:08 PM EDT

 
Blog | Josh Voorhees
Rutgers Fires Coach After Public Learns of Abuse School Already Knew About
Wednesday, April 03, 2013, at 10:23 AM EDT

 
Blog | Justin Peters
Could Rutgers Coach Mike Rice Be Arrested For Assaulting His Players?
Wednesday, April 03, 2013, at 3:07 PM EDT

 
Blog | Abby Ohlheiser
Fate of Alabama's Abortion Clinics Could Be Decided By New Rules
Wednesday, April 03, 2013, at 3:31 PM EDT

 
Blog | David Weigel
Reince Priebus Wants the Media to Rebrand Planned Parenthood, Please
Wednesday, April 03, 2013, at 3:40 PM EDT

Advertisement
 
Future Tense | Will Oremus
Forty Years Ago Today, Snarky Tech Journalists Made Fun of the First Cellphone
Wednesday, April 03, 2013, at 2:10 PM EDT

 
Blog | Slate V Staff
Here's to 40 Years of Huge, Weird, Wonderful Cellphones (VIDEO)  
Wednesday, April 03, 2013, at 4:48 PM EDT

 
Blog | Josh Voorhees
Illegals No More: The Language at the Center of the Immigration Debate
Wednesday, April 03, 2013, at 2:22 PM EDT

 
Future Tense | Torie Bosch
On Facebook, "Like" Can Mean "Dislike." Get Over It.
Wednesday, April 03, 2013, at 4:18 PM EDT

 
Blog | David Weigel
Read One of the Fundraising Letters Rand Paul is Sending on Behalf of a U.N.-Skeptical Gun Rights Group
Wednesday, April 03, 2013, at 4:31 PM EDT

 
Blog | Emma Roller
Hillary 2016 Supporters Are an Intrepid Bunch
Wednesday, April 03, 2013, at 11:07 AM EDT

 
Blog | David Weigel
Opening Act: The Boring Resurrection of Mark Sanford
Wednesday, April 03, 2013, at 8:38 AM EDT

 
Politics | John Dickerson
Let the Race Begin!
Tuesday, April 02, 2013, at 8:53 PM EDT
Why silly speculation about the 2016 presidential race can do some real good.
 
Blog | Matthew Yglesias
Would More Immigrant Engineers Be Bad for American Engineers? Who Cares?
Wednesday, April 03, 2013, at 10:01 AM EDT

 
Blog | Matthew Yglesias
The Vicious Cycle of ObamaCare Obstruction
Wednesday, April 03, 2013, at 10:26 AM EDT

 
Blog | David Weigel
The Social Media #Fail of the Mark Sanford Race
Wednesday, April 03, 2013, at 10:54 AM EDT

 
BEST FEATURED STORIES
header
College Professor Asks Whether Rape Should Be OK if the Victim Doesn't Remember It
header
Forty Years Ago Today, Snarky Journalists Made Fun of the First Cellphone
header
The People Who Stayed Behind in Fukushima Might Have Been Better Off Than Those Who Fled
header
The 1922 Straw Hat Riot Was One of the Weirdest Crime Sprees in American History
 
Copyright 2013 The Slate Group | Privacy Policy
The Slate Group | c/o E-mail Customer Care | 1350 Connecticut Avenue NW Suite 410 | Washington, D.C. 20036

Unsubscribe | Forward to a Friend