02 Jun 2013 - Tomi Junnila
It’s been a couple of years since I’ve blogged anything more than to announce family events etc, and I felt I need to work on my writing skills. Thus, I decided to start blogging under my own home page on mostly technical topics that I encounter in my work.
At the moment, I’m working on three different projects: a ship stability program for onboard use (WPF), a hosted accounting application for non-profits (ASP.NET MVC, Entity Framework), and a Windows Phone project I’m keeping under the wraps for now.
Which brings me to my current dilemma: Since I plan on blogging about stuff I run into in my work, how should I post about it? To put it differently, do I mind blogging about my actual projects and their technical issues? On the one hand, it’s less work for me if I don’t have to invent some other scenario to highlight my problem of the day. On the other hand, if I do tell specifics about my actual implementation, this could 1) work as negative marketing since it would describe works-in-progress rather than a finished project, and 2) provide useful information to my competitors (not really in terms of giving them information how to do X, but possibly set me up for litigation – this is not a field I’m familiar with at all).
Well, I think I’ll see if that is a problem that needs to be solved at all – the first posts I’ve thought of are somewhat more generic so I shouldn’t have issues with them.