Apache Flex and the imperfect Web

This document summarizes a presentation about Behaviour Driven Development (BDD) given by Alexandru Badiu. It begins by explaining some of the shortcomings of test-driven development (TDD), such as not being able to test full functionality and refactoring dependency on early tests. It then describes the key features of BDD, including using a common language that all stakeholders can understand, producing tests, documentation, and specifications, and supporting tools like Gherkin and Cucumber. The document provides examples of how BDD is implemented in PHP using Behat and in Drupal using the Behat Drupal Extension. It concludes by inviting the audience to discuss employment opportunities.

The document discusses the history and challenges of front-end development. It notes that initially there were many different front-end tools that made selection difficult. Frameworks became popular but could be incompatible and difficult to decouple. It suggests that ES6 and React provide a good foundation for building front-ends, as React code can be written in ES6 and they avoid issues of other frameworks.

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

This document discusses HTML5 and web technologies. It provides an agenda and overview of key topics including what HTML5 is, how it evolves HTML incrementally, and new APIs like drag and drop, forms, canvas, and web sockets. It also discusses cross-browser support, uses of technologies like CSS3, SVG and WebGL across devices, and references for further information.

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.

Microservices, cloud, continuous delivery heavily influenced how modern teams build software systems. Come to this talk to learn how our team rebuild frontend stack of several newspapers significantly reducing cycle time and creating fun work environment that lets great developers be great. Some of the things I’ll share: - how respecting the Web makes us faster - what we learned running 12factor apps on Heroku - nuances of Continuous Delivery that you won’t find in books - thinking process behind our decisions and some of the change patterns we used Video: http://www.schibsted.pl/2015/07/enterprise-makeover-part-16-creating-lean-enterprise/ http://www.schibsted.pl/2015/07/enterprise-makeover-part-26-use-the-web-dont-abuse-it/ http://www.schibsted.pl/2015/07/enterprise-makeover-part-36-rethinking-agile-practices/ http://www.schibsted.pl/2015/07/enterprise-makeover-part-46-cloud-native-development-on-heroku/ http://www.schibsted.pl/2015/07/enterprise-makeover-part-56-continuous-delivery-orchestration/ http://www.schibsted.pl/2015/07/enterprise-makeover-66-organizational-change-summary/

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.

Why packaging javascript as a static asset leads nowhere on the long run? Possible solution is rethinking the way the javascript is served

The buzz about the upcoming major reincarnation of AngularJS, with its hot mix of excitement and critics, has somehow shadowed the immediate gains enabled by the recent 1.3 and 1.4 releases. This code-based talk will introduce concepts such as the "Controller As" syntax, component-based directives, the new router and bind once, to demonstrate how mixing these currently available Angular features with good design patterns (and a bit of ES6) provides concrete improvements in performance, modularity, testability and developer productivity to our apps now. Furthermore, it will show how the main ideas at the basis of Angular 2.0 (API simplification, consistency, even more componentization and interoperability with ES6 and Web Components) can be applied to the design and implementation of 1.x applications, helping us both being more productive now & simplifying the upgrade to the "new" Angular.

This document discusses the challenges of large monolithic frontend applications and proposes microfrontends as an architectural approach to address these challenges. It describes different patterns for implementing microfrontends, including mini single-page applications (SPAs) separated by links, a single SPA with multiple independently developed components, and using web components for tighter integration. Key challenges discussed are performance, shared dependencies, and inter-component communication. Examples and demos of single-spa and Angular elements are also referenced.

Presented by Brian Dillard (Pathfinder Development). This Web 2.0 Expo 2008 (San Francisco) session examines the ways in which standards bodies, browser vendors and library/plug-in authors are shaping the future of our foundational web technologies - and how individual developers can participate in that process. Brian's Blog: http://blogs.pathf.com/agileajax Brian's Company: http://www.pathf.com

This document provides an agenda for Developer Tools slides presented by Tomoya Asai at a Mozilla Workshop in Tokyo on October 6th, 2011. The agenda includes introductions to the Web Console, Inspector (Highlighter), Style Editor, CSS Doctor, Scratchpad, GCLI (Graphical CLI), and Source Map developer tools. Links are provided for further information and video demonstrations of some of the tools. The presentation aims to demonstrate various developer tools and allow time for questions.

Talk held on a Smashing Magazine Meetup February, 27th 2012 in Frankfurt (Germany) about current problems with developers, designers and clients in front-end development

This document discusses using a proxy server to render single page applications for search engines and legacy browsers. It introduces the concept of a server-side backbone that runs the same backbone application code on both the client and server. This allows rendering the initial HTML on the server to avoid problems with robots and speeds up loading for users. It also discusses some of the challenges in implementing this approach like emulating the DOM and browser APIs on the server. Overall it presents server-side rendering as a way to solve crawlability and legacy browser support problems for single page apps.

This document summarizes a presentation about how the large open source Firefox OS project works. It discusses fundamentals like version control using Mercurial and Git, issue tracking with Bugzilla, continuous integration using Travis and TBPL/Jenkins for daily builds. It also covers collaboration tools like Wikis, emails, and video conferencing used by the geographically distributed team. The presentation aims to provide insights for other projects on building an open source project at Mozilla's scale.