Smashingconf nyc-final

The document discusses moving a library to adopt Web 2.0 technologies and tools. It outlines 12 steps for getting organizational buy-in and determining the scope and parameters of training staff. It describes a training program conducted at the Oakville Public Library where staff were trained on blogs, RSS feeds, social bookmarking, wikis, instant messaging and social networks over two sessions. Staff feedback was positive and most completed the optional program. It recommends follow up sessions to maintain momentum and encourage use of the new technologies.

This document discusses standards for building websites and applications across different devices and browsers. It notes that many companies have solutions for implementing standards like HTML5. It provides demos and memos on using HTML5 basics safely and developing for the future by utilizing what browsers can do on the client side. It also includes various resources for learning more about HTML5, checking browser support, and moving the web forward through open standards.

My presentation about Semantic We for distributed social networks. Given at Web Directions South 08. http://south08.webdirections.org/

What you should know about devops? Slides from presentation I gave during 10th J-Labs Academy meetup.

This keynote show cases the trajectory of Ortus Solutions since its founding in 2006 and the future of Ortus flagship products ColdBox, CommandBox and FORGEBOX

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 future technologies of the web, and how our time is equally well spent cleaning up the web of now.

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.

A quick reminder of how we make it too complex for ourselves as web developers these days, and how changes in the browser world mean mainly one thing: build to standards.

Connecting open source software and web accessibility projects with some ideas behind physical disability hacks.

This document discusses progressing web development and applications. It talks about some common criticisms of the web, including that browsers differ too much and the web is too flexible. However, it argues that browser differences allow for innovation and flexibility is one of the web's strengths. It promotes an approach of focusing on capabilities rather than browsers. The document also discusses progressing technologies like service workers and progressive web apps that can make applications work offline and feel more like native apps while still being web-based. It concludes by arguing the web is not going away and is a great platform to build upon.

Codemotion Rome 2015 - As developers, we know things break. We also know how to fix them. What we don't do is do this efficiently. Instead we seem to have a perverse fascination telling one another and the world how broken things are. If you look, however, how cool technology is these days, what tools we have at our disposal and the latest changes in the last excuse we had: "What about IE?" it is time to stop complaining and get to work. Our job is to build things that people want to use. Not to complain about our tools. This is what people looking for excuses do. We're better than that.

The document discusses tensions in web development between new and old approaches. It notes clashes between techniques and tools, and how developers have become focused on engineering over user experience. However, it argues developers should care more about creating excellent, long-lasting work by focusing on the essentials and giving more "shits" about quality over short-term trends or competition. Developers are encouraged to build for everyone using minimum viable tools and talents.

The document discusses issues with the current state of the web including slow page load times and large file sizes. It suggests that overuse of third-party scripts and advertisements have degraded the user experience. The author calls for simplifying web pages, prioritizing users over technology, and increased collaboration between browser makers and web developers to rebuild the web. Simplifying code, updating outdated libraries, and assuming unknown browsers are capable instead of limited can help improve the web.

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

It is easy to think what we have as developers is what people use and that lead us to make the web bloated.

- The web development community needs to focus more on quality, accessibility, and standards compliance rather than constant innovation and new techniques. Browsers have come a long way but still struggle to balance implementing new features while maintaining compatibility. - Web pages have gotten slower and larger over time due to an emphasis on appearance over performance and a reluctance to drop legacy techniques. Many modern solutions make the web more complex without real benefits. - Developers should provide better feedback to browsers, demand stronger support for baseline functionality, and stop catering to outdated browsers to encourage continued progress toward an interoperable web. Simpler, more sustainable approaches would benefit all.

We can be brilliant developers, but we won’t succeed—and won’t lead our organizations to succeed—without a new perspective (if you will) and new assumptions about the components of the “technology ecosystem” that are fundamentally critical to our success. This includes the operators, QA team, DBAs, security folks, and even the pure business contingent—in most cases, each of these individuals and groups plays a critical role in the success of what we create and give birth to as developers. What we do in isolation might be genius, but if we insulate ourselves—especially with arrogance—from these colleagues, neither our code nor our organizations will realize their full potential, and most will fail. The bottom line is that our old ways are no longer viable, and as the elite within our industry, we will be the leaders and heroes who discard old assumptions and adopt a new perspective in this exciting journey to digital transformation—where the impossible can become reality.

