Blog overview 2011
|09 January 2012|
In good tradition hereby the blog overview of last year. A bit late this time, but for good reasons (see the overview of the month december).
This year I expect to write a bit more. The subjects will stay the same, and as you could sense from the posts of last year my focus will be on all phases of the application lifecycle. So, Model Driven Development will still get attention, but also cloud and Platform-as-a-Service, as well as requirements capturing, social, and agile. As my first (and only) post with video material was the second popular post last year, I will try to post more video content this year.
Top 10 posts
Based on traffic, these are the top 10 posts in 2011:
- 5 types of Model Driven Software Development
- Why there is no future for Model Driven Development
- DSL development: 7 recommendations for Domain Specific Language design based on Domain-Driven Design
- 8 reasons why Model-Driven Development is dangerous
- Why aren't we all doing Model Driven Development yet?
- Architecture, a definition
- 15 reasons why you should start using Model Driven Development
- MDE - Model Driven Engineering - reference guide
- Language Workbench Competition 2011
- What every architect should now know about the Service Component Architecture (SCA)
I didn't take the time of publishing into account when looking at the statistics. So, articles posted more recently are less likely to show up in the top 10, unless they are very popular. From that perspective number 2 is notable.
Top 10 search terms
These are the top 10 search terms people have use when visiting my blog via a search engine:
- model driven development
- model driven engineering
- enterprise architect
- architecture vs engineering
- domain specific language
- soa framework
- model driven software development
- service component architecture
- architecture definition
- service identification
Blog summary for 2011
- Interview on Pattern Based Engineering: Lee Ackerman, asked me a couple of questions about the use of patterns at Mendix and the relation with Model-Driven Development.
- Why there is no future for Model Driven Development: this post was based on a talk I did in Nantes (France) and includes the slides and a full video of my talk. The main message is that we need to focus on all phases in the application lifecycle, not just development.
- The quest for Business Agility: Emergent Architectures: a long article which clearly describes my views on designing, modeling, and building an agile enterprise with help of emergent architectures.
- Code Generation 2011: just an announcement of the fishbowl session I organized at the Code Generation conference.
- Why aren't we all doing Model Driven Development yet? An analysis of the main concerns which prevent people to use MDD. Initiated an interesting discussion.
- Language Workbench Competition 2011: A lot of new initiatives in the field of language workbenches are arising to facilitate the creation of Domain Specific Languages (DSLs) and their accompanied code generators and IDEs. They all have their own strengths and weaknesses, so a competition to learn about them sound like a great idea back in 2010... and it was! This article describes all tools presented at LWC2011 as well as the opinions of the attendees. A nice overview of DSL tool space!
- Making Model-Driven Software Development live up to its promises: the "sound bites" of the fishbowl discussion I hosted at Code Generation 2011. It was a good discussion on the future of MDD in four sections: marketing, alignment with programming, focus on problem domain, and education.
- The Platform-as-a-Service for the Agile Enterprise: I shared a bit more about my work this time by describing the new major release of our products. This article perfectly fits in the subjects I normally cover like Model-Driven Development, app development, agile, and cloud.
- Managing your application landscape: engineered or emergent: this article was triggered by the Application Landscape Report of Capgemini and defines two different approaches to manage an application landscape.
- Well... moving to a new house doesn't leave you with a lot of time...
- Enterprise Agile: 3 characteristics: there is a difference between an agile team in a start-up (or enterprise!), working in some sort of vacuum, and an agile team operating within the broader context of an enterprise. This article looks at some characteristics to make the difference more clear.
- My first... :)
Blog overviews of previous years: