I recently went through my draft posts and found this little post about 3 podcasts, I at the time thought were quite awesome. For some reason, I never got around to publishing it, but since I still think they are quite awesome here they are: I thought I might share a few good podcasts I’ve listened to recently. Yehuda Katz - Rails/Ember/Rust Jose Valim - Elixir Matz (Yukihiro Matsumoto) - Ruby The main reason I found these podcast interesting is that it tells the story behind some very prominent people in our industry and for 2 of them, it seems they started in programming by pure accident and turned out awesome!

Last year I had the pleasure of speaking at the DDD conference here in Brisbane. It was a really good experience and I enjoyed doing the talk a lot. One of the great things about the DDD conference is the engagement of the audience and community and thus the amount of feedback you get as a speaker. A lot of the comments I got were really positive which I obviously appreciate immensely. But I also got quite a lot of good suggestions on things to improve, like;

Why 🔗As a consultant, I sometimes work with clients that aren’t using the best source control software that is currently available. This sometimes means that git is not the preferred tool for source control. Even though you can’t always control the infrastructure of your workplace, it doesn’t need to be an excuse to stick with suboptimal tools to do your job. You are better than that! My main gripe with TFS (or any centralized source control system that I know of) is the branching story. The lack of easy local branching (and later, sharing of these) really inhibits my typical workflow. The fact that a centrally-controlled server is the only possible way to create such a branch is a fundamental problem with TFS and it’s tooling ecosystem, and cannot currently be solved without changing away from TFS. As a consequence, organisations that use TFS tend to treat the entire concept of a branch something that needs to be centrally controlled and managed.

I recently started a new job. Actually I moved from Copenhagen to Brisbane, Australia with my whole family, just to try living and working in a different country - and of course to give our 3 kids and ourselves a great experience/ adventure. Anyway, I got a job in the Australian consultancy Readify and one of the perks there is PD or Professional Development for up to 20 days a year. 20 days where I can work with/learn whatever I feel like (well almost. I need to justify the relevance of the topic and I have to produce something that my colleagues can benefit from too). Yeah I know pretty sweet! So the last 2 days I have had my first PD and my goal was to get familiar with RethinkDB.

The last few weeks I have been working with a customer to implement Azure AD B2C login for their internal systems and I thought I might share my experience with you. What is Azure AD B2C 🔗First of all I might need to explain a few things, like what B2C is (assuming here that you know what Azure and AD are) and what kind of problem I am solving with it. First of all the name B2C simply means business to consumer and is in preview with another new variant of AD called B2B (Business to Business). It is intended to make it easier to set up authentication with multiple social identity providers like Facebook, Google or LinkedIn as easy as can be. But B2C also provides a way to sign up users without a social identity by providing a local account type - which in turn really is just a modified version of an AD account. For the local account B2C provides all the necessary plumbing like signup, password and user management, such that the consuming application never need to store any sensitive information. You can find a lot more information in the B2C documentation here.

Introduction 🔗I have had this blog brewing for a while, but have not really had the time to finish it before - I might get back to why in a later post. Anyway here goes: I started out hosting it on Heroku. It’s a great way of hosting web applications and you can start out on their free tier which also has a lot of free add-ons like Postgres and New Relic. How ever i like to tinker and a Pluralsight course - Mastering Your Own Domain by Rob Conery - inspired me to be more in control. For instructions on how to run Ghost on Heroku I used this guide by Greg Bergé.