<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mikko Vuorinen on Medium]]></title>
        <description><![CDATA[Stories by Mikko Vuorinen on Medium]]></description>
        <link>https://medium.com/@mikko.vuorinen?source=rss-68c6702f1b91------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*k6B9qsSi_xh9qgCE.</url>
            <title>Stories by Mikko Vuorinen on Medium</title>
            <link>https://medium.com/@mikko.vuorinen?source=rss-68c6702f1b91------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 00:15:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mikko.vuorinen/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Aurelia on Azure DevOps]]></title>
            <link>https://medium.com/@mikko.vuorinen/aurelia-on-azure-devops-d38c5ef33d20?source=rss-68c6702f1b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/d38c5ef33d20</guid>
            <category><![CDATA[aurelia]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[dotnet-core]]></category>
            <dc:creator><![CDATA[Mikko Vuorinen]]></dc:creator>
            <pubDate>Sun, 07 Jul 2019 21:22:41 GMT</pubDate>
            <atom:updated>2021-01-20T20:41:35.139Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GP6TrKQU33IZg4Q2hGhllg.png" /></figure><h4>How to set up Azure Pipelines for Aurelia application</h4><p>This article describes how to set up a CI/CD pipeline for an Aurelia SPA client. During the article we will create an example pipeline that covers all the steps from commit to release.</p><h3>The Application</h3><p>One of the easiest ways to get started with Aurelia is the <a href="https://aurelia.io/docs/cli/basics">Aurelia CLI</a>, which guides you through few key decisions on the tooling, and generates a skeleton application with all the required configuration already in place.</p><p>The sample application used in this article is created with the CLI, and the following choices are made based on personal preferences:</p><ul><li>Platform: <strong>.NET Core</strong></li><li>Bundler: <strong>webpack</strong></li><li>Transpiler: <strong>TypeScript</strong></li><li>Unit testing: <strong>Jest</strong></li><li>Integration testing: <strong>Protractor</strong></li></ul><p>You should be able to follow this article no matter what you choose, but using a different platform or a different unit testing framework will require different configuration for some of the tasks.</p><h3>Azure Pipelines</h3><p>As part of Azure DevOps, Microsoft provides full cloud-hosted CI/CD service under the name <em>Azure Pipelines</em>. Common to many Azure products, the pricing model is very tempting for individual developers. The free tier will most likely be enough to get you started — and hooked.</p><p><a href="https://azure.microsoft.com/en-gb/services/devops/pipelines/">Azure pipelines | Microsoft Azure</a></p><p>First thing is to sign up to Azure DevOps, or just sign in with your existing Azure account. Once you’re in, you can create a new project within the default organization, or create a new organization. This is all part of the bigger DevOps picture, but I will be focusing only on the Pipelines part of it.</p><p>Microsoft has a comprehensive documentation for Azure DevOps. For example the <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/languages/dotnet-core?view=azure-devops">Build, test and deploy .NET Core apps</a> page covers most of the steps to go through and tasks to define to get a simple .NET Core pipeline up and running. There are few occasions where the documentation is not quite enough or doesn’t cover some gotchas for a specific use case. Those are sometimes covered in the Feedback-section at the end of the article, so make sure to check them if you run into problems.</p><h4>Source Code</h4><p>To set up the pipeline, first you will need to select where the source code is located. If you are just trying out or starting from scratch, there are several options, but the simplest by far is GitHub. By installing the <a href="https://github.com/marketplace/azure-pipelines">Azure Pipelines application in GitHub</a>, you can add and maintain the pipeline configuration from the Azure DevOps site, without having to manually create the YAML file. Access for the application can be restricted to specific repositories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*I0YuA54eQj4kZ6F6jrPBig.png" /></figure><h4>YAML</h4><p>Configuring pipelines inevitably becomes complicated over time. Having configuration stored in text format within the version control alongside the application source code is extremely useful. This is where YAML steps in.</p><p>Azure Pipelines is based on YAML configuration files (although there is a non-YAML option still available). When you create a pipeline for the repository, a file named <a href="https://github.com/vuorinem/AureliaAzurePipeline/blob/2b10dc9ef33b038ff87a050ac504e9037db85902/azure-pipelines.yml"><strong>azure-pipelines.yml</strong></a> is added to the repository root. We will build up the YAML file in the next section of this article, but here is what the default file looks like once the pipeline has been created:</p><pre># ASP.NET Core<br># Build and test ASP.NET Core projects targeting .NET Core.<br># Add steps that run tests, create a NuGet package, deploy, and more:<br># <a href="https://docs.microsoft.com/azure/devops/pipelines/languages/dotnet-core">https://docs.microsoft.com/azure/devops/pipelines/languages/dotnet-core</a></pre><pre>trigger:<br>- main</pre><pre>pool:<br>  vmImage: &#39;ubuntu-latest&#39;</pre><pre>variables:<br>  buildConfiguration: &#39;Release&#39;</pre><pre>steps:<br>- script: dotnet build --configuration $(buildConfiguration)<br>  displayName: &#39;dotnet build $(buildConfiguration)&#39;</pre><p>As the <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&amp;tabs=schema">Azure DevOps YAML documentation</a> suggests, the best way to get started with YAML is to dive in and build a pipeline using it. The simple syntax and the choice of keywords makes it fairly straightforward to see what each configuration does. A selection of pre-defined tasks and the intellisense in the online YAML editor within Azure DevOps makes it even easier to get your hands dirty without burning your fingers.</p><h3>The Pipeline: From Commit to Release</h3><p>Now that you have the source code repository linked to Azure DevOps, you can start adding steps to the pipeline, which the <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops">pipeline agent</a> will run through when a new build is triggered. We will tackle building up the pipeline step-by-step.</p><h4>Step 0: Trigger and Agent</h4><p>The connection to a GitHub repository is specified when creating the Pipeline in Azure DevOps, but the specific trigger is specified in the YAML file. For our CI build, a simple main-branch trigger is enough:</p><pre>trigger:<br>- main</pre><p>For more complicated scenarios such as specific tags, paths or pull requests, you can take a look at the <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=azure-devops&amp;tabs=yaml">Build pipeline triggers</a> documentation.</p><p>The <strong>pool</strong> configuration specifies the type of the <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops">pipeline agent</a><strong> </strong>where the pipeline is executed. Azure DevOps has a selection of <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops">Microsoft-hosted agents</a>, where you can select the one that fits the purpose and has the required software. There are more options for setting up pipeline agents, but we’ll do fine with the default choice of latest ubuntu linux.</p><pre>pool:<br>  vmImage: &#39;ubuntu-latest&#39;</pre><h4>Step 1: Install .NET Core</h4><p>This step is only required if the agent does not have the right version of .NET Core already installed. Our application has been <a href="https://github.com/vuorinem/AureliaAzurePipeline/commit/fefd1f76fc645e1db80f4afd80345e1192995fb5">updated to latest .NET Core</a> release available at the moment, which is not one of the <a href="https://github.com/Microsoft/azure-pipelines-image-generation/blob/master/images/linux/Ubuntu1604-README.md">pre-installed SDK’s</a> in our agent.</p><p>We can install .NET Core version 2.2.300 with the following <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/dotnet-core-tool-installer?view=azure-devops"><strong>DotNetCoreInstaller</strong> task</a>:</p><pre>- task: DotNetCoreInstaller@0<br>  inputs:<br>    version: &#39;2.2.300&#39;</pre><h4>Step 2: Install JavaScript dependencies</h4><p>Next step is a straightforward call to install the dependencies defined in <em>package.json</em>. This can be done with the <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/command-line?view=azure-devops&amp;tabs=yaml">Command Line task</a>, which has a shortcut <strong>script</strong> in the YAML schema:</p><pre>- script: yarn install<br>  displayName: &#39;yarn install&#39;</pre><p>The command shows that we use <strong>yarn</strong> to install the node modules on the agent. Yarn is also used later when running build and test scripts that are defined in package.json.</p><p>The <em>displayName</em> parameter can be used to change how the task is displayed in the logs. This is especially useful for command line tasks that would otherwise display just “ CmdLine” without any information which command was executed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/402/1*H9sSxrzfKwKkf94TYNLEkA.png" /></figure><h4>Step 3: Run unit tests</h4><p>We can run unit tests with another command line task in <em>azure-pipelines.yml</em>:</p><pre>- script: yarn test<br>  displayName: &#39;yarn test&#39;</pre><p>This works fine, and the build will fail if any of the tests fail, as would be expected. However, to get details about the failed tests, we would have to look into the build logs of the failed test task. To fix this, we will need to make sure that the test results are reported in a format that Azure Pipelines understands, and for that we will need to make a small change to the application.</p><h4>Step 4: Publish test results</h4><p>The <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/test/publish-test-results?view=azure-devops&amp;tabs=yaml"><strong>Publish Test Results</strong> task</a> supports formats like XUnit, NUnit 2 and 3 and JUnit. Our Aurelia application uses <a href="https://jestjs.io/">Jest</a> to run the tests, and by default the test results are published in json, lcov, text and html format. To get the test results to show up in the pipeline Tests tab, we can use <a href="https://github.com/jest-community/jest-junit"><strong>jest-junit</strong> reporter</a> to output results in JUnit format.</p><blockquote>Note: If you use a test framework other than Jest, you will need to find a JUnit compatible output for it (such as <a href="https://github.com/karma-runner/karma-junit-reporter">karma-junit-reporter</a>).</blockquote><p>First we need to install the reporter as a development dependency by running the following command:</p><pre>yarn add jest-junit -D</pre><p>Then we can add the reporter in <em>package.json</em>:</p><pre>{<br>  // ...<br>  &quot;jest&quot;: {<br>    &quot;reporters&quot;: [<br>      [&quot;jest-junit&quot;, { &quot;output&quot;: &quot;./testresults/jest-junit.xml&quot; } ]<br>    ]<br>  }<br>}</pre><p>When specifying the jest-junit reporter, we also set the output path where the test results will be stored. This way we can tell the Azure Pipelines task where to find the test results. The complete step for publishing test results will then look like this in <em>azure-pipelines.yml</em>:</p><pre>- task: PublishTestResults@2<br>  condition: succeededOrFailed()<br>  inputs:<br>    testResultsFormat: &#39;JUnit&#39;<br>    testResultsFiles: &#39;$(System.DefaultWorkingDirectory)/testresults/*.xml&#39;</pre><p>The <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/process/conditions?view=azure-devops&amp;tabs=yaml"><strong>condition</strong>-property</a> is required to make sure test results are published for failed tests as well as successful ones. Each task has an implicit condition that prevents it from executing if the <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/process/expressions?view=azure-devops#job-status-functions">job status</a> has been set to <em>Failed</em>. By adding a condition <em>succeededOrFailed()</em> we allow publishing test results in case some of the tests fail. This will not change the job status, so it doesn’t affect any subsequent tasks.</p><p>Once we save the changes, push them to the main branch and wait for the pipeline to complete, we should see the test results in Azure DevOps. If there is a <a href="https://github.com/vuorinem/AureliaAzurePipeline/commit/d3ccee9327cd96b8ffc51ac0bad58d47ade1e31e">commit that fails a test</a>, the failed test will be highlighted and you can see more details on where and how it failed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dsgBQIFoH1iD3sMCurMa-g.png" /></figure><h4>Step 5: Publish code coverage</h4><p>Publishing code coverage can be done with the <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/test/publish-code-coverage-results?view=azure-devops"><strong>Publish Code Coverage</strong> task</a>. Again, we will need to tell Jest to output the code coverage report in a format that is supported by the task. Luckily one of the two supported formats is Cobertura, which is also built in to Jest, so all we need to do is add the configuration in <em>package.json</em>:</p><pre>{<br>  // ...<br>  &quot;jest&quot;: {<br>    &quot;coverageDirectory&quot;: &quot;&lt;rootDir&gt;/testresults/coverage&quot;,<br>    &quot;coverageReporters&quot;: [<br>      &quot;cobertura&quot;<br>    ]<br>  }<br>}</pre><p>Then we add the task to publish the test coverage from the path which we specified above:</p><pre>- task: PublishCodeCoverage@1<br>  inputs:<br>    codeCoverageTool: &#39;cobertura&#39;<br>    summaryFileLocation: &#39;  $(System.DefaultWorkingDirectory)/testresults/coverage/*.xml&#39;</pre><p>Note that the <em>coverageDirectory </em>in Jest configuration will need to match with the <em>summaryFileLocation</em> in the YAML step. As a result of a successful build, there should now be a Code Coverage tab in the build details:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ngiC-Tbf0df1llfKMNWAhQ.png" /></figure><h4>Steps 6: Publish the application</h4><p>Once we have checked that the tests pass, we can publish the application. Because our Aurelia application is set up to run on .NET Core platform, we can use the <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/dotnet-core-cli?view=azure-devops"><strong>.NET Core CLI</strong> task</a> to publish it:</p><pre>- task: DotNetCoreCLI@2<br>  inputs:<br>    command: publish<br>    arguments: &#39;--configuration $(BuildConfiguration)<br>    zipAfterPublish: True</pre><p>When you add the above task at the end of the pipeline and a new build is triggered, you might run into some issues with webpack or copying files. If that’s the case, have a look at the Troubleshooting section at the end of this article. Otherwise that should be all you need, and you have a zipped application ready to be deployed.</p><h4>Step 7: Deploy</h4><p>The last step of the pipeline is to deploy the published application. The simplest way to do this is to set up a Azure App Service that is dedicated for the pipeline, and deploy using the <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/targets/webapp?view=azure-devops&amp;tabs=yaml"><strong>Azure Web App Deployment</strong> task</a>.</p><p>But before you can deploy from Azure DevOps into your App Service, you will need to set up a <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&amp;tabs=yaml"><strong>service connection</strong></a>. The documentation for <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/library/connect-to-azure?view=azure-devops">Microsoft Azure service connection</a> describes in detail how to set up the connection.</p><p>Here’s what you should see once everything is set up. Make a note of the name of the service connection you entered (“AureliaBlogARM” in the screenshot).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M-tcq4_uwBDraxMPIq8MGA.png" /></figure><p>The deployment task below makes use of pipeline variables to avoid committing environment-specific configuration in the source code. The task in <em>azure-pipelines.yml</em> looks like this:</p><pre>- task: AzureRmWebAppDeployment@4<br>  displayName: &#39;Deploy to Azure App Service&#39;<br>  inputs:<br>    azureSubscription: &#39;$(DeploymentServiceConnectionName)&#39;<br>    appType: webApp<br>    WebAppName: &#39;$(DeploymentWebAppName)&#39;</pre><p>The two variables are <em>$(DeploymentServiceConnectionName)</em> and <em>$(DeploymentWebAppName)</em>. These can be set when editing the pipeline in Azure DevOps on the Variables page:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/521/1*fwFnoidRiZaVpvgKL2y6_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1RlH94kGZqzVCp3ekiDiRw.png" /></figure><p>The service connection name should match the Azure service connection that you added earlier. The Web App name should match the name of the App Service in Azure portal where you want to deploy the application to.</p><p>Once the variables are set, you can commit your last step. After few minutes, your Aurelia application should be up and running. Check out mine at <a href="https://aureliaazurepipelines.azurewebsites.net/">aureliaazurepipelines.azurewebsites.net</a>.</p><h3>Troubleshooting</h3><h4>Publishing Issue 1: Webpack sourcemaps</h4><p>When the pipeline tries to run the Publish task, you might see the following error message in the log files:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/741a1eab6c7b153f75289e6bc0f7509c/href">https://medium.com/media/741a1eab6c7b153f75289e6bc0f7509c/href</a></iframe><p>The cause of this issue seems to be a <a href="https://github.com/mozilla/source-map/issues/385">bug in the source map generator</a>. One simple solution for this is to remove source maps from the publish output. If this doesn’t sound ideal, you can look into the <a href="https://github.com/mozilla/source-map/issues/304">original bug report</a> and follow some of the other suggestions mentioned there.</p><p>To disable source maps, modify the <a href="https://github.com/vuorinem/AureliaAzurePipeline/commit/225da61e5b6931d5e4b7fd566884c60106ac52a8#diff-11e9f7f953edc64ba14b0cc350ae7b9d">devtool-configuration in webpack.config.js</a> to match the following code:</p><pre>devtool: production ? <strong>&#39;none&#39;</strong> : &#39;cheap-module-eval-source-map&#39;</pre><h4>Publishing Issue 2: Dist files not found</h4><p>The publishing task can also fail with the following error message (with any number of “Could not copy” errors):</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e7661b4e22cc6497c4d1b924b281bd2a/href">https://medium.com/media/e7661b4e22cc6497c4d1b924b281bd2a/href</a></iframe><p>This is an issue most likely caused by running both MSBuild based publish tasks for the .NET Core application and Gulp based build tasks for the Aurelia application. Somewhere along the line the list of files in <em>wwwroot/dist</em> folder gets out of sync, and MSBuild tries to publish files that no longer exist. To fix this, you can make sure the dist-folder is cleared before publishing.</p><p>Add a dotnet clean task before the publish task:</p><pre>- scriot: dotnet clean<br>  displayName: &#39;dotnet clean&#39;</pre><p>Remove the dist-folder when running the clean-up by adding the following task to the <em>project.csproj</em> file:</p><pre>&lt;Target Name=&quot;CleanDist&quot; AfterTargets=&quot;Clean&quot;&gt;<br>  &lt;RemoveDir Directories=&quot;wwwroot\dist&quot; /&gt;<br>&lt;/Target&gt;</pre><p>Thank you for reading! I hope you learned few things, or at least got excited to try out Azure Pipelines. If you have any suggestions or spot something that would need clarification, please leave a comment or message me in twitter <a href="https://twitter.com/mvuorinen">@mvuorinen</a>.</p><p><em>Title image modified from </em><a href="https://www.flickr.com/photos/freshyill/3219638385"><em>Super Mario Brothers 1–1 Desktop</em></a><em> by </em><a href="https://www.flickr.com/photos/freshyill/"><em>Coleman</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d38c5ef33d20" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NDC { London } 2019 — Wrap-Up]]></title>
            <link>https://medium.com/@mikko.vuorinen/ndc-london-2019-wrap-up-cc5166563dea?source=rss-68c6702f1b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc5166563dea</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Mikko Vuorinen]]></dc:creator>
            <pubDate>Mon, 04 Mar 2019 00:55:08 GMT</pubDate>
            <atom:updated>2019-03-22T16:28:26.688Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m0HuGmIEa9z8KPNxUnzS5A.png" /></figure><h3>NDC { London } 2019 — Wrap-Up</h3><p>The largest tech conference for .NET developers in Europe found its way to London at the end of January. A range of excellent speakers and interesting topics kept me going (and tweeting) through the three days and 20 different talks.</p><p>In this post I will give a quick overview of some of the most interesting talks I attended. Recordings are available in <a href="https://www.youtube.com/channel/UCTdw38Cw6jcm0atBPA39a0Q">NDC Conferences YouTube channel</a>, so I have added links to the talks and definitely recommend you check those out.</p><h4>Wednesday { 30th January }</h4><p>The first keynote kicked off the conference on Wednesday morning, with a frighteningly incisive thoughts on how social media has surfaced the issues in our relationship with information and misinformation. In the talk titled <a href="https://youtu.be/ADakATOLtEQ"><em>Welcome to the Machine</em></a>, <a href="https://twitter.com/hhariri"><strong>Hadi Hariri</strong></a> dives deep into the problem and explains how we’ve ended up welcoming a combination of Orwellian and Huxleian dystopy. So, clearly a perfect start for a tech conference! In all seriousness, it was a wake up call to start paying much more attention to the ethics of the work we do, and to think about how to be a more responsible individual as a developer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*0c6inTS1dzrdH9hfSr1b9w.png" /></figure><p>Later on, one of the highlights of the day was <a href="https://twitter.com/claresudbery"><strong>Clare Sudbery</strong></a>’s talk on <a href="https://youtu.be/IUAmowond7w">how to teach and communicate with experienced developers</a>. The talk really sparked joy for me, and I ended up going to many more talks on learning, teaching and leadership. In Sudbery’s talk I learned why empathy is a key factor in successful communication, how safety and security drive efficiency in the workplace, and I left with one of the most brilliant insights I’ve learned in a while: <em>nobody should be given the goal to strive for perfection — they will be condemned to fail to reach that goal</em>.</p><p>After the conference I also listened to a .NET Rocks! podcast episode 1621: <a href="https://dotnetrocks.com/?show=1621"><em>Teaching Experienced Developers with Clare Sudbery</em></a>, which was a nice recap of the talk, plus some interesting side discussions. The sketchnotes by <a href="https://twitter.com/ijohnson_TNF">Ian</a> are another excellent summary of the talk. And if you haven’t, do take a look at his other <a href="https://twitter.com/IJohnson_TNF/media">sketchnotes</a>, from NDC and a lot of other conferences as well!</p><h3>Ian on Twitter</h3><p>Teaching new tricks by @ClareSudbery #ndclondon #sketchnotes</p><p>Communication in distributed systems was one of my focus areas during the conference. A perfect start into the topic was <a href="https://twitter.com/jbogard"><strong>Jimmy Bogard</strong></a>’s talk <a href="https://youtu.be/IMvrg0bN9-o"><em>Life Beyond Distributed Transactions</em></a>, that explains thoroughly the problems we face when migrating from traditional ideas of building systems on atomicity and other <a href="https://en.wikipedia.org/wiki/ACID_(computer_science)">ACID</a> principles into a highly connected and fast evolving environment of clouds and microservices. He continues by introducing <em>messaging </em>as a solution, including both the theoretical architecture with its queues, dispatchers and transactional boundaries explained, and hands-on code examples.</p><h4>Thursday { 31st January }</h4><p>On the second day I continued on the topic of learning, first with <a href="https://twitter.com/reverentgeek"><strong>David Neal</strong></a>’s <a href="https://www.youtube.com/watch?v=LzKCwhVYGa4"><em>Leadership Guide for the Reluctant Leader</em></a>. He pointed out that every one of us has strengths and potential to impact our work place and communities in positive ways. Everyone can be a leader, and there are leadership skills and virtues that we all should learn to be better leaders.</p><p><a href="https://twitter.com/oliravi"><strong>Olivia Liddell</strong></a>’s talk on <a href="https://youtu.be/RpS0PRYnD5E"><em>Improving Your Communication Skills</em></a> had many strategies and practical advice on how to become better at communicating with people, especially when teaching and talking about technical topics for different audiences. The talk and the discussion afterwards was full of advice for speaking and teaching, and also for communicating in one-to-one conversations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*28rhKMC4wlNSiA-rc0qcAA.png" /><figcaption>(<a href="https://www.freepik.com/free-photos-vectors/background">Background vector created by rawpixel.com — www.freepik.com</a>)</figcaption></figure><p>After several talks on “people skills”, one thing was becoming clear to me: in all communication, be it teaching, public speaking, leadership or meetings, the key to success is empathy. Understanding your listeners’ perspective makes communicating more efficient and a more pleasant experience for both parties.</p><p>In more technical side of the talks, I surprised my co-workers (and myself) by choosing a <a href="https://youtu.be/e6idWxzGiKE">WPF/WinForms talk</a> for my Thursday afternoon entertainment. <a href="https://twitter.com/onovotny"><strong>Oren Novotny</strong></a> explained how .NET Core 3 will allow desktop development to make use of .NET Core capabilities such as performance improvements and side-by-side installation, and what kind of changes it will bring to the platform. The talk had great advice on how to decide if/when migrating to Core makes sense.</p><p>Another excellent technical talk, and continuation to my distributed communication journey, was <a href="https://twitter.com/ICooper"><strong>Ian Cooper</strong></a>’s <a href="https://youtu.be/2YJpkl2uZ18"><em>Data on the Inside, Data on the Outside</em></a>. To tackle the issues that arise when data is distributed into multiple independent services (instead of a central database), Cooper tells how separating data that resides inside a single service from data that is visible to outside the service boundary can help (based on the paper <a href="http://cidrdb.org/cidr2005/papers/P12.pdf"><em>Data on the Outside versus Data on the Inside</em></a> by Pat Helland). The talk also expands on topics like reference data and versioning, messaging and event-driven architecture, <a href="https://martinfowler.com/articles/201701-event-driven.html#Event-carriedStateTransfer">Event-Carried State Transfer</a> and logs versus queues. So definitely worth watching through if you are interested in how to handle data in mircoservice architecture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/377/1*JdQjIjVFqemiQBEVF2R14Q.png" /></figure><h4>Friday { 1st February }</h4><p>The final conference day started with <a href="https://twitter.com/shanselman"><strong>Scott Hanselman</strong></a>’s pleasantly demo-heavy keynote <a href="https://youtu.be/a2IK82xn2uE"><em>The Microsoft Open Source Cinematic Universe — Phase 2</em></a>. He explains Microsoft’s journey to the properly open-source .NET Core, and demonstrates the powerful command-line tools and cross-platform capabilities of .NET Core 3. Examples include Core running on desktop, WebAssembly, and a tiny IoT device <a href="https://www.wildernesslabs.co/Meadow">Meadow</a> from Wilderness Labs that runs .NET in a microcontroller. I’m really looking forward to coding with <a href="https://github.com/dotnet/iot/">dotnet IoT</a>!</p><p>Possibly the most interesting and very likely the most difficult talk I attended was about <a href="https://youtu.be/-ykrmDmVAHs"><em>Async injection</em></a> by <a href="https://twitter.com/ploeh"><strong>Mark Seemann</strong></a>. It tackles the problem of leaky abstractions when we change the implementation of a dependency to be asynchronous. Seemann goes through the process of applying the concept of monads to the problem, and reaches the solution that replaces dependency injection with behaviour injection. There is also a more general lesson in the story, about how to answer a question when the question itself is the problem, by un-asking the question. I got much more out of this talk than just an explanation of how to solve the problem of leaky abstractions. After going through the accompanying blog post about <a href="http://blog.ploeh.dk/2019/02/11/asynchronous-injection/">Asynchronous Injection</a> and its <a href="https://github.com/ploeh/asynchronous-injection">sample code</a>, I will look into the recommended read <a href="https://en.wikipedia.org/wiki/G%C3%B6del,_Escher,_Bach"><em>Gödel, Escher, Back: An Eternal Golden Braid</em></a>, and hopefully I will finally get my feet wet with functional programming as well.</p><p>My final pick, and arguably the most important one, is <a href="https://twitter.com/likeOMGitsFEDAY"><strong>Jennifer Wadella</strong></a>’s and <a href="https://twitter.com/jonskeet"><strong>Jon Skeet</strong></a>’s <a href="https://youtu.be/EDxbZK0Imzw"><em>Society (n+1).0: smashing the patriarchy and other ways of changing the world</em></a>. Just reading the comments on YouTube and seeing the number of downvotes compared to other (some of them equally non-technical) talks, it is quite clear that we still have a lot to learn about feminism. Just mentioning that word makes people defensive, even in seemingly progressive tech industry conferences and workplaces, including my own. The talk first goes through the problems we face when discussing about feminism, such as the lack of shared vocabulary, and concepts like <a href="http://geekfeminism.wikia.com/wiki/Toxic_masculinity">toxic masculinity</a> that are easily misunderstood. Later on, Wadella and Skeet bring up some of the symptoms of patriarchy in our society, and also touch on sexism that is far more common and everyday problem than most men can imagine. As recommended by Skeet, the next book for me to read will be <a href="https://www.goodreads.com/book/show/21251323-everyday-sexism"><em>Everyday Sexism</em></a>, but if you’re not quite ready to pick up a book, you can head to the <a href="https://everydaysexism.com/">Everyday Sexism Project website</a> to read how different people experience sexism in their lives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/923/1*QOOAgFwrhGqd-907hSQkmA.png" /></figure><p>Thank you for reading! I would love to hear your thought on the talks, so please leave a comment below or tweet me @mvuorinen.</p><p>I also plan to write a follow-up post to go more in-depth into a specific topic, including more background research and my personal opinions and experiences. Let me know in the comments if you have a topic you would like to read more about.</p><p>Updated on 22nd March 2019: All the talks I mentioned are now available on YouTube, and I have added the links above.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc5166563dea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NDC { London } 2019 — Start the Hype!]]></title>
            <link>https://medium.com/@mikko.vuorinen/ndc-london-2019-start-the-hype-49e638db07ed?source=rss-68c6702f1b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/49e638db07ed</guid>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[london]]></category>
            <dc:creator><![CDATA[Mikko Vuorinen]]></dc:creator>
            <pubDate>Mon, 26 Nov 2018 11:50:51 GMT</pubDate>
            <atom:updated>2018-11-26T11:50:51.007Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pLEQ5_bXvGNxTPMbh4_t2g.png" /><figcaption><a href="https://www.flickr.com/photos/palojono/9141421753/">Sunset view of London from Level 39</a> by <a href="https://www.flickr.com/photos/palojono/">Jono Hey</a></figcaption></figure><h3>NDC { London } 2019 — Start the Hype!</h3><h4>First peek at the conference agenda</h4><p>About 69 days, 9 hours, 59 minutes and 22 seconds from the writing of these words, I will be at the Queen Elizabeth II Centre in Westminster, London, UK. Sounds fancy! And it definitely looks like I’m in for a fancy treat.</p><p>The developer conference NDC London 2019 will take place at the end of January, and I’m going to be there! I will be covering the highlights before, during and after the conference, so expect to see me tweetin’ and bloggin’ away for several months. This time I’ll take a quick look at the agenda and some of the most interesting speakers.</p><p>The first thing to note when looking at the <a href="https://ndc-london.com/agenda">agenda</a> is that there are two keynote speakers, <a href="https://twitter.com/hhariri">Hadi Hariri</a> on Wednesday morning and <a href="https://twitter.com/shanselman">Scott Hanselman</a> on Friday morning. Quite unlike the keynote by <a href="https://twitter.com/MadsTorgersen">Mads Torgsen</a> at NDC Oslo earlier this year, the two London keynote speakers paint with a rather broad brush, and from what I can see, the picture is closer to art than science. With the rest of the three days packed with in-depth technical nitty gritty, I believe the keynotes will fit in perfectly.</p><p>Next thing to note is that there are <strong>so many good talks</strong>! The very first session after the keynote has for example <a href="https://twitter.com/billwagner">Bill Wagner</a> on <a href="https://ndc-london.com/talk/nullable-reference-types-are-coming-are-you-ready/">nullable reference types</a>, <a href="https://twitter.com/ethomson">Edward Thomson</a> on <a href="https://ndc-london.com/talk/a-piece-of-git/">Git</a>, and <a href="https://twitter.com/DamianEdwards">Damian Edwards</a> with <a href="https://twitter.com/davidfowl">David Fowler</a> on <a href="https://ndc-london.com/talk/what-you-need-to-know-about-asp-net-core-2-2/">ASP.NET Core 2.2</a>. And while I wonder how to decide between the three, I realize that a fourth talk about <a href="https://ndc-london.com/talk/observability-and-the-development-process/">development and observability</a> by <a href="https://twitter.com/cyen">Christine Yen</a> sounds so cool that I need to consider choosing it even over the D&amp;D duo.</p><p>Going through the whole agenda and looking in to the talks and speakers would take a long time, and I will definitely do that at some point, but for now I will just pick few that piques my interest.</p><ul><li>For a long time now I have been meaning to try GraphQL, but haven’t really got to it. <a href="https://ndc-london.com/talk/graphql-will-do-to-rest-what-json-did-to-xml/">GraphQL Will Do To REST What JSON Did To XML</a> by <a href="https://twitter.com/gethackteam">Roy Derks</a> looks like it might be the perfect nudge.</li><li>With a growing interest towards event-driven architectures, I would definitely be keen to listen to the <a href="https://ndc-london.com/talk/life-beyond-distributed-transactions-an-apostates-implementation/">Life Beyond Distributed Transactions: An Apostate’s Implementation</a> by <a href="https://twitter.com/jbogard">Jimmy Bogard</a>. And I’m really keen to look into the article it refers to.</li><li><a href="https://twitter.com/meekrosoft">Mike Long</a> has a practical but research-based approach to DevOps in <a href="https://ndc-london.com/talk/avoiding-the-agile-alignment-trap-with-devops/">Avoiding the Agile Alignment Trap with DevOps</a>, which could prove to be extremely useful.</li><li>Without doubt the <a href="https://ndc-london.com/talk/panel-discussion-on-the-future-of-net/">Panel discussion on the future of .NET</a> is one to keep an eye on.</li><li>Again there is a bunch of interesting talks on personal and career growth, like <a href="https://ndc-london.com/talk/beyond-developer/">Beyond Developer</a> by <a href="https://twitter.com/tastapod">Dan North</a>, <a href="https://ndc-london.com/talk/think-like-a-trainer-improving-your-communication-skills/">Think Like a Trainer: Improving Your Communication Skills</a> by <a href="https://twitter.com/oliravi">Olivia Liddell</a>, <a href="https://ndc-london.com/talk/leadership-guide-for-the-reluctant-leader/">Leadership Guide for the Reluctant Leader</a> (oh yes!) by <a href="https://twitter.com/reverentgeek">David Neal</a> and <a href="https://ndc-london.com/talk/teaching-new-tricks-how-to-enhance-the-skills-of-experienced-developers/">Teaching New Tricks — How to enhance the skills of experienced developers</a> by <a href="https://twitter.com/ClareSudbery">Clare Sudbery</a>. And most likely even more. I’ll definitely pick some of those.</li><li>Something completely new to me would be <a href="https://ndc-london.com/talk/introducing-razor-components-in-asp-net-core-3-0/">Introducing Razor Components in ASP.NET Core 3.0</a> by <a href="https://twitter.com/danroth27">Daniel Roth</a>. There’s also a talk dedicated to Blazor by <a href="https://twitter.com/stevensanderson">Steve Sanderson</a>, <a href="https://ndc-london.com/talk/blazor-a-new-framework-for-browser-based-net-apps/">Blazor, a new framework for browser-based .NET apps</a>.</li><li>There’s also a journey all the way from history in <a href="https://ndc-london.com/talk/how-we-got-here-the-history-of-web-development/">How We Got Here — The History of Web Development</a> by <a href="https://twitter.com/richcampbell">Richard Campbell</a> to the future in <a href="https://ndc-london.com/talk/futurology-for-dummies-the-next-30-years-in-tech/">Futurology for Dummies — the Next 30 Years in Tech</a> by <a href="https://twitter.com/markrendle">Mark Rendle</a></li></ul><p>In summary, the agenda looks great, as I expected it would. Compared to the NDC Oslo agenda, it’s a bit broader and less technology-intensive, with quite a few talks that go beyond software. Still, it’s definitely one of the most developer-centered conferences. I’m really looking forward to it, and I can’t wait to spend three days running around like a headless Chrome and tweeting my way through the talks :).</p><p>That’s it for now, but rest assured, there’s more where this came from!</p><p><em>Are you coming to NDC London?</em> Leave a comment, I would love to hear your thoughts, and maybe catch up at the conference.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49e638db07ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NDC Oslo: The Experience]]></title>
            <link>https://medium.com/@mikko.vuorinen/ndc-oslo-the-experience-e2b73b34ea79?source=rss-68c6702f1b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2b73b34ea79</guid>
            <category><![CDATA[experience]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[oslo]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Mikko Vuorinen]]></dc:creator>
            <pubDate>Thu, 01 Nov 2018 11:54:22 GMT</pubDate>
            <atom:updated>2018-11-01T11:54:22.897Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9DhnpVysgwJq5woyeFcyig.png" /></figure><h4>Tweeting my way through the 3 days and 17 talks</h4><p>In June 13–15, I attended the NDC 2018 conference in Oslo, Norway. For three days I sat (or stood) in 17 talks about and around software development, wrote 150 tweets, and learned about security, architecture, microservices, event sourcing, front-end frameworks, career development and more. For three nights I relaxed, made some networking attempts, and got lost in the streets of Oslo.</p><p>I will leave more technology-focused topics for other articles. In this one, I wrap up the the experience and the atmosphere from the few days in Oslo.</p><h3>Tuesday</h3><p>The journey started from Aberdeen airport with my colleague Ben, and a delightfully quick flight straight to Oslo. I had never been in Norway, so this was my first proper contact with the country of expensive beer and second-happiest people in the world (there might be a connection there, just look up Finland).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/383/1*ed1KrPGVmjXL8EvHhLB6lQ.png" /><figcaption>All ready for takeoff!</figcaption></figure><p>As soon as we arrived in the central station, the schedule was packed, pretty much all the three days until our return flight. After the check-in to the hotel, a quick shower and a snack, we headed to the NDC Community Tuesday. Like many developers, I’m really bad at talking to people I don’t know (and most of the time to those I know as well), so the “mingling” was pretty much non-existent at that point. I will need to push myself a bit more next time.</p><p>The first talks of the week were provided by the Norwegian .NET User Group. Kasey Uhlenhuth, Mads Torgersen and Jon Skeet gathered a full room. It was quite exciting to finally get to see some big names in person, and I got a nice sneak peek to what’s to come in the following days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vbk1DZHfJ4cxg_0j6FopRw.png" /><figcaption>First talk of the week: Kasey Uhlenhuth and the future of Visual Studio</figcaption></figure><p>After the meetup, we navigated our way (i.e. followed some people who looked like they knew where they were going) to the Geekbeer gathering at a local pub called Mekaniske Verksted, with a bit weird angle to hipsterity, including stuffed jeans as a decoration. Well, now that I look at it, it does kind of contribute to the “mechanics’ workshop” feeling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XH6bFfkYjCtU-Oe8UcYMBg.png" /><figcaption>Mekaniske Verksted</figcaption></figure><p>After a couple successful choices of beverages, I had a chance to chat with an NDC veteran from Oslo. We talked first a bit about the history of NDC, and later about our work and how individual circumstances have a great influence on how companies approach new technology. After a while, and with the next morning in the back of my head (as well as increasingly empty stomachs), Ben and I headed back to grab some dinner, after which I basically fell down into the bed.</p><h3>Wednesday</h3><p>The great thing about hotels is that the temptation of the buffet breakfast easily beats the inconvenience of the early start. Quite happy with the offerings, I was all fed and ready at the conference center well before (almost 5 minutes that is) the start of the keynote.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UWu6cQo_mRY0wp7Dmn7y6g.png" /><figcaption>Less than 3 minutes to go, the buzz is real!</figcaption></figure><p>I had seen the venue the previous night at the community meetup, but it was nothing like the the view on the day, with all the stalls and full of people. I may be an introvert, but I do like a bit of buzz every now and then, so I was quite impressed and looking forward to the show when I stepped into the main arena.</p><p>Someone mentioned to me at some point how one of the differences between NDC and the likes of Build and Google IO is that NDC is developer-centred, to the extent that the keynote speaker stage is literally in the centre of all the developers that gather around.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nQsTzeO9pEYVgmA6ZlufsQ.png" /><figcaption>Mads Torgersen on the keynote stage</figcaption></figure><p>The rest of the day went by in a flash. Thanks to the ingenious idea of serving food in small portions throughout the day, I managed to get a good meal by grabbing a quick bite every now and then between the talks. And a fair amount of coffee of course. One of my favourites was the fresh green salad that they actually grew behind the stall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0fygfGtd--QvYMopZHvaxw.png" /></figure><p>By the end of the first day I was totally overwhelmed with everything. I don’t know how I managed to sit through every single session with so much content, and still pay attention without much trouble to be honest. Most of it is definitely thanks to the very good speakers and the range of topics to make sure there was always at least few interesting talks to choose. Tweeting also helped me to avoid fatigue by keeping me active during the talks, and kept my mind working so that I could pick the main points, quotes, and interesting views from the speakers.</p><p>After the final talk, while walking out from the venue and looking at the beautiful weather, I was very much looking forward to relaxing with a light run into the streets of Oslo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j1oRHsFl-CAoEAkwfHRuzw.png" /><figcaption>I found a map!</figcaption></figure><p>I ended up spending well over an hour running here and there (honestly couldn’t really tell where, I only relied on Google Maps when I really needed to get back for dinner).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zKNb-sC9XUyQFM58QI5Xcw.png" /><figcaption>Dinner at the Oslo harbor</figcaption></figure><h3>Thursday</h3><p>The second conference day was even more packed than the first one. Luckily I now had some experience with the breakfast buffet and it’s vegetarian offerings to optimize my morning schedule.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ir6XO5YwDN14a3WqTRcb_g.png" /><figcaption>The local brew</figcaption></figure><p>When it came to selecting which talks to go to see, I took the liberty of going a bit outside my planned schedule. The original idea was to re-visit my plan after the first day, once I had more of an idea what the conference was like and what was the focus and level of the talks. However, I didn’t really have time or energy to do that after the first day, so I decided to take my picks on the spot. In some cases I had a chat with Ben so that we could divide and conquer.</p><p>With more confidence and caffeine in my veins than the first day, some of the talks prompted me to ask few questions from the speakers after the talk. I ended up having less time to walk around to the next talk, and sadly less time to browse and munch the offerings of the food stalls. I made sure to make it up by getting my fair share after the last talk. Although some of the foods ran out (especially when you’re restricted to veggie/fish), there were still plenty to go around until the end of the day.</p><p>On top of the seven talks, Thursday evening included the NDC Party and the fully packed PubConf event with more… “talks”. I’m not a fan of crowds, and find it quite difficult to talk to anyone when there are hundreds of people around, so I was very keen on joining a group of locals when we got to an invite to a pub after the party. Somehow we ended up having a chat with someone in the NDC agenda committee, and I conveniently started to dream about one day giving a talk at NDC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KuCeyzAMlVubqlOeGlu8Kw.png" /><figcaption>Live music at the NDC Party</figcaption></figure><h3>Friday</h3><p>The last day of the trip got a perfect start with an overdose of fruit-filled pancakes. A less perfect side effect was that I was few minutes late from the first talk…</p><p>Although the last day was a bit of a stub because we had to catch a flight back to Aberdeen, I learned a lot about perhaps unexpected topics. One of the most interesting events of the day was <a href="https://twitter.com/thehwshow">The Hello World Show</a> panel discussion. Four panelists gave a short talk on topics of their interest and answered to questions from the audience.</p><p>And then it was time to head home. It took a while to recover from the intensive three-day run and the travelling, but it was definitely worth every minute.</p><h3>Mikko Vuorinen on Twitter</h3><p>Made it safely back home in #Aberdeen from #NDCOslo! &quot;And all I got was this...&quot; 😉 @NDC_Conferences @ailon @BrighterCommand @DevExpress @knowitnorge @OctopusDeploy @Praqma @WixEng 😍</p><p>For those thinking if going to a conference is worth it, here’s few things I would highlight that I got out from NDC.</p><ul><li>Being a part of an event gives a feeling of being part of the community. It took me a while to get over the the term “community” being something more than just a cliché, but understanding that there are people struggling with the same problems and that you can actually help each other is actually meaningful. Behind every stack overflow answer, there’s a fellow engineer.</li><li>Hearing talks where new technology is being critically assessed and used in practice gives a different kind of excitement from what you get from a marketing events or technology evangelists. To put it in other words, instead of “that’s cool, I want to try that!” you get “that’s interesting, I should add that to my toolbox.”</li><li>Unlike a lot of events, in NDC you are among other developers who understand the daily struggles of making a software tick more than anyone. You can feel it from the way the speakers speak, how the audience asks questions, and how the party is full of people trying to find a seat just because standing alone is clearly more awkward than sitting alone.</li><li>Although there’s heaps of content available online, and NDC as well has most of the talks available online, how likely it is for you to listen through 17 talks within one week? Having several days dedicated to learning, and really with no other choice, is just an awesome chance to learn a lot.</li><li>If you’re anything like me, you will get excited imagining yourself standing in the front of the audience and giving a talk about something that you passionately want other developers to know about. It might take a while, but I don’t think there’s any chance I will be giving up on my dream of giving a talk at a conference like NDC.</li></ul><p>Thank you for reading! As always, please leave a comment if you have anything you would like to ask.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2b73b34ea79" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ScotSoft 2018 Wrap Up]]></title>
            <link>https://medium.com/@mikko.vuorinen/scotsoft-2018-wrap-up-23f37bbe4dc9?source=rss-68c6702f1b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/23f37bbe4dc9</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[scotland]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[conference]]></category>
            <dc:creator><![CDATA[Mikko Vuorinen]]></dc:creator>
            <pubDate>Mon, 01 Oct 2018 13:40:08 GMT</pubDate>
            <atom:updated>2018-10-12T14:21:27.812Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jrPCAFTMG4NbAmXXU2r_Sg.png" /></figure><p>This year’s <a href="https://scotsoft.scot/">ScotSoft</a>, the annual developer conference in Edinburgh on 27th of September, offered tracks on <em>testing</em>, <em>security</em>, <em>fintech</em>, <em>blockchain</em>, and other interesting talks including an excellent keynote by <strong>Dylan Beattie</strong>. Here’s a list of talks I attended with some key takeaways.</p><h4><a href="https://twitter.com/dylanbeattie">Dylan Beattie</a>: Happy Code</h4><p>The keynote was probably the most interesting talk of the day, with a lot of good advice on topics like learning and user experience.</p><ul><li>The user experience of development tools, just like any software, is affected by different learning curves. For successful teams, it is important that developers are happy learning and using the tools.</li><li>There should be a clear path <strong>leading the user from the problem to the solution</strong>, while teaching the user how to solve the problem on their own the next time it occurs. This also applies to things like error messages and debugging tools.</li><li>Web frameworks that abstract out not just the implementation but also the structure of the web and how it works can be decremental for learning. Moving outside the framework’s “comfort zone” can be difficult.</li><li><strong>Monitoring </strong>gives early visibility of problems and allows solving them proactively. This is much more pleasant experience for developers, users and managers than reacting to a complaint.</li><li>Logging is needed to diagnose problems. Different logging levels should be used appropriately to reduce unnecessary notifications. (See also <a href="https://labs.ig.com/logging-level-wrong-abstraction">https://labs.ig.com/logging-level-wrong-abstraction</a>)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6J_i0riTrH1Elt18oB2GOA.png" /><figcaption>A slide from the keynote showing one way to ensure different logging levels are used appropriately.</figcaption></figure><ul><li>Naming helps with remembering, familiarizing and referring to all things that can be named. It also builds a sense of ownership and responsibility over systems.</li><li>We all build user experiences, and sometimes the users are other developers. It is our own responsibility to make sure that the user experience is good.</li></ul><h4><a href="https://twitter.com/MrHinsh">Martin Hinshelwood</a>: A DevOps story</h4><p>The story of the Microsoft VSTS (now <a href="https://azure.microsoft.com/en-us/blog/introducing-azure-devops/">Azure DevOps</a>) team adopting agile methodology and DevOps.</p><ul><li>Using “one engineering system to rule them all” helps to remove friction between teams and makes moving between teams easier.</li><li>Agile is not wild west. There are guiding principals to align the way how different teams and individuals work, while other practices are decided more autonomously by each team. <strong>The line between aligned and autonomous</strong> should be drawn with shared understanding.</li><li>Using continuous delivery forces some level of merging between development and testing, because at the end of each development cycle there should be something ready (and tested) to be delivered.</li><li>Collecting telemetry from production is essential for spotting and solving problems, as it is practically impossible to catch all the problems in the testing environment.</li></ul><h4><a href="https://twitter.com/alistairhann">Dr Alistair Hann</a>: Building an Open Health Platform</h4><ul><li>There are surprising similarities between information systems in health care and travelling industries. With data stored in isolated silos and controlled by outdated software, it is challenging to build a nationwide platform for open data.</li><li>The key for a great solution is working with all the different parties and stakeholders as much as possible, and using or creating standards that benefit everybody.</li><li><strong>Deployment != Delivery</strong>. It is not enough to ship the solution and be done with it. Making sure that the users have access to the solution, and its features are understood and correctly used, is essential for success. This requires both quantitative monitoring and qualitative feedback.</li></ul><h4><a href="https://twitter.com/rocketbootkid">Richard Paterson</a>: Talking about talking (about testing)</h4><p>The opening talk for the new testing track was not what I expected, but definitely a useful and encouraging talk. There were so many good advice on public speaking that I couldn’t keep up writing all of them down, so I’m really happy to get my hands on the slides.</p><ul><li>All of us know something that someone else might not know. That’s why your story is worth sharing.</li><li>There’s rarely one right way of doing things. Bringing your personality into a talk will show others your unique way.</li><li>The most important advice to help you give a best possible talk and avoid the fear and anxiety: <strong>Prepare! </strong>Spend enough time building the talk, practice as much as you can, use recordings to see and hear yourself talking.</li></ul><h4><a href="https://twitter.com/NJMarham">Nicola Marham</a>: Open Banking</h4><p>I wasn’t sure what to expect from the FinTech track, but I was quite excited when I listened to the possibilities of <a href="https://www.openbanking.org.uk/">Open Banking</a>.</p><ul><li>There are very interesting innovations throughout the history of banking. Some of the ones that we now take for granted are surprisingly recent.</li><li>Some of the most recent innovations that are in some way related to banking are <a href="https://en.wikipedia.org/wiki/Face_ID"><em>FaceID</em></a>, <a href="https://www.behaviosec.com/"><em>BehavioSec</em></a>, <em>Dynamic CVV</em> and <em>biometric contactless</em>.</li><li>European legistlation <a href="https://ec.europa.eu/info/law/payment-services-psd-2-directive-eu-2015-2366_en"><em>PSD2</em></a><em> </em>allows third party providers to use banking services such as transaction details and payment initiation to create new solutions and banking services.</li></ul><h4><a href="https://twitter.com/colinhewitt">Colin Hewitt</a>: How to Succeed with SaaS</h4><p>The next FinTech talk was focused on the business side of open banking, with experiences from the success of <a href="https://floatapp.com/">Float</a>.</p><ul><li>The holy grail of SaaS: large market, scale for larger customers, network effect, become a platform.</li><li>Keys for success: product stickiness (make changing the provider unattractive), price expansion, solve a core pain point, low effort to get started, multiple stakeholders.</li><li>A more general takeaways for building a successful product: think about the business model from the very beginning, start with something that solves the correct problem, and <strong>concentrate on solving the problem</strong> instead of the product. Market and user research are essential tools for this.</li></ul><p>This is not the first time I ran into the idea that is best described by the <a href="https://leanservicecreation.com/">Lean Service Creation</a> folk: “Love the problem, not the solution.”</p><h4><a href="https://twitter.com/FedeCharosky">Federico Charosky</a>: Security in the time of DevOps</h4><p>Last talk of the day was packed with security-related information and expertise. I found myself struggling to keep up at times, but learned a lot!</p><ul><li>Historically developers have been working more or less separate from the security concerns. With the integration of development and operations in DevOps, security should also be a part of the equation.</li><li>Security industry used to concentrate on identifying problems and protecting systems from them. Recently it has moved forward to work from the assumption of a breach, focusing on detecting them, minimizing the effects, and recovering.</li><li>Traditional security practices can now be mostly automated using tools that identify security issues and help protecting against them. There are tools that, for example, analyze the source code or go through the dependency tree. These tools are regrettably rarely used, even when there are free options available.</li></ul><p>I hope you enjoyed the article, and found some interesting ideas. Also check out my <a href="https://medium.com/@mikko.vuorinen/scotsoft-2017-ba0069007704">ScotSoft 2017 write-up</a>.</p><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23f37bbe4dc9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[See you at NDC { Oslo } 2018!]]></title>
            <link>https://medium.com/@mikko.vuorinen/see-you-at-ndc-oslo-2018-3e10db968fe?source=rss-68c6702f1b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e10db968fe</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[conference]]></category>
            <dc:creator><![CDATA[Mikko Vuorinen]]></dc:creator>
            <pubDate>Sun, 10 Jun 2018 17:30:09 GMT</pubDate>
            <atom:updated>2018-06-10T17:30:09.681Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AcSQk9wzlorJJ1flVS24vA.jpeg" /><figcaption><a href="https://www.flickr.com/photos/arild_storaas/227482918/">Nydalen T</a> by <a href="https://www.flickr.com/photos/arild_storaas/">Arild Storaas</a> (CC BY-NC-ND 2.0)</figcaption></figure><h4>The plan for my first NDC conference</h4><p>My employer <a href="https://www.codify.ltd.uk/">Codify</a> has given me an excellent opportunity to go to <a href="https://ndcoslo.com/">NDC Oslo</a>, which is one of the major developer conferences worldwide. To get as much as I can out of it, preparation is the key. Here’s what I have planned for my three days in Oslo.</p><h3>Preparing to prepare</h3><p>The first push for me to start preparing was a tweet by <a href="https://twitter.com/NDC_Conferences">@NDC_Conferences</a>. It included a link to a book by <a href="https://medium.com/u/7f6a1877be4b">Alan Mendelevich</a> that — based on the title — seemed just what I needed and perfectly timed:</p><h3>NDC Conferences on Twitter</h3><p>Our NDC Oslo 2018 speaker @ailon wrote this great book called &#39;Conferences for Introverts&#39;. Use our special coupon link and get the e-book for free https://t.co/6Hbaq5ZADY #ndcoslo</p><p>I decided to <a href="https://t.co/QbIPp3dUEO">grab a copy</a> to my Kindle. For the next several lunch breaks and weekend café visits, I switched <a href="https://www.goodreads.com/series/49118-culture">the Culture</a> to the conference guide. And I was awarded with an impressive experience and insight that clearly came from a like-minded introvert. The book sparked my enthusiasm, not just for the chance to listen to the conference talks and learn from experienced speakers first-hand, but also to participate in interesting discussions, meet other developers, get to know people around the world and let them know me. That almost sounds like… networking.</p><p>The most influential part of the book, something that changed completely how I (try to) introduce myself to new people, was the idea how to handle a simple “What do you do?” question:</p><blockquote>The thing “you do” is not necessarily what occupies most of your time on business days. It’s the thing you want to be known for, or the thing that you are most passionate about, or the thing you want to get into.</blockquote><p>After reading the quote above and a paragraph about elevator pitch, I realized how boring it would be if someone explained what they do to by listing things that every developer struggles with most of their day. There’s so much in software engineering that I’m passionate about. And to figure I can actually tell that to people I meet!</p><p>The book helped me to get started with preparing. Next step was the actual planning.</p><h3>The Agenda</h3><p>However important all the off-schedule events are, conferences are there because of the contents. NDC Oslo consists of two days of workshops and three days of talks. My trip will be limited to the the last three days, so I went through all the talks and bookmarked the most interesting ones. I might or might not go with the ones I’ve chosen here, but the main idea was to get an overview of the contents, and to dig a bit deeper into the most interesting ones.</p><p>NDC has a lot of contents, so the first thing I did was to decide a theme I would concentrate on. Last year <a href="https://medium.com/@mikko.vuorinen/scotsoft-2017-ba0069007704">I attended ScotSoft 2017</a>, and that time I focused on AI and deep learning when choosing the talks. For me it worked better than trying to get a bit of everything, so I went with a similar approach for NDC. After the first quick run through the whole agenda, I decided to mostly pick talks about <strong>security</strong>, <strong>architecture</strong>, <strong>front-end</strong> and <strong>microservices </strong>(and a bit serverless), with a conscious decision to leave other interesting topics like machine learning, accessibility, containers and functional programming for another time.</p><p>So, with a goal of filtering down the list of talks into something more manageable, here’s what I ended up with and why (in the order of appearance in the NDC agenda page).</p><h4><strong>Wednesday</strong></h4><p><strong>9.00–10.00</strong></p><p><a href="https://ndcoslo.com/talk/keynote/"><em>Keynote: A Penny for Every Object</em></a> by <a href="https://twitter.com/MadsTorgersen">Mads Torgsen</a><br>Well, this one is quite obvious: it’s Mads Torgsen, and it’s the keynote.</p><p><strong>10.20–11.20</strong></p><p><a href="https://ndcoslo.com/talk/we-didnt-stop-to-ask-if-we-should-understanding-build-vs-buy/"><em>We Didn’t Stop to Ask If We Should: Understanding Build vs. Buy</em></a> by <a href="https://twitter.com/toddhgardner">Todd Gardner</a><br>For a bespoke software company like Codify, it is invaluable to understand how the decisions to build or not to build are (or should be) made.</p><p><a href="https://ndcoslo.com/talk/the-web-that-never-was/"><em>The Web That Never Was</em></a> by <a href="https://twitter.com/dylanbeattie">Dylan Beattie</a><br>The history of “double-you-double-you-double-you” is quite interesting as it is, so there’s a lot of potential for an alternate history being quite intriguing. Definitely sounds more like a relaxed talk, in case I want something like that at the time.</p><p><a href="https://ndcoslo.com/talk/c/"><em>C# 8</em></a> by <a href="https://twitter.com/jonskeet">Jon Skeet</a><br>A bit out of my scope, but I would like to see Jon Skeet on stage, and knowing more about C# is always good. There’s a lot in C# 8 that I’m really looking forward to.</p><p><a href="https://ndcoslo.com/talk/microservices/"><em>Insecure Transit — Microservice Security</em></a> by <a href="https://twitter.com/samnewman">Sam Newman</a><br>This one fits right into my focus area. And Sam Newman is probably one of The People to listen to when it comes to microservices.</p><p><a href="https://ndcoslo.com/talk/im-pwned-youre-pwned-were-all-pwned/"><em>I’m Pwned. You’re Pwned. We’re All Pwned.</em></a> by <a href="https://twitter.com/troyhunt">Troy Hunt</a><br>From what I’ve heard, Troy Hunt can be quite entertaining speaker. And it’s about security! And it’s Troy Hunt!</p><p>So that’s 5 options for the first time slot where I actually had to choose. Not a good start…</p><p><strong>11.40–12.40</strong></p><p><a href="https://ndcoslo.com/talk/lightweight-microservice-collaboration-using-http/"><em>Lightweight microservice collaboration using HTTP</em></a> by <a href="https://twitter.com/chr_horsdal">Christian Horsdal</a><br>I’m currently working with mostly .NET technologies, so having a microservices talk with ASP.NET Core examples sounds tempting.</p><p><a href="https://ndcoslo.com/talk/authorization-for-modern-applications/"><em>Authorization for modern Applications</em></a> by <a href="https://twitter.com/leastprivilege">Dominick Baier</a><br>Anything that can make authorization easier is always good. IdentityServer is something I have explored a bit, so it’s interesting to see a talk from one of it’s creators.</p><p><a href="https://ndcoslo.com/talk/frontend-development-2018-whats-in-your-stack/"><em>Frontend Development 2018 — What’s in your stack?</em></a> by <a href="https://twitter.com/stefanjudis">Stefan Judis</a><br>This is one of not too many front-end talks. It goes without saying that keeping up with the progress of front-end stack is difficult, let alone knowing how to pick the right tools. Hearing how others have approach this problem is definitely worth the time.</p><p><a href="https://ndcoslo.com/talk/implementing-the-clean-architecture-in-net-core/"><em>Implementing the Clean Architecture in .NET Core</em></a> by <a href="https://twitter.com/ICooper">Ian Cooper</a><br>It’s good to always have architecture in the back of your mind while coding to make sure what you write makes sense in the big picture, even if the task at hand is not directly architecture-oriented. The more experience with architecture you have, the easier it is to put in practice. With hands-on .NET Core specific examples, this will definitely be useful.</p><p>And once again I’ve got 4 options, so unless Friday’s talk <a href="https://ndcoslo.com/talk/hello-multiverse-quantum-computing-and-you/"><em>“Hello, Multiverse!” — Quantum Computing and You</em></a> really delivers over expectations, I won’t be able to go to all four.</p><p><strong>13.40–14.40</strong></p><p><a href="https://ndcoslo.com/talk/the-power-of-roslyn/"><em>The Power of Roslyn</em></a> by <a href="https://twitter.com/kuhlenhuth">Kasey Uhlenhuth</a><br>This one is here mostly because Roslyn ans live analyzers are awesome!</p><p><a href="https://ndcoslo.com/talk/preprocessors-frameworks-and-css-in-js-or-how-i-learned-to-stop-worrying-and-love-the-website/"><em>Preprocessors, Frameworks, and CSS in JS or: How I Learned to Stop Worrying and Love the Website</em></a> by <a href="https://twitter.com/jackiebackwards">Jackie Balzer</a><br>The synopsis promises everything I want from a front-end talk: experiences over multiple years, tool and technology migrations, real-world problems and non-ideal solutions.</p><p>For the first after-lunch session I actually managed to pick just two. I will most likely go with the second choice that is more web-focused.</p><p><strong>15.00–16.00</strong></p><p><a href="https://ndcoslo.com/talk/give-it-a-rest-tips-for-designing-and-consuming-public-apis/"><em>Give it a REST — Tips for designing and consuming public API’s</em></a> by <a href="https://twitter.com/westleyl">Liam Westley</a><br>REST has been a topic of discussion at my workplace, so this is definitely one I want to see. Like the one above, also this one promises that “we’ll examine everyday issues”. Bring it on!</p><p><strong>16.20–17.20</strong></p><p><a href="https://ndcoslo.com/talk/user-experience-for-professionals/"><em>User Experience for Professionals</em></a> by <a href="https://twitter.com/paalholter">Paal Holter</a><br>There several talks on usability and accessibility, but I’ve mostly chosen to leave that topic for another time. But a promise of being able to advocate for UX in B2B environments is quite tempting.</p><p><a href="https://ndcoslo.com/talk/protecting-encryption-keys-with-azure-key-vault/"><em>Protecting Encryption Keys with Azure Key Vault</em></a> by <a href="https://twitter.com/stephenhaunts">Stephen Haunts</a><br>Keeping passwords and other sensitive configuration details safe is a key part (no pun intended) of secure deployment, especially in multi-tenant environments. So I wouldn’t mind having an experienced speaker and author explaining it in detail.</p><p><a href="https://ndcoslo.com/talk/a-practical-guide-to-graph-databases/"><em>A Practical Guide to Graph Databases</em></a> by <a href="https://twitter.com/bechbd">Dave Bechberger</a><br>Graph databases have been a bit of a daydream of mine for some time now. The main problem has been the practical side of moving from relational to graph database and understanding the trade-offs, and this is exactly what this talk promises to deliver.</p><p>The second last session of the day was again one with many very interesting options, so I will have to give it another thought later.</p><p><strong>17.40–18.40</strong></p><p><a href="https://ndcoslo.com/talk/an-opinionated-approach-to-asp-net-core/"><em>An Opinionated Approach to ASP.NET Core</em></a> by <a href="https://twitter.com/OdeToCode">Scott Allen</a><br>In addition to Scott Allen being Scott Allen (for those who don’t know, he’s really good at making you learn things), there is a lot to like in this talk. Project organizing is difficult, and it is always good to learn new/different/better ways of doing it. And with ASP.NET Core as the platform, it will be quite straightforward to take the learning back to everyday work.</p><p><a href="https://ndcoslo.com/talk/technical-debt-isnt-technical/"><em>Technical debt isn’t technical</em></a> by <a href="https://twitter.com/einarwh">Einar W. Høst</a><br>There is something in this talk that caught my interest. It is probably best described at the end of the synopsis: “…we must instead improve the way we collaborate and build our understanding of the problem we are trying to solve.” A bit vague, maybe, but it could be a start of a wonderful talk.</p><h4>Thursday</h4><p><strong>9.00–10.00</strong></p><p><a href="https://ndcoslo.com/talk/rise-of-the-tech-influencer-small-steps-you-can-take-to-increase-your-reach/"><em>Rise of the Tech Influencer — Small steps you can take to increase your reach</em></a> by <a href="https://twitter.com/msandfor">Michelle Sandford</a><br>This is the first of several career-oriented talks that I have chosen to include in my list. Ever since I left the university and realized how in business world, software engineering is rarely done the way that is the most efficient, gives the best results, or the happiest customers, I have desired to be able to make a difference. I’m hoping to catch at least a couple talks like this to boost my skills and enthusiasm in that area, and the talk by Michelle Sandford sounds like a perfect start.</p><p><a href="https://ndcoslo.com/talk/from-sql-to-azure-cosmos-db/"><em>From SQL to Azure Cosmos DB</em></a> by <a href="https://twitter.com/jbogard">Jimmy Bogard</a><br>Azure Cosmos DB has some very attractive features, but before jumping in, I must have better understanding of the trade-offs and how they affect the application structure and development. One of the key concerns is the different transactional model, which I hope this talk will shed some light on.</p><p><a href="https://ndcoslo.com/talk/serverless-architectural-patterns/"><em>Serverless architectural patterns</em></a> by <a href="https://twitter.com/theburningmonk">Yan Cui</a><br>One in to the architectural heavyweight series, with the contents that covers a lot of the the basic building blocks for serverless architecture. In contrast to other more practical talks, this is to deepen the understanding of serverless.</p><p><a href="https://ndcoslo.com/talk/typescript-decorators-higher-order-functions-in-disguise/"><em>TypeScript Decorators — Higher Order Functions in Disguise</em></a> by <a href="https://twitter.com/returnthis">Damjan Vujnovic</a><br>With <a href="https://aurelia.io/">Aurelia</a>, I use decorators constantly, but with only few exceptions I have almost never written decorators myself. Knowing how powerful they are, there is definitely a lot to gain from a better understanding of authoring decorators.</p><p>That’s quite a heavy start for the second day. I will most likely have a better idea of what I want after the first day, but for now I just couldn’t choose between the four talks.</p><p><strong>10.20–11.20</strong></p><p><a href="https://ndcoslo.com/talk/2018-the-year-of-web-components/"><em>2018 — The Year of Web Components</em></a> by <a href="https://twitter.com/DKundel">Dominik Kundel</a><br>I’ve heard this one before. Maybe this time it’s actually happening? Maybe. I would certainly like it. In any case, I want to be ready before the rest of the world is.</p><p><a href="https://ndcoslo.com/talk/implementing-authentication-and-authorization-with-asp-net-core-2/"><em>Implementing Authentication and Authorization with ASP.NET Core 2</em></a> by <a href="https://twitter.com/ZeroKoll">Chris Klug</a><br>The description hits the spot when describing the difficulties in configuring different authentication scenarios. Just a small difference can mean that the way you configured it last time doesn’t work this time at all, and you need a completely different approach.</p><p>These two talks are completely different from each other, so it will be up to the feeling at the day to decide which one I will go for.</p><p><strong>11.40–12.40</strong></p><p><a href="https://ndcoslo.com/talk/domain-driven-design-hidden-lessons-from-the-big-blue-book/"><em>Domain-Driven Design: Hidden Lessons from the Big Blue Book</em></a> by <a href="https://twitter.com/ntcoding">Nick Tune</a><br>While maybe a bit out of scope, this talk is in the core of software development skills that I think are the most important when building applications that are meant to last. There’s a lot I have to learn about DDD, so this talk is the perfect opportunity.</p><p><a href="https://ndcoslo.com/talk/architecting-your-next-spa/"><em>Architecting your next SPA</em></a> by <a href="https://twitter.com/GuyNesher">Guy Nesher</a><br>The topic of this talk is extremely interesting, but the description doesn’t reveal much. Learning how others see the advantages and disadvantages of different front-end libraries is definitely useful, and I’m wondering if Aurelia gets any mentions.</p><p><a href="https://ndcoslo.com/talk/hacking-your-work-life-balance-to-take-over-the-world/"><em>Hacking your work life __ balance to take over the world.</em></a> by <a href="https://twitter.com/likeOMGitsFEDAY">Jennifer Wadella</a><br>Time management is something I struggle all the time. With the holy trinity of my wife, my sport, and my code, I feel like whenever I spend extra time on one, I’m limiting what I can achieve with the others. And admit it, Jennifer Wadella is awesome!</p><p><strong>13.40–14.40</strong></p><p><a href="https://ndcoslo.com/talk/choose-your-own-adventure-the-tech-career-version/"><em>Choose your own adventure: the tech career version</em></a> by <a href="https://twitter.com/nabeelahali">Nabeelah Ali</a><br>Another one of the career talks, with a lot of topics that I’d be really interested in learning about. The idea of measuring success in my own terms sounds like it would help achieving my long-term goals.</p><p><a href="https://ndcoslo.com/talk/modern-security-with-microservices-and-the-cloud/"><em>Modern Security with Microservices and the Cloud</em></a> by <a href="https://twitter.com/SandeepDinesh">Sandeep Dinesh</a><br><a href="https://www.vaultproject.io/">The Vault project</a> is probably more or less an open-source option for the likes of Azure Key Vault, so this talk probably has similarities with <a href="https://ndcoslo.com/talk/protecting-encryption-keys-with-azure-key-vault/">Protecting Encryption Keys with Azure Key Vault</a> on Wednesday, but this one might have more general approach to the problem.</p><p><a href="https://ndcoslo.com/talk/vuejs-yet-another-js-framework/"><em>VueJS yet another JS framework?</em></a> by <a href="https://twitter.com/larsmarslars">Lars-Martin Hejll</a><br>Within the last year, <a href="https://vuejs.org/">VueJS</a> has gained enormous popularity, so without doubt knowing more about it is useful.</p><p><strong>15.00–16.00</strong></p><p><a href="https://ndcoslo.com/talk/how-to-network-if-youre-scared-of-people/"><em>How to network if you’re scared of people</em></a> by <a href="https://twitter.com/korachuta">Kasia Rachuta</a><br>Scared of (new) people? Check. Need to network? Check. This might be the perfect follow-up to the book I read to prepare for NDC.</p><p><a href="https://ndcoslo.com/talk/adapting-asp-net-core-mvc-to-your-needs/"><em>Adapting ASP.NET Core MVC to your needs</em></a> by <a href="https://twitter.com/filip_woj">Filip W</a><br>Knowing ASP.Net Core as well as possible, and getting an idea how much Core is used compared to the traditional .NET Framework, is one my goals for NDC. This talk is hopefully an opportunity to do both.</p><p><a href="https://ndcoslo.com/talk/security-in-cloud-native/"><em>Security in Cloud-Native</em></a> by <a href="https://twitter.com/robinem">Robin Minto</a><br>Back to security, this talk is a more high-level view on securing serverless (and otherwise cloud-native) applications. Considering that security and serverless were both in my list of key topics, this should be quite high in my list.</p><p><strong>16.20–17.20</strong></p><p><a href="https://ndcoslo.com/talk/finding-your-service-boundaries-a-practical-guide/"><em>Finding your service boundaries — a practical guide</em></a> by <a href="https://twitter.com/adamralph">Adam Ralph</a><br>Quite often “the big rewrite” is the developers’ biggest dream, and then it becomes their worst nightmare. I’ve heard of slicing functionality out of a monolith into microservices, but where to take the slice and how does that work in practice? Sounds like Adam Ralph might have some answers.</p><p><a href="https://ndcoslo.com/talk/building-event-driven-microservices-with-event-sourcing-and-cqrs/"><em>Building Event-Driven Microservices with Event Sourcing and CQRS</em></a> by <a href="https://twitter.com/lidanh">Lidan Hifi</a><br>It’s quite difficult for me to sound convincing when talking about events, queues, and eventual consistency as a replacement for traditional relational, centralized database. Leaning more about the architecture style and its patterns would definitely improve my confidence. A real-world example that is used in an invoicing system sounds very interesting.</p><p><strong>17.40–18.40</strong></p><p><a href="https://ndcoslo.com/talk/web-application-security-trends/"><em>Web Application Security Trends</em></a> by <a href="https://twitter.com/chwenz">Christian Wenz</a><br>The more you know about security the better. If this talk includes even one way of attacking web applications that I wasn’t aware before, it will most likely be worth it.</p><p><a href="https://ndcoslo.com/talk/betting-on-evolutionary-architecture/"><em>Betting on Evolutionary Architecture</em></a> by <a href="https://twitter.com/boicy">James Lewis</a><br>It is quite easy to see the benefits (or in lot of cases, the need for) evolutionary architecture, but it is not an easy feat in practice. There would be a lot to gain from knowing more about the techniques and tools.</p><h4>Friday</h4><p><strong>09.00–10.00</strong></p><p><a href="https://ndcoslo.com/talk/security-holes-in-git/"><em>Security Holes in Git</em></a> by <a href="https://twitter.com/ethomson">Edward Thomson</a><br>Knowing that any tool used for development can be a threat for security is important, and knowing what those threat us is the first step in preventing vulnerabilities and avoiding security holes.</p><p><a href="https://ndcoslo.com/talk/attacking-modern-web-technologies/"><em>Attacking Modern Web Technologies</em></a> by <a href="https://twitter.com/fransrosen">Frans Rosén</a><br>This is one more talk to gain knowledge about security threats. Only AWS and Google Cloud are mentioned, but no doubt this will cover areas that apply to the tools and infrastructure I use.</p><p><strong>10.20–11.20</strong></p><p><a href="https://ndcoslo.com/talk/the-hello-world-show-live-with-spencer-and-heather/"><em>The Hello World Show Live with Spencer and Heather</em></a><em><br></em>As an interview-style talk, this sounds quite interesting and will probably be a welcome change to other talks. I’m looking forward to see the list of interviewees when they are announced.</p><p><strong>11.40–12.40</strong></p><p><a href="https://ndcoslo.com/talk/the-history-of-net/"><em>The History of .NET</em></a> by <a href="https://twitter.com/richcampbell">Richard Campbell</a><br>As a listener of <a href="https://www.dotnetrocks.com/">.NET Rocks</a>, I’m quite certain Richard Cambell will make this a good show. I have been on .NET train for relatively short time — I did some C# 8 years ago but for full time only 3 years —</p><p><a href="https://ndcoslo.com/talk/super-large-ultra-fast-mega-scaling-cloud-computing/"><em>Super large, ultra fast, mega scaling cloud computing.</em></a> by Espen Brandt-Kjelsen<br>With “billions of data points”, this sounds like proper big data talk. The most interesting aspect is bringing out the downsides of the cloud, which is maybe not discussed quite as often as it should be.</p><p>Unfortunately that will be the end of my NDC visit this year, as I will need to head to the airport for my flight after lunch time.</p><h3>Conclusion</h3><p>Going through the NDC agenda proved to be a very time-consuming task. Putting the decision why I had picked the talks I did was even more work. I learned more about the talks and the speakers, and ended up changing some of the picks because of that extra though that I need to put into them when writing it all up.</p><p>I hope this post has been helpful to you. I know it has been for myself, and I’m quite interested to see which talks I end up going to.</p><p>Let me know if you are coming to NDC, I would love to get to know developers from around the world!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e10db968fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Aurelia skeleton with webpack and ASP.NET Core]]></title>
            <link>https://medium.com/@mikko.vuorinen/aurelia-skeleton-with-webpack-and-asp-net-core-af9dc5f5b233?source=rss-68c6702f1b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/af9dc5f5b233</guid>
            <category><![CDATA[configuration]]></category>
            <category><![CDATA[aspnetcore]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[aurelia]]></category>
            <dc:creator><![CDATA[Mikko Vuorinen]]></dc:creator>
            <pubDate>Sun, 04 Mar 2018 03:23:09 GMT</pubDate>
            <atom:updated>2018-03-04T03:23:09.194Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*iL3Iy9HXCxfGe8i_FicMKQ.png" /></figure><h4>Configuration for creating new Aurelia applications</h4><p>Configuring Aurelia is not difficult, but to get everything set up — so that the development, debugging and deployment of your application is quick and easy — is not a quick or an easy task. Last few days I have spent some time to build up configuration that works the best for me.</p><p>The configuration I ended up with is available on GitHub at <a href="https://github.com/vuorinem/aspnet-aurelia-webpack-skeleton">vuorinem/aspnet-aurelia-webpack-skeleton</a>. This post explains how and why I ended up with that specific set up.</p><h3>ASP.NET Core</h3><p>The core of the skeleton is based on an empty <a href="https://github.com/aspnet/templating/tree/release/2.1/src/Microsoft.DotNet.Web.ProjectTemplates/content/EmptyWeb-CSharp">ASP.NET Core template</a>. It provides a simple file server, with MVC added to it in order to create an index page using SPA fallback routing and tag helpers.</p><pre>app.UseMvc(routes =&gt; {<br>   routes.MapRoute(<br>      name: &quot;default&quot;,<br>      template: &quot;{controller=SpaIndex}/{action=Index}&quot;);<br><br>   routes.MapSpaFallbackRoute(<br>      name: &quot;spa-fallback&quot;,<br>      defaults: new { controller = &quot;SpaIndex&quot;, action = &quot;Index&quot; });<br>});</pre><p>The <em>asp-append-version</em> tag helper acts as an alternative to adding a content hash to the filename and updating references within the html page:</p><pre>&lt;script src=&quot;./dist/main.js&quot; asp-append-version=&quot;true&quot;&gt;&lt;/script&gt;</pre><h3>Aurelia</h3><p><a href="http://aurelia.io/">Aurelia</a> is currently my favourite front-end framework. The main reason is the simplicity and cleanliness of all framework-related code in the application. The framework API is remarkably unobtrusive, giving the developer freedom to build the application the best way they see fit.</p><p>In the skeleton, Aurelia is configured in the <a href="https://github.com/vuorinem/aspnet-aurelia-webpack-skeleton/blob/v1.0.0-beta.1/src/main.ts">main.ts</a> file that is the entry point of the application. For most uses, standard configuration is a good start:</p><pre>aurelia.use.standardConfiguration();</pre><p>The one line sets up the default binding language, template resources, event aggregator, browser history implementation and router. These could be set up individually if some of them are not needed and could be removed (to reduce bundle size).</p><p>Development logging is only enabled when debuggin (see later for setting up the <em>__DEBUG__</em> flag):</p><pre>if (__DEBUG__) {<br>   aurelia.use.developmentLogging();<br>}</pre><h3>Webpack</h3><p>Configuring <a href="https://webpack.js.org/">webpack </a>is definitely the most complicated part of the set up. Fortunately with the <a href="https://medium.com/webpack/webpack-4-released-today-6cdb994702d4">release of webpack 4</a>, it is becoming much less of a pain. With the skeleton I decided to start from an empty configuration file, got a single JavaScript file “bundled” and running on the browser, and worked my way up step by step, adding more files, TypeScript transpiling, CSS loading with autoprefixer, and SASS compiling. Then I configured <a href="https://webpack.js.org/configuration/dev-server/">webpack-dev-server</a> with HMR (Hot Module Reloading), split the configuration for different use cases, and finally added some configuration and optimisation for production builds.</p><p>There are four options for running webpack, all of which can be started up using the scripts defined in <a href="https://github.com/vuorinem/aspnet-aurelia-webpack-skeleton/blob/v1.0.0-beta.1/package.json">package.json</a>:</p><pre>&quot;scripts&quot;: {<br>   &quot;start&quot;: &quot;webpack-dev-server --config webpack.development-hmr.js --open&quot;,<br>   &quot;watch&quot;: &quot;webpack --config webpack.development.js --watch&quot;,<br>   &quot;build&quot;: &quot;webpack --config webpack.development.js&quot;,<br>   &quot;publish&quot;: &quot;webpack --config webpack.production.js&quot;<br>},</pre><p>When using Visual Studio, the <em>build </em>script will automatically run after building the project, and <em>publish </em>script when publishing. This is defined in <a href="https://github.com/vuorinem/aspnet-aurelia-webpack-skeleton/blob/v1.0.0-beta.1/Client.csproj">.csproj file</a> (that is much cleaner in Core compared to the traditional .NET Framework), for example:</p><pre>&lt;Target Name=&quot;WebpackPublish&quot; AfterTargets=&quot;BeforePublish&quot;&gt;<br>   &lt;Exec Command=&quot;yarn run publish&quot;&gt;&lt;/Exec&gt;<br>&lt;/Target&gt;</pre><p>Scripts <em>watch </em>and <em>start</em> need to be started up manually.</p><p><strong>Watch </strong>can be used to automatically build new version of the application when saving changes to a file, which works when running the application using IIS Express from Visual Studio or the .NET runtime.</p><p><strong>Start</strong> on the other hand will start up a separate web server and open the application with the browser, automatically loading changes to the browser when saving any of the source files. Because the .NET application is not running, an <a href="https://github.com/vuorinem/aspnet-aurelia-webpack-skeleton/blob/v1.0.0-beta.1/webpack-devserver-root/index.html">alternative index page</a> is needed for this type of development. This is included in <em>webpack-devserver-root</em> folder.</p><p>One of the key goals of developing the skeleton was to provide a configuration that works in different scenarios and for different users. In the simplest case, developer opens up the solution in Visual Studio and expects it to work by clicking Start. For more complicated uses, say developing a new feature or fixing a complex bug, using a separate dev server and HMR allows much faster inner loop of development (code-run-debug), saving developer’s time and focus.</p><p>The resulting webpack configuration is fairly simple and straightforward. One tweak I added was the <em>__DEBUG__ </em>flag that is set to <em>true </em>for development builds and <em>false </em>for production builds:</p><pre>new webpack.DefinePlugin({<br>   __DEBUG__: JSON.stringify(&quot;true&quot;),<br>}),</pre><p>The value of the flag can be used in any source file, but TypeScript requires it to be declared before using it, so this line is added to the <a href="https://github.com/vuorinem/aspnet-aurelia-webpack-skeleton/blob/v1.0.0-beta.1/src/main.ts#L5">main.ts</a>:</p><pre>declare const __DEBUG__: boolean;</pre><h3>Output</h3><p>As described above, there are different ways of using the skeleton, and these result in different output. For development, everything is bundled up in <em>dist/main.js</em> in the <em>wwwroot </em>(for ASP.NET Core server) or <em>webpack-devserver-root</em>. Production build will extract CSS into a separate <em>app.css</em> file that is referenced in the <a href="https://github.com/vuorinem/aspnet-aurelia-webpack-skeleton/blob/v1.0.0-beta.1/Views/SpaIndex/Index.cshtml#L7-L9">index page</a> when running in production.</p><p>Note that the ExtractTextPlugin for webpack 4 is currently a pre-release, so using it requires adding “<em>@next”</em> as a version range when installing the package.</p><p>Webpack output for production can be optimised for size by switching the <em>mode</em>-configuration from <em>development</em> to <em>production</em>. In addition, our configuration sets the <em>NODE_ENV </em>environment variable to <em>production</em>, which some libraries use for optimising their output. With the very simple sample application, the size of main.js drops from 2 295 KB (majority of which is sourcemaps) to 293 KB + 150 KB in app.css.</p><h3>Further development</h3><p>The configuration set up for the skeleton is by no means exhaustive. There are several improvements that would be useful for most of the applications, and these will most likely be included in the skeleton in near future.</p><h4>Polyfills</h4><p>Aurelia itself uses Promises, which are not supported by Internet Explorer. In addition to switching the TypeScript target to ES5, supporting IE would require adding a Promise polyfill (like <a href="http://bluebirdjs.com/">Bluebird</a>) to the bundle and defining the global <em>Promise</em> variable to use the polyfill.</p><h4>Code splitting</h4><p>As the size of the application grows, and the number of dependencies increases, using just one bundle for all the code can easily become the bottleneck of the application start up performance. Webpack’s tools for code splitting can be extremely useful in keeping the load times under control.</p><p>Thank you for reading! Please check out the <a href="https://github.com/vuorinem/aspnet-aurelia-webpack-skeleton">source code from Github</a>, and feel free to give any feedback or comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af9dc5f5b233" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ScotSoft 2017]]></title>
            <link>https://medium.com/@mikko.vuorinen/scotsoft-2017-ba0069007704?source=rss-68c6702f1b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba0069007704</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[hci]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[robotics]]></category>
            <category><![CDATA[dotnet]]></category>
            <dc:creator><![CDATA[Mikko Vuorinen]]></dc:creator>
            <pubDate>Thu, 19 Oct 2017 14:06:40 GMT</pubDate>
            <atom:updated>2017-10-19T14:06:40.791Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>DotNet inspiration and deep dive to deep learning</h4><p>I had a pleasure to attend ScotSoft, an annual software developer conference in Scotland, on 5th October in Edinburgh. There was a range of topics discussed during the conference, in three or four simultaneous sessions. My choices ended up concentrating on AI. Here’s a collection of my thoughts and notes on the talks that I attended on the day.</p><h3>The Cloud and The Browser</h3><p>The conference started off with an excellent talk from the open-source Microsoft sell-out, .Net guy loved by the community, <a href="https://www.hanselman.com/"><strong>Scott Hanselman</strong></a>. I had mostly only seen him in the ASP.Net community stand-up videos, chatting with his workmates from a home office in the middle of LEGOs and gadgets. His keynote talk definitely had more professional and rehearsed feel in it, but it was delivered with same down-to-earth tone with just enough awkwardness to make it relatable.</p><p>The idea behind the talk was to think of the cloud as a supercomputer, and the browser as a virtual machine that runs JavaScript. Or nowadays any language that compiles to a web assembly. The talk convinced me that I’ve ignored web assembly long enough and it’s time to give it serious consideration. Sure enough, as soon as the talk had finished, I was browsing GitHub for the source code for web assembly polyfills to better understand the technology and its feasibility in current day browsers.</p><h3>Jennifer Jensen on Twitter</h3><p>Javascript is an OS #ScotSoft2017</p><p>Another important takeaway from the talk was to appreciate the different layers of understanding when working with technology that hides complexity. The cloud gives us tools to magically create and scale infrastructure or deploy and run applications without knowing how it all is implemented. While it’s definitely not possible to understand every single detail — how an application is being run, how a VM is created within a physical computer, or how the data is being moved around in network, memory and disks — we do need to know and appreciate the fact that all this is happening under the hood when we use the abstractions.</p><p>As a good speaker, Hanselman kept the audience intrigued and entertained. The inception moment of the talk was when he demoed Netscape Navigator running on Windows Workspaces inside a VM inside a HTML page inside 3D scene (the page showing up as a screen of a computer) in a browser. Lesson learned: whatever it is, you can do it in the browser.</p><h3>Artificial Intelligence, Robots and User Interfaces</h3><p>The bulk part of my conference consisted of AI related talks, with the content ranging from specific data clustering algorithms to ethical dilemmas of AI decision-making. Each one of the four talks is explained below, from a keen observer’s perspective, my practical experience with AI being still rather limited.</p><h4>Explainable AI and Case-based Systems</h4><p>All the buzz around deep learning and neural networks leaves some aspects of AI with less attention than they might deserve. <a href="http://www.rgu.ac.uk/">RGU</a> professor <a href="http://www.rgu.ac.uk/dmstaff/craw-susan"><strong>Susan Craw</strong></a> explained how <a href="https://en.wikipedia.org/wiki/Case-based_reasoning">Case-based reasoning</a> (CBR) differs from Model-based reasoning, and why it might sometimes be a better fit. She points out that while both novices and experts in a field can learn new information just as well, experts know better <em>how </em>to apply their knowledge, and that kind of intelligence is difficult to embed in an AI. CBR concentrates on <em>what </em>has solved the problem in past to help make the decision in a new, previously unknown situation.</p><p>According to Craw, one of the major benefit of CBR is that its decisions are <strong>explainable</strong>. Unlike decisions made by a neural network, CBR can (and does, to improve it’s accuracy) explain why a certain decision was reached from the given input. Explainability did also come up in some of the later talks, so I can see why it makes CBR more attractive.</p><p>The <strong>robustness </strong>of CBR systems was another benefit brought up by Craw. Where Mode-based systems require re-learning to be able to handle completely new situations, CBR can better utilize existing knowledge when facing “unknown unknowns”. My understanding was that this is because MBR generalizes the data it uses for learning when it builds it into the model, but CBR uses the data itself as the model, and only does the generalization locally (when making the decision). While the similarity of the unknown situation still needs to be determined to make a decision, the solutions from the original data can be used to solve the new situation without re-modeling the solution space.</p><p>During the Q&amp;A session at the end of the talk, I heard Craw commenting that “AI strength is in decision support, not decision making”. In the world of driverless cars and rocket-landing AI, for me, that sounds a bit too… safe.</p><h4>From Lab to the Real World — Robustness and Reproducibility in Robotics</h4><p>The next speaker, <a href="http://www.macs.hw.ac.uk/~kl360/"><strong>Katrin Lohan</strong></a> from <a href="https://www.hw.ac.uk/">Heriot-Watt University</a>, brought up the challenges in getting robots from protected lab environment into the world of natural interaction interfaces. Real world applications would require more robustness and better reproducibility of robotics research, manufacturing and behaviour.</p><p>While going through the research in the <a href="http://www.macs.hw.ac.uk/RoboticsLab">Robotics Lab</a> and common challenges they face, Lohan mentioned <strong>open source</strong> code as a way of improving reproduciblity of studies and systems. She also told about <a href="http://www.ros.org/">ROS</a>, an “operating system” for robots that makes hardware control much easier. But not all robots run ROS, and controlling the hardware is often one of the most difficult and time-consuming part of developing robots.</p><p>Lohan showed a video that demonstrates how immediate response from the robot can improve communication. Children in the autistic spectrum have been part of the robotics lab studies on social communication. Robots could help the users by improving their learning, while at the same time learning from the special user group to bridge the gap between robot and human behaviour.</p><h3>Caroline McC on Twitter</h3><p>Interesting how robots help with research into autism in children @bluerabbit9281 @HeriotWattUni @EDINrobotics #scotsoft2017 @scotlandis</p><p>Lohan also showcased several projects from the <a href="https://sites.google.com/site/hwinteractionlab/">Interaction Lab</a>, which has a team in the <a href="https://developer.amazon.com/alexaprize">Alexa Challenge</a> finals.</p><h4>AI Ethics</h4><p>When we returned from the break for the next talk, there was a lego man waiting on each seat. Sadly, I forgot to take mine with me after the talk, but I did manage to immortalize the guy with my phone:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*c8HCL1dMOGV_Y6Pdi6Zdsg.png" /></figure><p>The speaker, <a href="https://twitter.com/RealBenGilburt"><strong>Ben Gilburt</strong></a> from <a href="https://www.soprasteria.co.uk/">Sopra Steria</a>, used only about half the reserved time for his presentation, encouraging attendees to fill in the other half with questions and open discussion. The topic was much more abstract, including the current limits and future of AI, and the ethical problems that emerge when we delegate decision making to something that cannot be held accountable the same way as a person can.</p><p>While AI has been a hot topic in recent years and it’s rapid development is evident, we are still far away from imitating any human-like intelligence. Current use of AI is still practically always some specialized scenario, and no machine can handle the range and rate of learning compared to even a 5-year-old child. Gilburt said that general artificial intelligence is said to be “20 years in future”, and it has been that for decades now, ever since the first uses of the word ‘AI’. It will probably continue to be “20 years in the future” for a good while. Not to mention the audience’s favourite topic, singularity.</p><p>Gilburt pointed out that we need common rules for how we develop and apply artificial intelligence. Algorithms and machine learning is bound to be affected by our own biases. Research has shown that issues such as discrimination and racism are very much present in automated decision making. The new <a href="http://www.eugdpr.org/">EU General Data Protection Regulation</a> (<strong>GDPR</strong>)— enforced from 25 May 2018 — is in part laying some ground rules to avoid the most drastic ethical consequences of the rapidly increasing usage of AI. There’s an excellent, freely available paper on <a href="https://arxiv.org/abs/1606.08813">GDPR’s impact on machine learning</a>, including it’s problems and shortcomings. The regulation and AI ethics in general is an extremely complex and interesting topic, and Gilburt’s talk just scratched the surface.</p><p>Another topic of the talk was the change in our behaviour because of our familiarity with computer interfaces. As an example of this, Gilburt showed two pictures of student’s facial expressions during a lecture, one recent and one from several decades ago. Reading the emotions from faces was much easier in the latter picture. Gilburt explained that in most computer interfaces we use, even when using them to communicate between each other, facial expressions have no value for the speed or quality of communication. This has caused us to give less value for expressing our emotions in everyday interactions. One way to turn this over would be to create interfaces that react to facial expressions and emotions.</p><h4>Discreet Computing and AI modeling techniques</h4><p>The last talk of the AI track was by the <a href="https://www.st-andrews.ac.uk/">University of St Andrews</a> professor and chair of Human Computer Interaction, <a href="https://aquigley.host.cs.st-andrews.ac.uk/"><strong>Aaron Quigley</strong></a>. I was immediately thrown back to Uni when he started the talk by mentioning <a href="https://sigchi.org/">SIGCHI</a> and ACM. The feeling just got stronger by the ever growing speed of slides that explained different ways of building representational models for machine learning. And I must admit, I liked that feeling, and started to think if I should pursue my goal of getting a PhD.</p><p>The first part of the lecture was about modeling data for visual representations by reducing its dimensions, so that it can be interpreted by human without the need for machine learning. I just about recognized some terms like <em>principal component analysis</em>, but when it got to specific methods of clustering (<em>quadtree geometric clustering</em>, <em>k-means</em>), and ways of generating decision trees (<em>ensemble methods</em> / <em>random forest</em>), I was making notes like a fresher before exams.</p><p>In addition to the techniques, Quigley provided some views on AI that are worth stopping to think about. He made a case that not everything needs to use deep learning that makes explainability a very difficult problem. That is especially important now that GDPR is on its way. Also, with our mobility needs and ubiquitous computing, connectivity is not always a given, and cloud is not the answer for everything.</p><p>Like any self-respecting academic, Quigley had still about 50 slides left before the last minute of the talk, so there was no much time left for discussion. The only question was about explainability of AI decision making, which had been a recurring theme in every one of the talks. Quigley mentioned that although it is much more complex question with deep learning compared to techniques like decision trees, there is ongoing research into this in universities and enterprises because of its importance, and we ought to see some results in near future.</p><h3>DotNet Now</h3><p>Before the last AI talk by Quigley, I stepped outside the track to catch Scott Hanselman’s second talk on .Net Core. Even though I had been trying to keep up to date with .Net, and even watched several of the <a href="https://live.asp.net/">ASP.Net community standups</a>, it was still quite inspiring to see and hear all that live without staring at a screen (especially after Ben Gilburt telling how we’re ruined by computer interfaces and can no longer show emotions 😉).</p><p>Hanselman started with some hisrory of .Net, and mentioned how the framework was actually open-sourced first time 15 years ago. Although technically open source, the lack of community input and bad licensing prevented the framework from getting the benefits of a proper open source project. With .Net Core, the intention was to fix that, and get the community involved from the very beginning. This meant that not just the code, but all the decision making was made transparent and the community was given all the possible tools to take part.</p><p>Another major change in .Net Core compared to .Net Framework was to make it cross-platform. This doesn’t only allow using it in multiple platforms, but it also diversifies the technologies that it interacts with, preventing developers from getting a tunnel vision and seeing everything through Windows glasses. Being influenced by developers throughout the technology field, .Net Core also gets its share of innovations in Linux and Mac, Javascript and PHP, NoSQL and GraphQL and so on.</p><p>An important part in making .Net libraries portable between .Net implementations is .Net Standard. With a standard API that library authors can rely on being available in any implementation, libraries can easily be used in all platforms. This also makes porting old .Net applications to Core more feasible as the libraries they depend on can be made available for both traditional .Net and Core.</p><p>.Net Core also tries to address the problems with updating the framework by allowing multiple versions to be installed side by side. This means that the application can depend on any currently installed version. It can even include the whole framework within a self-contained package. This of course increases the package size considerably, but in the future something like tree-shaking could possibly be used to drop any unused dependencies to decrease the size.</p><p>During his talk, Hanselman also revealed some extremely well kept secrets of the command prompt. Do you know what pressing <em>F7</em> does in cmd? I didn’t!</p><p>Fast and simple developer experience is something that interpreted languages have by design as they don’t require a separate <em>build</em> step. Hanselman talked about developer’s inner loop, basically meaning the task switching between coding and testing the code. With <em>dotnet watch</em> tool, the project gets implicitly built every time a source file changes, making the developer experience much nicer (I’ve used it and I definitely agree). With the next version, .Net Core 2.1, build time should also be improved.</p><p>At the end of the talk Hanselman demonstrated building a .Net Core application and publishing it for Linux from a Windows laptop. By publishing a self-contained executable, the application was able to run in any Linux machine, and Hanselman chose to show how to run it in a <a href="https://www.raspberrypi.org/">Rasberry Pi</a>. That got me quite interested in buying my own Rasberry and get a feeling of extreme cross-platform in action.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba0069007704" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Aberdeen CodeTheCity #9]]></title>
            <link>https://medium.com/@mikko.vuorinen/aberdeen-codethecity-9-29d2c57c62db?source=rss-68c6702f1b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/29d2c57c62db</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[open-data]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Mikko Vuorinen]]></dc:creator>
            <pubDate>Thu, 21 Sep 2017 16:27:29 GMT</pubDate>
            <atom:updated>2017-09-21T16:27:29.996Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>First-timer experiences</h4><p><a href="http://codethecity.org/">CodeTheCity</a> is a volunteer-organized, “civic hacking initiative interested in hack weekends, open data, workshops, and idea generation tools”. On the weekend of September 16–17, they ran an event for planning and prototyping ideas around <a href="http://codethecity.org/hack-weekends/code-the-city-9-health-signposting/">Health Signpostin</a>g.</p><p>Until last weekend, I had managed to avoid all the hackathons and meet-ups, mostly because of how much I move around and how slow I am making new contacts. This was the perfect opportunity for me to start networking.</p><p>With my company <a href="http://codify.ltd.uk/">Codify</a> promoting this event to its employees and supporting anyone who decided to put in the time and effort to attend, I decided to go for it. In the end there were two of us going, so luckily I didn’t have to go alone.</p><h3>Event Flow</h3><p>I didn’t know what to expect from the weekend, so I headed to the venue with an open mind (while admiring the beautiful surroundings at the University of Aberdeen). After some coffee, introduction from the organizers, and the mandatory getting-to-know-each-other-game (which could have been worse), we were split into groups and started to build some common understanding around the subject. It took me a while to understand what “health signposting” actually meant and the type of users, problems and data we were dealing with, but by the noon I had a pretty good idea of what the aim of the weekend was.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*GxFOLdfx4Sw0Y1941ITAvg.png" /><figcaption>Couldn’t stop myself from stopping to take a few pictures while walking to the event venue.</figcaption></figure><h4>Understanding the problem</h4><p>The volunteers were initially split into two groups to talk about the problems the health service professionals, their clients and service developers were facing. One group consisted of the developers, and the other had participants from various areas in health services. For the developers, the starting point was a high-level architecture design of a “health service information database aggregator” formed during previous CodeTheCity events. We then moved on to talking about practical solutions how the implementation of the aggregate could be started.</p><h4>Forming developer teams</h4><p>A lot of the talk in the developers group was around the key problem in the current solution: how to keep the data up to date and consistent between the different databases, that contained similar and partly overlapping data. This proved to be most likely more complicated than a weekend of coding could solve, so we eventually came up with a more practical idea for a prototype. The idea was to aggregate data from three separate databases, and provide a user interface for searching information from them. The group of developers was split into the UI team and the API team. As part of the API team that was responsible of aggregating the data and providing it in simple form for the UI team, I started investigating one of the database API’s, <a href="https://www.aliss.org/">ALISS</a>. I also worked on designing the core functionality of the aggregator.</p><h4>Tools, tools, tools…</h4><p>Getting to try out new tools was one of the things I was looking forward to, so I was happy to choose <a href="https://nodejs.org/en/">Node.js</a> and <a href="https://expressjs.com/">Express</a> as our back-end technology. With the deployment I went with more familiar <a href="https://azure.microsoft.com/">Azure</a>, although <a href="https://docs.microsoft.com/en-us/azure/app-service/app-service-web-get-started-nodejs">running Node.js server</a> added an interesting twist to it. In the end I ended up spending most of the afternoon trying to find an easy way to deploy the API from our <a href="https://github.com/CodeTheCity/ALISS-API">Git repository</a>. The satisfaction was audible when the API successfully returned a json response for the first time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NnpXYqZFGe5pEWpxeQOhtg.png" /><figcaption>Activity Logs from Azure, when the Node.js application starts up successfully for the first time.</figcaption></figure><p>During the first day of the event, I mostly talked with one of the other developers who was also working on the API, getting data from a database that we called MILO (<a href="https://getinvolved.org.uk/">https://getinvolved.org.uk/</a>). He was a computer science student, who also happened to be from Finland, came from the same city, had been in the same school, and was also called Mikko. Talk about a coincidence! He was the one with most experience on Node.js, so he had a big part in designing the aggregator core.</p><h4>Working towards the prototype</h4><p>The next day was all about getting something completed and ready to be showcased to other teams. The API team finished the work by tidying up the data received from the databases. The third database connection was added through a temporary API and a database built up from a single spreadsheet in a USB stick by Sam, another Codifier in our team. Once the API was more or less completed, the API and UI teams merged back into a one big team, to give a finishing touch to the prototype. Just before the final show-and-tell I spend a moment teaching two of the UI team developers with no previous front-end experience how to use Javascript to display search results (retrieved from the API) in a HTML page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*jezwE3ZG_grvCTnrMW_txw.png" /><figcaption>Sam from Codify working on adding search endpoint to the temporary API</figcaption></figure><h4>Final presentations</h4><p>The final task of the event was to present the prototype and how it came about to other teams, and — to my horror and still continuing embarrassment — to a video camera.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*87F1jFGVDf4BYXObmIXFGQ.png" /></figure><h3>Reflection</h3><p>Looking back to the event after few days of recovery, I’m really happy that I decided to attend. I will definitely keep an eye on future CodeTheCity events and also other community events.</p><p><a href="https://twitter.com/codethecity">code the city (@codethecity) | Twitter</a></p><p>I’ll finish up with a list of the most memorable things that I learned and experienced during the weekend. I also added some feedback about the event to help make my and anyone else’s experience even better the next time.</p><h4>Key takeaways</h4><ul><li>Learning and trying out new technology (that I’ve been wanting to try)<br>- server-side JavaScript with Node.js and Express<br>- deploying Node.js application in Azure Web App<br>- local git deployment in Azure</li><li>Accidentally running into new technology<br>- a glimpse to <a href="https://www.elastic.co/products/elasticsearch">ElasticSearch</a><br>- a glimpse to server-side Python (figuring out how <a href="https://github.com/aliss/engine/tree/master/engine">ALISS engine</a> works)</li><li>A bit of teaching<br>- front-end development to first-timers</li><li>Working together with people in different positions, from different backgrounds and with different goals</li></ul><h3>Mikko Vuorinen on Twitter</h3><p>Got some experience with @nodejs @expressjs and stumbled into @elastic #elasticsearch, nice first day of #CodeTheCity #Aberdeen.</p><h4>Feedback about the event</h4><ul><li>Good communication in all sides: our team, other teams, organizers<br>- Talking to anyone was as easy as it could possibly be when meeting a bunch of new people for the first time</li><li>People helping each other<br>- Everybody was there to learn something, and everybody was there to teach something</li><li>Developer-only teams didn’t have the constant “user” feedback that is essential for early-phase prototyping. Forming teams around ideas instead of splitting into developers and non-developers could help directing both the ideas (more feasible) and the prototype (more valid for users).</li><li>A lot of ideas was developed throughout the week, but only one of them was built into a prototype. The benefit was that we got quite far with the one prototype, but on the other hand there were other ideas that could have been awesome as a prototype.</li><li>Working in our group was really fluent, but because the focus was on the back-end with not much visible results, it was quite difficult to demonstrate to others and to evaluate if we were going to the right direction (considering end-users).</li><li>Although the teams were divided into mostly developers and non-developers, people from each team were also helping other teams. This way the developers could validate the prototype every now and then by talking to people that better understood the end-users. On the other hand, this meant that people from the other groups needed to jump from their idea to give their input into our prototype. Keeping in groups (that could each have dedicated developers) could give a chance for each group to focus and dig deeper into specific idea from multiple perspectives.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29d2c57c62db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Aurelia and Azure AD B2C Authentication]]></title>
            <link>https://medium.com/@mikko.vuorinen/aurelia-and-azure-ad-b2c-authentication-351fbe2de348?source=rss-68c6702f1b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/351fbe2de348</guid>
            <category><![CDATA[oauth]]></category>
            <category><![CDATA[azure-active-directory]]></category>
            <category><![CDATA[aurelia]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Mikko Vuorinen]]></dc:creator>
            <pubDate>Mon, 24 Jul 2017 23:23:23 GMT</pubDate>
            <atom:updated>2017-07-28T20:50:24.000Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*Z16FpYzAtWwnXeVMp7I54A.png" /></figure><h4>Using hello.js with Azure Active Directory B2C Tenant to authenticate Api calls within Aurelia application</h4><p><em>Identity as a service</em> allows web applications to use fully featured, well maintained and secure service to handle user authentication. With Azure AD B2C, customer-facing applications can improve user experience by providing single sign-on (SSO) with social media platforms like Facebook, Google and Twitter, as well as email / username based sign-up.</p><p>In this article, I will go through setting up the AD tenant in Azure and using hello.js within Aurelia application to sign in users. Microsoft offers a comprehensive <a href="https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-overview">documentation for Azure AD B2C</a>, but there is quite a lot to go through, and I found the guides and samples missing some key details that took way too long for me to find out by trial-and-error. This article aims to provide an easy start for setting up the authorization provider (Azure AD B2C Tenant) and the client application (Aurelia SPA).</p><p>The source code for the application created in this article is open-source (MIT) and available in GitHub at <a href="https://github.com/vuorinem/aurelia-azureadb2c">https://github.com/vuorinem/aurelia-azureadb2c</a>.</p><h3>Setting up Azure AD B2C Tenant</h3><h4>Creating directory</h4><p>If you don’t have an existing AD B2C directory to use, you can get started by creating a new resource in Azure portal and searching for “b2c”. The directory will have a unique url such as myadb2ctenant.onmicrosoft.com.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cv3O5Y_Cx_3j1qlHPTJReg.png" /><figcaption>Creating new Azure AD B2C Tenant in Azure portal</figcaption></figure><p>When you are logged in in Azure with an account that has access to the directory, it will show up in the user menu on the right hand side of the portal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/243/1*WrHNYjrjQjFxHWlSbZ51sA.png" /><figcaption>Directories in Azure portal user menu</figcaption></figure><h4>Azure AD B2C Settings</h4><p>The page for configuring the AD B2C resource is different from the AD B2C Settings page (below). To access the settings page, you might need to switch the directory from the user menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Recyw5O6th5oTw4N5OSP0A.png" /><figcaption>Azure AD B2C Settings page in Azure portal</figcaption></figure><p>In the settings page, you can select the identity providers that can be used to log in to your application. Adding a provider in Azure is simple, but setting up the application on the provider side (such as <a href="https://developers.facebook.com/">Facebook for developers</a> or <a href="https://console.developers.google.com/">Google developer console</a>) usually requires few extra steps. Luckily Azure documentations has <a href="https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-overview#how-to-articles">step-by-step instructions how to set up the providers</a>, currently for Facebook, Google+, Microsoft Account, Amazon, and LinkedIn.</p><h4>User attributes</h4><p>The <em>user attributes</em> page (or “blade” as they are called in Azure documentation) shows all the attributes that can be collected from users on sign-up or sign-in. You can also add custom attributes if you need to collect data that is not available as a built-in attribute. Available attributes can be restricted by application and <a href="#3fba">policy</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vA5jLdTUhDJxkToasdzejg.png" /><figcaption>List of User attributes in AD B2C Tenant settings</figcaption></figure><h4>Registering application</h4><p>To use Azure AD as the identity provider for your application, the application needs to be registered in the portal. This will create an unique application ID that is needed when requesting user to sign in.</p><p>For web applications, a reply URL is required so that the user can be securely redirected to the application after the sign-in. I will set up the sample application to run locally, so the return URL will be on localhost, on port 9000. The application will need to be built to handle the sign-in response in <em>https://localhost:9000/login-redirect</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/851/1*3gIxln1G-lVfZQoSmPl3QA.png" /><figcaption>Registering AD B2C application in Azure portal</figcaption></figure><p>For more details, see the Azure documentation page <a href="https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-app-registration">Register your application</a>.</p><h4><strong>Scopes</strong></h4><p>For the authentication to work properly, you will need to define at least one scope for the application in <em>Published scopes</em> blade in the application configuration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uH1BWB-QItEGlvA3-CK6-g.png" /><figcaption>Scope configuration for application</figcaption></figure><p>You can select the name and value of the scope however you like. Note that when using the scope, it needs to be prefixed with the App ID URI in application properties. The final scope value will be something like:</p><pre>https://my-ad-tenant-name.onmicrosoft.com/my-app-name/scope-value</pre><p>If the scope defined in the login request is anything else, the login will fail.</p><p>When you have added the scopes, the application needs to be allowed access to those scopes. This is done from the<em> API access</em> blade, just above the Published scopes. Just add a new access specification for your application and select the scopes from the list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*93UTxoXfVUogFIEjx64bPw.png" /><figcaption>Adding API access to selected scopes for the application</figcaption></figure><h4>Policies</h4><p>Policies define different authentication scenarios that are supported by the AD tenant, such as creating a new account, signing in with an existing account, or editing profile details. These are described in the <a href="https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-reference-policies">Built-in policies documentation</a>.</p><p>A <em>sign-up or sign-in policy</em> can be used as a simple solution for both sign-up and sign-in purposes. The policy itself is easy to set up by selecting the identity providers that can be used, attributes that are required from the user (in case of a new user sign-up), and the claims that are available in the token to be read by the application.</p><p>Note that when referring to the policy with its full name, it should be prefixed by <em>B2C_1_</em>, so for example the full name of the policy below will be <em>B2C_1_signupsignin</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V8-7tkD9S6zzYSb4Xf_w0g.png" /><figcaption>Setting up a new <em>sign-up or sign-in</em> policy in Azure portal</figcaption></figure><p>The <em>Page UI customization</em> section can be used to change the sign-up/sign-in page layout and how the user attribute form fields are displayed. These are worth going through especially if you use custom sign-up attributes.</p><h3>Aurelia application and hello.js</h3><p>The client application is responsible for requesting the user to sign in and adding the access token to all the authenticated API requests. In our case, this will be a JavaScript application built on Aurelia. As a starting point, I will <a href="https://github.com/vuorinem/aurelia-azureadb2c/commit/5def0add8c3b0b4ed053b0ac9943f9af0cb9ee30">create a new application</a> using <a href="http://aurelia.io/hub.html#/doc/article/aurelia/framework/latest/the-aurelia-cli">Aurelia CLI</a>.</p><h4>Installing hello.js package</h4><p><a href="https://adodson.com/hello.js/">Hello.js</a> is a JavaScript OAuth client library that works with any standard authentication provider. It takes care of redirecting the browser (or opening a pop-up window) to prompt the user to log in, and stores the access token when the user is redirected to the application.</p><p>Microsoft also has it’s own library, <a href="https://github.com/AzureAD/microsoft-authentication-library-for-dotnet">MSAL</a> (Microsoft Authentication Library), but <a href="https://github.com/AzureAD/microsoft-authentication-library-for-js">MSAL port to JavaScript</a> is still in preview (although “suitable for use in a production environment” as mentioned on the repository readme), and <a href="https://stackoverflow.com/questions/44228493/how-to-properly-import-and-use-the-msal-microsoft-authentication-library-for-js">importing it as a module doesn’t quite work as expected</a>. I also had some trouble trying to keep the user logged in when refreshing the page, so I ended up choosing hello.js which seemed to be much easier to get working.</p><p>Microsoft also provides <a href="https://github.com/Azure-Samples/active-directory-b2c-javascript-hellojs-singlepageapp">a sample application</a> that demonstrates how to use hello.js for Azure AD B2C authentication. The application is a good starting point, but it doesn’t show all the necessary set up.</p><p>Npm can be used to install hello.js and it’s type definitions:</p><pre>npm i hellojs<br>npm i @types/hellojs</pre><p>Unfortunetely the type definitions are currently for an older version, and for example the sample application from Microsoft is not compatible with the older typings. This means that the code from the sample app will not transpile when using TypeScript. I have created a <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/pull/18318">pull request in DefinitelyTyped repository to update hello.js typings</a>. It will probably be a while until/if the pull request will be merged in, so meanwhile you can either use the old definitions, or get the <a href="https://github.com/vuorinem/aurelia-azureadb2c/blob/f5db6b0/custom_typings/hellojs/index.d.ts">updated hello.js definition</a> from my sample application.</p><h4>Azure AD B2C configuration</h4><p>First step in using hello.js is to configure your AD tenant to be used as an authentication provider. In <a href="https://adodson.com/hello.js/modules">hello.js modules documentation</a>, there is a list of currently supported provider modules and instructions for writing your own. To set up Azure AD B2C you can call the init()-method with following parameters:</p><pre>hello.init({<br>  azureAD: {<br>    oauth: {<br>      version: 2,<br>      auth: AD_URL + &#39;/authorize&#39;,<br>      grant: AD_URL + &#39;/token&#39;,<br>    },<br>    scope_delim: &#39; &#39;,<br>  }<br>});</pre><p>The property key <em>azureAD</em> is just an arbitrary name for the hello.js module. Subsequent calls to the AD provider should use that name.</p><p><em>AD_URL</em> is the base URL of the two OAuth2 endpoints. The URL is in the following format:</p><pre>https://login.microsoftonline.com/te/[AD]/[POLICY]/oauth2/v2.0</pre><p>where AD is the full name of the tenant (e.g. my-ad-tenant-name.onmicrosoft.com) and policy is the full name of the policy (e.g. B2C_1_signupsignin). You can check the URL’s from the OpenID “well-known configuration” page for your policy . The configuration is a .json formatted file, with properties <em>authorization_endpoint </em>and <em>token_endpoint</em>, that can be used in <em>auth </em>and <em>grant</em> configuration respectively. (See for example <a href="http://docs.akana.com/cm/api_oauth/aaref/Ref_OAuthWellKnownConfiguration.htm">Akana OpenID documentation</a>)</p><p>A link to the well-known configuration page is shown on the top of the policy details page in Azure. At the bottom of the page there is also a link and a button to open the login-page for the currently selected application and scopes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*7px8Maw9pjJe6tKDKFY80A.png" /><figcaption>Policy details in Azure portal</figcaption></figure><p>Note that the selected token issuer in Token compatibility settings (see below) changes the link. When the issuer is set to the one starting <em>https://login.microsoftonline.com/</em><strong><em>tfp</em></strong><em>…,</em> the configuration will show OAuth url’s with <strong><em>/te</em></strong> and the policy name in the path. For the issuer without <strong>/tfp</strong>, the policy name will be added as a query string. Either URL’s should work fine, but I’m using the ones with <strong>/te </strong>in the sample application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*r11VDwGYcHFD-Vp5Cb6Elw.png" /><figcaption>Policy token configuration in Azure portal</figcaption></figure><p>Once the Azure AD provider has been set up, we need to set the application ID that our application uses. This a simple call to <em>init()</em> with an object that has providers as keys and application ID’s as values:</p><pre>hello.init({<br>  azureAD: &#39;xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx&#39;,<br>});</pre><h4>Sign-in</h4><p>Finally, it’s time to add the code to actually sign in the user. Or to be exact, open a sign-in page and handle the response. With hello.js, most of this happens automatically in the background as long as the hello.js script is being loaded when loading the page.</p><p>Calling <em>login()</em> with the following parameters will redirect user to the AD login page, and redirect back to the application once done. If the user has already signed in, the redirect will happen immediately without user interaction. The <em>display </em>parameter with the value <em>‘page’</em> tells hello.js to use browser redirect instead of a pop-up window, to avoid problems if the user has blocked pop-ups.</p><pre>hello.login(&#39;azureAD&#39;, {<br>  redirect_uri: &#39;https://localhost:9000&#39;,<br>  scope: &#39;openid https://my-ad-tenant-name.onmicrosoft.com/my-app-name/scope-value&#39;,<br>  response_type: &#39;token&#39;,<br>  display: &#39;page&#39;,<br>});</pre><p>Default login parameters can also be set in a the <em>hello.init()</em> call <a href="https://github.com/vuorinem/aurelia-azureadb2c/blob/bb1b5e68680e3f1dd6ba89a192afd267829171c3/src/auth/auth-service.ts#L22-L27">when setting application ID</a>.</p><h4>Sign-out</h4><p>When using single sign-on, there are different types of sign-out functionality. To end user session — instead of just removing authentication details from the client — we need to tell hello.js to call the end session endpoint. The URL for that is in the OpenID well-known configuration page with the key <em>end_session_endpoint</em>, but in AD B2C it is just the same as <em>auth </em>and <em>grant </em>URL’s except with <em>/logout</em> at the end.</p><p>Unfortunately this is not quite enough, as you can see if you try to set this as the logout-option in the first <em>hello.init()</em> call. The first problem, and the easier one to fix, is that the logout endpoint also requires a <em>post_logout_redirect_uri </em>parameter in the logout request. The parameter can be simply added as a query string to the logout URL.</p><p>The more tricky issue is that hello.js tries to use iframe to make the request to the logout endpoint, and Azure AD B2C does not allow this in any of the OAuth endpoints. The solution is to make the call ourselves, by setting the logout-configuration to be a function. The function gets called whenever hello.logout() for that provider is called with the <em>force</em>-option. It is not really a well documented feature, the best documentation is in the <a href="https://github.com/MrSwitch/hello.js/blob/v1.15.1/src/modules/facebook.js#L54-L70">built-in Facebook module in hello.js repository</a>, but it get’s the job done. Another option would be just to forget hello.js on log-out and just redirect to the URL, and use <em>hello.util.store</em> to clear authentication data from the client.</p><p>You can check the sample application to see the code for <a href="https://github.com/vuorinem/aurelia-azureadb2c/compare/63249dfc6cea01e8a6564b8455cbc65537758889...600e1a874a13cb6020c5b5c5e22d932803d3f3a8">implementing sign-out</a>.</p><h4>Aureliaize!</h4><p>There’s nothing fancy in the client-side code pasted here so far, and most of it is pretty close to the Microsoft’s <a href="https://github.com/Azure-Samples/active-directory-b2c-javascript-hellojs-singlepageapp">sample application</a>. The real fun starts when we start to integrate it with an Aurelia application.</p><p>As with most of the non-UI code, I decided to put the authentication code with all the hello.js references into a service class. That simply means that the class has <em>Service</em> at the end of its name, and it doesn’t have a template or implement any interfaces. The class is only used through dependency injection, which (by default) creates a singleton instance of the class.</p><p>The <a href="https://github.com/vuorinem/aurelia-azureadb2c/blob/master/src/auth/auth-service.ts">AuthService </a>class handles all the calls to hello.js and initializing the provider with Azure AD configuration. Constructor can handle all the initialization because it is all handled synchronously. (If something asynchronous needs to be called before initializing hello.js, all that would need to be handled in some other way as <a href="https://github.com/aurelia/dependency-injection/issues/88">constructors cannot be asynchronous</a>.) Configuration for the specific AD is held in a the <a href="https://github.com/vuorinem/aurelia-azureadb2c/blob/master/src/auth/auth-config.ts">auth-config.ts</a> file.</p><p>All the options that can be set beforehand have been set in the constructor, so the actual calls to <em>login()</em> and <em>logout()</em> are simple. We’ll only need to make sure to update authentication status whenever it might change. This might happen when the page is loaded (in case of a sign-in or sign-out response), so the first check should be in the constructor. Also after login and logout, the status should be updated. Hello.js has also some events that could be used to track changes in authentication status, by <a href="https://adodson.com/hello.js/#helloon">attaching event handlers with hello.on()</a>.</p><p>AuthService can be used simply by injecting it into any class. In the sample application, the main functionality is in app.ts and the UI in app.html. Log-in and log-out buttons call the respective AuthService methods, and their visibility is dictated by the authentication status.</p><h4>Make authenticated API call</h4><p>The final step is to make use of all the hard work we have done. From all the set up and code above, the most important artefact we get is the authentication token. Using the token we can call the API that requires authentication, by adding the token in the Authorization-header in the request.</p><p>With Aurelia, the simplest way to add a request header is to use an interceptor. Interceptors can be used to modify HTTP requests and responses. The implementation for authorization-header interceptor simply <a href="https://github.com/vuorinem/aurelia-azureadb2c/blob/45c72a09770af634fa5377f292a5eca374622366/src/auth/auth-service.ts#L47-L54">adds the header if there is a token available</a>. When making the API call, the <a href="https://github.com/vuorinem/aurelia-azureadb2c/blob/45c72a09770af634fa5377f292a5eca374622366/src/app.ts#L14-L15">HTTP client is configured to use interceptor</a>.</p><p>That’s it! The next stage would be to implement the API that receives the token and reads the user claims from it, but that will be a topic of another article.</p><h3>-end-</h3><p>Thank you for reading! I hope the article was useful, saved you some time or gave an inspiration to try something out. Any feedback is welcome, so feel free to comment or send a message!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=351fbe2de348" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>