The American Folklife Center Wikipedia Edit-a-Thon on Women Fieldworkers

Primary Place: American Folklife Center, Library of Congress

Saturday, February 8, 2020
11:00 AM – 3:00 PM EST

Join the American Folklife Center (AFC) on Saturday, February 8 for an edit-a-thon to expand the online presence of women who documented the world. This event is part of the AFC’s multi-year initiative to highlight, explore, and celebrate the contributions of women as ethnographic fieldworkers, and to call attention to the role of women in establishing many of the foundational collections that now enrich the AFC archive and ethnographic archives throughout the world.

During the edit-a-thon, we plan to add and/or expand entries for 25-30 women, both historical and contemporary, who have documented traditional culture. We will focus on collections in the AFC archive. The list of featured fieldworkers whose entries are to be edited will be posted in the near future. Activities will be centered at the Library of Congress in Washington, DC, but off-site participation is encouraged. The event starts with a “How to Edit” session presented by Wikipedia Foundation staff. They will be joined by AFC staff, who will assist on-site and off-site researchers and provide archival materials

Request ADA accommodations five days in advance at 202-707-6362 or ADA@loc.gov

Register for the event at the link!

African American Dollmaking and Puppetry: Renegotiating Identity, Restoring Community
Various speakers and artists, moderated by Camilla Bryce-Laporte

February 18, 2020, 11:30am-2:00pm
119 First Floor
Thomas Jefferson Building

African American artisans utilize ancient skills and innovative technologies to create dolls and puppets that are both whimsical and starkly serious. Their creations — incorporating clay, textiles, wood, glass, and found objects — embrace the somber reality of African American experiences and optimism for a boundless future. Working alone and in communities these artisans create dolls and puppets that articulate Black beauty, strength, style, spirituality, and truth. Their works, embodying older traditions and innovative vocabularies for storytelling, are designed to amuse, educate, and heal. Dolls of each of 8 makers will be displayed on tables from 11:30-12:00 pm and 1:30 pm-2:00 pm.

Folklorist Camila Bryce-Laporte will present six makers as they discuss their work and the stories behind that work. This will be followed with a question and answer session from 12 noon to 1:30 pm.

This program may deal with sensitive subjects and is aimed at adults rather than children.

Some of the dolls will be for sale through the auspices of the Library of Congress sales shop.

Click here for more information.

Please join us for an afternoon symposium:

James Hogg: Scotland's Shepherd Poet
February 21, 2020 1:00 pm - 6:00 pm
Whittall Pavilion, Thomas Jefferson Building, Library of Congress

This symposium will explore the work of James Hogg, “The Ettrick Shepherd” (1770-1835), an influential Scottish song-maker, folklore collector, novelist, and poet. Inspired by Robert Burns, colleague of Walter Scott, and friend of Lord Byron, Hogg played a major role in creating and promoting Scottish culture, within Scotland and internationally.

This free event, which is open to the public, will compare his work with that of more recent American performers and collectors, who also served as intermediaries between the worlds of folk, popular, and literary culture for the first time. Speakers will explore issues around field collecting, song transmission and creation over the past three centuries. An afternoon of presentations and discussions will be capped by a performance featuring renowned singer Sheena Wellington, who has recorded and performed some of Hogg’s best known songs.

Request ADA accommodations five days in advance at 202-707-6362 or ADA@loc.gov

Find further information at the link!

This is a reminder that the American Folklife Center at the Library of Congress invites applications for the Henry Reed Fund Award, which supports activities directly involving folk artists such as recording projects, apprenticeships, or performances. Find information about the Henry Reed Fund Award and other fellowships at the link--scroll down for the Henry Reed Fund. The past recipients link will also help provide a useful history of the award.

The deadline is 12:00 midnight, March 2, 2020.

Click here for more information.

The American Folklife Center (AFC) at the Library of Congress is delighted to announce that four (4) new Occupational Folklife Project collections are now available on the Library of Congress website. They are “Working the Waterfront: New Bedford, Massachusetts;” “Funeral Service Workers in the Carolinas;” “Illuminating History: Union Electricians in New York City;” and “Homeless Shelter Workers in the Upper Midwest.” The collections consist mainly of audio recordings of oral history interviews, with supporting photos and documents. The four new collections join previously released collections documenting the experiences of home health care workers, beauty shop employees, circus workers, gold miners, ironworkers, racetrack employees, and workers in the Port of Houston.

