> It's also hard to brew coffee if you tend to use off-the-boil. The best you'll get is about 93 C.
That sounds ideal for off-the-boil coffee brewing? At sea level I (and all the speciality coffee shops round here) aim for 91C, and I'll drop that to 88-89C for medium roast and lower if it looks on the dark side. Brew methods: Aeropress and cafetiere.
This is true, and even with black tea where you'd normally want hotter, I don't think anyone really pays attention
Thinking about it, we also had some "fancy" packet ramen from Momofuku. Good example there - those noodles take forever to cook compared to the deep fried ones. You'd have to soak, nuke in the microwave and still wait ages.
Most of the coffee we took down were light roast and how well the beans survived shipping/storage, how well they were roasted mattered much more.
There are a bunch of cafetieres as well, but I don't like the silt even with some of the techniques designed to minimize it.
Let's say you're thrown into a website you've never worked on before and asked to fix a styling problem. You can look in the browser tools, but the website will only be running the compiled production version, and if the team knows what they're doing there won't be source maps available.
So you've now found selectors in DevTools that you think are causing the problem, and you want to find them in the source code. In the case of many projects, that means searching through hundreds of small CSS files.
That's why you grep selectors, and where the pain comes. You have to start with the most specific rules that you found in DevTools, then start deleting parts from them until you find a non-nested rule that's in the source, yet still specific enough that you haven't got hundreds of matches to go through.
It would be great if something like ast-grep could take a CSS rule copied from DevTools and search for nested CSS that would compile to match it.
reply