The document discusses the evolution and future of web experiences across different devices and platforms. It notes how early web platforms lacked capabilities for rich experiences compared to native apps, but how modern web standards now provide access to device sensors, graphics, and other features. This allows the web to deliver more engaging experiences. The document advocates for building experiences that are responsive across different environments and devices, and pushing the capabilities of the web platform to better deliver digital services anywhere.

Creating Your Own Personal Learning Network presented by Cal Kjeller at Summer Professional Development Institute, Whitehall, PA

The way people experience the web will see dramatic change in response to new tools, expectations and constraints in the coming years. This session will highlight some major forces shaping our medium and lead us in thinking about how we should expect to evolve what we deliver in light of changes in hardware, mobile, wearable, data, and software among others. We will look to parallels in architecture, aircraft and other technologies and suggest future trends that will evolve. Attendees will gain a better understanding of the changing nature of our environment and the impact of all of these forces and is appropriate for anyone working in this field who is interested in what the future may bring. Attendees will leave ready to make their own decisions about how best to embrace these forces in their own work.

My presentation covering several ways how you can use nowaday's free web offers to save money and time for your company and thus securing your job.

Dans cette présentation, Chris Heilmann nous parlera des problèmes liés à l'adoption de standards du web récents, et décrira des façons de contourner ces difficultés. Un exemple simple est le manque de prise en charge native de l'audio et de la vidéo, et les problèmes des implémentations actuelles. La session illustrera concrètement comment régler des problèmes a priori sans solution en les attaquant sous un autre angle. Il s'agit essentiellement de trouver une façon pragmatique de vendre, implémenter et utiliser les standards plutôt que d'attendre que le marché adopte des technologies dont l'utilisation devrait être d'une évidence complète. Présentation originale : http://www.slideshare.net/cheilmann/working-in-the-now-presentation/

If you're running a tech start-up, it's essential that you familiarize yourself with the fundamentals of web development. Ultimately knowing how to "talk to the talk" will help you communicate better with developers, and overall just look really cool. In this hour and a half long workshop, Chris Castiglione, experienced developer and founder of One Month Rails, will tackle some development principles and answer questions to get you on the right path, such as, "Front-end vs. Back-end?", "Is UX necessary for my project?", "What is this Javascript function thingy, and why am I passing it strange math equations to it?" He will also have you coding a bit yourself! Leading a development team (without being a developer yourself) can sometimes feels like talking about dancing, and so this is an interactive and friendly environment in which to learn the basics. Come with questions, and a desire to have fun! OneMonth.com OneMonthHtml.com OneMonthRails.com

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.

Keynote at halfstackconf 2017 discussing the falsehood of the idea that in order to survive the automation evolution everybody needs to learn how to code. Machines can code, too.

Progressive Web Apps (PWAs) can provide app-like experiences through the web by making web content fast, reliable and engaging. While PWAs may not be necessary for all projects, they can help clean up and speed up current web-based projects. PWAs leverage new web capabilities like service workers to work offline, load fast, and improve the user experience without having to meet all the requirements of native apps.

This document discusses progressive web applications (PWAs) and their advantages over traditional native mobile applications. PWAs use modern web capabilities like Service Workers to deliver native-like experiences to users. Some key benefits of PWAs include their ability to work across platforms, have smaller file sizes for faster loading, support offline use, and provide simple update mechanisms compared to native apps. While PWAs do not have full access to device capabilities like native apps, they allow delivering app-like web content to users in a more accessible and reliable manner than traditional web pages.

Keynote at PNWPHP covering Machine Learning and How we should go about using it to build human interfaces.

This document discusses progressive web apps (PWAs). It notes that PWAs aim to make web apps feel like native mobile apps by being discoverable, installable, linkable, safe, responsive and progressive. The document outlines some key characteristics of PWAs, including that they need to be served from secure origins and have app manifests. It also discusses some common misconceptions around PWAs and notes that as PWAs improve, they will continue to blur the line between web apps and native mobile apps.

This document discusses the differences between CSS and JavaScript and when each is most appropriate to use. It argues that CSS is often underestimated in favor of JavaScript solutions. CSS has advanced significantly with features like calc(), media queries, animations/transitions, flexbox, grid, variables and more. These powerful features allow many tasks to be accomplished with CSS alone without needing JavaScript. The document encourages embracing the "squishiness" of the web and considering CSS more when building interfaces.

