It’s 2019, promise me you will stop implementing large monolithic applications that take forever to load and even longer to develop on. The future of the web is JavaScript, APIs, and Markup; known as the JAMstack. See how GatsbyJS, Headless CMS, and GraphQL are the next decade’s tech instead.

Sites that take forever and a day to render a web page have horrible consequences to your users and your goals, and don’t just take my word for it. A recent study by Akamai shows that every 100-millisecond delay in website load time can hurt conversion rates by 7%. That’s because the tech we have been using was architected long ago.

Join my session and I’ll show you how to leverage a Microservice Architecture, the best Static Site Generator out there, Headless CMS, and Microsoft Azure to deliver a static website that can be deployed easily on dozens of services. You will be able to forget about the last decade’s tech problems of complicated deploys, server maintenance, and scaling fears.

Flutter is Google’s cross-platform mobile platform for crafting high-quality native interfaces on iOS and Android in record time. Flutter works with existing code, is used by developers and organizations around the world, and is free and open source.

Together we will start with an empty Flutter project and build it up step by step into a usable app. Along the way, you will pick up some of the fundamentals of Flutter development as well as the fundamentals of the Dart language. This intro will equip you with enough of a base to start building your own mobile apps in record time!

Project Repo: https://github.com/donwardpeng/Flutter-DetTechWatch

Regular expressions are everywhere. But they don’t scale in several important ways:

• Performance: Almost every implementation uses exponential backtracking, which can stall mining of big data, where input format anomalies are likely.
• Large collections of regex: Building collections of regex is fraught, because they don’t compose well. And too few libraries support naming patterns for re-use, especially across different programming languages.
• Perhaps most importantly, regex don’t scale to teams of people, because they are famously hard to read, understand, and maintain.

The Rosie Pattern Language (RPL) addresses all of these scale challenges: big data is processed in predictable (usually linear) time in the input size; packages of composable patterns are easily shared; and it has a readable syntax, with named patterns, flexible whitespace, and comments, like a programming language.

The web has been steadily moving towards richer client side experiences for a long time now. A lot of people point to GMail as the beginning of the single page app phenomenon, and it has only grown since then. Your users expect a rich interface from your application now, and you need to deliver it.

But the migration to SPAs hasn’t been without its problems. Fundamentally, SPAs are actually two applications: a client side application that runs in your users browser, and the server side application that it communicates with it. Since you have now fundamentally built a distributed app you have added a whole slew of new problems into your world. How do you keep the business rules in sync between the systems? Have all of the error cases been accounted for? How do we manage releases between these separate, but tightly coupled applications?

What if your server side application could provide a rich clientside experience without the Javascript? Introducing Phoenix LiveView a way to have your cake and eat it too.

ReasonML is a new language and way to build not just websites powered by ReactJS, but powers a whole new ecosystem of utilization. Electron apps, CLIs, VM-based servers and any application JavaScript currently has can be improved using ReasonML. Build native CLI tools that are fast. Build native MacOS apps that don’t have to require all of Chrome and a 100mb min bundle size. Run your ReasonML apps on bare metal!

The power that comes with ReasonML will change the way we write our JavaScript apps today. I’m excited to share with you what the future looks like!

Tests are critical for verifying that we’re building the software we want; however, a good test suite is hard to achieve. Setting up scenarios is boring, repetitive, and time consuming. Not to mention we have to think of all these edge cases before our users exploit them.

Property-based testing introduces developers to a new way of thinking about testing. We can create thousands of clever tests with just a small amount of code. We can then spend our time and effort effectively to help make sure the assumptions of our software hold true.

The most popular databases in the world all speak SQL, and almost 60% of Stack Overflow members use SQL. SQL is the query language that dominates when it comes to interacting with data. Data has changed since the 1970s; it’s no longer just stored in flat tables, but as rich, hierarchical object structures like JSON. SQL isn’t dead though, it just needed to evolve a little bit. In this session, you’ll learn about the next iteration of SQL: SQL++. Born from a UCSD research project, SQL++ is backwards-compatible and can work with heterogeneous data, with or without schemas and indexing. It is still the readable, declarative, highly composable language that you’re used to, but with extra super-powers. This session will focus on the enhancements that SQL++ brings, will show some of the databases that are already implementing it (including Couchbase, AsterixDB, Drill), and guidance on why and when to use it. You will enter with SQL skills and leave with big data skills.

Do you ever get tired of writing unit tests for ridiculous edge cases? Are you stuck on an old AngularJS app and need to modernize it, unsure how to move forward? Are you an FP lover looking for something more cohesive than lodash/fp and Ramda? Do you have a need for high-reliability in your project’s domain? Maybe the barrage of JS frameworks & libraries, ES features, TypeScript features, and package security issues are wearing you down.

Well, look no further! I will introduce you to Elm, a fun way to build reliable web apps. We will look at common issues with reliability in popular frameworks and explore some of the ways Elm prevents them. Along the way, we’ll see how Elm reduces JS fatigue and makes happier developers. At the end, I will show how you can easily introduce Elm into an existing Angular or React app.

With Swift 5 and ABI stability, Swift has matured into a language ready for new adopters. In this talk, Leo gives an introduction to Swift development as well as its journey.

In this session, Leo will cover the basics of the syntax and how it is similar to other languages. This session will explain some differences such as Optionals, Enumerations, and Error Handling. We then build our first iOS Application with navigation, tabs, and a table view.

By building the application, we can get into some of the patterns and practices in iOS development including Delegation, Protocol-Oriented Programming, and Functional Programming. Lastly, we’ll get into the basics of Apple Watch development and how we can carry our skills to the watch.

If you are interested in getting started with Swift and developing for the Apple Watch, you’ll want to check this workshop out.

What You'll Need...

• macOS Computer with latest version of macOS installed
• macOS Mojave 10.14.4 - for more info on how to upgrade macOS check out this link: https://support.apple.com/en-us/HT201541
• Xcode 10.2.1 - for more info on how to download Xcode, check out this link: https://itunes.apple.com/us/app/xcode/id497799835?mt=12

Elm is a functional programming language for front-end web development. Elm has been gaining popularity as it aims to solve many of the main pain points of the modern JavaScript developer.

In this workshop, participants will build a small Elm app from the ground up. We'll start with basic syntax, explain how "The Elm Architecture" guides us as we develop our app and walk through Data Modelling and working with JSON APIs

We assume prior knowledge only of JavaScript or another imperative or object-oriented language.