Of Gaps, Fillers and Empty Spaces… Fronteers2015 closing keynote

This document provides a list of social bookmarking sites, search engine submission sites, article submission sites, document sharing sites, press release submission sites, and classified ad posting sites. Some of the sites listed include Facebook, LinkedIn, Twitter, Google, Bing, Yahoo, Ehow, Github, Issuu, SlideShare, Dropbox, Box, NPR, Prnewswire, Craigslist, Quikr, Gumtree, and OLX. The document serves as a reference for sites where users can submit and share various types of content online.

The document discusses the need for ubiquitous and holistic information architecture across channels to create integrated experiences for users. It notes that information is blurring the lines between digital and physical experiences, and that users expect consistency as they transition between platforms. To meet these expectations, information architecture must be designed holistically rather than by channel, and must focus on the overall user journey rather than individual touchpoints. Bridges between experiences like on-ramps and off-ramps are needed to make information architecture truly integrated.

The document discusses digital storytelling, which it defines as "telling stories with digital technologies." It provides various definitions of storytelling, noting it involves conveying messages, experiences, and ideas from one person to another. It also lists different forms of digital tools and media that can be used to facilitate digital storytelling, such as videos, images, and audio. The document emphasizes how digital storytelling allows for creative self-expression and sharing information with others through technology.

Presented by Beth Tribe, Michael Sauers & Bobbi Newman @ Computers in Libraries 2009 on 30 March 2009.

With the adoption of responsive design, we’re finding that our pixel-perfect content is no longer being placed in pixel-perfect boxes on pixel-perfect websites. Placeholder content no longer suffices during development. Copy-and-paste doesn’t work in migrating between designs. Rather, website design is more strongly informed by our content than ever before. With these changes we need to rethink how content affects our development workflow as well as understand how content and messaging affect layouts. • Learn why you need to be an advocate for content at all phases of a project. • Explore the fundamental content types and content rules that will shape how your content flows and is viewed by visitors. • Learn how content choreography can help you keep your most important message the focus of your site.

This presentation was given at Thursdays At Starling at Wake Forest University on February 3, 2011. This presentation is about the intersection of libraries, technology, and education and the future of libraries.

While the community (rightly) celebrates the tremendous growth of WordPress as a platform, there’s a significant disconnect between what community members know about WordPress and what folks outside the community know. Getting outside the WordPress bubble – by participating meaningfully in other conferences, conversations, and communities – helps bring new ideas into our community and also helps us bring WordPress into new contexts.

This document summarizes key lessons and ideas from the Airport Social Media Summit. Some of the main points include: using Twitter to share breaking news and engage customers; focusing on quality photos that showcase planes and the airport; listening to customers and taking action on their feedback; and being entertaining, timely and unexpected in social media posts. The document also provides links to resources from summit presenters.

This document discusses the evolution of learning and technology from cave paintings to modern eportfolios. It provides examples of how students can use eportfolios to store, track, reflect on, and showcase their learning and experiences over time. The document suggests that eportfolios allow for continuous personal development and reflection, unlike traditional learning management systems which focus more on course content.

Using real data to create more authentic and empathetic products - from a talk at an internal Cisco design conference

This document summarizes Anne Helmond's research mapping the changing blog practices in the Dutch blogosphere from 1995 to 2005. It discusses how early Dutch blogs were primarily "linklogs" and "lifelogs" that focused on linking to other blogs and sharing personal content. Over time, the blogosphere shifted to "platformlogs" as more blogs moved to social media platforms like Facebook. The research aims to analyze the hyperlink networks between blogs annually using the Internet Archive to track this evolution from independent blogs to platform-centered blogs.

Not sure what content strategy is? Don't care? Hopefully this talk will change your mind... Forget boring case studies - instead I'll be looking at content strategy in the real world, particularly an area near and dear to my (and maybe your) heart - online dating! From a year in the wilds of Plenty of Fish and OkCupid, find out what on earth we content strategists do, why it matters, and most importantly how it can help you get to first base.

This document discusses predictions for the future of WordPress and the role of users in shaping its future. It explores different types of WordPress platforms for blogs, CMS, enterprises and frameworks. The document encourages users to get involved by contributing as developers, designers, or community members to help create the kind of WordPress and community they want.