Through the Occupational Folklife Project (OFP), the AFC has now amassed more than 1,000 interviews with hundreds of contemporary American workers representing scores of trades and occupations. These hour-long oral history interviews feature workers discussing their current jobs, formative work experiences, training, aspirations, occupational communities, hopes for the future, and on-the-job challenges and rewards. They tell stories of how workers learned their trades, their skills and work routines, legendary jobs (good and bad), respected mentors, and flamboyant co-workers. They document the knowledge, dedication and insights of American workers, and add workers’ voices to the permanent record of America’s history preserved at the Library of Congress, America’s national library. Adding the collections to the Library of Congress website enables researchers, educators, and members of the public to access them from their homes, schools, and local libraries. OFP interviews can also be accessed at the AFC’s Reading Room at the Library of Congress in Washington, DC.

AFC Director Betsy Peterson notes: “AFC’s innovative Occupational Folklife Project enables researchers and members of the public to have direct access to hundreds of hours of fieldwork with some of America’s most eloquent, engaging, and passionate spokespeople for the trades and occupations that shape our shared national culture. These oral histories not only enrich our current understanding of our fellow Americans, but will inform scholars and researchers for generations to come about the lives of workers at the beginning of the 21st century. Listeners will be able to access the oral histories, images and fieldwork that previously could be accessed only by visiting the Library of Congress in Washington. ”

The OFP was launched in 2010. It is funded in part by AFC’s Archie Green Fellowships, which support teams of researchers throughout the United States, who perform interviews documenting a particular occupation.

New OFP collections available online are:

Working the Waterfront: New Bedford, Massachusetts
The New Bedford Fishing Heritage Center (NBFHC) received an Archie Green Fellowship to document workers on the New Bedford, Massachusetts, waterfront for the Occupational Folklife Project (OFP). Folklorist and NBFHC Executive Director Laura Orleans, working with anthropologists Madeleine Hall-Arber and Corinn Williams and oral historian Fred Calabretta, recorded oral histories with 58 workers involved in diverse fishing-related trades on the New Bedford waterfront. Documented tradespeople range from fish packers to net makers, navigational electronic technicians to marine divers, and maritime upholsterers to ice house workers. The individual interviews are supplemented by striking workplace portraits taken by gifted New Bedford photographer Phillip Mello, who was also interviewed about his job as general manager at Bergie’s Seafood. Mello has been taking photographs of his fellow waterfront workers since 1975, and his work is currently on exhibit at the American Folklife Center.

Funeral Services Workers in the Carolinas
Folklorist Sarah Bryan of Durham, North Carolina, received an Archie Green Fellowship from the American Folklife Center to document the work of funeral services workers in North and South Carolina. She explored how, through their work, funeral service workers engage with the funerary folklore and religious beliefs of diverse Carolina communities, including African American, Gullah, Jewish, Scottish and Scots-Irish, as well as more recently arrived immigrant groups. Interviewees included directors of multi-generational funeral homes and other funeral workers from diverse backgrounds and experiences. A total of 16 interviews are included in this collection; many are accompanied by photographs and historical images.

Homeless Shelter Workers in the Upper Midwest
Social services worker, writer, and documentarian Margaret Miles of Minneapolis, Minnesota, received an Archie Green Fellowship from the American Folklife Center to document workers in the emergency homeless services in three interrelated Midwestern urban centers: Bismarck, North Dakota; Minneapolis-St. Paul, Minnesota; and Chicago, Illinois. She recorded interviews with overnight shelter advocates, meal and clothing center coordinators, street outreach workers, daytime drop-in supervisors, and housing case managers and others who work to resolve housing issues and assist individuals with financial crises, employment, addiction, illness, or mental health concerns. As she notes: their work makes them "master-navigators of complex systems such as healthcare, social security, corrections, veterans’ benefits, and tenant-landlord law." This collection consists of 18 interviews with shelter workers serving diverse communities of clients, including ex-offenders, abused women, LGBT and Native American youth, and individuals with HIV/AIDS. Many of the interviews are accompanied by images by Miles's co-documentarian, photographer Catherine ten Broeke. Troyd Geist, Folklorist for the North Dakota Arts Council, served as a consultant to the project.

