537 Matching Annotations
  1. May 2022
  2. Apr 2022
    1. For this reason, the Secretary of State set out a vision1 for health and care to have nationalopen standards for data and interoperability that are mandated throughout the NHS andsocial care.
    1. Prof Peter Hotez MD PhD. (2022, February 7). 1: BA.2 some evidence that it’s even more transmissible than the original omicron which is more transmissible than delta, and so forth. If it takes hold like it did in Denmark it will slow the descent of original omicron here [Tweet]. @PeterHotez. https://twitter.com/PeterHotez/status/1490669166176702466

    1. ReconfigBehSci. (2021, October 28). China (pop. 1.4 billion) is still pursuing a zero covid strategy, which means 20% of the world’s population still officially lives under such a strategy https://nytimes.com/2021/10/27/world/asia/china-zero-covid-virus.html (not endorsing strategy here, just pointing out that ‘return of Elvis’ maybe warped comparison?) [Tweet]. @SciBeh. https://twitter.com/SciBeh/status/1453658335534800896

  3. Mar 2022
  4. Feb 2022
    1. Google killed SG&E about one year after Stadia launched, before the studio had released a game or done any public work. In a blog post announcing Stadia's pivot to a "platform technology," Stadia VP Phil Harrison explained the decision to shutter SG&E, saying, "Creating best-in-class games from the ground up takes many years and significant investment, and the cost is going up exponentially."

      I suspect Google wanted faster, more measurable results than is possible with game development. There's a reason why tech companies are vastly more profitable than game companies.

      I don't particularly see the shame in changing a strategy that isn't working. As an early user of Stadia I do see the lost potential though, maybe that's where this is coming from.

  5. Jan 2022
    1. For example, if you pre-build a swordman, a spearman and an horseman in 4 cities, you can produce a total of 12 units in 3 turns. This make you save a lot of gold in units maintenance for a good amount of turns.
    1. Prof. Christina Pagel. (2022, January 19). This makes it so clear that the release of all measures right now (esp masks, esp schools) is only to protect himself & his job. Boris has zero interest in protecting others from getting sick, needing hospital or dying. Or protecting businesses, schools, NHS from disruption. [Tweet]. @chrischirp. https://twitter.com/chrischirp/status/1483884632651313152

    1. The Business Strategy stems from a detailed strategic planning process. However, the question we want to answer in this article is whether we can execute multiple strategies side by side while they do not interfere with each other. We compare multiple strategies for business, information provision and IT and focus on Strategic planning.

      Business strategy alignment and the secrets of strategic planning https://en.itpedia.nl/2022/01/02/business-strategie-alignment-en-de-geheimen-van-strategische-planning/ The Business Strategy stems from a detailed strategic planning process. However, the question we want to answer in this article is whether we can execute multiple strategies side by side while they do not interfere with each other. We compare multiple strategies for business, information provision and IT and focus on Strategic planning.

  6. Dec 2021
    1. ReconfigBehSci. (2021, December 18). One thing I keep coming back to in my thoughts is the formerly respected scientists who completely lost their way in this pandemic. Is there something we could be teaching young researchers that would help minimise this in future? Are there norms of science we could strengthen? [Tweet]. @SciBeh. https://twitter.com/SciBeh/status/1472172123829456897

    1. “Businesses in these areas will also have more difficulty hiring and retaining workers who do not wish to be at further risk of contracting Covid. Therefore, businesses can prepare for 2022 by either mandating vaccination or offering significant incentives for employees to get vaccinated, including the booster shots,” he advised.

      Areas of low vaccination grade, the mindset of wisdom or fear?

  7. Nov 2021
    1. Saving Your Wallet With Lifecycle Rules Of course, storing multiple copies of objects uses way more space, especially if you’re frequently overwriting data. You probably don’t need to store these old versions for the rest of eternity, so you can do your wallet a favor by setting up a Lifecycle rule that will remove the old versions after some time. Under Management > Life Cycle Configuration, add a new rule. The two options available are moving old objects to an infrequent access tier, or deleting them permanently after
    1. S3 object versioning Many of the strategies to be discussed for data durability require S3 object versioning to be enabled for the bucket (this includes S3 object locks and replication policies). With object versioning, anytime an object is modified, it results in a new version, and when the object is deleted, it only results in the object being given a delete marker. This allows an object to be recovered if it has been overwritten or marked for deletion. However, it is still possible for someone with sufficient privileges to permanently delete all objects and their versions, so this alone is not sufficient. When using object versioning, deleting old versions permanently is done with the call s3:DeleteObjectVersion, as opposed to the usual s3:DeleteObject, which means that you can apply least privilege restrictions to deny someone from deleting the old versions. This can help mitigate some issues, but you should still do more to ensure data durability. Life cycle policies Old versions of objects will stick around forever, and each version is an entire object, not a diff of the previous version. So if you have a 100MB file that you change frequently, you’ll have many copies of this entire file. AWS acknowledges in the documentation “you might have one or more objects in the bucket for which there are millions of versions”. In order to reduce the number of old versions, you use lifecycle policies. Audit tip: It should be a considered a misconfiguration if you have object versioning enabled and no lifecycle policy on the bucket. Every versioned S3 bucket should have a `NoncurrentVersionExpiration` lifecycle policy to eventually remove objects that are no longer the latest version. For data durability, you may wish to set this to 30 days. If this data is being backed up, you may wish to set this to as little as one day on the primary data and 30 days on the backup. If you are constantly updating the same objects multiple times per day, you may need a different solution to avoid unwanted costs. Audit tip: In 2019, I audited the AWS IAM managed policies and found some issues, including what I called Resource policy privilege escalation. In a handful of cases AWS had attempted to create limited policies that did not allow `s3:Delete*`, but still allowed some form of `s3:Put*`. The danger here is the ability to call `s3:PutBucketPolicy` in order to grant an external account full access to an S3 bucket to delete the objects and versions within it, or `s3:PutLifecycleConfiguration` with an expiration of 1 day for all objects which will delete all objects and their versions in the bucket. Storage classes With lifecycle policies, you have the ability to transition objects to less expensive storage classes. Be aware that there are many constraints, specifically around the size of the object and how long you have to keep it before transitioning or deleting it. Objects in the S3 Standard storage class must be kept there for at least 30 days until they can be transitioned. Further, once an object is in the S3 Intelligent-Tiering, S3 Standard-IA, and S3 One Zone-IA, those objects must be kept there for 30 days before deletion. Objects in Glacier must be kept for 90 days before deleting, and objects in Glacier Deep Archive must be kept for 180 days. So if you had plans of immediately transitioning all non-current object versions to Glacier Deep Archive to save money, and then deleting them after 30 days, you will not be able to.
  8. Oct 2021
    1. COPE

      Create Once, Publish Everywhere

      So when I talk about adaptive content, I popularized a case study from NPR in which they outlined their catchily-named approach to publishing web content, which they called COPE. It stands for Create Once, Publish Everywhere. And in NPR’s model, they maintain a single content model for their article form. So in this content structure, they would have for an article a title, a short title, a teaser, a short teaser, several images attached to the article, an audio file, the body text, whatever metadata was attached to the article, and they could serve up a different combination of that more granular content based on the type of device someone was using.

    2. Adaptive: Content, Context, and Controversy
    1. For myself, Symphony was a proving ground for the COPE approach to content strategy and content management championed by Karen McGrane: create once publish everywhere.
    1. COPE: Create Once, Publish Everywhere

      Adaptive Content

      COPE: Create Once, Publish Everywhere

      With the growing need and ability to be portable comes tremendous opportunity for content providers. But it also requires substantial changes to their thinking and their systems.

  9. getuikit.com getuikit.com
    1. WordPress & Joomla from the UIkit creators

      Run for Water

      I used one of these themes for the redesign of the Run for Water site. I transitioned away from Jamstack, because the organization is centred around volunteers, and it was important to empower them to easily make changes to the marketing front end of their organization. The WordPress theme has a beautiful interface for managing content. However, it goes against the philosophy of COPE (Create Once, Publish Everywhere), recommended by Karen McGrane in her presentations on Content in a Zombie Apocalypse.

      Symphony

      My interest in the subject of Adaptive Content goes back to the days when Symphony was my tool of choice.

    1. Lucas, C., Vogels, C. B. F., Yildirim, I., Rothman, J. E., Lu, P., Monteiro, V., Gelhausen, J. R., Campbell, M., Silva, J., Tabachikova, A., Peña-Hernandez, M. A., Muenker, M. C., Breban, M. I., Fauver, J. R., Mohanty, S., Huang, J., Shaw, A. C., Ko, A. I., Omer, S. B., … Iwasaki, A. (2021). Impact of circulating SARS-CoV-2 variants on mRNA vaccine-induced immunity. Nature, 1–9. https://doi.org/10.1038/s41586-021-04085-y

  10. Sep 2021
  11. Aug 2021
  12. Jul 2021
  13. www.theguardian.com