<inconsequential webpage bug report> First few images link to the full size version of the _next one_ </inconsequential webpage bug report>
373 karma · joined May 30, 2011
2. In most of US/EU you get them for $5 in up to _two weeks_, or in two days for $5+$2X or more which adds up quicklyand can be more than the rest of the project. Even next day shipping loses out badly to making it yourself in ~30 minutes, turns into two days delay unless you're lucky to have an idea in the morning and time to work on it in the next afternoon, a lot of the time i see people bodging things i'd make another board for because it's just easier.
https://en.wikipedia.org/wiki/Calibri#In_crime_and_politics
I feel like I remember the topic having its own list article but can't find any trace of it.
If you're already making that then building a type checker wrapper on top of it makes perfect sense.
I think this should give a more staircase-y plot, with jumps when the size of each individual copy passes whole multiple of cache line width.
I think this way you don't need to fight prefetching, and there will be one read-modify-write per operation except right at the edges which is another signal.
It is or at least was pretty common to hear about flavonols, flavonoids and specifically quercetin in various foods and their purpoted health benefits. Seems we've moved on to other compounds that are not yet known to be ineffective.
We all want to make something and pick methods in pursuit of that. I always liked light, airy, bubbly, crispy things which drove me to high hydration and savory, beery, bready things which drove me to long fermentation. For pizza this means i liked bubbly high crusts and savory thin as a pancake pizza bassa, so that's what i tried to make.
When it's getting old i deliberately fold in extra flour. Notice it doesn't take that much to push it down because the quantities are quite small -- i've settled on 144g flour, ignoring everything else at ×1.75 it's 252g of dough, it'll take 18g of extra flour to push it all the way down to classic 66%, that's a heaping tablespoon. And i rarely really reach 75%, i aim for just under 75% and generally end up making 72~74% after including what it absorbs as i work it.
Oh, and another thing i should have mentioned is that if the dough is older i make sure to fold it few times more and work a bit more fresh flour into it. And i use high hydration (as high as i can make it, about 72~75%), when i pull it out from the fridge it's _wet_ so even when it's as old as it should be (2~7 days) the crust will be mostly fresh flour.
The trick is that there is no trick and you just let it overferment but pick style that will work well with it. You need savory toppings to go with the taste, e.g. salami and maybe sharper tasting cheese. Making very thin pie will be difficult with dough so weak so don't do that, it won't rise very high so don't make it too thick either.
And 14 days is the furthest i recommend taking it. As i wrote above two to seven days is best, of course it tastes differently after seven than after two days but both are good and perfectly within the canon of 'pizza' and you can prepare it anyhow you want.
Beyond that you're pushing it, but since the topic is what shortcuts you can take i'll still recommend more than you need and using it longer than you'd think to over trying to make it the same day. 30~40 minutes from a decision to a pizza, it does taste right too.
You still have to think of it ahead of time but this removes need for coordination and lets you do it in batches.
Also I just make one kind of starter bread dough in batches and then make everything out of it, some things as-is (bread for first ~4 days, bread dough pizzas for 14 days), some by mixing it with fresh dough (bread afterwards, everything else). But i'm specifically after the heavily fermented dark dough taste.
Also for benford's law to show up you want your data to span several orders of magnitude (so e.g. you have numbers in tens, hundreds and thousands) and for a datapoint to be about as likely to give an n-digit number as a n+1-digit number, not everywhere and not exactly but it needs to dominate over there being ten times times as many of them with each step.
Do you have a name or source or something? Can't really google that.
If this is how much evidence you need to dismiss something without checking, then you'll dismiss everything and you'll never find out if/when the hunch was wrong.
UT1 is an evolution of solar time, and wobbles when Earth does because it's using the Earth and Sun (and other bodies) as a clock.
UTC is TAI with leap seconds added when UT1 drifts too far away.
It's easier to educate the motivated than motivate the educated.
Some 10-15 years ago someone built dirt simple radio tags this way. Just a microcontroller, with a capacitor and an antenna trace connected to some io pin. I loved that hack.
And many of these were _bad_, C++ was a different language back then and the culture of how you write C++ was different. There were times when it was fashionable to write OO spaghetti almost as bad as the stereotypes about java, or templates that worked except for some unforeseen footgun (then you could template libraries that worked correctly but figuring out how was a trip). And before all of that there was a decade when C++ compilers were just _full_ of bugs, and before that there was no standard and every compiler was different. The negative stereotypes about C++ come from all that.
I think he had every reason to fear that e.g. he would have to fight someone who implemented control flow using an inheritance hierarchy because it's a pattern. And he could find himself in the minority.
(Also I'd say there are still counterproductive fads, and it's still common to write C++ that's beautiful on the outside and completely inscrutable inside, or generally pay a huge price in code size and complexity for marginal gains elsewhere, or to depend on optimizations that don't trigger. Same in many other higher-level languages but somehow not in C.)
Second, more important, i don't remember any talk of adapting C++ to bare metal programming, while there is an ongoing cooperation with rust folks already.
It _may_ become something only far right nuts say, same as with frogs and other 4chan stuff -- young people invent something, culture drifts, dumber or isolated people are least likely to drift with it and most likely to have violent views, eventually mostly violent people say something and the rest stops saying it because they don't want to be taken for one of the violent group -- but i don't think it has happened already.
In related news you just found out why many adults treat anything and everything teenagers do is something rude and offensive that needs to be suppressed. Teenagers are loud and annoying so their stuff is something loud and annoying people do. It's something you need to control.
Or i might be wrong, this can change quickly, but then the author can be wrong too.
I don't think that was what ibains was going for, though i don't fault you for seeing this in that comment. (Especially that i don't think this course suffers from that problem and generally i think things are rapidly improving on this front.)
That problem to me and i think to him too is that quite a lot of things that such courses tend to teach as well thought out, well working solutions and approaches just don't work very well and frequently i find comments on what's a 'good taste' solution and what isn't that are completely my understanding of the problem space which is why.
E.g. in parsing (as that's the topic he mentioned): First, lots of people just spend way too much time on it. And they focus on parts that are of zero use to beginners (like explaining all several grammar families) and then use obtuse parser generators that save no work and sometimes use them in bizarre way (like picking a lalr parser generator then hand editing the output to support a not-quite-lalr language). Meanwhile a recursive descent parser is easy to write, fast and gives pretty good error messages with _very_ little work. You do need to know enough about grammars to be able to write one down and know if it describes an ambiguous language etc so this should be taught, but you don't need to understand the language zoo well.
Fast convolution algorithms use FFT and run in O(n log n) time, which is why fast multiplication algorithms are based on FFT and why everyone was looking for O(n log n) one, which was found like a year ago.
(Though from what i can tell in "Faster Convolutions" section the article claims you can easily build O(n log n) multiplication using FFT which doesn't work as it ignores carries)
Still, feel you on the retail apocalypse, and how every other new internet darling can somehow skirt taxes or... and the problem is unfixable until right after it doesn't matter anymore. It took something like twenty years for Amazon to start paying US sales taxes most of the time, in many cities Uber's business model was price dumping etc.
Polish wikipedia says up to 86% of seeds carry it but without source. This paper [1] says 70% of 'wild populations' of related L. perenne, implies infection in darnel (L. temulentum) is also prevalent, but notes most populations have low frequency of infected individuals and then tries to explain that.
[1]: https://mivegec.ird.fr/images/stories/PDF_files/0250.pdf
But nobody knows the generic name (the acronym isn't even in the wikipedia article) so fly by night vendors use 'kapton' wherever they can get away with it.
(and as with teflon, iirc they sell other polymers under the name of kapton too)