Keyboard shortcuts for taking a screenshot on OS X

OS X comes with some really nice keyboard shortcuts to take screenshots. The problem is that I keep forgetting exactly which shortcut does. So for the purpose of having a place to look them up the next time I forget - here they are

Saving to a file on the desktop

  • -Shift--3: Take a screenshot of the screen
  • -Shift--4, then select an area: Take a screenshot of an area
  • -Shift--4, then Space, then click a window: Take a screenshot of a window

Saving to the clipboard

  • -Ctrl-Shift--3: Take a screenshot of the screen
  • -Ctrl-Shift--4, then select an area: Take a screenshot of an area
  • -Ctrl-Shift--4, then Space, then click a window: Take a screenshot of a window
Read more
© Copyright 2013, Andreas Håkansson

A full day of open-source at tretton37

What do you get when you take 50 developers, 12 open-source projects and a full day of coding? You get a tretton37 team knowledge day, with focus on contributing to open-source projects!

It is not often that I blog about my work, but this is just so awesome that it had to be shared. So, about once per quarter we try and organize a company knowledge day, where we take everyone off their billable assignments and cuddle up at our office for a full day of awesome.

Read more
© Copyright 2013, Andreas Håkansson

Copying virtual machines between Azure subscriptions

I recently found myself in the need to copy a couple of Azure Virtual Machines from one subscription to another. Not having used Azure that much before, I figured there must be support to perform this kind of migration from inside the Azure portal itself.

Turns out there isn't, but that does not mean it is impossible, or even hard for that matter. Once you figure it out, it is actually quite frictionless and smooth.

Read more
© Copyright 2013, Andreas Håkansson

Community maintained Nancy F# templates for Visual Studio

Not too long ago, I posted about the Visual Studio templates for Nancy and how we had taken the (tough) decision to only maintain C# templates outselves. Not because we do not see value in supporting other languages, but solely because of the shear amount of work that is required to maintain a single template.

Maintaining 9 templates (as we do with out C# templates) is a time consuming process, and the time required to support additional templates scales linear to the amount of templates we add.

We reached out the authors of the VB.NET templates and F# templates, as well as our community, and ask them to maintain the templates themselves. I didn't take long for the F# community to step up to the plate...

Read more
© Copyright 2013, Andreas Håkansson

On the Nancy templates for Visual Studio

A while back we introduced Nancy templates for Visual Studio, which gave you the ability to create a new Nancy project that has Nancy added out-of-the-box. This meant no more creating an empty ASP.NET web application, removing all those pesky project references and installing the Nancy nugets, just to get up and running.

Unfortunately we have not been able to update these template with every new release of Nancy, which means you have had to update the Nancy Nugets to make sure you where using the latest build.

Believe me when I tell you that this has not been out of laziness, but rather the instinct to survive, but hopefully we've taken a couple of important decisions to remedy this in the future

Read more
© Copyright 2013, Andreas Håkansson

I am back and this time I am taking control

When Posterous closed down on April 30th 2012, they took my blog with them. I made sure I downloaded my content before the service shut down but did not make any effort in relocating. Why? I had gotten to the point where I thought there was something inherently wrong with the way that blogging services and blog engines work.

A blog, in its purest form, is nothing but information with a bit of formatting, added to make it look nice, yet each service (and engine) seem to have need to mangle the content. They do this by either converting your data into HTML, thus losing the initial separation of content and formatting, and/or store it in a proprietary format. Either way, as soon as you have handed over your post, you are no longer in control and that bugs me.

Looking around for options on how to solve this, I got more and more keen on the idea of using GitHub Pages, that lets you write your posts using Markdown and then automatically convert them to static pages using Jekyll.

The things that really appealed to me were

  • I would get to write my content in a very neutral markup language
  • I could store my posts in a normal Git repository
  • The pages would be static and there would be no need for databases or other software to run it
Read more
© Copyright 2013, Andreas Håkansson