This is my site for fun and work. I am Sander, a software architect.
Centrical is my playground. Blogs, news and resources are updated regularly.
My articles are published on Infoworld, AutomatiseringsGids and Emerce, too.
I gather worldwide news, whether it is about e-commerce or service oriented architectures.
My resume, the Web Unified Process and the general conditions are offered in several formats.
Some more information about me is shown here, like a resume, professional history and more.
Things I do are audits, architecture design and strategic advice.
Read the cases of customers like Akzo Nobel, Sanoma Publishers and VNU.
To contact Centrical, you could either use the contact information or fill out the contact form.
Past publications, sorted by date of publication, are shown in my archive.
A short overview on what this website has to offer is shown here.
For a legal disclaimer and privacy issues according to international laws, check out this chapter.
For access to the systems of Centrical, you could use this entry.
This is an rss feed for news only. After clicking, copy the URL into your feedreader.
Stuff that happens to me sometimes inspires me to write. It may be nonsense, though.
WUP (Web Unified Process) is a lightweight and agile development method for web projects.
This where I keep technical posts that might come in handy.
Archive
19 January 2005
One size fits none
Scott Ambler explains that there are no universal rules; excerpt from in the latest newsletter from Software Development Magazine, 19-01-2005.
The IT community operates on a fundamental assumption of software development "best practices," demanding that we use them on all projects. For example, model reviews, detailed requirements documents, change control boards (CCBs) and pair programming are typically referred to as best practices. But reality reveals that one size does not fit all: I believe that these are actually contextual practices that work in some situations, but not others -- there's really no such thing as "best practices."
More
The IT community operates on a fundamental assumption of software development "best practices," demanding that we use them on all projects. For example, model reviews, detailed requirements documents, change control boards (CCBs) and pair programming are typically referred to as best practices. But reality reveals that one size does not fit all: I believe that these are actually contextual practices that work in some situations, but not others -- there's really no such thing as "best practices."
More
You are trying to view the newsticker in a browser that doesn't support it. I am sorry.