Illuminating History: Union Electricians in New York City
New York researcher and electrician Jaime Lopez, in affiliation with SUNY Empire State College's Harry Van Arsdale Jr. School of Labor Studies (HVASLS) and The International Brotherhood of Electrical Workers (IBEW, Local #3) in Queens, New York, received an Archie Green Fellowship from the American Folklife Center to document the occupational culture of urban IBEW electricians, who “through manufacture, installation, and maintenance serve the greater New York City area.” Lopez worked with a research team that included labor faculty Barrie Cline and labor historian Anne D’Orazio from HVASLS, Queens-based artist/documentarian Setare S. Arashloo, and Local #3 electrician Paul Vance. Folklorist Naomi Sturm served as consultant to the project. The team recorded 22 oral histories with IBEW Local #3 electricians reflecting a wide range of ages, backgrounds, experiences, and occupational specialties. Many interviews are accompanied by worksite photographs and photographs of union-related activities.

Click here for more information.

Barker Library - TA443.P58 I57 2013

Barker Library - TA439.W8 2018

Online Resource

Hayden Library - QH452.7.W35 2019

Hayden Library - QH309.D866 2018

Hayden Library - QH315.K545 2018

Online Resource

Hayden Library - QH450.L83 2019

Hayden Library - QH447.H554 2017

Online Resource

Online Resource

Online Resource

Online Resource

Hayden Library - QH438.7.C656 2017

Hayden Library - QH431.B6324 2018

Online Resource

Hayden Library - QH447.G4666 2018

Hayden Library - QH588.S83 K45 2019

Online Resource

Dewey Library - QH331.E85 2018

Online Resource

Dewey Library - QH332.B25 2019

Online Resource

Online Resource

Dewey Library - QH588.S83 S7456 2019

In her Full-Featured Art Direction for the Web presentation at An Event Apart in Chicago, Mina Markham shared her approach to building Web pages that work across a variety of browsers, devices and locales. Here's my notes from her talk:

• Full-featured art direction is progressively enhanced, localized for a particular user, yet inclusive of all visitors and locations.
• Start with the most basic minimal viable experience for the user and move up from there. Semantic markup is your best baseline. Annotate a Web site design with HTML structure: H1, H2, H3, etc. From there, gradually add CSS to style the minimal viable experience. If everything else fails, this is what the user will see. It may be the bare minimum but it works.
• Feature queries in CSS are supported in most browsers other than IE 11. We can use these to set styles based on what browsers support. For instance, modular font scaling allows you to update overall sizing of text in a layout. Feature Query checker allows you to see what things look like when a CSS query is not present.
• Localization is not just text translation. Other elements in the UI, like images, may need to be adjusted as well. You can use attributes like :lang() pseudoclass to include language specific design elements in your layout.
• Inclusive art direction ensures people can make use of our Web sites on various devices and in various locations. Don't remove default behaviors in Web browsers. Instead adjust these to better integrate with your site's design.

In his Beyond Engagement: the Content Performance Quotient presentation at An Event Apart in Chicago, Jeffrey Zeldman introduced a new metric for tracking how well Web sites are performing. Here's my notes from his talk:

• The number one stakeholder request for Web sites is engagement: we need people using our services more. But is it the right metric for all these situations?
• For some apps, engagement is clearly the right thing to measure. Think Instagram, long-form articles, or gaming sites. For others, more time spent might be a sign of customer frustration.
• Most of the Web sites we work on are like customer service desks where we want to give people what they need and get them on their way. For these experiences, speed of usefulness should matter more than engagement.
• Content Performance Quotient (Design CPQ) is a measure of how quickly we can get the right content to solve the customer's problem. The CPQ is a goal to iterate against and aim for the shortest distance between problem & solution. It tracks your value to the customer by measuring the speed of usefulness.
• Pretty garbage: when a Web site looks good but doesn't help anyone. Garbage in a delightfully responsive grid is still garbage. A lot of a Web designer's job is bridging the gap between what clients say they need and what their customers actually need.
• Marlboro's advertising company (in the 50s) rethought TV commercials by removing all the copy and focusing on conveying emotions. They went from commercials typically full of text to just ten words focused on their message.
• Mobile is a great forcing function to re-evaluate our content. Because you can't fit everything on a small screen, you need to make decisions about what matters most.
• Slash your architecture and shrink your content. Ask: "why do we need this?" Compare all your content to the goals you've established. Design should be intentional. Have purpose-driven design and purpose-driven content. If your design isn't going somewhere, it is going nowhere.
• We can't always have meetings where everybody wins. We need to argue for the customer and that means not everyone in our meetings will get what they want. Purpose needs to drive our collaborations not individual agendas, which usually leak into our Web site designs.
• It’s easy to give every stakeholder what they want. We've enabled this through Content Management Systems (CMS) that allow everyone to publish to the site. Don't take the easy way out. It’s harder to do the right thing. Harder for us, but better for the customer & bottom line.
• Understanding the customer journey allows us to put the right content in the right place. Start with the most important interaction and build out from there. Focus on key interactions and build out from there. Sometimes the right place for your content isn't your Website -for video it could be YouTube or Vimeo.
• Customers come to our sites with a purpose. Anything that gets in the way of that is a distraction. Constantly iterate on content to remove the cruft and surface what's needed. You can start with a content inventory to audit what is in your site, but most of this content is probably out of date and irrelevant. So being in a state of constant iteration works better.
• When you want people to go deeper and engage, to slow down... scannability, which is good for transactions, can be bad for thoughtful content. Instead slow people down with bigger type, better typographic hierarchy, more whitespace.
• Which sites should be slow? If the site is delivering content for the good of the general public, the presentation should enable slow, careful reading. If it’s designed to promote our business or help a customer get an answer to her question, it must be designed for speed of relevancy.

