Erase and Rewind - Open Web Camp 2015

This document discusses JavaScript and ES6. It covers some of the historical issues with JavaScript, the learning process, dependency on libraries/frameworks, and new features in ES6. It also discusses transpiling code to support older browsers, standards and interoperability challenges, and new JavaScript engines like ChakraCore that could break monopolies.

- 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.

This document discusses challenges facing web developers and proposes ways to address them in a responsible manner. It notes that web principles of maintainability, accessibility, and flexibility are often challenged by a focus on visuals over content and a belief that things should look the same everywhere. It argues that developers internalize these challenges too much by releasing things too quickly without proper crafting. The document calls on developers to be more responsible for their work by always questioning authority and avoiding blind faith in new technologies or browser innovations. It stresses the importance of focusing on users over other priorities and addressing issues through love rather than punishment.

The document discusses the history and future of JavaScript and Node.js. It covers the promises and problems of JavaScript, how Node.js helped address some issues but created new ones like monoculture. It then discusses how ES6 and the ChakraCore engine can help modernize JavaScript and break the Node monoculture by providing an additional engine option. The author hopes for less drama, embracing change, simplicity, inclusiveness, and prioritizing users over developers.

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.

This document discusses upgrading JavaScript to ES6 and using TypeScript as an alternative. It covers some of the old issues with JavaScript, the learning process, tooling challenges, and dependency on libraries/frameworks. ES6 promises to address many of these with new features, but browser support is still evolving so transpilation is needed. TypeScript is presented as a shortcut that provides type safety and class-based syntax without transpilation overhead. The document also mentions the ChakraCore JavaScript engine as a promising new development.

Microsoft has become more open in recent years by open sourcing many products, making products cross-platform, and making training materials openly available. This open approach makes business sense for Microsoft as it attracts developers, allows employees flexibility, and taps into outside skills. Examples of Microsoft's success with open source include the Edge browser, Visual Studio Code editor, TypeScript transpiler, and ChakraCore JavaScript engine. The presenter encourages attendees to help promote Microsoft's open products and projects through conference talks, writing, and contributing translations and code.

“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.

In the last year or so things changed drastically. Everybody uses an iPhone6, is connected 24/7 at high-speed without data caps, is healthy, has shiny teeth and loves spending money on your products. All you need to do is constantly innovate and you'll be a major success. The term for this is "the modern web". Another word for it is nonsense. There is a web people want and there is one that people use. We should start thinking about upgrading the one people use and stop chasing our own tail trying to mimick other environments.

This document summarizes Chris Heilmann's talk about making ES6 available to all with ChakraCore and TypeScript. It discusses issues with JavaScript like lack of type safety and classes, and how ES6 and tools like Babel and TypeScript help address these. It also introduces ChakraCore, a new JavaScript engine that can make ES6 available in more places like Node.js and provides benefits like improved performance compared to other engines. Overall, it outlines how tools and technologies are helping modernize JavaScript and expand where it can be used.

Keynote of the second You Gotta Love Frontend conference in Tel Aviv/Israel talking about what to expect of the web in the near future.

JavaScript is arguably the most important language in the world. It comes included in nearly every desktop and mobile browser. It powers the client-side of apps like Facebook and GMail. It is the language of choice for mobile development environments like Apccelerator's Titanium and Apache's Cordova (aka Adobe's PhoneGap). It is even on the server now in Node.js. Yet when programmer's run into performance issue with JavaScript their first inclination is to blame its interpreted nature, not realizing that simple changes in the structure of their code can result in sometimes significant improvements in performance. In this session I will show five quick changes you can make to your JavaScript code to improve its performance and explain why they work.

The document discusses using JavaScript like a buffet, where developers should be flexible and not try to do everything with JavaScript or force their preferences on others. It encourages sharing code openly but also being considerate of different environments and users. Developers are advised to focus on quality over quantity and consider progressive enhancement over delivering all functionality at once.

ES6 and other extensions to JavaScript are exciting, but they have the problem that they are not backwards compatible. How can we deal with that issue? Or is it really one?

I built this presentation for Prime ICT Meetup that happened in Kathmandu on June, 2016. Here, I talk about What JavaScript really is and about some new features introduced in ES6. The first part of the slides are taken/influenced from David Crockford's talk called "Really. JavaScript" : https://www.youtube.com/watch?v=lTWGoL1N-Kc

1) The document discusses high-performance JavaScript and describes how the speaker's company, Plaxo, almost failed to launch their product because it was too slow. 2) It presents a mantra for high-performance JavaScript: be lazy, be responsive, be pragmatic, be vigilant. 3) Some techniques discussed include writing less code, loading JavaScript on demand, drawing UI late, yielding to keep the interface responsive, and profiling relentlessly.