The document introduces the speaker as Patti and says she has 5 minutes to tell her story. Patti then says she is torn between two lovers, Macintosh and Microsoft. She mentions having used various online tools like iNing, iJing, iMoodle, and Google. Patti wanted to become a teacher. It provides links to the speaker's blog and Doodlekit page for more information and credits the sources of various pictures used in the presentation.

This document discusses instructional technology and how it requires teamwork across various departments on a campus. It lists many tools that instructional technology teams use to support teaching and learning such as games, clickers, podcasts, just-in-time instruction, blogs, webinars, tutorials, and workshops. It also illustrates the collaborative process needed with a step-by-step diagram showing the roles of Amy, Lynda, Beth, and Hannah on the instructional technology team.

This document is the result of a common student project as part of our advanced Master Seminar in “Logistic Case Studies” at the University of Applied Sciences Konstanz, Department of Business Administration The project conducted by Prof. Dr. Michael C. Hadamitzky, Center of Supply Chain Management and Logistics comprehends an external analysis of AMAZON.COM - the pioneer of disruption and digitalization The project gave us the opportunity to examine the latest developments in Value Chain Management and digital innovation.

created for staff at CVL Resources https://sites.google.com/site/cvltraining/intro-to-cloud-computing

- libSass is a C/C++ implementation of Sass that compiles Sass much faster than the Ruby implementation. It allows Sass to be used by more developers and integrated with JavaScript build tools. - Eyeglass is a Node.js module that allows Sass modules to be distributed through npm and imported into Sass files. It provides file system access and tools for defining Sass functions in JavaScript. - Eyeglass aims to recreate popular Compass features like sprites and make them compatible with libSass and distributed through npm modules. This will provide an ecosystem for shared Sass code and assets without relying on Ruby.

Presentation on digital collaboration and music given by Lisa Welchman at Fronteers 2015 in Amsterdam, October 8.

Test-driven development is generally regarded as a good move: it should result in simple decoupled design, your tests tend to cover behaviour not methods, and far fewer bugs. However, just getting unit tests in on a real, commercial project is hard - switching to TDD is even harder. Often you can start a project with good intentions and coverage, then the deadline looms and the tests go out then the hacks come in. So, instead of beating ourselves up about not being perfect let's look at an interative approach to adopting TDD principles. We'll look at tactics for selling TDD to your client, boss and colleagues. This talk will also cover methods for making TDD easier for you by showing you what tools you can use to integrate it into your development environment. In the project itself, we'll examine how we can make small but permanent steps towards full TDD, without losing that progress when deadlines hit. We'll also cover a few methods for learning on your own time and how the whole process can actually be made quite enjoyable.

With more and more sites falling victim to data theft, you've probably read the list of things (not) to do to write secure code. But what else should you do to make sure your code and the rest of your web stack is secure ? In this tutorial we'll go through the basic and more advanced techniques of securing your web and database servers, securing your backend PHP code and your frontend javascript code. We'll also look at how you can build code that detects and blocks intrusion attempts and a bunch of other tips and tricks to make sure your customer data stays secure.

Talk from 4Developers '12 and PHP Barcelona '11 It’s fun to architect your application to handle millions of pageviews, but in reality that’s time where you could be adding features. We’ll examine some practical solutions for designing your platform to deal with increasing traffic and how to add those features on an incremental basis. This will take us through options for scaling the code and additional methods for scaling the infrastructure.

The document discusses circuit breakers and how they can be used to protect systems from failures. It introduces the basic concept of a circuit breaker and its states. It then explores different modules and ways circuit breakers could be enhanced, such as having processes coordinate, automatic monitoring of system health, different signals of unhealthiness, and approaches to recovery. Key questions are raised about how circuit breakers could be implemented including whether processes should coordinate, who determines unhealthiness, and how to safely test new circuit breakers.

The document consists of a series of tweets from the account @synedra with the hashtag #FILive. Each tweet is followed by a photo credit citing various Creative Commons licenses. The document promotes live footage from an event but provides no other context or details about the event itself.

