Comments for erik dörnenburg

Comment on Dependency Structure Matrix by Schauderhaft » Introducing Degraph for Visualizing Package Dependencies

Schauderhaft » Introducing Degraph for Visualizing Package Dependencies — Sun, 24 Feb 2013 06:29:42 +0000

[...] that tell you when you have dependency cycles. Most of the time they show you the problem as a dependency structure matrix. Unfortunately it is really hard to identify a bunch of classes that you can pull out of a package [...]

Comment on The Buy-vs-Build Shift (part 1) by Taming the Hippo (CMS) Beast | thekua.com@work

Taming the Hippo (CMS) Beast | thekua.com@work — Sat, 12 Jan 2013 17:06:07 +0000

[...] a product, or the platform will often dictate and limit your ability to do things. My colleague Erik Dörnenburg has been writing more about this [...]

Comment on The Buy-vs-Build Shift (part 1) by Barrett Raymond

Barrett Raymond — Mon, 31 Dec 2012 09:16:04 +0000

Bespoke software development in standard isn’t directed at the plurality of the market but to particular vendors and corporations or groups.

Comment on Making ESB pain visible by Vaibhav Tyagi

Vaibhav Tyagi — Wed, 12 Dec 2012 20:16:33 +0000

Sorry instead of understood wrong I want to type i understood wrong.

Comment on Making ESB pain visible by Vaibhav Tyagi

Vaibhav Tyagi — Wed, 12 Dec 2012 20:15:46 +0000

Hi Erik,

Nice Diagram. I think that you published one side of the problem or understood wrong.

We have to go one level up to think about ESB usage. ESB is not just for publishing the services. There are lot of things required at Enterprise Level like Governance, Scaliblity, Security, Flexiblity, Maintaineablity, Multi Application Integration, Messaging Framework so we have to consider other factors before jump to the conclusion.

Comment on How toxic is your code? by Cezar Coca

Cezar Coca — Wed, 28 Nov 2012 08:53:12 +0000

We found this visualization technique very useful on refactoring projects. In order to integrate it in our Continuous Integration environment we managed to create a Sonar Plugin to collect the violation and render the chart.

More details can be found here:
http://docs.codehaus.org/display/SONAR/Toxicity+Chart+Plugin

The above plugin can be installed from the Sonar Update Center

Thank you Eric for this inspiring post

Comment on The Buy-vs-Build Shift (part 1) by Core Competency at Mark Needham

Core Competency at Mark Needham — Sat, 24 Nov 2012 12:44:32 +0000

[...] my colleague Erik Doernenburg has a slightly different take on this where he considers whether software development as a concept is a core competency and explains how for publishing companies it now needs to be [...]

Comment on The Buy-vs-Build Shift (part 1) by Buy vs Build: Driving from the problem at Mark Needham

Buy vs Build: Driving from the problem at Mark Needham — Sat, 17 Nov 2012 16:57:31 +0000

[...] colleague Erik Doernenburg has written a couple of articles recently discussing the reasons why people buy and build IT solutions and one part in particular resonated with me: it is also possible, and not [...]

Comment on The Buy-vs-Build Shift (part 2 and 3) by H

Fri, 16 Nov 2012 18:41:27 +0000

@Erik. Thank you. I will check that out and look forward to purchasing the book when it’s out. Will read the PDF for now.

Comment on The Buy-vs-Build Shift (part 2 and 3) by Marc

Marc — Wed, 14 Nov 2012 15:43:31 +0000

Good analysis.
You put into words what I experienced over the years with bought-software.