As a layman (please humour me, I realise this could be a daft question) is failure to report results generally a sign of anything relating to the outcome, or is it equally likely to be something mundane?
I get that you were being deliberately a wee bit provocative, but If you honestly believed that of every manager you had, you would have been a horrible co-worker.
And if the system works sans-ethics, is that a problem beyond moralistic gatekeeping?
Since the main objection in the article was the military coopting the practice - The basic tenants of mindfulness, as I understand them, are not anybody's property - no matter how compelling the publisher's advances are.
And let's be honest with ourselves - the stationary and toilet paper the military buy have the implicit eventual aim of making them better at making things dead. I'm not convinced mindfulness training for troops is the problem here.
Sure, there are rogue teachers, but that has applied to everything from spurious gurus through to homebrew religions. At trial of sounding callous, caveat emptor surely?
Nothing Mindfulness (as a brand) teaches is a super-secret arcane mystery fercryinoutloud! If nothing else, the government spending time and money on it can only do wonders to validate it and cement it in the public conscious.
How long did they wait before publishing? We don't know, it doesn't matter. Simply stating that they didn't respond had the desired effect, and - as you rightly pointed out - does nothing to diffuse the story. The implication of the story being that not only are Google potentially taking advantage of vulnerable people to further their unspoken, morally grey agenda, but it may also have a racially questionable angle.
Alternately, they wanted to train their facial recognition dataset with certain characteristics on the cheap.
That in itself is interesting, but probably wouldn't get as many clicks. It's bottom drawer "I leave you, dear reader, to draw your own conclusions" stuff.
Doesn't matter, I suspect - It works within the narrative and implies they have something to hide. It's good /tabloid/ journalism, and poor investigative journalism.
Yeah, the search vs shop tension is the big question.
The difference being that Google are ostensibly a search engine, who are looking to monetize and leverage their ubiquity - Amazon are a book store grown to titanic proportions looking to maximize profits.
The same, but different.
I fully support Amazon's divergent empire being broken up into sperate companies, but for the moment Amazon.com - the online marketplace - is still an internet shopfront.
I think their point is simply that "it's their store" - and to be brutally honest, I agree.
Two not-entirely-random examples of similar behaviour:
Supermarkets place their own brand merchandise where they feel it'll sell best. Undeniably good business, and certainly no reason for concern.
Perhaps more questionably, but bare with me - Google place AMP content, which is to say content they have made their product by merit of some ToS/caching slight of hand, front and center. Is it exactly the same as what Amazon are doing? Well, no. Is it placing content they want consumed above other content irrespective of merit or consumer benefit? Probably.
Similarly Amazon are doing what businesses do and promoting their most profitable products, straddling both the above examples. Whether it's best for the customers is open to debate, but it doesn't change that it's entirety their prerogative.
Realistically for companies rolling their own managers, it should be a gradual multi-year process.
Initially mentoring less experienced developers, then into running a small team, scaling up the managerial aspects and learning to let go of the code, hire great people and trust them to deliver over time.
The modern industry moves faster than that, new roles are machine gunned into our inboxes, we are told you can't stand still or you're hurting your own career.
Those aren't mutually exclusive situations, but it's certainly made more difficult by their orthogonality.
Nestlé signed a deal with them at the beginning of April, according to TheKingOfBelAir's comment above, which would lead me to believe they were at least involved with the study.
I was suprised the degree to which selector performance is a negligible overhead in normal use these days.
Was browsing through the docs for some Vue+CSS library or another recently, and the author had done quite a lot of research into this, was interesting.
They were heavily using the square bracket html-attribute selector notation, although I'm not sure if it performs better now, or if modern processors are just that much faster.
I'm taking about classes with an enforced 1:1 relationship with a DOM node, via a unique computed className.
Since there is no requirement for a cascade for this, you've effectively made an ID out of a class.
All the reasons styling off IDs isn't ideal in the traditional CSS metaphor still apply, specificity, verbose stylesheets, etc. But now it's defined as a class too.
Is a single purpose class still a class? Not in the conventional sense - In CSS' lexicon it's a group of things, right?
I've got nothing against the approach - it solves a problem - but it's not how CSS was intended to be used.
CSS modules, CSS components, BEM, heck even Sass and Less fall into the same area of trying to wrangle huge unsorted lists of loosely composed attributes into something meaningful.
So if there is a requirement to bend the rules, the problem is with CSS itself.
Heck, even at the most rudimentary level of organising your CSS falls foul - the accepted best method for sorting attributes within a selector anybody seems to have come up with is alphabetical, which feels weird because it weaves layout, typographical and aesthetic behaviours. Why alphabetical? Because nothing else makes much sense, ...so it wins out by default?
I still maintain CSS is a mess from top to bottom.
It never scaled terribly well in its original state, and with every iteration became more bloated, so we came up with methods of controlling the sprawl; but imo glut of Modern CSS Implementations and their many and varied permutations not only feel like they are not only fighting against the original concepts, but also against each other.
Which isn't to say they're bad or anything, but simply that CSS is old, everything else has changed dramatically, its probably time we went back to the drawing board.