Even if I'm a little late to the end-of-year recap things, I decided to do a little recap of 2022 in AntennaPod.
You have to export your db from antennapod and input it into the website, but all data stays in the browser.
Feel free to look at the source code on GitHub and give feedback!
Also adding new stats is pretty easy, just follow what I've done on the existing stats.
Most people prefer cheaper (in this case box wine) because it's often sweeter and it's supposed to be consumed right away.
I do agree with him on the '(most) wines nowadays are pretty good' but I disagree on the 'so there is no reason to pay more than $10 for a bottle of wine' part. Once you get to maybe 30-40$ it can plateau but you can get some amazing wines for 20.
Also the sample size is only of 8, and even if they are 'veterans', some couldn't discern a white from a red...
I find the white vs. red results shocking, I’ll need reproduce the same wine tasting at home. Having said that they used botabox for all their white vs red, and bota box indexes on the sweeter side + normalizes flavors —- I can see how that blurs the lines. I can also see how choosing oddball wines would make it difficult for example: Willamette valley pinot noirs don’t register for me as a pinot. Go ahead and try for yourself: buy the willamette vs. sonoma pinot noir from la crema: the sonoma oozes pinot while the willamette I would categorize as a cab.
Yeah I'll try too out of curiosity, I could see how one could mistake a pinot for a cab or really any one grape for another, since winemaking/climate/soil can make a lot of difference.
I would try that but I'm in Europe so I don't have easy access to American wines, but I think I know what tou mean!
~3k to ~5k dollars a month, no vesting, and I'm not sure if there's a bonus structure. At least 22% of the Clojure workfoce make entry-level money by US standards, so the other 78% must be doing pretty good
The key thing is to make the majority of the code portable enough to run on a PC. I find the best way to do that is to keep things data-oriented, using Plain Old Data type data structures and pure functions as much as possible. Alternative view: isolate out any device-specific pieces, like I/O into as small and simple pieces as possible. When one takes this mindset one realizes that even things that are considered as "device specific", like device drivers usually have a lot of logic that can actually be separate from the I/O. And by having a swappable I/O backend (say for I2C) one can actually test the vast majority of this logic on a computer.
One should also have an implementation of the Hardware Abstraction Layer (HAL) that is "host", allowing to run on a PC, potentially with virtual inputs and outputs. This allows to run essentially all of the firmware on a PC. If one uses a embedded-friendly test framework, like Unity, then one can also run the same tests that is used on the PC on the device - to make sure that there is no difference when ran on host vs device.
Unfortunately, the code from embedded device vendors is rarely amenable to this, so that code can end up as "untestable" under this scheme. For them portability" is only considered between their own hardware devices, not to a computer. Then one has to trust that they have done their own QA. Which is usually not that great - looking at you ST HAL....
