This is something I've been working on a bit myself.

Figuring out which files change is relatively easy (as you've demonstrated). Figuring out what the impact of that is quite hard in non-compiled languages (tools like Maven, Buck, Bazel, etc do this well for compiled languages). I.e. In a repo which is primarily JavaScript, I can get the list of changed files, and hopefully have unit test files which are obviously linear to those. However, knowing if these are depended on by other files/modules (at some depth) is much harder. Same for integration tests -- which of these are related?

I believe the typical approach is to have project.yml list its dependency projects. Build a DAG(error on cycles) and then build all changed and downstream projects.

Very rudimentary explanation of what cookies are and a few of the things WordPress uses them for -- wrapped in a massively self-promotional post complete with attempted push notifications. This post should be flagged.

This article seems to have a trove of interesting data, but struggles to generalize many conclusions out of it.

I think that's because it's a thinly veiled advertisement.

I'm the author. We wanted to showcase some scenarios and that's it.

I would love to hear any suggestions of what else we can gather and report.

Sure... so, showing "here is a weird disk pattern -- they were running X on top of it -- consider not running X on SSD" with a sampleset of 1 is a logical fallacy and kinda a bizarre post.

For small samplesets, going deep to understand unnecessary writes, tuning the clients and showing less SSD wear after tuning would be interesting. Or, assuming you have more than 1 client of each of these situations aggregating the data to show patterns would be far more useful. As has been mentioned elsewhere, for inspiration, Backblaze has really nice posts analyzing their device wear.

Thanks. That makes sense.

But while we do have a lot of clients, I really think that all of their setups are unique in some way. So starting from that we didn't find more Redises on ceph dumping a lot.

> tuning the clients and showing less SSD wear after tuning would be interesting. Is just not an option for us, as we only do monitoring and don't have any ways of tuning.

Apple has notoriously aggressively focused on a future-facing scalable way. I.e. where they see enough of the market in say 5 years (i.e. firewire, USB-C). However, they have been wrong before, AND I don't think anyone can argue that they aren't focusing on non-mobile hardware right now.

While it's easy to say "just trust apple, they're doing it for the shareholders," I think it's also fair to say that they're losing their touch in this venue.

It used to be the only reason you didn't buy a Mac for pro creative-type work was the price. Now there are many great reasons from ergonomics to computing power.

Not (really) on iOS web.

As a basic user of the platform (where my employer has Slack Enterprise Grid), I've always expected this is the case and planned my communication accordingly.

I don't think this is an explanation for the current status and gains of Twitter. Trump has been president for over a year, and has been a prolific tweeter for far longer. If anything, Trump tweets are less novel and more common place then they've been to date.

I think the activity on twitter being referred to is about Trump's presidency, not (mainly) about Trump's tweets. Same reason why cable news is raking it in.

Your comment is pretty unashamedly self-serving and not entirely on topic. Storify was curated, yours intentionally doesn't overlap on the heart of this product.

I don't think there's anything wrong with unashamedly self-serving. All plugs by developers are self-serving, and trying to enforce the veneer of modesty will just cause people to be more subtle and tricky. Better to allow so long as the interest is disclosed (which he did).

So really, the only possible reason to down vote is being off topic (which could definitely apply to this case).

That seems like a strawman and openly hostile to debate with people who do not vote like you.

I've been in some newsrooms where this becomes a slippery slope... they're saying the small daily articles are just there to fund the rest, but those get sensationalized headlines, misleading social images... but it's okay because it's just paying for the real journalism... which somehow just never seems to get prioritized.