Recently, there has been a move by the major browser vendors to simplify the development of software through the new Web Components standard. Polymer, a free open-source library by Google, makes use of this new standard to make web software reusable (see YouTube, newly built using Polymer). Firebase, a collection of cloud services, combined with Polymer, make for a compelling development platform for web and mobile apps and the new push for mobile web apps. In this talk we will cover Polymer, Firebase and the major services of Google Functions, Hosting, RealTime and Firestore Databases. Examples will be shown of a production app in progress.
Simon Gauvin is an expert in the field of UX, mobile and cloud computing with 25 years of experience developing several startup software companies. He was former VP of Applications Technology at Plazmic Inc. (acquired by RIM in 2002) where he led the development of a mobile media platform for Warner Brothers and Disney in the Japanese mobile market. He completed Ph.D. research in Computer Science at Dalhousie University and has been published in several leading academic journals. Simon has authored software patents, invented and developed several new programming languages, and used this work to co-found Vizwik.com, a visual programming mobile app development platform. He recently co-founded another startup, Safelii Inc., which is using mobile and AI technology to help improve health and safety services for employees in corporations. He is also a freelance Chief Technology Officer consulting for small to medium sized companies in Atlantic Canada.
Why is software architecture so important? What is it, anyway? How can "clean" software architecture actually make software development easier, faster, and less-painful?
"Uncle" Bob Martin has attempted to take the most robust and battle-tested architectural patterns and boil them down into "one architecture to rule them all"--in a matter of speaking...
We'll briefly look at what "Clean Architecture" is and what problems it attempts to solve. Then we'll focus on how we might implement it in a .NET Core application with practical tips from real-world experience sprinkled throughout.
James Hickey is currently the senior software developer at IronFlow Technologies. He focuses on improving software development processes, automation and architecture. His current technical interests include .NET Core, Event Sourcing, Microservices, etc.
Kotlin is a statically typed, concise, safe, and pragmatic programming language that runs on the JVM and other platforms. It has been gaining in popularity over the last year ever since Google announced official support for Kotlin on Android. There are a lot of misconceptions out here of what Kotlin is and what it is good for. This talk focuses on dispelling some myths about kotlin and serves as a general introduction to the language.
Akiri has been using Kotlin for server and API development, replacing a traditional Java based stack. Content for this talk is based on practical experience building a product using Kotlin.
Chris Dail is a Senior Director of Software Engineering at Akiri, a healthcare networking startup. He has 15 years of experience building software products in various roles including as a software developer, architect, and manager. Chris is a programming language enthusiast and is passionate about clean, readable code.
Since 2003, Arduino has revolutionised physical computing with open-source hardware and software (and a community) that prioritises ease of use. As a result, hundreds of thousands (if not millions) of people can call themselves "embedded systems programmers" without knowing much about the microcontroller (MCU) that they're programming. And that's okay.
But hiding the microcontrollers' complexities comes at the cost of flexibility and performance. Fortunately, the Atmel line of MCUs is in a unique position to bridge the worlds of Arduino and traditional (i.e., industrial-grade) embedded systems programming.
This presentation will cover the required "starter kit" of hardware and software, the required "starter kit" of C/C++ concepts, the basics of digital I/O, the basics of analogue I/O, a demo. project, and (as usual) a list of "gotchas."
Best practices for design patterns: KISS, DRY, SOLID. You all know these, but they could be far from being part of your daily activities. What you might see every day might instead be "God-class," duplicate code, unnecessary complexity, feature-envy and many other terrible practises. "Code smell" is a generic term to group these under one keyword, but in most cases it indicates an issue with the design and a disregard for common best practices. Let's try to identify these, list them, and suggest solutions with some examples.
Etienne Mermillod is a lead developer with TKS. He has previously worked on a Financial Analysis Dashboard, minind data from another system. He has also worked for SMEs to some of the biggest French companies, mostly in .NET but also with ActionScript and Python. He fights dirty code every day and helps others achieve better designs. Knowledg- transfer being one of his core values, he now invests some his time mentoring people and presenting these concepts. Apart from his day-job, Etienne is a hardcore gamer and likes competitive activities (such as table tennis and badminton).