Many of us have one or more manual steps in our deploy and release processes. This leads to a lot of time spent waiting for the right people to do the job. Also, errors often occur due to steps forgotten or done incorrectly. This often leads to high walls between the testers, IT-ops and the developers.
This talk will start out with some general continuous delivery, the why's, where you'll get to know the actual benefits of applying continuous delivery and the arguments you need to be allowed to spend time on it. Then we will move over to the how's. By demonstrating how you can use TeamCity and OctopusDeploy to configure automated builds and one-click deployment of both an asp.net website and a windows service, and how you can migrate your current manual process into an automated one. Along the way, we will be discussing how OctopusDeploy chooses solves specific problems, and other ways you might handle those issues.
Deploying a service
Deploying a website
Writing PowerShell deployment scripts
The NuGet package format
Using the OctopusDeploy web api
Rolling back failed deployments
Strategies to move from manual to automated/one-click deploy
Connecting the issue tracker
Ever felt you spend more time packing deployments, configuring test environments and deploying the latest build, in order to please the testers, than you spend writing actual code? Had your flow interrupted by the boss wanting a demo environment set up for a customer demo? We simply can't be interrupted in our creational flow of #awesome code by the worldly dealings of these simpletons! Fortunately, built into the Windows Azure Platform, there is great support for Continuous Delivery of the greatness you just built. With little fuss you can set up automated builds, test runs and deployments so that you may focus on what’s important – the uninterrupted development experience. Everything that can be automated must be automated!
After a 3-year long struggle, the IETF finally released the OAuth2 specification(s). While all the big players (like Google, Microsoft and Facebook) are already using it, more and more people want to follow. But there is big confusion about what OAuth2 really is, what its uses cases are and which problems it can actually solve. At the same time, also the security experts out there don’t really agree if OAuth2 is a complete failure, or not - or something in between. Dominick walks you through OAuth2, its use cases and pitfalls.
Modeling web services using the HTTP API approach has become pretty much the standard approach. This also means that these APIs must be ready for all the security scenarios around identity and access control. These range from simple username/password and service to service communication, over enterprise integration to token based authentication and delegated authorization. In addition we also have to deal with different client types likes native desktop or mobile clients, browser clients and classic web applications. Dominick shows you how this all comes together.
Apps that are merely functional no longer cut the mustard – today, our users expect apps that empower them through beautiful, intuitive user interfaces.
It’s time to fight back against the old adages that developers are color blind, visually impaired code monkeys with no sense for usability and in general should not be expected to know their wireframes from their pants. To keep up with the competition in today’s app markets, you need to build apps that offer a great user experience. Some solve this by hiring actual UX experts, but that is no excuse for developers not to know at least the basics of the craft. And besides, when you learn enough to thread water, UX is FUN!
In this talk, you’ll learn five simple tricks that will help take your UI from something the cat dragged in to something your users will love. Even if you’re “just a color blind developer.”