We wish you all the best for Christmas!
I should not say this in public because I’m a Swiss Guy, but I love the German Community ;). I’ve been giving Usergroup speeches in many German cities over the last few years. Every community event I attended in Germany was fully organized, well-coming, and the community engaged with the speakers and workshop leads. One of the most unusual events in Germany is starting in a few days in Leipzig. It is the Developer Openspace 2015. Here are a few impressions:
Abstract: An Open Space is a conference without speakers or a fixed agenda. Similar to a BarCamp the crowd meets every morning (at a developer-friendly time), and everyone is invited to suggest a session-topic. That can be the latest hot shit from Silicon Valley (or Seattle) everyone has heard about and wants to discuss with others, or something you are highly interested in, so you’re looking for some fellow experts to give you an introduction.
As part of the pre-unconference sessions on Friday, I will be giving a full day workshop about async/await and the Russian Doll model by applying that knowledge to an almost production-ready service bus-library.
Sounds interesting? Don’t miss that community opportunity and visit the official web page, book your flight/train/cab and let’s meet for a beer in Leipzig in October.
Picture shamelessly stolen from Thomas Bandt.
I listen to a few podcasts. Mainly technical ones. I recently got a hint from Mike Minutillo about a podcast called “Stuff I learned yesterday”. I was blown away when I started listening to this podcast. It makes you think more about stuff that you learned. Furthermore, this podcast is full of stories from the podcasters themselves but also from the community. You’ll find the podcast here
One of the recent inspiring and very emotional episodes are
If you have lost someone in your life like I did, you know why I like this one.
Are they even listening?
If you are a parent, like I am, you know why I like this one.
Subscribe! It is emotional, inspiring, makes you laugh, cry, think…
Post picture by http://www.gotcredit.com/
I recently announced Machine.Specifications.Resharper 1.1.0 release. This is the last release I did for Machine.Specifications. I’m taking a step back from the project. Let me give you a bit of background how I ended up maintaining Machine.Specifications and why it’s time to move on. Continue reading
For a little more than seven years bbv Software Services AG has been my first employer after my studies at the University of Applied Sciences in Horw, Lucerne. Today it’s time to say goodbye. But before I talk about my new future allow me to take a step back and reflect on my bbv Software Services experience. Continue reading
Thanks to Matt Ellis and some bug hunting of me I can proudly say that we have released Resharper 9 integration for Machine.Specifications. You can now install the plugin by using the provided extension manager in Resharper 9.
For those who are using Resharper versions older than 9 I pushed an update for the plugin for Resharper 8.2. It resolves an issues when you switch from Debug to Release mode or vice versa while having a unit test session open. If you did, you actually had to restart Visual Studio so that the Resharper plugin picked up the correct output path location of the specs assembly. Older Resharper versions are no longer supported as well as the installation via batch files. If you find anyting feel free to open issues on the github repository.
This is a really quick announcement. I recently released Machine.Specifications 0.9.0. With that release I introduced a breaking change: I disabled the console output capturing by accident. If you are using console outputs in your specs and need to see them then I strongly advise you to upgrade to Machine.Specifications 0.9.1. You only need to upgrade the Machine.Specifications nuget package in your solution. None of the other components are affected. This is the beauty of the new architecture 😉
Have fun and sorry for the inconvenience!
Today we released the next version of Machine.Specifications. This release implements an important feature to move on in the future. We implemented a complete runner dependency abstraction. What does that mean? Let me take a step back.
The picture above shows the state of Machine.Specifications previous to V0.9.0. The console runner, the resharper runner, the TDnet runner and more were directly dependent upon the same Machine.Specifications version. This means when we release a new version of MSpec you actually had to use also the new version of the ReSharper, Console runner and more. This was not only for you as a user cumbersome it was also for us as the maintainers of the library. We had a massive repository with everything in it and released all as a “big chunk”. That made working, forking and all other git operations heavyweight because the repository was quite large. Continue reading