Last week I gave a talk about the lessons learned during the exponential growth of our company the last six years. I was invited to to talk at the Appsterdam meetup in Delft about “growing pains”. In other words: what lessons did we learn when our company grew from 3 to 100 employees. I enjoyed the preparations as much as the actual talk, as it forced me to step back.
I finished my last blog post by introducing a Platform-as-a-Service subcategory called “Application Delivery Platform-as-a-Service“ as a way to distinguish platforms that focus on improving the entire application delivery lifecycle (and not just application development or deployment). I would like to clarify my views on Application Delivery and PaaS a bit more. My first attempt has been published on InfoQ yesterday. The short summary: business agility is key, so focus.
Platform-as-a-Service (PaaS)… I guess you heard this term quite a bit last months. I wrote about PaaS earlier when arguing that Model-Driven Engineering is essential for the success of a PaaS and when I announced the new major release of our platform. If you look at the industry perception of PaaS the main definition is something like: it is a public cloud platform where you put code in and get.
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.
No, this is not a typo… I really mean Enterprise Agile, not the subject of some of my previous articles about Agile Enterprises. I hear you sigh: do you really need to put the enterprise moniker in front of everything? Although this is a fair question I think enterprise agile is not just a buzz word. Agile on a bigger scale, in a big enterprise, is different from agile in.
Companies often have more applications than the business needs. This means IT is spending resources on legacy applications instead of focusing on business innovation and growth. This years Application Landscape Report published by Capgemini concluded: One of the top priorities of today’s CIO is to build closer alignment between IT and the business. However to achieve this goal, IT first needs to deal with its own inhibitors to change. We.
If you have been wondering why I was a bit quiet lately… it was for the good cause! Today we launched the third major release of the Mendix platform, which is quite a memorable moment. My team did an awesome job and when I look at the result I can only feel proud! As I have been sharing a lot of my thoughts last years, I want to take the.
Model Driven Development proponents see a lot of advantages of using MDD techniques. Higher development speed, increased quality, more cost-effective, empowering less-experienced developers, just to name a few. If you look at these promises the question arises why the whole world isn’t using MDD right now? Why don’t we hear a lot of MDD success stories? In a recent article I wrote about some of the main concerns which prevent.
May 24th the first Language Workbench Competition have been held in Cambridge (UK) as a warming-up of the Code Generation conference. The idea for a language workbench competition originates from a group of people during Code Generation 2010. 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.
About a month ago Kees Dijk asked a question on the programmers StackExchange titled “Why aren’t we all doing model driven development yet?“. He reiterates his question also as “What do you see as the biggest problems that make you not even consider model driven development?“. It shouldn’t be a surprise that I’m interested in these kind of questions. The answers, in this and other discussions about this subject, are.