Application developers support unprecedented rates of change – functionality must rapidly evolve to meet changing customer needs and to respond to competitive pressures while user populations can grow dramatically and unpredictably. To address these realities, developers are selecting document-oriented databases for schema flexibility, scalability and high performance data storage. In this session, we will get hands on with Azure’s NoSQL document database service. Azure DocumentDB offers full indexing of JSON documents, SQL query capabilities and multi-document transactions. Learn how to get started with Azure DocumentDB and hear about some of the recent improvements to the service.

We browse the Internet. We host our applications on a server or a cloud that is hooked up with a nice domain name. That’s all there is to know about DNS, right? This talk is a refresher about how DNS works. How we can use it and how it can affect availability of our applications. How we can use it as a means of configuring our application components. How this old geezer protocol is a resilient, distributed system that is used by every Internet user in the world. How we can use it for things that it wasn’t built for. Come join me on this journey through the innards of the web!

The document discusses various browser security mechanisms that can help improve the security of web applications. It describes mechanisms like subresource integrity, which prevents tampering of external assets; referrer policy and noopener, which help prevent information leaks; and Content Security Policy, which helps prevent cross-site scripting attacks. It also discusses using HTTPS, HTTP-only and secure cookies, sandboxed iframes, and HTTP Strict Transport Security to further enhance security. The document provides explanations and examples of how to implement many of these browser-enforced security mechanisms.

Practical tips for dealing with projects involving legacy code. Covers investigating past projects, static analysis of existing code, and methods for changing legacy code. Presented at PHP Benelux '10

The presenter examines the ups & downs of adopting a microservices architecture and discusses why, in most cases, the pros outweigh the cons. In this presentation, participants see how to build & integrate microservices using popular open source tools and risks & mitigation strategies (including load balancers, circuit breakers, tests, & more) to increase software quality.

Presented at FITC's Web Unleashed 2016 in Toronto by Haris Mahmood, Shopify Overview The content publishing industry took the world by storm some years ago by providing its users visual tools to update, manage, and publish their content. Large players have existed for quite some time, but now find themselves on uncertain grounds. Newer, smaller players are also entering the space with new and innovative ideas. This talk aims to review the industry’s history, examine how it stands today, and take a deep dive into its future. Objective To explore the content publishing industry’s past and present, and take a deep dive into its future. Target Audience Web developers, content publishers, freelancers, agencies Five Things Audience Members Will Learn The history of the content publishing industry The landscape today The limitations and strengths of the various offerings Directions the industry is progressing to A roadmap of the future for the content publishing industry FITC produces events for digital creators in Toronto, Amsterdam, NYC and beyond Save 10% off any of our events with discount code 'slideshare' Check out our events at http://fitc.ca or follow us at https://twitter.com/fitc

This document summarizes a presentation about DNS (Domain Name System) for developers. It discusses the basics of how DNS works to map domain names to IP addresses, different DNS record types like A, CNAME, and MX records, DNS zones, security considerations like cache poisoning and DNSSEC, using DNS for failover, load balancing, and CDNs, storing configuration data and doing service discovery in DNS, and some unconventional uses of DNS like tunneling HTTP and IP traffic over DNS. The presentation provides examples and demonstrations of these DNS concepts and techniques.

Redis is an open source, in-memory key-value data store that can be used as a cache or database. It supports various data structures like strings, hashes, lists, sets and sorted sets. Redis has features for transactions, pub/sub messaging and scripting. Data can be sharded across multiple Redis instances for large datasets or high throughput needs. Common use cases include caching, sessions, pub/sub, rate limiting and autocompletion.

Every digital marketer should add a governance layer to their digital strategy. Only an integrated approach that ties organizational change to your digital strategy, will help you move forward.

This document discusses securing micro-services through centralized authorization using JSON Web Tokens (JWTs). It proposes storing permissions data in the JWT payload to simplify authorization checks across services. The JWTs can be issued by an identity provider like Okta or Active Directory, and signed to ensure integrity. Services would verify the JWT signature and check the included permissions to authorize actions. This approach aims to make authorization centralized, simple, scalable, and easily manageable compared to existing authorization solutions.

