tumblr oqy30pO0Wh1w4fo5oo1 r1 1280
tumblr oqy30pO0Wh1w4fo5oo2 r1 1280
tumblr oqy30pO0Wh1w4fo5oo3 r1 1280
tumblr oqy30pO0Wh1w4fo5oo4 r1 1280
tumblr oqy30pO0Wh1w4fo5oo5 r1 1280

gadotsdiana:

Wonder Woman (2017) dir. Patty Jenkins

tumblr pj76cpZ62g1qeiz5bo1 1280

tha-boy:

literally

Brussels Sprouts

It’s that time of year again, when a lot of people will enact great tragedies on that most underappreciated of vegetables, the Brussels sprout.

This is the correct way to prepare Brussels sprouts. It’s also one of the easiest and lowest-effort. The ingredients are few and simple. The work is minimal. It requires very little skill and is easy to learn. If you’ve never had Brussels sprouts prepared like this, you’ll be amazed at how good they taste. In fact, you may learn for the first time that they even have a taste, and that it is sweet and delicious, and not at all improved by bacon, cream, or vinegar, or whatever other awful tortures people put these things through.

Ingredients

  • Brussels sprouts, ideally all roughly the same size
  • Some salt
  • Plenty of oil

Steps

Rinse the sprouts.

Cut them in half longitudinally. That is, so that the cut goes through the stem, and you have two symmetrical halves. Don’t cut them along the equator, if you do that they’ll shred. Put them in a bowl and try not to break them up too much, but don’t sweat it if a few leaves fall off.

Put enough oil in a large flat pan so that it covers the bottom. Heat it up.

While it’s heating, place the sprouts in the oil flat side down. Don’t just dump them all in there. This is important. Cover the bottom, but do not do more than one layer. Every sprout should have its flat face fully flush against the bottom of the pan.

If the sprouts start to absorb some of the oil, put some more in. The bottom should be covered, but they should not be swimming.

Toss any stray leaves in there just kinda randomly, it’s fine.

Throw a bit of salt on them. I give it a good “shooka-shook” from the salt shaker, probably like a quarter teaspoon or so, but this is pretty flexible. Make them, and if they’re not salty enough, put some more salt on them and use a bit more next time.

The cooking time and heat will need to vary based on the size of the sprouts. The goal is to burn the bottom and let the insides steam in the little dome of Brussels sprouts leaves. Big sprouts will take longer to cook the insides, so you’ll use a lower heat and cook for longer. Little sprouts, turn that shit up (but if the oil starts smoking, that’s too hot, back off a bit). If you get it a bit off, it’s fine. Just means that they might have to get a little more or less browned.

They’re done when the top is dark green and the bottom is completely browned (but not black, that’s probably too much).

Use a tongs to pick one of them up and check if they’re done. Other than that, do not fucking touch them. They don’t need to be messed with, stirred, moved around, or touched. They just need to burn and steam, and that’s it.

Results

They taste like sweet popcorn. I’m serious. The crunchy bottom tends to soften pretty quickly, so sooner you eat them, the better, but this is usually not a problem. (And they’re still good when they’re not super crispy, just a little less amazing.)

15099334 1515029755179276 953561633966260224 n

18645619 1909008672722154 2098837199138062336 n

Node + JS Foundation

npmjs:

Today the Node.js and JS Foundations announced an intent to merge.

tl;dr – This is a good thing. I’m psyched.

The JavaScript community is a big and diverse group of people, doing lots of stuff. Most companies in the world use JavaScript, and at npm, we have a unique view into the shape and scope of this ecosystem.

The overwhelming majority of JavaScript users are people making websites, using modern frameworks, and tooling built in Node.js. They are trying to get a job done, and they want streamlined tools that make them more able to do their jobs. Many of them are not what we might have thought of as “Node Devs” a few years ago (though many are). Their websites run on every back-end platform, including but not limited to Node.js, and they all have to ship a website to browsers, which means JavaScript. Node.js is the dominant platform for building the tools for doing this, and npm is the place where platforms, modules, and tooling are distributed and shared.

A split between “back-end” and “front-end” JavaScript makes less and less sense in light of the way that this community has grown over the last 9 years since Node.js was released. (Wow, has it really been that long? Time flies.) A fast-growing community means that most of the people writing websites, using Node.js-powered tooling and pulling libraries and frameworks from npm, have only been doing it for less than 2 years. The split may have felt normal to those of us involved in 2009, but it seems unnatural and awkward to most working in the field today. It’s just JavaScript. It runs on servers, and on the command line, and in browsers, and you use npm and a bunch of other tools it provides. Is “babel” a front-end tool or a back-end tool? Why are there two groups, when it’s mostly the same people?

Node.js getting more integrated with the broader JS community means that the project can more effectively advocate for server-side use cases, and can get better feedback from those who are depending on Node.js to power the tools they use to ship websites.

As one of the companies at the center of JavaScript development, we at npm are thrilled to see the two major JavaScript foundations joining forces to provide a forum for the entire Open Source JavaScript community. Consistency of governance, processes, and policies can make it easier for devs in disparate JavaScript projects to collaborate and coordinate, removing an unnecessary barrier to innovation. Both foundations now have an established history of iterating on their processes. I hope that this new shift provides a chance to retrospect on what worked, what didn’t work, and what can be improved by working together.

On a personal note, I got involved with Node.js in the first place because I wanted to live in a world where front-end, back-end, tooling, and infrastructure coding did not require constantly shifting my brain around to a whole new language. I couldn’t have predicted how npm would become so relevant to the world of web development, and it’s more than I would have thought to hope for. There’s a lot of open questions about what exactly a merged foundation will look like, but I’m very happy to see things move in this direction.