InfoQ Homepage Conferences Content on InfoQ
-
Painful Java Puzzlers and Bug Patterns
Bill Pugh dissects three Java puzzlers and bug patterns, explaining how to fix them, what is lessons to be learned, and how to avoid such coding mistakes.
-
Techniques for Scaling the Netflix API
Daniel Jacobson covers the history of Netflix’s APIs, adaptation for the cloud, development and testing, resiliency, and the future of their APIs.
-
JavaScript Today and Tomorrow: Evolving the Ambient Language of the Ambient Computing Era
Allen Wirfs-Brock reviews the evolution of JavaScript, observing its current status and foreseeing its near future, supporting the idea that JavaScript’s role will be even more predominant.
-
Agile/UX Panel
Jeremy Sutherland, Darius Kumana, Eewei Chen, Darci Dutcher, and Richard Muscat (moderator) discuss the relationship between Agile and UX design.
-
Building Applications with jQuery UI
Scott González demoes creating web applications with jQuery UI, showing the widget factory, the unified API, how to create new widgets, the CSS framework, and themes.
-
CSS3 and Sass
Mark Volkmann introduces CSS3 and Sass, a tool extending CSS with variables, selector nesting, mixins and selector inheritance, the resulting code being converted to regular CSS before deploying.
-
Automatic Performance Programming?
Markus Püschel proposes to solve scientific calculation performance problems with code generation tools, introducing Spiral, an automatic performance programming framework for linear transforms.
-
Uptime in High Volume Messaging Systems — Lessons Learned
Erik Onnen shares lessons learned while designing the architecture, implementing it, and releasing it into operations at Urban Airship, providing hosting for mobile services.
-
Retrospectives: A Bit of Ceremony Can Be Useful
Aino Corry’s message is that if we skip retrospectives there will be problems that we don’t understand where they come from nor what to do to solve them.
-
Architecting for Failure at the Guardian.co.uk
Michael Brunton-Spall talks about various types of system failure that can happen, sharing the lessons learned at the Guardian and measures taken to prevent and mitigate failure.
-
Decisions, Decisions
Dan North engages the audience into a discussion about the tradeoffs involved in making decisions regarding the team composition, development style, architecture, and deployment solutions.
-
The Frustrated Architect
Simon Brown discusses the role of the software architect, challenging some of the current assumptions and trying to redefine it in the context of Agile development.