This document discusses moving from a monolithic architecture to microservices. It notes some advantages of microservices like improved tools, language and library usage, and faster deployment times. However, it cautions against simply following "microservices mantras" and stresses the importance of being ready to receive attacks rather than relying on the likelihood they won't occur. Microservices should share nothing and start independently, but still aim for high availability and responsiveness as a system. The document provides additional reading resources on monoliths, microservices, and systems thinking.

Reveal.js is an HTML presentation framework that allows users to create beautiful presentations using HTML. It has features like vertical slides, nested slides, Markdown support, different transition styles, themes, slide backgrounds, images, video, tables, quotes, and linking between slides. Presentations can be exported to PDF and custom states and events can be triggered on each slide. The framework is touch optimized and works on devices like mobile phones and tablets.

The document discusses how developers have become disconnected from users as technology has advanced. It argues that developers should focus on building interfaces that are simple, human-centered, and empower users rather than just improving tools. Machine learning and AI can be used to build helpful interfaces, but developers must focus on the human experience and inclusive design. The talk aims to inspire developers to use their skills to improve people's lives rather than just profit or automation.

A talk about innovation and impostor syndrome. A talk about the next web that's coming and the technology we have, but forgot.

Great design isn’t about beauty; it’s about knowing the right questions to ask, uncovering the right places to look, and agreeing on the right problems to solve. At ThoughtWorks Live Australia 2016, Stephanie Rieger (Director of Design & Strategy at Yiibu) talked about three mindsets that combine design, business strategy, and technology to drive growth and embed experience design within your organisation.

Chris Heilmann gave a keynote address at SmashingConf discussing issues with modern web development. He expressed frustration with frameworks prioritizing new features over compatibility, developers focusing only on the latest technologies and platforms, and the web becoming fragmented across closed platforms. However, he advocated improving support for older browsers through tools like Enterprise Mode on IE, prioritizing performance, accessibility, and building for all users rather than just those on new devices.

Chris Heilmann gave a keynote address at SmashingConf discussing issues with modern web development. He expressed frustration with frameworks prioritizing new features over compatibility, developers focusing only on the latest technologies and platforms, and the lack of support for older browsers in enterprise environments. However, he argued web developers should focus on building accessible products for all users, request features to improve compatibility, and make the web enjoyable for everyone again.

Chris Heilmann gave a keynote address at SmashingConf discussing issues with modern web development. He expressed frustration with frameworks prioritizing new features over compatibility, developers focusing only on the latest technologies and platforms, and the lack of support for older browsers in enterprise environments. However, he argued web developers should focus on building accessible products for all users, request features to improve compatibility, and make the web enjoyable for everyone again.

The document summarizes key points from a presentation given by Chris Heilmann at SmashingConf NYC in June 2015. Some of the main ideas discussed include: - The web has become overly complex with too many frameworks, tools, libraries, and content being produced. - As developers, we tend to build for ourselves and our peers rather than for general users, focusing more on recognition than usability. - The assumptions we have about users' knowledge and engagement levels with technology often do not match reality. - Despite advances, the modern web experience can be cluttered, slow, and difficult for many users. - There are opportunities to simplify and improve the web by removing unnecessary code and technologies.

The document discusses the evolution of the web from progressive web apps to native mobile apps and back again to progressive web apps. It notes that early mobile web faced issues like small screens, poor connectivity and unreliable browsers, leading to the rise of native apps. However, app distribution issues like slow updates and the "walled garden" approach of app stores have led to a renewed interest in progressive web apps that work offline but do not require app stores, allowing for more open distribution like the original web.

The document discusses key lessons learned from Walt Disney World about attention to detail, customer service, and creating a magical experience. It emphasizes that every person plays an important role and each small detail matters. Disney World succeeds by making customer service a top priority, rewarding employees, and maintaining high standards of cleanliness, safety and customer satisfaction.

Keynote presentation for Keene State College Faculty Technology Showcase (Feb 19, 2011). Join the Revolution! http://secretrevolution.us/ Audio available at http://cogdogblog.com/wp-content/audio/keene-state-2011.mp3

