long time trolls such as @pjh and @Polygeekery tend to have a bit more rope to play with as they are pretty good about keeping questionable content in the garage too.
Really? They must really be good at keeping their trollery in the garage, because I don't have that impression of them at all. (I stay away from the garage)
They both start threads I have to move to the garage from time to time.
They're both getting better at parking those directly instead of waiting for the inevitable. It's usually stuff that is only tangentially garage material, but the conversation often manages to find its way there.
Yeah, and the last one of mine she had to move I intended to post in the garage to begin with but I did so from mobile and something got lost in translation.
Status: So, my latest Microsoft Band 2 also developed the crack in the rubber band it is notoriously known for. This is actually my 4th band now (the first replacement was DOA, the other two developed the crack as well).
After MS support had hemmed-and-hawed a bit about "you're just out of the 1-year warranty!" last time but were graciously replacing it nonetheless, I knew that I was in for a bit of an argument this time around, due to two reasons:
The purchase is approaching two years now (end of October, to be exact) and, more importantly,
They don't have any Bands anymore (out of stock everywhere).
So, the guy tried the "the one-year warranty is over!" spiel. Which is when I explained to him that, while the one-year period is indeed over, EU-wide law actually states that it's two (2) years.
Granted, the first year is a "we'll replace it, no questions asked" period whereas for the second year I would actually have to prove that it's not my fault...
... but how difficult do you think such a proof would be, considering that I already had two replacements for this exact reason and also the forums are full of other people's pictures with the same problem?
Confronted with that fact, the agent in question (whom I don't blame at all) has escalated the issue and now they're checking about "warranty extension" or something. Given that they're out of stock, I predict that I might get a refund instead.
Lighthouse is an open-source, automated tool for improving the quality of web pages. You can run it against any web page, public or requiring authentication. It has audits for performance, accessibility, progressive web apps, and more.
SET "field_that_references_bar" = NULL
FROM "foo" AS "f1"
LEFT OUTER JOIN "bar" ON "f1"."field_that_references_bar" = "bar"."field_referenced_by_foo"
WHERE "f1"."id" = "foo"."id"
AND "bar"."field_referenced_by_foo" IS NULL;
Also, so I'm on Twilight III, which requires me to go to a bunch of places including jumping puzzles to capture the darkness. One of them is Weyandt's Revenge in LA, and after screwing up the initial entrance part a couple of times, I realised there was a superpower way to get through that section flawlessly every time.
Bring a necro, switch to shroud, observe inability to take damage from the stalagmites.
In general, tuples are useful for smudging things a bit when dealing with a complex mass of data for a short period of time, but they don't really replace a well designed class...
There are a number of developers about who really don't get this fundamental fact, and instead create horrors based on sending tuples all over the place under the misguided impression that this is faster. It's virtually never the case; the advantage of tuples is for when you need a class whose scope is very local and where you don't need any methods.
We've got some of this sort of code at work; the devs in question were former students of ours. They were convinced that they could do things faster by doing tuples all over the place. We've been converting their algorithms to use our production library — with classes! the horror! — and are getting two to three orders of magnitude of speedup, despite the whole thing still being in Python (and therefore disgustingly slow).
There is a dish that we make occasionally that I do not have a name for, but it is basically grilled veggies with spaghetti with pesto.
Take three squash (yellow, zucchini, whatever is handy), a red onion, 2-3 ears of corn on the cob and a couple of bell peppers and slice them up in to grillable sizes. (1/2" slices for the squash and onion, bell peppers in to any size that won't fall through your grill grates) Coat everything with a few tablespoons of olive oil and season liberally with salt and pepper. I put all but the corn and onions in a large bowl so that I can toss it while I season it to make it easier and quicker. Corn and onions are put on a platter and drizzled and seasoned.
Heat your grill to high and start your water to boil. Grill all of the veggies until they have some good grill marks and light charring. Corn will take the longest and goes on first, squash next along with onions and peppers go on last. Pull all of the veggies when they are done and take them inside and drop the spaghetti in the water to cook while you chop the veggies up in to large but bite-size pieces and cut the corn off the ear and then toss with ~1 cup of pesto (I prefer to make my own as store bought is too oily for me, but store bought would work also).
Once the spaghetti is done, reserve a cup or two of the pasta water and drain well and toss with the pesto/veggie mixture. Season with more salt and pepper if needed, maybe drizzle over some lemon juice and add some chopped parsley and grape/cherry tomatoes sliced in half. If too thick, loosen it up with the pasta water.
Super yummy, pretty healthy (the pesto does add quite a bit of oil) and does not need any meat to go with it but a grilled chicken breast would probably pair well. Also, it makes a ton so you can either feed a crowd or have leftovers for lunch for the week.
Tonight for dinner I have had steaks in the garage fridge drying for a few days to be served with Austrian potato salad, grilled corn and grilled romaine.