This document contains the transcript of a presentation by Chris Heilmann on web development. Some of the key points discussed include: - The benefits of progressive enhancement and using HTML, CSS, and JavaScript together to build robust and accessible websites. - How limitations in early design can foster creativity. - The importance of error handling and defensive coding practices. - Embracing new technologies like Service Workers and Manifests to build Progressive Web Apps. - Rethinking the idea that JavaScript is unreliable and should not be depended on, as modern browsers have made it a capable tool.

“If Tetris has taught me anything, it’s that errors pile up and accomplishments disappear” is a common quote and it seems we’re living this to its full extend as web developers. We fail to celebrate the successes we have and the tools that are at our disposal but we’re never short of finding reasons why things don’t work. We also tend to pile on technology on technology to solve problems that may actually not exist and thus clog up the web. In this talk Chris Heilmann wants to remind us what we achieved and how we should celebrate it and how we should stop trying to solve problems that are simply beyond our control.

How to use generative AI tools like ChatGPT and Gemini to generate story ideas for investigations, identify potential sources, and help with coding and writing. A talk from the Centre for Investigative Journalism Summer School, July 2024

we may assume that God created the cosmos to be his great temple, in which he rested after his creative work. Nevertheless, his special revelatory presence did not fill the entire earth yet, since it was his intention that his human vice-regent, whom he installed in the garden sanctuary, would extend worldwide the boundaries of that sanctuary and of God’s presence. Adam, of course, disobeyed this mandate, so that humanity no longer enjoyed God’s presence in the little localized garden. Consequently, the entire earth became infected with sin and idolatry in a way it had not been previously before the fall, while yet in its still imperfect newly created state. Therefore, the various expressions about God being unable to inhabit earthly structures are best understood, at least in part, by realizing that the old order and sanctuary have been tainted with sin and must be cleansed and recreated before God’s Shekinah presence, formerly limited to heaven and the holy of holies, can dwell universally throughout creation

In Odoo 17, confirmed and uninvoiced sales orders are now factored into a partner's total receivables. As a result, the credit limit warning system now considers this updated calculation, leading to more accurate and effective credit management.

Curricuum Map in Grade 7 English aligned with matatag

Now we can take look into how to configure time off types in odoo 17 through this slide. Time-off types are used to grant or request different types of leave. Only then the authorities will have a clear view or a clear understanding of what kind of leave the employee is taking.

Howe Writing Center - Orientation Summer 2024

This book for Allied Health Sciences, DPT and BS Nursing for 1st and 2nd semester.

...

NLC Grade 3 PPT week 1 ................................................

In Odoo, separate discount account can be set up to accurately track and manage discounts applied on various transaction and ensure precise financial reporting and analysis

In Odoo, the pivot view is a graphical representation of data that allows users to analyze and summarize large datasets quickly. It's a powerful tool for generating insights from your business data. The pivot view in Odoo is a valuable tool for analyzing and summarizing large datasets, helping you gain insights into your business operations.

COM322 Assessment - Story 2

"DANH SÁCH THÍ SINH XÉT TUYỂN SỚM ĐỦ ĐIỀU KIỆN TRÚNG TUYỂN ĐẠI HỌC CHÍNH QUY NĂM 2024 KHỐI NGÀNH NGOÀI SƯ PHẠM"

Front desk officers are responsible for taking care of guests and customers. Their work mainly involves interacting with customers and business partners, either in person or through phone calls.

(𝐓𝐋𝐄 𝟏𝟎𝟎) (𝐋𝐞𝐬𝐬𝐨𝐧 𝟏.𝟎)-𝐅𝐢𝐧𝐚𝐥𝐬 Lesson Outcome: -Students will understand the basics of gardening, including the importance of soil, water, and sunlight for plant growth. They will learn to identify and use essential gardening tools, plant seeds, and seedlings properly, and manage common garden pests using eco-friendly methods.

Here we are going to discuss how to store data in Odoo 17 Website. It includes defining a model with few fields in it. Add demo data into the model using data directory. Also using a controller, pass the values into the template while rendering it and display the values in the website.

NLC Lessons Grade 10