The document summarizes key points from a talk given by Chris Heilmann at SmashingConf NYC in June 2015. Some of the main ideas discussed include: how developers have created an echo chamber focused on tools and recognition rather than users; how the web has become cluttered and broken despite new technologies; and how detecting users through user-agent sniffing and reliance on non-standard features has perpetuated problems. The talk calls for a renewed focus on users, standards compliance, and cleaning up old and unnecessary code to improve the web.

This document discusses designing seamless customer experiences across digital and physical channels. It tells a story of a car accident victim's frustrating experience trying to get their car repaired due to a lack of integration between their insurance company's digital and physical systems. The document argues that as the physical and digital worlds collide, organizations must design holistic, interactive experiences that satisfy customers' information needs whenever, however, and wherever they engage with a brand. It encourages attendees to open their eyes to opportunities to improve customer experiences through better organization of information.

1) The document introduces the concept of "Rawk The Web", a manifesto aimed at increasing diversity in the tech industry by encouraging more voices from varied backgrounds. 2) It notes a lack of diversity at many tech conferences and calls for more inclusion to foster innovation. 3) The manifesto provides guidance on getting started, including getting clear on goals, gaining inspiration from others, getting support, and developing a plan to create content, build connections, propose ideas, and promote one's work.

The AMP Project (Accelerated Mobile Pages) has been launched as an open source initiative between tech companies, search engines, publishers, CRM providers, CMS providers and social media platforms as a solution to speed up the mobile web. What is AMP? Why is it needed? How does it achieve its speed? Where is the project at now? What does the future hold for AMP? To AMPFinity and Beyond

1. The document discusses the rise of social media and its potential uses for prevention work. It provides examples of how social media has been used successfully by various prevention organizations to engage communities and youth. 2. Various statistics are presented showing high rates of internet, email, and social media use among teens and adults in the US. Different social media tools are described that could be used to connect, listen, engage, and collaborate with communities. 3. The presentation emphasizes that social media is here to stay and that prevention professionals need to embrace new ways of communicating online to remain relevant and engage communities. Case studies of successful social media use in prevention are provided.

My session from AFP congress, on how to be ready to discover and expand on current events that may or may not go viral. The session also teaches how to make sure you are in a positision where your organisation can try to be the one chosen when something like the Ice Bucket Challenge happens. Oh, and there's a rant about slacktivism in there too.

The document discusses how to maximize search engine results page (SERP) potential by enhancing website listings with rich snippets. It explains what rich snippets are, why they are important for increasing click-through rates, and how to implement different types of rich snippets like reviews, recipes, and videos using microdata, microformats, or RDFa. Tools for testing rich snippets are also recommended.

Opening keynote for the 2010 Canadian eLearning Conference, Edmonton, Alberta. Tell everyone to join the revolution at http://secretrevolution.us

Christian Heilmann gave a talk on hacking and innovation at a university hack challenge. He defines hacking as altering systems to do what you want using available resources, and sees it as a way to have fun and drive unrestrained innovation. He encourages attendees to find something annoying with current systems and build workarounds. To hack effectively, one needs access to data sources, the data itself, and ways to reach users. He provides examples of his own hacks that make systems more accessible or filter data for specific uses. The talk aims to show attendees their potential and get feedback on explanations of development resources.

This document discusses low-budget marketing strategies and tactics. It provides numerous examples of companies and organizations that were able to successfully market themselves and drive results with little to no money spent. Some of the key strategies mentioned include leveraging relationships, bartering or exchanging services, creating engaging content, finding unconventional partnerships, utilizing free online tools and communities, and thinking creatively about how to gain exposure and attention through stunts or humor. The overall message is that marketing does not require a large budget if you have the right strategies, skills, assets, or willingness to invest time and effort.

Chris Heilmann gave a talk celebrating beautiful web sites but noted that many sites could be more optimized. He highlighted that the average site is over 2 MB in size, with images making up over 1 MB of that. Many sites use unnecessary libraries, send high resolution images to all devices, and include autoplay videos without checking connection speed. However, newer browser capabilities like Flexbox, Service Workers, and camera/microphone access provide opportunities. Sites should cut unnecessary code, optimize images, and leverage new technologies to create accessible experiences for all types of users on today's capable browsers.