A talk about future technologies of the web, and how our time is equally well spent cleaning up the web of now.

Image analysis is hot topic and we've decided to share some thought on what's currently available on the market for image analysis services

The document discusses how the web is changing and provides advice on how content creators can adapt. Specifically: - The mobile platform has become dominant, with people spending more time consuming media on mobile than desktop. Mobile and tablet visitors now account for more page views than desktop. - Search engines like Google are no longer the main driver of traffic as social networks like Facebook can now drive more visitors. Pinterest is also emerging as a new "human edited" search engine. - The lines between media and distribution platforms are blurring as platforms like Facebook Instant Articles host content directly. Content needs to work across multiple closed systems. - Private messaging on platforms like WhatsApp and Snapchat are rising in popularity

90% of all media interactions today are screen-based. There are two distinct ways people move among screens to get stuff done: simultaneously and sequentially. Google's study shows how these two modes of interaction trigger specific behaviors such as online shopping, & which devices people are using at the various stages of these interactions.

A best practice guide with insider tips to improve, process improvement. Share your tips for improving process improvement below!

This document describes Philosophy IB's approach to business process design and optimization. It outlines a six-step ADVANCE methodology: Analyze, Design, Validate, Advise, Envision, and Communicate & Execute. This methodology involves analyzing the current processes, designing optimized new processes, validating the new designs with stakeholders, advising on change management needs, envisioning the new processes visually, and executing implementation through communication and training. The goal is to improve productivity, reduce cycle times, clarify roles, and increase compliance through more efficient, usable, and repeatable business processes.

The document discusses common pitfalls that organizations face when implementing process improvement efforts. It outlines the top 8 pitfalls, including not treating the process improvement effort as a project, leading process change with a tool instead of people, and failing to conduct an assessment of the current state before beginning improvements. The document provides recommendations for avoiding each pitfall, such as putting a project manager in charge, defining processes before procuring tools, and conducting an assessment to understand the starting point. In summary, avoiding pitfalls can dramatically increase the chances of a successful process improvement effort.

Neste tempo de muita correria, rsss, tudo para 'ontem', fizemos um guia resumindo as atividades essenciais para Mapear Processos de Negócios, veja como ficou.

This document presents a process for creating business process success. It discusses the importance of measurement that is linked to culture, where process performance can be genuinely managed and improved. An example process for relocation management is shown, with identification of potential metrics such as the number of days to analyze the process and estimated cost savings. Measurement is highlighted as a key part of improving processes and achieving business goals.

O documento descreve o plano de gerenciamento de mudanças organizacionais de um projeto. Ele inclui seis principais entregas: 1) avaliação da prontidão para mudança, 2) plano de ação para prontidão, 3) mapeamento de pessoas-chave, 4) plano de comunicação, 5) plano de treinamento e 6) gestão do projeto de mudança. O objetivo geral é preparar a organização para as mudanças do projeto e garantir sua aderência ao novo por meio de avaliações, planos de a

Este documento discute métricas e ferramentas para mensuração e monitoramento em mídias sociais. Ele apresenta quatro âmbitos de métricas (alcance, adequação, influência e engajamento) e discute ferramentas como web analytics, YouTube Insights, Facebook Insights e ferramentas de busca e classificação de perfis como Klout e PeerIndex.

