Also, there are APIs for acquiring real-world mailing addresses inside of "subdivided" warehouses. The only way to verify that a person isn't a bot is to make babies with them.
959 karma · joined April 28, 2017
With MS, the EEE process should be your null hypothesis when you are trying to predict their behavior.
Having said that, I am not against the idea of taking advantage of an opponent who prostrates themselves, just make sure that you can safely extricate yourself from the trap. If you want to deploy on Azure, make sure it's a multi cloud deployment with some insulation above the infrastructure, like Mesos or Kube. Which precludes using the more specialized services, but seriously, who pipes unencrypted data through 3rd party message queues? That's just crazy.
Last year, I was building a simple SVG based chart dashboard for internal usage. Being a NoJS guy, I would sometimes disable JS while developing, on purpose or otherwise, and aside from forcing me to manually hit refresh in the browser, things generally worked. I added a couple links (styled as buttons) for zooming, to supplement the JS based drag-window zoom, and let the browser scroll the potentially very wide SVG chart within a div. If necessary, I could have even embedded the whole thing in an iframe, to avoid triggering whole page reloads, but our caching story was tight enough to compensate. Also, the React-rendered SVG represented the bulk of the markup on the page anyway.
Interactive visualisation, no JS needed. It added maybe an extra 10% to my workload (we already had the SSR stack), and helped me to avoid a variety of little glitches that plague many client-only apps, glitches that users learn to tolerate with mild disgust. The satisfaction of seeing our in-house dashboard pop up "instantly" with data, while Parsely and New Relic were still churning spinners or stuttering while waiting on JS, or even waiting for initial data after waiting on JS, was very cathartic. TTI can equal TTR, we have the technology, we've had it for a decade or so.
https://wiki.kerbalspaceprogram.com/wiki/Cheat_Sheet#Delta-v...
If the fissile material could be acquired by asteroid mining, then it would never need to pass through the Earth's atmosphere. I know that still sounds way out there, but I think that uranium or thorium would actually be a great material for kicking off asteroid mining. A small amount will pay off in a big way, it is a very dangerous thing for humans to mine on Earth, and, like the parent mentioned, we really don't want to fly it around where it can fall on us.
Earlier, I made some notes and walked away from the problem, because it was getting frustrating. Then, while I was checking this out, I started thinking "Imagine how complex this would have been if I had done it in C++" Then the immediately following thought was "Well, in C++, I would instead build it like so, because it needs to be thread safe." Problem solved, obvious-in-hindsight solution.
Even though my problem wasn't caused by a low level threading mistake, thinking about the problem in the context of a more primitive tool helped me to better understand how my own tools are working.
What really amazes me more than anything though, is how willing some of us are to trust Microsoft all of a sudden. They did damage to the software and web communities that will take us decades to recover from, but with another round of "embrace", we are right back in the old loop. Reminding people of their history is now considered rude; our own communities have been co-opted by the MS PR machine.
Heck, a vanilla Wordpress install would have been sufficient for this, if they don't have resources for anything other than a free off-the-shelf solution.
CREATE TABLE queries IF NOT EXISTS (
name varchar(64),
version varchar(64),
query text,
description text
);
NOTIFY chat 'Alice: Bob, please insert that query into the new queries table, and then NOTIFY "chat" with the name and version of it';
LISTEN chat;
Asynchronous notification "chat" with payload "Bob: See update-rank, v. borked-1" received from server process with PID 8448.
Asynchronous notification "chat" with payload "Bob: I have it set to update in a temp table, so we don't have to reset the real table" received from server process with PID 8448.
SELECT queries.query FROM queries WHERE name="update-rank" AND version="borked-1"
INTO query;
\echo query
-- "Looks sane, let's run it"
DO $$ EXECUTE query INTO result $$; -- Something like that, I'm guessing.
\echo result
Bonus points if you edit the query by shelling out to sed or butterflies.
Gotta start somewhere. Proposals that come with a working prototype probably fare much better than those that are purely theoretical.
While you're at it, please also s/\s+$//g on save. Those unintentional trailing spaces really clutter up Git history, and that comprehensive, clean history is what enables the team leads to do their job without bugging you on Slack. It also signals carelessness, or at least a lack of care for personal tools, and has your name attached to it.