In her Data Basics presentation at An Event Apart in Chicago, Laura Martini walked through common issues teams face when working with data and how to get around/work with them. Here's my notes from her talk:

• Today there's lots of data available to teams for making decisions but it can hard to know what to use and how.
• Data tools have gotten much better and more useful. Don't underestimate yourself, you can use these tools to learn.
• Google Analytics: The old way of looking at data is based on sessions are composed of page views and clicks with timestamps. The new way is looking at users with events. Events can be much more granular and cover more of people's behaviors than page views and clicks.
• Different data can be stored in different systems so it can be hard to get a complete picture of what is happening across platforms and experiences. Journey maps are one way to understand traffic between apps.
• You can do things with data that don't scale. Some visualizations can give you a sense of what is happening without being completely precise. Example: a quantified journey map can show you where to focus.
• Individual users can also be good data sources. Zooming in allows you to learn things you can't in aggregate. Tools like Fullstory replays exactly what people did on your Website. These kinds of human-centric sessions can be more engaging/convincing than aggregate measures.
• Data freshness changes how people use it in their workflows. Having real-time data or predictive tools allows you to monitor and adapt as insights come in.
• How do you know what questions to ask of your data? HEART framework: happiness, engagement, adoptions, retention, and task success. Start with your goals, decide what is an indicator of success of your goals, then instrument that.
• To decide which part of the customer journey to measure, start by laying it all out.
• There's a number of good go-to solutions for answering questions like: funnel analysis (shows you possible improvements) or focus on user groups and split them into a test & control (allows you to test predictions).
• The Sample Size Calculator gives you a way to determine what size audience you need for your tests.
• Quantitative data is a good tool for understanding what is happening but it won't tell you why. For that, you often need to turn to qualitative data (talking to people). You can ask people with in-context small surveys and similar techniques.
• Often the hardest part of using data is getting people on the same page and caring about the metrics. Try turning data insights into a shared activity, bet on results. Make it fun.
• Dashboards surface data people care about but you need to come together as a team to decide what is important. Having user-centric metrics in your dashboards shows you care about user behavior.
• Data can be used for good and bad. Proceed with caution when using data and be mindful where and how you collect it.

In his The Case for Progressive Web Apps presentation at An Event Apart in Chicago, Jason Grigsby walked through the process of building Progressive Web Apps for your Web experiences and how to go about it. Here's my notes from his talk:

• Progressive Web Apps (PWAs) are getting a lot of attention and positive stories about their impact are coming out. PWA Stats tracks many of these case studies. These sorts of examples are getting noticed by CEOs who demand teams build PWAs today.
• A PWA is a set of technologies designed to make faster, more capable Web sites. They load fast, are available online, are secure, can be accessed from your home screen, have push notifications, and more.
• But how can we define Progressive Web Apps? PWAs are Web sites enhanced by three things: https, service worker, and a manifest file.
• HTTPS is increasingly required for browsers and APIs. Eventually Chrome will highlight sites that are not on https as "insecure".
• Service Workers allow Web sites to declare how network requests and the cache are handled. This ability to cache things allows us to build sites that are much faster. With service workers we can deliver near instant and offline experiences.
• A Web manifest is a JSON file that delivers some attributes about a Web site. Browsers use these files to make decisions on what to do with your site (like add to home page).
• Are PWAs any different than well-built Web sites? Not really, but the term helps get people excited and build toward best practices on the Web.
• PWAs are often trojan horses for performance. They help enforce fast experiences.

Feels Like a Native App

