How to separate the f2 e and sde in web development for_taobaotaobao.com
This document discusses the reorganization of a development team at Cisco WebEx. It proposes separating front-end developers (F2E) and server-side developers (SDE) into different teams for improved productivity, quality, and skill development. It also recommends establishing explicit requirements, change control processes, and an agreed-upon data interface specification to facilitate separation and cooperation between the F2E and SDE teams.
Hunter Loftis discusses building mobile apps using HTML5. He recommends first considering whether the app could be built natively or as a hybrid app. If using mobile HTML5, he provides practical guidelines including using micro libraries, limiting DOM updates, storing data locally, keeping code asynchronous, and embracing features like geolocation. The key is to aim low, debug on devices, and have fun building the mobile app.
This document discusses various topics related to technology companies and their products. It covers browsers like IE, Chrome, and Safari, as well as companies like Google, Apple, software programs, and individuals. For each topic, it lists 2-4 related sub-topics or recent updates to products from those companies. The document ends with a bonus section asking about education level.
Considering most designers in DiDi's design team were more familiar with the mobile platform than desktop, This presentation focus on mobile: how to present a graceful web page on mobile devices? how to take the advantage of adaptivity for web pages? what is the design trend in recent years? In the end, I reviewed some concepts that frequently be discussed by UI developers.
This document summarizes techniques for building web reading applications. It discusses using modular scripts and responsive design for building structured web apps. It also covers HTML5 concepts, web apps versus native apps, and keeping code DRY. Additionally, it provides examples of using Stylus and Jade for CSS preprocessing and HTML templating. Key techniques discussed include range and selection, real-time collaboration, web storage, widgets, typographic design for reflowable and fixed-layout reading, and font rendering optimizations.
Javascript引擎实现 discusses the key components of a Javascript engine including the interpreter, compiler, memory manager, garbage collector, standard library, debugger, and JIT. It describes the theoretical basis of memory management and different garbage collection approaches. It also explains several important Javascript concepts like the prototype chain, scope chain, lexical scope, call objects, closures, and how prototypes enable prototype-based programming.
The document discusses user behavior tracking system architecture. It describes how client-side logging of user interactions like mouse movements, clicks, and scrolls is sent to a Marmot server. The server logs include event types, timestamps, and custom data. Relative coordinates are calculated on the client using DOM paths and element positions. Key interaction paths are identified and similar paths detected for experiments. User defined coordinates (UDC) and an AB testing framework for experiments are also mentioned. Big data is stored using Hadoop Distributed File System (HDFS).