TULSA TECHFEST 2016


Home
Attendees
Register NOW!
Agenda
Speakers
Sponsors
Tracks
Prizes
Sponsor
Reasons
FAQs
Community
Media Kit
  

 Featured Speakers

 Bio

Michael Perry, Principal Consultant, Improving

Michael Perry, Principal Consultant, Improving

Software is math. Every class is a theorem. The compiler is the proof. And unit tests check our work.

Michael has recorded Pluralsight courses on CQRS, XAML Patterns, and Cryptography, in addition to Provable Code. He maintains the spoon-bending Assistant, Correspondence, and Jinaga open-source libraries. He podcasts about the intersection between software and mathematics at qedcode.com. And he helps his clients at Improving benefit from the power of software mathematics.
Visit Michael Perry on Link!Follow Michael Perry on Twitter!Like Michael Perry on Facebook!Visit Michael Perry on LinkedIn!Visit Michael Perry on Mvp!Hack with Michael Perry on Github!

 Sessions

Jinaga: The Universal Web Back-End

How many web applications have you built? For each one, you build a front-end consisting of a UI and interaction logic, and a back-end consisting of an API and a database. Every new feature touches all of those layers. Let me cut your work in half. I'll show you Jinaga, the only back-end that your web application ever needs. Code against a simple JSON model. Jinaga replaces the API and the database. Jinaga treats application state as the relationship among immutable JSON documents. Identify the user with a JSON document containing their public key. Capture each user action as another document. Watch for related documents to update the user interface. Jinaga will store your messages, and send them to other browsers watching in real time. You usually have to use Socket.io to get real-time updates separate from your RESTful API. But with Jinaga, it's all the same thing. Load data from the Jinaga back-end, and it just updates when changes occur.
Aug 5th - 10:45 AM
Aug 5th

Xamarin Without the Forms

Xamarin Forms interfaces are limited to a small set of layouts and controls. If you want to truly customize your user experience across devices, then you need to design native interfaces for iOS and for Android. But what about all of the other goodness that you give up by skipping Xamarin Forms? For example, what about data binding? Assisticant is a dependency tracking framework for mobile applications. It binds native interfaces to observable and computed properties. You get to write clean, decoupled code. Assisticant determines the time and order of updates to refresh the UI in the most efficient way possible. Write your shared app logic and models in a Portable Class Library. Write all of your persistence, web access, and tests just once. Then customize only the part that makes iOS and Android applications unique: the user interface. Use the native interface builders with all of the richness of the platform-specific control palette and none of the compromise. Then just bind your portable view model to each native UI and let Assisticant take care of the rest.
Aug 5th - 1:00 PM
Aug 5th

All Requests are Asynchronous

When should you use a service bus vs. a web service call? When should you use REST vs. SOAP? Should you use CQRS? Should you build Microservices? Take a look under the hood of your network stack. What promises does it make? What promises can it actually keep? We have many architectural choices to make within a distributed system. Those decisions depend upon the nature of the messaging infrastructure upon which we build. Different options are good for different parts of the system. But some of the advice that you may have heard is wrong. Learn what's really happening inside of the components you choose. And use that knowledge to build more reliable distributed systems.
Aug 5th - 2:45 PM
Aug 5th
 
 

 Proud Sponsors