• Does your organization have a Web site? Do you make money off your Web site? If so, you probably need a Progressive Web Site.
• Not every customer will have your native app installed. A better Web experience will help you reach people who don't. For many people this will be their first experience with your company, so you should make it as good as possible.
• Getting people to install and keep using native apps is difficult. App stores can also change their policies and interfaces which could negatively impact your native app.
• The Web can do much more than we think, the Web has APIs to access location, do fast payments using fingerprint identification, push notifications, and more.
• What should we use to design PWAs? Native app styles or Web styles? How much does your design match the platform? You can set up PWAs to use different system fonts for iOS and Android, should you? For now, we should define our own design and be consistent across different OSs.
• What impact does going "chrome-less" have on our PWAs? You loose back buttons, menu controls, system controls. Browsers provide us with a lot of useful features and adding them back is difficult. Especially navigation via the back button is complex. So in most cases, you should avoid going full screen.
• While not every person will add your PWA to their home screen, every person will "install" your PWA via the service worker.
• An app shell model allows you put your common UI (header, footer, nav, etc.) into the app cache. This makes the first loading experience feel a lot faster. Should you app shell or not? If you have architected as a single page app, this is possible but otherwise might not be worth the effort.
• Animating transitions can help with way-finding and polish on the Web. This gives Web sites even more personality.

Installation and Discovery

• Using a Web manifest file, allows you specify a number of declarations for your app. In addition to name, icon, and even theme colors.
• Once you have a PWA built and a manifest file, browsers will being prompting people to install your Web site. Some Browsers have subtle "add" actions. Other use more explicit banner prompts. "Add to home screen" banners are only displayed when they make sense (certain level of use).
• Developers can request these banners to come up when appropriate. You'll want to trigger these where people are mostly likely to install. (like checkout)
• Microsoft is putting (explicitly and implicitly) PWAs within their app store. Search results may also start highlighting PWAs.
• You can use Trusted Web Activity or PhoneGap to wrap native shells around your PWA to put them into Android and iOS app stores.

Offline Mode

• Your Web site would benefit from offline support. Service Workers enable you to cache assets on your device to load PWAs quickly and to decide what should be available offline.
• You can develop offline pages and/or cache pages people viewed before.
• If you do cache pages, make it clear what data hasn't been updated because it is not available offline.
• You can give people control over what gets cached and what doesn't. So they can decide what they want available for offline viewing.
• If you enable offline interactions, be explicit what interactivity is available and what isn't.

Push Notifications

