Drawing inspiration from and parallels with some of the lessons learned from our collective migration towards functional programming languages and data-orientation, Chas provides part of one such discourse.
Governments spend hundreds of billions of dollars on technology, but they can adopt modern practices to reduce costs and improve services. And here’s the thing: they are.
Architects are still designing systems like they did in the ‘70s. This talk isn’t about big, slow data; this talk isn’t about small, fast data. This talk takes a nuanced path through most of the rest which sits somewhere in between, with tradeoffs aplenty.
The internet of things is everywhere, but how do you interact with devices? This presentation will walk through using Apache Cordova to communicate with Arduino over Bluetooth.
Join Diana Larsen in an exploration of ways coaches and managers can use the model to show the path to reliable Agile competence and find the “Agile” that’s right for them.
We rely on distributed databases and queues to store and process data reliably, but many fall short of their marketing promises. In this installment of the Jepsen project, we’ll explore what “strongly consistent” really means, and find out whether various databases live up to their claims.
In this talk, we’re going to learn how to incorporate Grunt: The JavaScript Task Runner into our build process to help automate often-marginalized tasks that center on the “Front Half” of your app (you know, the half of your app you take for granted).
This is a talk sharing TripCase’s (http://phonegap.com/app/tripcase/) experience with (and without) PhoneGap Build. We’ll walk through our journey and discuss how it shaped expectations on how quickly we should be getting our code in the hands of fellow testers and stakeholders.
The game has changed: we write interactive web applications, we distribute the processing of huge data sets and our services need to be available at all times. This new breed of applications comes with its own set of requirements and forces us to establish new blueprints for designing our systems. In this talk, we ask … Read More
By separating the type checker from the compiler, we avoid infecting the rest of the language with the massive complexities of a static type system. Our compiler is simple and robust, our language design is unrestricted by an arbitrary type system, and our users are free to choose the right type system for the job.
In this talk, we explore this idea further and demonstrate what such a type system is like to use.
