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.
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
Barely good enough
The simple definition of an agile model? It's just barely good enough.
Similarly, a document is agile when it's just barely good enough. Although
traditionalists may balk at this definition, agile models (and similarly agile
documents) are the most effective. If a model is not yet good enough, you
clearly have more work to do. If a model is more than good enough, you've
invested too much time in creating it, and therefore you've wasted your
stakeholder's money. When a model, or a document, is just barely good
enough it's most effective.
Scott Ambler (Agile Modeling) explains, in the Software Development Magazine newsletter from december 2004.
More
Trust first in XML security
"Trust then verify" was Ronald Reagan's maxim for international arms control. A similar maxim can be applied to security architectures in cross-firewall XML projects: "Trust then validate".
Let's just hope for the new Gorbatsjov, shall we?
Sun and Microsoft...
Sun and Microsoft: So far, so good"Taking an intentionally cautious tone, Microsoft and Sun Microsystems executives said Wednesday that the first eight months of their 10-year partnership have yielded small, but significant progress."
SOAP performance
W3C announced the
advancement of three technical reports to Proposed Recommendations
offering an optimal way to transfer binary data like images in Web
services messages. Produced by the XML Protocol Working Group, SOAP Version 1.2 is a lightweight protocol for
exchanging structured information in a decentralized, distributed
environment such as the Web.
- Using an XML Schema datatype, XML-binary Optimized Packaging (XOP) allows efficient serialization of XML element content.
- Using a XOP-based selective encoding, the SOAP Message Transmission Optimization Mechanism optimizes hop-by-hop exchanges between SOAP nodes.
- The Resource Representation SOAP Header Block allows applications to carry a representation of a resource in a SOAP message.
You are trying to view the newsticker in a browser that doesn't support it. I am sorry.
