Off topic but I bet you could tell the difference between an espresso shot pulled after stirring the grounds to ensure even distribution vs one that hasn't been messed with. I'm not saying you can tell the difference between stirring with a toothpick vs stirring with tiny metal tines. You can actually observe a difference in how the water flows through the grounds, you can measure how much coffee has been extracted into the water with a refractometer, and you can do a blind taste test and identify which is which. If the grounds are not evenly distributed, you get channels where the water passes through under high pressure, and this over extracts those grounds making the shot taste extremely bitter, and other grinds are left untouched or under extracted. I was very skeptical of this until I observed it myself.
Most people don’t realize that making espresso is quite complex due to seemingly minute factors like these. When you’re pushing water through grounds at very high pressure, there are a lot of things that have to line up to get a great shot.
Not only a great shot but consistent shots, that's even harder. I really don't understand the gripe OP has against WDT because it is really about eliminating those minute variables so that the process is reproducible.
It is about improving the packing of grounds by breaking up the subtle clumping that occurs during grinding to reduce channeling where water finds an easy path so part of the puck is over extracted and other parts are under extracted.
If you already had perfectly even flow, it's not going to improve anything. That might be true with great equipment or a very forgiving bean. It might also be true if WDT isn't enough to fix your channelling alone so there is more left to fix. This leads you to watching slow-mos of your pulls and inspecting pucks :)
One of the most amusing quotes in the movies given how obvious the statement must have seemed at the time. Tanenbaum made a statement hinting at the same development in the famous usenet debate with Torvalds in 1992.
"Of course 5 years from now that will be different, but 5 years from now everyone will be running free GNU on their 200 MIPS, 64M SPARCstation-5."
No, no, RISC architecture was already changing everything. I mean, RISC made possible not only the Newton, but also the Alphas that shortly after that powered AltaVista, and the SGIs that powered significant parts of the US nuclear stockpile stewardship program (not to mention some movie visual effects). And arguably without the pressure from RISC we wouldn't have seen the adoption of OoO and the micro-op approach that was already starting to boost CISC performance when the movie came out.
A fair amount of that seems fixable with better color choices and fonts/size. It's curious to me that cloudcraft hasn't improved it. Lightish orange on a white background, for example?
Join a humble group that embodies Detroit hustle and works hard in reinventing how leading brands do promotions. One where you'll accelerate career development not from programs or courses, but from diving into the things you’re passionate about exploring. Leave your mark on our growing company and incredible city.
* React
* Ruby on Rails
Accepting candidates with strengths with one part of the stack looking to grow in others. Quikly celebrates diversity, equity, and inclusion and is committed to creating an inclusive environment for all employees.
For what it's worth, my Model 3 from December 2018 with 35K miles on it has only had one issue (with squeaking upper control arms) and they replaced it under warranty, coordinated through the mobile app. I haven't had any other issues that would indicate build quality is terrible.
Same here - I have a 2018 model 3 and its gone in once to get a warning for the seat belt fixed. Its got 45k miles and had no other issues. Best car I've owned.
The best car I ever owned is my current car, a 16 year old Audi that had many prior owners and has nearly 300.000km on the teller. Its never given me trouble and anything you run into you can fix yourself with volkswagen parts. The build quality comes into play sooner than later.
Ah that's good to hear. I have heard some model years of Audi were notorious for reliability, maybe coinciding with the dips in VWAG quality in general, but they are one of the few makers of station wagons selling them in the US anymore and I might seriously consider an A4 or A6 wagon...
I think maybe a lot of their bad rep came from the all road "Air suspension" era...although the simple fix was to install regular shocks/springs.
Agree, Mine is a Model 3 from May 2018 with 22k. I've only had a couple of small issues, (Infotainment computer would fail to wake back up often and a bad switch on break pedal meant to register a foot but no press) both fixed with no issues. Judging by the serial number on my included diecast mine was close to one of the first 12k produced.
I think a machine learning algorithm wouldn't care about that, because with a large enough training data set it would start to account for that and be able to accurately predict energy output based on the image alone.
Regardless of how big the dataset is, the image recognition algorithm is bound to get confused by the large differences in colour that exposure and sensitivity results in. It will likely look for the overall gray-to-blue gradient and estimate results from that; on the gray end of the things alone, the camera settings make a very, very big difference. You can't really tell the algorithm to ignore these and only determine the level of 'cloudiness.'
Another issue with this dataset is the overlay changing over time in text content, font, and colour. The algorithm might overfit and think e.g. yellow font presence means higher output simply because the output was higher during that period. You could strip away the text, but then you're introducing potential errors into the dataset yourself.
Haven't seen this page before (although admittedly I only have a mac, I don't use any of Apple's other services/devices) but I like how it feels... "Apple".
First of all they convert the time automatically as someone already posted, which is a very welcome surprise.
The second (and most surprising for me) thing was that they only have 2 statuses: "Available" and "Issue". And while most status pages have trained us to expect that the antithetical of green is red that it immediately catches your eye, in this case it is a simple yellow diamond which is much less alarming. I sense the PR department had its saying in how to present service availability issues.
Very few communication services are truly P2P; it's way more likely to have syncing issues and is virtually impossible without at least a handshake. Even Signal, which does have syncing issues due to being mostly P2P, requires a server for the initial handshake.
