The Failure of Communication
Explaining is hard. Things that seem crystal clear to you can be completely foreign to others, and when I started planning on Blogifier, concept looked very natural and not even worth explanation. Seriously, the whole “architectural” diagram would look something like this – web application (Blogifier) using component (Blogifier.Core) to encapsulate common blogging functionality.
Nothing hard about it, right? Wrong, I bump into people over and over telling me they have no idea what I’m trying to accomplish. Different people. Smart people. To make things worse, the Core component did a good job pretending to be an application on its own – it has sample app that only needed for testing, but people took it and ran away.
I’m hoping to fix this miscommunication soon. We just released Blogifier.Core 1.2, and this will hopefully be the last “Core” to worry about. Moving forward, this will be what it was supposed to be all along – just a component like jQuery or Bootstrap so you can build your application on top of it.
The application we are building is Blogifier. That is, just “Blogifier”, without “Core”. It is, accidently, a blog. It references Core so it does not have to deal with all the common plumbing, like database, services, APIs and so on. We going to add all the bells and whistles to make it fun modern application everyone would love and wanted to use. It will run on Windows or Linux, have install and, later, in-place upgrade to the latest version. The work just started, but we already have code repository integrated with demo site, so if you are interested in progress and want to make your opinion heard please follow the trail.
Hope this clears things a little bit, if not – don’t hesitate to ask any questions.