The document discusses the importance of meeting design and how it can be used to transform meetings. It defines meeting design as "the purposeful shaping of both the form and the content of a meeting to deliver on crucial business objectives." Meeting design presents an opportunity to reduce costs and increase value. The document outlines frameworks for meeting design, including identifying stakeholders and their needs, defining objectives, and developing design interventions. It provides examples of innovative meeting formats and room designs. The conclusion discusses future trends in meeting design and resources for learning more.

O documento discute estratégias de marketing jurídico, incluindo desenvolvimento de novos negócios focado no cliente, geração de inteligência a partir de sistemas de controle e desafios da venda cruzada como individualismo entre advogados. Ele também aborda a otimização da carteira de clientes para focar nos 20% mais rentáveis.

O documento discute gestão de processos e produtividade. Aborda temas como estratégia, gestão da mudança, gestão da qualidade, gestão de processos e gestão da produtividade. O autor é Marcos Magnanti, especialista nessas áreas e professor de pós-graduação.

This is a low-key, simple presentation for the small business owner. Use this method to get a visual on bottlenecks, and create new processes that make work productive and fun.

O documento discute os benefícios da gestão visual no ambiente de trabalho. Apresenta 8 manifestações principais da gestão visual, incluindo quadros de controle, quadros kanban e salas de reunião visual. Também discute como a visualização de dados pode melhorar a comunicação, medição de desempenho e resolução de problemas.

How can an organisation begin to develop a standardised estimation approach and what benefits can be achieved.

Mobile Search Moments: Understanding How Mobile Drives Conversions from Google & Nielsen. Understanding mobile search, how mobile search drives multi-channel conversions, how mobile search drives behavior in the moment & perceptions of mobile search ads.

O documento apresenta as técnicas e vantagens do mapeamento de processos nas empresas, incluindo padronizar processos para melhorar a eficiência, medir resultados e atender clientes de forma consistente.

We hear it all the time in marketing teams and agencies, but is it really true? Are creativity and structure really mortal enemies? Eleven marketing thought leaders weigh in and help set the record straight.

It is safe to say that more and more entrepreneurs are artists, and artists of all kinds are entrepreneurs. The trend is only on the rise as all things (art, science, technology, business, culture, spirituality) are increasingly converging. Creativity is the common theme that drives both entrepreneurs and artists alike. But creative people are often also paradoxical. Creative people are humble and proud. Creative people tend to be both extroverted and introverted. Creative people are rebellious and conservative. How creative are you?

This document summarizes a talk given by Chris Heilmann at ForwardJS in 2015. Heilmann discusses the state of web development technologies and how developers have focused too much on experimental features that are not ready for production use. This has led to a fragmented web where browsers implement features differently. He argues developers should focus on standardizing and improving existing web standards rather than constantly introducing new technologies. ES6 is highlighted as a priority for improving existing JavaScript.

There are a number of options when going mobile, and it's not slowing down. Why choose one over the other? What are the strengths and pitfalls? What's right for your customers and users? We'll go over each option, with examples of how you can come to the right strategy around your mobile offerings.

This document discusses 6 rules for responsive web design: 1. Responsive design doesn't end with squishy layouts - optimize based on user capabilities rather than just screen size. 2. There is no responsive pixie dust - streamline workflows and use rapid prototypes and style tiles to communicate fluid layouts. 3. Your workflow will change - iterate designs quickly through prototypes rather than big reveals. 4. Your tools will change - leverage preprocessors like SASS and frameworks like Foundation for responsive coding. 5. The web is responsive by default - prioritize content and build APIs to support multiple platforms. 6. Embrace unpredictability - acknowledge the constraints of different devices

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

This document summarizes a presentation given by Michael Fienen and Dylan Wilbanks on the topic of accessibility and usability. The presentation argues that accessibility and usability have many similarities and should be considered together from the beginning of a project. It provides recommendations for making templates, forms, and videos accessible. It also discusses testing for accessibility and strategies for getting buy-in for accessibility within an organization, emphasizing an early and iterative approach. The overall message is that accessibility should be a priority from the start of any project to create a better experience for all users.