Interview with Trevor J. Royce, MD MS MPH, author of Analysis of Price Transparency via National Cancer Institute–Designated Cancer Centers’ Chargemasters for Prostate Cancer Radiation Therapy

Interview with Michael L Lipton, MD, author of Associations of Apolipoprotein E ε4 Genotype and Ball Heading With Verbal Memory in Amateur Soccer Players

Interview with Paulina Salminen, MD, PhD, and Suvi Sippola, MD, authors of Quality of Life and Patient Satisfaction at 7-Year Follow-up of Antibiotic Therapy vs Appendectomy for Uncomplicated Acute Appendicitis: A Secondary Analysis of a Randomized Clinical Trial

Interview with Schuyler Jones, MD, and Adrian F Hernandez, MD, MHS, authors of Rationale and Design of the Aspirin Dosing—A Patient-Centric Trial Assessing Benefits and Long-term Effectiveness (ADAPTABLE) Trial

Interview with Ajita S. Prabhu, MD, and Michael J Rosen, MD, FACS, authors of Robotic Inguinal vs Transabdominal Laparoscopic Inguinal Hernia Repair: The RIVAL Randomized Clinical Trial

Interview with Brad Spellberg, MD, author of Evaluation of a Paradigm Shift From Intravenous Antibiotics to Oral Step-Down Therapy for the Treatment of Infective Endocarditis: A Narrative Review

Interview with Naiyer A. Rizvi, MD, author of Durvalumab With or Without Tremelimumab vs Standard Chemotherapy in First-line Treatment of Metastatic Non–Small Cell Lung Cancer: The MYSTIC Phase 3 Randomized Clinical Trial

Interview with Mara A. Schonberg, MD, MPH, author of Effect of a Mammography Screening Decision Aid for Women 75 Years and Older: A Cluster Randomized Clinical Trial, and Quyen Ngo-Metzger, MD, MPH, author of The Life and Death of Mammograms in Patients 75 Years and Older—To Screen or Not to Screen?

Interview with Titus Josef Brinker, MD, author of Effect of a Face-Aging Mobile App–Based Intervention on Skin Cancer Protection Behavior in Secondary Schools in Brazil: A Cluster-Randomized Clinical Trial

Bank of England's statement that Britain could be headed for its biggest economic slump in over 300 years due to the coronavirus lockdown also weighed on the investor sentiment

All that happened in the markets today

Microsoft is one of the leaders in the cloud computing segment segment, besides Alphabet (Google) and Amazon, making the stock attractive

BSE Sensex ended at 31,642.70, up 199 points or 0.63 per cent, with HUL (up nearly 5 per cent) being the top gainer and NTPC (down nearly 4 per cent) the biggest loser

Debt categories continued to see redemptions. Credit risk funds saw a bulk of the outflows at Rs 19,238 crore, registering the worst month for the category in 13 months

Aversion to debt products has contributed to renewed interest in the category

I mentioned this the other day via Michelle Barker’s coverage, but here I’ll link to the official announcement. The main thing is that we’ll be getting gap with flexbox, which means:

.flex-parent {
  display: flex;
  gap: 1rem;
}
.flex-child {
  flex: 1;
}

That’s excellent, as putting space in between flex items has been tough in the past. We have justify-content: space-between, which is nice sometimes, but that doesn’t allow you to explicitly tell the flex container how … Read article “Chromium lands Flexbox gap”

The post Chromium lands Flexbox gap appeared first on CSS-Tricks.

Goan diagnostic system manufacturer, Tulip Diagnostics (P) Ltd, has received the nod from the Central Drugs Standard Control Organisation (CDSCO) to manufacture ‘Coviscreen’, a rapid, double antigen test for total antibodies to Sars-Cov2 virus.

While many other parts of the country are bracing for a heatwave, India Meteorological Department (IMD), Goa, has said the state may be spared of the phenomenon and may only face a slight increase in temperature.

I think a lot about Danielle’s talk at Patterns Day last year.

Around about the six minute mark she starts talking about gaps and overlaps.

