Fronteers Spring Conference Amsterdam 2016 keynote

This document discusses various techniques for optimizing the frontend performance of web applications. It provides 5 rules: 1) Only optimize when it makes a meaningful difference. 2) Download resources in parallel to reduce page load time. 3) Eliminate unnecessary requests through techniques like merging, inlining, sprites and caching. 4) Defer parsing of JavaScripts when possible to improve perceived page load speeds. 5) Consider factors like server location and content delivery networks to improve global performance.

An overview of the steps required to build Javascript apps before and get them ready for deployment. It explains how Grunt helps us to validate, minimize and package our code.

Managing technical debt requires making prudent decisions about design and quality. It is important to 1) register any new debt, 2) assess existing debt, 3) monetize the debt to establish a debt limit, 4) pay down high-interest debt first, and 5) continuously monitor trends to adapt over time. Transparency is key through registering debt, inspection via monetization, and adapting practices as needed.

(reposting with clearer title) Performance tuning presentation from WindyCityRails 2010. Why performance matters The right way to approach it Front end testing tools Automated testing tools Common problems and the ways to solve them in Rails Rails specific tools bullet slim_scrooge rack bug request log analyzer rails indexes

Performance tuning presentation for Chicago Rails Conference. Focusing on Front end page improvements

This document discusses using Tungsten Replicator to consolidate data from sharded schemas into a single schema in real-time with minimal lag. It provides an example of accounts data stored across multiple branches in different schemas. Filters are used to modify replication events before applying them to consolidate the data into a central schema. Installation and provisioning steps are outlined to set up the master and slave databases and initialize the data.

The document provides technical recommendations for SEO, including: 1. Removing URL parameters, implementing rel="alternate" for mobile sites, and using HREFLANG tags to group international sites. It also recommends diagnosing actual site speed issues, implementing Twitter Cards, and getting familiar with JavaScript, jQuery, and debugging tools. 2. Auditing AJAX implementations to ensure all content and links are crawlable without JavaScript. It notes Google can now index some JavaScript-rendered content like Facebook comments. 3. When making recommendations, being prescriptive, but when auditing, being cautious of the costs of changes if content is already being indexed. Fix only what's necessary, not purely for technical purity.

This document discusses profiling PHP applications to improve performance. It recommends profiling during development to identify inefficiencies. The document introduces Xdebug for profiling PHP code and Webgrind, a PHP frontend for visualizing Xdebug profiles. It provides an example of profiling a sample PHP application, identifying issues, making code changes, and verifying performance improvements through re-profiling.

This document provides an introduction and overview of Angular, including: - Angular is a front-end web framework best for single page applications. - It uses dependency injection to allow services to be injected, decorated, and mocked. - Directives allow extending and augmenting HTML behavior, and are compiled by Angular to link them to scopes. - Data binding in Angular syncs scope data with the DOM via one-way and two-way binding. - Promises represent the future state of asynchronous operations and can resolve other promises.

This document discusses how web design firms can compete with internal GIS teams by providing web-based GIS (WebGIS) applications. It notes that WebGIS requires learning new tools like JavaScript, AJAX, and RESTful services. To protect their work, internal GIS teams need to learn these new web technologies and prioritize usability over features to create responsive applications. The document advocates for an iterative development process with a focus on performance and usability testing.

Progressive Web Apps are a new approach to application development that combines the best of the web and the best of native apps. They are reliable, fast and engaging like native apps while also being responsive and capable of being installed like regular web pages. The key technologies that enable Progressive Web Apps are service workers, app manifests, and responsive design. Service workers allow for caching assets and serving cached responses even when offline. App manifests provide metadata that makes the app feel like a native application to the user. Responsive design ensures the app works across different screen sizes.

Riza Fahmi is the Curriculum Director of Hacktiv8, a company he started with Ronald Ishak, in an attempt to solve the developer hiring crunch that has hindered the growth of many aspiring tech startups in Indonesia. Through a 12-week immersive curriculum offered through Hacktiv8, aims to raise the quality of web developers and connect them with the best tech companies in the country. Knowledge sharing is deeply engrained with his passion and is evident through involvement in many initiatives such as becoming a lecturer at Universitas Budi Luhur; becoming an organizer for JakartaJS, Meteor Jakarta and React Indonesia; a speaker at Singapore Elixir Meetup, GeekCamp, Lambda Jakarta and much more to come. *** This slide was shared at Tech in Asia Product Development Conference 2017 (PDC'17) on 9-10 August 2017. Get more insightful updates from TIA by subscribing techin.asia/updateselalu