We are obsessed with coding and creating automated workflows and optimisations. And yet our final products aren't making it easy for people to use them. Somewhere, we lost empathy for our end users and other developers. Maybe it is time to change that. Here are some ideas.

This document discusses ways to improve how web developers learn best practices through browser and tooling improvements. It suggests that linting and inline insights directly in code editors could help prevent mistakes by flagging issues early. A tool called webhint is highlighted that provides one-stop checking and explanations of hints related to performance, accessibility, security and more. The document advocates for customizing hints based on a project's specific needs and environment. Overall, it argues for accelerated learning through context-sensitive, customizable best practices integrated into development workflows.

This document discusses privilege in the context of social media and the internet. It acknowledges privileges like internet access, the ability to communicate, and supportive online communities. It warns that machine learning and algorithms risk creating echo chambers and guided messaging if they are not kept in check by human curation. The document advocates taking back the web for decent, thinking and loving humans and using privileges to help others gain access to learning, communication, and communities.

JavaScript is a bigger world than a language these days. Time to take stock and find happiness in that world.

This document discusses artificial intelligence and how it can help humans. It covers that AI is not new, having originated in the 1950s, and is now more advanced due to increased computing power. It also discusses how AI utilizes pattern recognition and machine learning. The document then covers several applications of AI including computer vision, natural language processing, sentiment analysis, speech recognition/conversion and moderation. It notes both the benefits of AI in automating tasks and preventing errors, as well as the responsibilities of ensuring transparency and allowing people to opt-in to algorithms.

The document discusses concerns about the perception and realities of coding careers. It expresses worry that coding is seen solely as a way to get a job rather than as a means of problem-solving. While coding can provide fulfilling work, the document cautions that the need for coders may decrease with automation and that the role may evolve from coding to engineering. It suggests a future where machines assist with repetitive coding tasks and people focus on delivering maintainable, secure products with attention to privacy and user experience.

PWA are a hot topic and it is important to understand that they are a different approach to apps than the traditional way of packaging something and letting the user install it. In this keynote you'll see some of the differences.

This document discusses privilege in technology and perceptions of technology workers. It acknowledges the privileges that tech workers enjoy, such as access to resources and high demand in the job market. However, it also notes problems like peer pressure, lack of work-life balance, and imposter syndrome. Both tech workers and the public have skewed perceptions of each other - tech workers feel others do not appreciate or understand their work, while the public sees tech workers as antisocial or caring only about profit. The document encourages taking small steps to improve the situation, such as being kind to oneself, considering others, sharing knowledge, and focusing on quality over quantity of work.

The document provides five ways for JavaScript developers to be happier: 1) Concentrate on the present and focus on creating rather than worrying about the past or future. 2) Limit distractions by streamlining your development environment and using an editor like VS Code that consolidates features. 3) Make mistakes less likely by using linters to catch errors as you code. 4) Get to know your tools better like debuggers to avoid console.log and gain insights to build better solutions. 5) Give back to others in the community by being helpful rather than causing drama.

The document discusses progressive web apps (PWAs) and provides suggestions for improving them. It notes that while PWAs aim to have engaging, fast, integrated, and reliable experiences like native apps, they still have room for improvement in areas like speed, integration, and reliability. It emphasizes that PWAs should adhere to web best practices and provide actually useful experiences rather than just focusing on technical features. The document encourages helping the PWA effort by providing feedback, using and contributing to tools, keeping messaging up-to-date, and promoting high-quality examples.

Chris Heilmann gave a talk at BTConf in Munich in January 2018 about machine learning, automation worries, and coding. He discussed how coding used to refer to creative programming within technical limitations but now often refers to programming for work. He addressed common worries about new technologies and dependencies, and argued that abstractions are not inherently bad and help more people build products together through consensus. The talk focused on using tools to be more productive and enabling rather than seeing them as dangers, and creating solutions for users rather than fighting old approaches.

The document provides advice and encouragement for someone starting out with JavaScript development. It discusses how JavaScript can be used in many environments like browsers, apps, and servers. It recommends resources like MDN and tools like linting to help avoid mistakes. It emphasizes that this is an exciting time for JavaScript and advises setting priorities and standards, being involved in the community, and bringing new voices and perspectives.