Gaps are where hidden complexity live. If we don’t have a category to cover it, in effect it becomes invisible. But that doesn’t mean it’s not there. Unidentified gaps cause inconsistency and confusion.

Overlaps occur when two separate categories encompass some of the same areas of responsibility. They cause conflict, duplication of effort, and unnecessary friction.

This is the bit I keep thinking about. It’s such an insightful lens to view things through. On just about any project, tensions are almost due to either gaps (“I thought someone else was doing that”) or overlaps (“Oh, you’re doing that? I thought we were doing that”).

When I was talking to Gerry on his new podcast recently, we were trying to figure out why web performance is in such a woeful state. I mused that there may be a gap. Perhaps designers think it’s a technical problem and developers think it’s a design problem. I guess you could try to bridge this gap by having someone whose job is to focus entirely on performance. But I suspect the better—but harder—solution is to create a shared culture of performance, of the kind Lara wrote about in her book:

Performance is truly everyone’s responsibility. Anyone who affects the user experience of a site has a relationship to how it performs. While it’s possible for you to single-handedly build and maintain an incredibly fast experience, you’d be constantly fighting an uphill battle when other contributors touch the site and make changes, or as the Web continues to evolve.

I suspect there’s a similar ownership gap at play when it comes to the ubiquitous obtrusive overlays that are plastered on so many websites these days.

Kirill Grouchnikov recently published a gallery of screenshots showcasing the beauty of modern mobile websites:

There are two things common between the websites in these screenshots that I took yesterday.

1. They are beautifully designed, with great typography, clear branding, all optimized for readability.
2. I had to install Firefox, Adblock Plus and uBlock Origin, as well as manually select and remove additional elements such as subscription overlays.

The web can be beautiful. Except it’s not right now.

How is this dissonance possible? How can designers and developers who clearly care about the user experience be responsible for unleashing such user-hostile interfaces?

PM/Legal/Marketing made me do it

I get that. But surely the solution can’t be to shrug our shoulders, pass the buck, and say “not my job.” Somebody designed each one of those obtrusive overlays. Somebody coded up each one and pushed them into production.

It’s clear that this is a problem of communication and understanding, rather than a technical problem. As always. We like to talk about how hard and complex our technical work is, but frankly, it’s a lot easier to get a computer to do what you want than to convince a human. Not least because you also need to understand what that other human wants. As Danielle says:

Recognising the gaps and overlaps is only half the battle. If we apply tools to a people problem, we will only end up moving the problem somewhere else.

Some issues can be solved with better tools or better processes. In most of our workplaces, we tend to reach for tools and processes by default, because they feel easier to implement. But as often as not, it’s not a technology problem. It’s a people problem. And the solution actually involves communication skills, or effective dialogue.

So let’s say it is someone in the marketing department who is pushing to have an obtrusive newsletter sign-up form get shoved in the user’s face. Talk to them. Figure out what their goals are—what outcome are they hoping to get to. If they don’t seem to understand the user-experience implications, talk to them about that. But it needs to be a two-way conversation. You need to understand what they need before you start telling them what you want.

I realise that makes it sound patronisingly simple, and I know that in actuality it’s a sisyphean task. It may be that genuine understanding between people is the wickedest of design problems. But even if this problem seems insurmoutable, at least you’d be tackling the right problem.

Because the web can’t survive like this.

Today marks ten years since the publication of HTML5 For Web Designers, the very first book from A Book Apart.

I’m so proud of that book, and so honoured that I was the first author published by the web’s finest purveyors of brief books. I mean, just look at the calibre of their output since my stumbling start!

Here’s what I wrote ten years ago.

Here’s what Jason wrote ten years ago.

Here’s what Mandy wrote ten years ago.

Here’s what Jeffrey wrote ten years ago.

They started something magnificent. Ten years on, with Katel at the helm, it’s going from strength to strength.

Happy birthday, little book! And happy birthday, A Book Apart! Here’s to another decade!

Singh, Gurcharan, 1945- author

Seigneur, Christian, 1952- author