• Push notifications can help you increase engagement. You can send notifications via a Web browser using PWAs.
• Personal push notifications work best but are difficult to do right. Generic notifications won't be as effective.
• Don't immediately ask people for push notification permissions. Find the right time and place to ask people to turn them on. Make sure you give people control, if you'd don't they can kill them using browser controls.
• In the next version of Chrome, Google will make push notification dialogs blocking (can't be dismissed) so people have to decide if they want notifications on or off. This also requires you to ask for permissions at the right time.

Beyond Progressive Web Apps

• Auto-login with credential management APIs allows you to sign into a site using stored credentials. This streamlines the login process.
• Apple Pay on the Web converged with the Web Payment API so there's one way to use stored payment info on the Web.
• These next gen capabilities are not part of PWAs but make sense within PWAs.

How to Implement PWAs

• Building PWAs is a progressive process, it can be a series of incremental updates that all make sense on their own. As a result, you can have an iterative roadmap.
• Benchmark and measure your improvements so you can use that data to get buy-in for further projects.
• Assess your current Web site's technology. If things aren't reasonably fast to begin with, you need to address that first. If your site is not usable on mobile, start there first.
• Begin by building a baseline PWA (manifest, https, etc.) and then add front-end additions and larger initiatives like payment request and credential api later.
• Every step on the path toward a PWAS make sense on their own. You should encrypt your Web sites. You should make your Web site fast. These are all just steps along the way.

In his Putting the 'Design' in Design Systems presentation at An Event Apart in Seattle, Dan Mall talked about the benefits of design systems for designers and how ensure they can be realized. Here's my notes from his talk:

• Most content in design systems are not for designers but for developers. This helps to scale design efforts when there's a lot more developers than designers (typical in many companies).
• But where does design and designers fit within a design system? Are they no longer required?
• Design can be part of strategy and big picture thinking but most designers are good at making designs and iterating them, not working across the company on "big D" design.
• When it comes time to make a design system, most people start with "let's make some components!". This is problematic because its missing "for ____". What's the purpose of our design system? Who is it for?
• Design systems need a focus. One company's design system should not work for another company. A good "onlyness" statement can only apply to one company, it would not work for other companies.
• Design system principles can guide your work. Some are universal like: accessible, simple. Others should be very specific so you can focus on what matters for you.
• An audit of common components in design systems shows the coverage varies between companies; the components can focus on their core value.
• Instead of starting with making design components, think about what components you actually need. Then make some pilot screens as proofs of concept for a design system. Will you be able to make the right kinds of things?
• Don't start at the abstract level, start at the extract level. Take elements from within pilot designs and look for common components to pull out for reuse. Don't try to make it cover all use cases yet. As you work through a few pilots, expand components to cover additional use cases you uncover.
• The most exciting design systems are boring. About 80% of the components you're making can be covered by your design system. They allow you to remake product experiences quickly. The remaining 20% is what designers still need to do: custom design work.
• A good design system takes care of the stuff you shouldn't reinvent and allows you to spend time on where it matters.
• Creative people are driven by autonomy, mastery, and purpose. A good design system will enable all of these.
• The most common benefits of design systems are greater efficiency and consistency. But another important one is relief from having to do mundane design work. (editor's note: like maintaining & updating a design system!)
• The real value of a design system is to help us get back to our real work.

In his Move Fast and Don’t Break Things presentation at An Event Apart in Seattle, Scott Jehl shared a number of resilient patterns and tools to help us establish and maintain performant access to our Web sites. Here's my notes from his talk:

• For successful Web design, people used to suggest we move fast and break things. Today we've become more responsible but things can still break for our users if we're not mindful.
• So many factors that can compromise the delivery of our Web sites are out of our control. We need to be aware of these in order to build resilience into our designs.
• We used to use browser detection and feature detection to ensure our sites were supported across Web browsers. Progressive enhancement's importance ballooned as a wide range of new devices for accessing the Web, touch interactions, and more browsers became popular.
• Trying to make a Web site look and work the same across devices was broken, we realized this was the wrong goal and we need to adapt to varying screens, networks, input types, and more.
• Some practices stay good. Progressive enhancement and accessibility prepared us for many of these changes but it is also a performance enhancement on its own.
• Figuring out how to make Web sites faster used to be hard but the tools we have for measuring performance have been improving (like PageSpeedTest and WebPageTest).

Making Web Sites Fast

• First meaningful content: how soon does a page appear to be useful to a user. Progressive enhancement is about starting with meaningful HTML and then layering additional enhancements on top of it. When browsers render HTML, they look for dependencies in the file (CSS and Javascript) before displaying anything.
• CSS and Javascript are most often the render-blockers on sites, not images & videos. Decide if they need to load at high priority and if not, load async or defer. If you need them to run right away, consider server push (HTTP2) to send files that you know the browser needs making them ready to render right away.
• If your server does not support push, you can inline your critical CSS and/or Javascript. Inlining however is bad for caching as it does not get reused by other pages. To get around this you can use the Cache API to inline content and cache it as a file for reuse.
• Critical CSS tools can look over a series of files and identify the common CSS you need across a number of different pages for initial rendering. If you inline your critical CSS, you can preload the rest of your CSS (not great browser support today).
• Inlining and push are best for first time visits, for return visits they can be wasteful. We can use cookies for checking for return visits or make use of Service Worker.
• Time to interactive: time it takes a site to become interactive for the user. We should be aiming for interactivity in under 5seconds on a median mobile phone on 3G. Lower end phones can take a long time to process Javascript after it downloads.
• More weight does not mean more wait. You can prioritize when things load to make pages render much faster.

Keeping Web Sites Fast

• Making a web site fast is easier than keeping it fast. Over time, Web sites will add a number of third party services with unknown performance consequences.
• We can use a number of tools, like Lighthouse, to track performance unfriendly dependencies. Speed Curves will let you set performance budgets and see when things are over. This allows people to ask questions about the costs of what we're adding to sites.
• Varying content and personalization can increase optimizations but they are costly from a performance perspective since they introduce a second meaningful content render. Moving these features to the server-side can help a lot.
• Cloudflare has a solution that allows you to manipulate pages on their server before it comes down to browser. These server-side service workers allow you to adjust pages off the client and thereby avoid delays.
• Homepages and landing pages are often filled with big images and videos. They're difficult to keep performant because the change all the time and are often managed outside of a central CMS.
• For really image heavy pages, we can use srcset attributes to define multiple sizes of images. Writing this markup can be tricky if written by hand. Little helper apps can allow people to write good code.
• Soon we'll have a native lazy load feature in browsers for images and iframes. Chrome has it in testing now and can send aspect ratios before actual images.

In his Third-Party Software and the Fate of the Web presentation at An Event Apart in Denver, Trent Walton talked through the impact of third party scripts on Web sites and how to ensure they don't degrade performance and user experience. Here's my notes from his talk:

• With most client work, no one is paying attention to the impact of third parties on Web sites.
• Third parties are requests on a Web page coming from an external URL. Examples: TypeKit, Google Analytics, etc. People use third parties to get data to make product decisions, earn income (ads, marketing), add content (videos, fonts), add functionality (comments, chat, etc.).
• But third parties can also create issues. Loading scripts and files can really slow things down or provide an inconsistent UI and create privacy issues based on how they handle user data.
• If you care about the final deliverable for a Web site, you need to be aware of the impact of third parties on your product. All the work we do on optimizing images, code, and designs can be quickly outweighed by the addition of third party scripts to a site.
• Starting with the categories of 3rd party scripts helps you get a good sense of why people are using them: Advertising, A/B testing Tools, Analytics, Social Media, CDN, Customer Interaction, Comments, Essential.
• Looking at the top third party requests across the Alexa top 46 sites in the United States shows 213 different domain sources. The average site has 22 different domains. News sites have the most third party domains.
• Several tools can help you understand what's happening with third party scripts on a site. Request Map Generator can help you create a visualization of the different third parties on your Web site to help create awareness of what's happening on your site. Chrome's Lighthouse tool has a similar set of capabilities.
• How do third parties impact end users? Does your site depend on third parties to function? As more people block these components, will it break? Re-marketing can create creepy experiences as content begins "follow" you online.
• Web builders are on the front lines. We can advocate for the right approaches to privacy and data management. Though some of these conversations may be hard, it's our responsibility to end users.
• Web browsers now have tools to help you manage third party scripts like cookies and cross-site tracking. But most people are likely not turing on the stricter versions of these features.
• If you control a site, you can decide what third parties you want to include. But what about sites you don't control? Consider the perspective of your clients/companies and present data that explains the impact of third party on conversion and user experience.
• Establish some standards for third party integrations: determine the value, avoid redundant services, work with a performance budget, comply with privacy policies.
• Audit the third parties on your site and include data that illustrates how they perform against your standards. Compare this audit to competitors in order to set benchmarks or comparisons.
• Get specific insights: there's usually a few instances of third parties that have become redundant, unnecessary, or are blocking page rendering. These wins create credibility and illustrate impact.
• Maintain ongoing conversations with teams to make effective decisions about third parties on your sites.

In his Slow Design for an Anxious World presentation at An Event Apart in Denver, Jeffrey Zeldman espoused the benefits of design that aims to increase comprehension and intentional use. Here's my notes from his talk:

• We live in fast times and care a lot about making things faster for people. In this world, "slow" is often associated with friction. But some things are better slow.
• Fast is best for transactional customer-service designs. We optimize our checkout flows for efficiency and our code for performance. Likewise, service-oriented content must be designed for speed of relevancy. Getting to content like driving directions, return policies, and more should be quick and easy for customers.
• Slow is best for comprehension. Reading slowly helps us understand more of what we read and even transactional sites have some content that we want people to understand more deeply.
• There's lots of resources for site optimization but few for slowing people down so they appreciate and understand our content.
• Legibility means you can read what's on the page. Readability is where the art comes in. You don't need to be a graphic designer to improve readability. When focusing on readability you're focusing on absorption not conversion.
• Improving readability means putting the focus on content and removing distractions. The service Readability optimized Web pages for this by removing ads, third party widgets, and more.
• Considering different reading modes like in bed, at breakfast, on your lap, etc. can trigger ideas for layout and type for sites. For example, big fonts can help you lean back and take in content vs. leaning in and squinting.
• Big type used to be a controversial design choice on the Web but now has been adopted by a number of sites like Medium, Pro Publica, and the New Yorker.
• To be readable: use big type (16px should be your smallest size); use effective hierarchy for type; remove all extraneous elements in your layout; art direction helps you call attention to important content; make effective use of whitespace.
• Art direction can bring unique emotion and resonance to articles online. In a world of templates and scalability, distinct art direction can help people take notice of intentional high value content.
• Macro-whitespace is the bigger columns and padding around content we often associate with high-end luxury brands. Micro-whitespace is the space in between letter forms and between the lines of type. Consider both in your designs
• Ensure your content is branded so it stands out. When all content looks like the same it all appears to have equal value. Have a brand that sticks out to be more trusted.
• With all these techniques we're trying to get people to lean back and have a good "readable" experience on the Web.

In his The New Design Material presentation at An Event Apart in Denver, Josh Clark outlined how designers can integrate Machine Learning and other new technologies into their product designs. Here's my notes from his talk:

• Designers and front-end developers have a role to play in Machine Learning and new technologies overall. But how?
• Sometimes we get fascinated with the making of the product instead of enabling the service of the product (the end user experience). We sometimes care more about using the latest frameworks or technologies than making meaningful experiences.
• The last decade of digital design was shaped by mobile, the next one is already being shaped by machine learning. Machine learning is our new design material, how can/should it be used?
• When you encounter a new design material, ask: what can it do? how does it change us (both makers and society)?
• How can machine learning help us? If we could detect patterns in anything, how can we act on them? Recommendation (ranking results that match a context); Prediction (most likely result); Classification (grouping items into defined categorization); Clustering (discover patterns/categories based on item attributes); Generation (machines can make something).
• Get comfortable with casual (almost mundane uses of machine learning) uses of machine learning. We can add a little intelligence to many of our products using these techniques.
• While there are some early attempts at using machine learning to create Web designers, machines are really best at time-consuming, repetitive, detail-oriented, error-prone, and joyless tasks.
• How can we let people do what they do best and let machines do what they do best. How do we amplify our potential with machines vs. trying to replace things that we can do? Machines can help us focus our time and judgement on what matters (via pattern matching and clustering).
• What can machine learning amplify for us: be smarter with questions we already ask; ask entirely new kinds of questions; unlock new sources of data; surface invisible patterns.
• The job of user experience designers and researchers is to point machine learning at problems worth solving.

Characteristics of Machine Learning

• Machine learning is a different kind of design material. It has different characteristics we can learn.
• Machines try to find patterns in what we do but we're unpredictable and do weird things, so sometimes the patterns machines find are weird. Yet these results can uncover new connections that would otherwise be invisible.
• We need to design for failure and uncertainty because machine learning can find strange and sometimes incorrect results. This is different than designing for the happy path (typical design work), instead we need to design for uncertainty and cushion mistakes by setting the right expectations. Match language and manner to system ability.
• It's better to be vague and correct than specific and incorrect. Machines focus on narrow domains and don't understand the complete world. It's not real intelligence but scaled "interns" or "infinite tem year olds".
• Narrow problems don't have to be small problems. We can go deep on specific medical issue identification or identify patterns in climate change.
• We don't always understand how machine learning works, the systems are opaque. To help people understand what signals are being used we can give people some feedback on what signals inform recommendations or clustering.
• Because the logic is opaque, we need to signal our intention. Designers can help with adding clarity to our product designs. Make transparency a design principle.
• Machine learning is probabilistic. Everything is a probability of correctness, not definitive. We can surface some of these confidence intervals to our end users. "I don't know" is better than a wrong answer.
• Present information as signals, not as absolutes. Point people in a good direction so they can then apply their agency and insights to interesting insights.
• What do we want form these systems? What does it require from us? Software has values embedded in it (from its makers). We don't want to be self-driven by technology, we want to make use of technology to amplify human potential.
• We're inventing the future together. We need to do so intentionally.

How H&M, Zara and Marks & Spencer are buying viscose from highly polluting factories in Asia. By Natasha Hurley.

World food prices have been rising since 2000, but this sped up slightly in 2007, then sharply in early 2008. High prices have hit the urban poor especially hard, and led to food shortages, riots and demonstrations worldwide. IRRI is part of the Consultative Group on International Agricultural Research, a network of international agricultural research institutes started in the 1960s.

Revenue from operations stood at Rs 15,711 crore, up 4.69 per cent against Rs 15,006.3 crore in the corresponding quarter of the previous fiscal.

Net profit for January-March was $376 million, far below than expectations

According to analysts at ICICI Securities, the Rs 8,800 crore-exposure to the telecom sector may cast shadow over the bank's asset quality.

Emkay Global Financial Services expects net sales (revenue) to rise 2.3 per cent quarter-on-quarter (QoQ) and 16 per cent year-on-year (YoY) to Rs 18,552.7 crore

See the best, most relevant frontend courses online to take to succeed as a frontend developer in 2019 and beyond.

GlaxoSmithKline (GSK) is creating a data-focused culture and a global machine-learning team.

London : Routledge, 2017.

Edmonton, Alberta : Brush Education Inc., 2020

Berlin ; New York : Springer, [2007]