Free evening event.
Below are the sessions that have been submitted for voting.
Please note that we manually approve all entries so don’t worry if you have just submitted a session and it’s not appearing yet.
16 Session(s) have been submitted
A. Best [@_andrewb]
DDD helps us tame the inherent complexity of non-trivial software development. CQRS supports the same goal goal, while providing other tangible benefits like optimisation and scalability. ORMs take the heavy lifting out of transalting between the worlds of Object Oriented software and relational persistance layers.
Finding the sweet spot between these approaches can be a challenge. Some popular ORMs (cough Entity Framework cough) place burdensome constraints on DDD implementations, causing them to bend and contort in wierd and less-than-wonderful ways. They can also be sub-optimal for CQRS concerns. CQRS at times is viewed as introducing unwarranted overhead and complexity where it isn’t needed.
In this session we will explore a less-than-wonderful domain model that utilises a single ORM for all of its concerns, and then look at how we can break it apart utilizing a CQRS approach that employs the best tool for the job for each concern, while keeping complexity to a minimum.
A. Best [@_andrewb]
Software development. Solution architecture. Test driven development. Domain driven design. Cloud. Static vs dynamic typing. Test coverage. Pull requests. Package management. Infrastructure automation. Identity management. Security.
The above represent the tip of the successful delivery iceberg.
Software exists for people, and working with those people is the key to succesful delivery. Success in software delivery starts before the team’s boots hit the ground, and continues to be measured beyond the final sprint review.
In this session we will take a look at some targeted, specific non-technical practices and behaviours you and your team can employ to vastly increase your chances of a successful software delivery.
H. Andersson [@hnrkndrssn]
Not A Very Long Time Ago, In a Galaxy Not Very Far, Far Away.
Out of the shadows appears a framework that takes a different approach to building reliable web applications, an approach that generates no runtime exceptions and friendly (not just at compile time) errors. A functional programming language called Elm.
In this session, we will explore how to build a web application using Elm. We’ll start with the basics and move on to exploring the Elm architecture which is a simple pattern for architecting web applications. It allows us to create complex web applications that are easy to maintain and add new features to.
This talk requires no previous experience with functional programming languages, such as Haskell or F#, and is aimed at frontend developers that want to learn how to build reliable web applications with great performance and no runtime exceptions.
J. Yoo [@justinchronicle]
As a front-end, full-stack and/or mobile app developer, using APIs is inevitable. However, what if those APIs are not yet implemented? Should I wait for back-end developers to complete API implementation? Nah, we don’t need to wait for them as long as those API definitions are defined via RAML or Swagger.
In this session, Justin will talk about how beneficial API design-first approach will be, then how API spec is designed and mocked on MuleSoft API Manager, Azure API Management and Amazon API Gateway so that front-end, full-stack and/or mobile app developers can play around until the actual API implementations are done.
J. Yoo [@justinchronicle]
Testing applications is more than important nowadays. Traditionally, developers perform unit tests and/or integration tests in variety of environments. Now, we see serverless applications. How can we test those applications? That’s a tricky question.
In this session, Justin will demo how serverless applications, especially Azure Functions and Logic Apps, are written with considering testability. Then he will also show how those apps can be tested in a continuous integration pipeline, with various approach.
Forget SaaS, IaaS and PaaS - CaaP is where it’s at. People seem to ignore the importance of the culture and how it directly affects creativity, research, morale and the overall product. I’m here to prove to you, beautiful audience members, that a product is more than just the methodology, the technology or its utility; in the end, it’s the culture that will define the product and differentiate it from the plethora of competitors. Ignoring culture, and by extension your employees, could very well mean doom for your business.
Apps have transformed the way we work and do things; but they only truly work when they are connected. Traditionally, connecting applications required specialised skills and niche integration knowledge that not every developer wanted to learn.
However, the increasing diversity of apps and the growing availability of APIs result in much greater integration demands. Luckily, now we have Azure Logic Apps, a rich, robust, fully-managed and very cool Integration Platform as a Service (iPaaS) that enable us to integrate, with speed and ease, not only the new and shiny apps, but also those legacy systems that were born before the API era.
In this presentation, Paco will share the magic of Logic Apps and show how to easily build “serverless” integration apps based on this Azure offering.
J. Gallagher [@joelgall]
With the rise of Big Data & social networks, traditional Relational Databases have reached the limits of their abilities to handle inter-connected entities.
As a result, Graph databases have become more popular, with the likes of Microsoft and GitHub recently offering Graph solutions.
This talk will explain the theory behind Graph databases, when (and when not) to use them, and then demonstrate their power using Neo4j, one of the more popular graph databases.
This is a demonstration of a code quality analysis tool that doesn’t visualise the metrics – it “audiolises” them.
The concepts of poor code having smell and colour (usually red) is commonly accepted, but what about appealing to our sense of hearing as well as eyes and nose? Aeolian is an open source tool (written by the author) that generates MIDI music from code quality metrics, which begs the question:
What does poor quality code sound like? Justin Beiber’s latest? A Phillip Glass soundtrack? A Phil Spector wall of sound cacophony? Modern Jazz? 🙂
Likewise, what does good quality code sound like? Mozart? White noise?
How do commonly accepted musical concepts (keys, tempo, verse, chorus) apply when illustrating code quality.
The author (an amateur musician and long time producer of smelly code) will talk through the concepts of Aeolian and provide plenty of examples of how you can map code quality to music.
This will be a light-hearted talk and no knowledge of music theory is needed.
You have designed and deployed your application using Microservices patterns and deployed to production but it won’t take too long to realize managing tens, hundred or even thousand instances of services manually can quickly become a nightmare. How do you make sure your services are healthy? You do you do load balancing? What about configuration management across your services? Does your service rely on another service? How do you do service discoveries locally, let alone acorss multi-data centers?
Come to my talk and I’ll show you how this can be done relatively easily using Consul.
There’s a lot of buzz around using Microservices patterns to design your backend system, but surprisingly not a lot of people talk about how these services are ultimately tied back together on the frontend. This talk is about challenges you face when creating a UI for your Microservices and challenges you face to ensure service boundaries are respected while the code is still maintainable and loosely coupled.
Everyone heard about depression. But most of us are sure that this won’t happen to us. As we are strong and, as software developers, we are very logical. And depression is illogical. Right? It depends. Come to this session to hear some facts about depression, listen about my personal experience, and, the most important, what you can do about it.
About a year ago, I joined a team that was starting from scratch on a new project.
I’ll talk about how we settled on TypeScript, the tooling around TypeScript that helps keep everything under control, and show how you can put together a toolchain and process that balances moving quickly with producing correct code!
TypeScript’s recent claim to fame is its adaption by the Angular Team. That said perhaps you want to see what TypeScript + React looks like.
This session shows you benefits of this combo.
V. Love [@fly401]
You’ve burned your reputation, you’ve over promised, you’ve lost trust. This was the case for Blizzard Entertainment and their World of Warcraft subscribers. I know, I am one of them. Late August the Legion expansion was launched, and we all held our breath.
I spent 3 days playing a game, and it was the best technology experience I have ever had. I will discuss the history of past releases, the user experience and how it was communicated to us. We will learn a bit about the technology and solutions behind the problems that had plagued them in the past. The promises given, the expectations and the results.
Working in IT I saw a lot of correlations in this experience to releasing software. Come to this session and learn how you can bring users around and the expected results when you do.
09:00 Call for content opens
10:00 Ticket Wave 1 opens
12:00 Ticket wave 2 opens
18:00 Call for content closes
10:00 Voting opens
10:00 Voting closes
09:00 Agenda Published
Free evening event.