<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-6927217</id><updated>2011-07-08T02:47:34.961+02:00</updated><title type='text'>Peter Arrenbrecht's Blog</title><subtitle type='html'>Literate testing, JCite, Java, Excel for Java, Mercurial, and whatever else seems to long for a tweet.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>33</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-6927217.post-8310308454774819887</id><published>2008-01-23T15:18:00.000+01:00</published><updated>2008-01-23T15:25:56.355+01:00</updated><title type='text'>Threaded chat article and demo</title><summary type='text'>While nothing major, managing threaded conversations in chat has bothered me for quite a while. Yesterday I had an idea on how to improve matters:Works using existing chat infrastructure. Needs only augmented clients.Plays well even if other party uses a non-thread aware chat tool.Separates threads automatically based on interaction patterns.I've written an article and have created an online demo</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/8310308454774819887/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=8310308454774819887' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/8310308454774819887'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/8310308454774819887'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2008/01/threaded-chat-article-and-demo.html' title='Threaded chat article and demo'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-3775114825394072031</id><published>2007-12-05T09:51:00.001+01:00</published><updated>2007-12-05T09:54:47.983+01:00</updated><title type='text'>GMail diffs to find quoted text</title><summary type='text'>GMail is really so cool. I think rather than just relying on quotation marks (&gt; and such), it strips them and then diffs the message to its predecessors to find common chunks. I saw that in action when I sent an updated patch to a mailing list. In both versions, there were no quotation marks, but the second message, viewed in GMail, showed just what had changed versus the first message, the rest </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/3775114825394072031/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=3775114825394072031' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/3775114825394072031'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/3775114825394072031'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2007/12/gmail-diffs-to-find-quoted-text.html' title='GMail diffs to find quoted text'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-8168369333441810021</id><published>2007-11-29T11:24:00.000+01:00</published><updated>2007-11-29T12:58:28.181+01:00</updated><title type='text'>Using Throwable to trace the origin of an object</title><summary type='text'>When using components decoupled by queues or other intermediate data stores, it can be a pain to trace the origin of faulty data in the queue. In languages with decent support for stack traces, however, it's easy. In Java, you just add a temporary field public final Throwable createdBy = new Throwable(); to the class in question. Or, if you need to know who enqueued it where, you vary the </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/8168369333441810021/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=8168369333441810021' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/8168369333441810021'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/8168369333441810021'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2007/11/using-throwable-to-trace-origin-of.html' title='Using Throwable to trace the origin of an object'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-1294063219555470759</id><published>2007-11-24T11:10:00.000+01:00</published><updated>2007-11-24T11:13:04.375+01:00</updated><title type='text'>Literate Testing</title><summary type='text'>What I termed documentation-driven testing has before been penned literate testing, where the Python docTest people have summarized the essence very nicely indeed.</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/1294063219555470759/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=1294063219555470759' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/1294063219555470759'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/1294063219555470759'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2007/11/literate-testing.html' title='Literate Testing'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-5044045264248759383</id><published>2007-04-18T07:30:00.000+02:00</published><updated>2007-04-18T07:30:58.903+02:00</updated><title type='text'>Excellent Tests In Docs - Zope</title><summary type='text'>Zope Source Code Repository - markup - Zope: zc.queue/trunk/src/zc/queue/queue.txt</summary><link rel='related' href='http://svn.zope.org/zc.queue/trunk/src/zc/queue/queue.txt?rev=67933&amp;view=markup' title='Excellent Tests In Docs - Zope'/><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/5044045264248759383/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=5044045264248759383' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/5044045264248759383'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/5044045264248759383'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2007/04/excellent-tests-in-docs-zope.html' title='Excellent Tests In Docs - Zope'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-3648616410985794818</id><published>2006-12-27T17:29:00.000+01:00</published><updated>2006-12-27T17:47:53.769+01:00</updated><title type='text'>Local Builder Pattern Broken in Java?</title><summary type='text'>Time and again, when I want to break up a longish Java method into smaller parts, I find myself wishing back the by-reference parameters and access to surrounding local procedure variables of Pascal. Now, I know that the discipline of trying to always pass all required arguments explicitly, and to not rely on changes to by-ref params is often helpful. Nevertheless, sometimes it gets in the way. </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/3648616410985794818/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=3648616410985794818' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/3648616410985794818'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/3648616410985794818'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/12/local-builder-pattern-broken-in-java.html' title='Local Builder Pattern Broken in Java?'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-116435661358274666</id><published>2006-11-24T08:47:00.000+01:00</published><updated>2006-11-24T09:43:40.786+01:00</updated><title type='text'>Documentation Driven Development - Other Takes On The Theme</title><summary type='text'>I googled for "Documentation Driven Development" and came up with a number of links (why the heck did I not do this sooner?). SpliceIt seem to be doing it, but don't cite tests. There is no mention of integration with use-case-level tests.Vincent Massol had the experience when writing books about frameworks - always improved the underlying code. The message is: you have to be serious about </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/116435661358274666/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=116435661358274666' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/116435661358274666'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/116435661358274666'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/11/documentation-driven-development-other.html' title='Documentation Driven Development - Other Takes On The Theme'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-116377015481705452</id><published>2006-11-17T14:01:00.000+01:00</published><updated>2006-11-17T14:30:16.240+01:00</updated><title type='text'>Impressions: "Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries"</title><summary type='text'>I've recently read Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries by two lead architects on the .NET Framework. A mixed experience, I have to say. The book does offer good advice, but somehow, hardly anything seemed truly new. Maybe that is because I've already read Josh Bloch's Effective Java, but, I suspect, mostly because I have accumulated a fair </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/116377015481705452/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=116377015481705452' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/116377015481705452'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/116377015481705452'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/11/impressions-framework-design.html' title='Impressions: &quot;Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries&quot;'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-115860241739547832</id><published>2006-09-18T20:00:00.000+02:00</published><updated>2006-09-18T20:00:21.296+02:00</updated><title type='text'></title><summary type='text'>     Because I am now reading a book about Haskell, but also because when I   implemented the   gist   of Palo in Erlang, I was bitten by - tada! - a typing error, I decided to   port the code over to Haskell. While the functional core syntax of the two   languages is quite similar, here's one detail that took me a while to figure out: A case construct in Haskell always introduces new name </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/115860241739547832/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=115860241739547832' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115860241739547832'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115860241739547832'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/09/because-i-am-now-reading-book-about.html' title=''/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-115756367171798741</id><published>2006-09-06T19:27:00.000+02:00</published><updated>2006-09-06T19:27:52.390+02:00</updated><title type='text'>The Gist of Palo - Erlang In Action</title><summary type='text'>I have been asked to review the Palo code base. This is an open-source MOLAP database server. To get a feeling for what its core C code does, I reimplemented the gist of it in Erlang. Turns out it's really just a few lines when you have high-level functional constructs at your disposal. Out of curiosity, I then went and extended it so it really mimicks the Palo cube storage more closely, binary </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/115756367171798741/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=115756367171798741' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115756367171798741'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115756367171798741'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/09/gist-of-palo-erlang-in-action.html' title='The Gist of Palo - Erlang In Action'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-115744056669290697</id><published>2006-09-05T09:16:00.000+02:00</published><updated>2006-09-05T09:16:06.970+02:00</updated><title type='text'>Meta-data Enhanced Wiki</title><summary type='text'>I recently stumbled upon Diamond Wiki. This is a wiki enhanced by meta-data and navigation along meta-data dimensions. Interesting. Maybe a first step in the direction of something like an ad-hoc database. While deeply impressed with DabbleDB, I still think it should be possible to come up with something even more fluent, more ad-hoc.</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/115744056669290697/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=115744056669290697' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115744056669290697'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115744056669290697'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/09/meta-data-enhanced-wiki.html' title='Meta-data Enhanced Wiki'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-115581189367609587</id><published>2006-08-17T12:48:00.000+02:00</published><updated>2006-08-17T12:52:30.126+02:00</updated><title type='text'>DDT - Documentation Driven Testing</title><summary type='text'>What JCite really is about is what I am going to call DDT: documentation-driven testing. It is a discipline that complements and, during the conception of an API, really comes before  TDD: test-driven development.DDT weeds out them design bugs! :)</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/115581189367609587/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=115581189367609587' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115581189367609587'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115581189367609587'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/08/ddt-documentation-driven-testing.html' title='DDT - Documentation Driven Testing'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-115524272654296914</id><published>2006-08-10T22:08:00.000+02:00</published><updated>2007-06-14T17:30:31.381+02:00</updated><title type='text'>Beyond TDD: Documentation Driven Development</title><summary type='text'>There are quite a few articles extolling the virtues of test-driven development these days (here's one). And for good reason, too. Having done TDD for quite a while, I recently started combining it with documentation-driven design. This is what my open-source tool, JCite, is all about.With this approach, Isketch out the most important use cases,combine them into the index of a tutorial (links </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/115524272654296914/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=115524272654296914' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115524272654296914'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115524272654296914'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/08/beyond-tdd-documentation-driven.html' title='Beyond TDD: Documentation Driven Development'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-115280732326385266</id><published>2006-07-13T17:39:00.000+02:00</published><updated>2006-07-14T08:58:59.396+02:00</updated><title type='text'>FreeBSD in Virtual PC 2004</title><summary type='text'>I finally managed to install FreeBSD 6.1 in Microsoft Virtual PC 2004 with NATted networking behind a firewall. Here's how:Download the boot ISO image and mount it in the VM.Reset the VM.Run the FreeBSD setup until you have to choose the type of installation. Select "Standard".When asked to slice the disk, type A for "Auto", then Q for "Quit".When asked about the boot manager, select "Standard". </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/115280732326385266/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=115280732326385266' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115280732326385266'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115280732326385266'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/07/freebsd-in-virtual-pc-2004.html' title='FreeBSD in Virtual PC 2004'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-115260545602254807</id><published>2006-07-11T10:10:00.000+02:00</published><updated>2006-08-30T09:34:21.920+02:00</updated><title type='text'>RSpec and BDD - something crucial missing?</title><summary type='text'>RSpec Site: "RSpec provides a framework for writing what we call executable specifications of program behaviour. Since that’s rather wordy, we usually just call them specs. Some other people call these things examples."If I take a look at the examples on the RSpec site, I cannot help but wonder if just doing this (which they term "behaviour-driven development"), misses out on an important aspect </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/115260545602254807/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=115260545602254807' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115260545602254807'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115260545602254807'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/07/rspec-and-bdd-something-crucial.html' title='RSpec and BDD - something crucial missing?'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-115225881634487326</id><published>2006-07-07T09:53:00.000+02:00</published><updated>2006-07-07T09:54:25.476+02:00</updated><title type='text'>Jay Fields Thoughts: Use erb to insert dynamic text</title><summary type='text'>Jay Fields Thoughts: Use erb to insert dynamic text: "Tonight, I was writing up some new material and wanted to mix some examples with the text. I could have just pasted the code into the material; however, I wanted the material to update automatically if I updated the code. When working with Martin on his next book I got to experience the value in this practice first hand and it wasn't something</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/115225881634487326/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=115225881634487326' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115225881634487326'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115225881634487326'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/07/jay-fields-thoughts-use-erb-to-insert.html' title='Jay Fields Thoughts: Use erb to insert dynamic text'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-115164555083590419</id><published>2006-06-30T07:32:00.001+02:00</published><updated>2006-06-30T07:37:34.226+02:00</updated><title type='text'>Querying the Java Heap</title><summary type='text'>A. Sundararajan's Weblog:"As I mentioned earlier, Mustang (Java SE 6) comes with jhat - Java Heap Analysis Tool. We have added more features to jhat as of build 53 (released on Sep, 22, 2005). jhat now comes with mechanism to query the heap. jhat supports OQL - Object Query Language -- a SQL-like language to query your Java heap!"This is amazing news! It has, in fact, in one stroke returned my </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/115164555083590419/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=115164555083590419' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115164555083590419'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/115164555083590419'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/06/querying-java-heap.html' title='Querying the Java Heap'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-114970075136261476</id><published>2006-06-07T19:19:00.000+02:00</published><updated>2006-06-07T19:19:11.646+02:00</updated><title type='text'>Source Citing: Making Examples Work - arrenbrecht.ch</title><summary type='text'>Source Citing: Making Examples Work - arrenbrecht.ch: "People learn best from good examples. To be good, examples need to be correct. In every release. So a test for them is likely the single most important automated test you can write."</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/114970075136261476/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=114970075136261476' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/114970075136261476'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/114970075136261476'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/06/source-citing-making-examples-work.html' title='Source Citing: Making Examples Work - arrenbrecht.ch'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-114598292675740731</id><published>2006-04-25T18:30:00.000+02:00</published><updated>2006-04-25T18:35:26.776+02:00</updated><title type='text'>Google trumps Flock (well, at least for me)!</title><summary type='text'>As I posted earlier, I had this idea about bookmarks that are searchable using Google. Well, they've implemented it if you have personalised search enabled. There is a new link at the bottom to a bookmarklet for easily adding a bookmark within your Google account. Like del.icio.us, but searchable with Google. Cool! (I did, by the way, tell Google about this idea. I'd love to know if that had an </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/114598292675740731/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=114598292675740731' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/114598292675740731'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/114598292675740731'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/04/google-trumps-flock-well-at-least-for.html' title='Google trumps Flock (well, at least for me)!'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-114286078285812033</id><published>2006-03-20T14:19:00.000+01:00</published><updated>2006-03-20T14:19:42.896+01:00</updated><title type='text'>arrenbrecht.ch</title><summary type='text'>My new personal and professional home pages are up!</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/114286078285812033/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=114286078285812033' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/114286078285812033'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/114286078285812033'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/03/arrenbrechtch.html' title='arrenbrecht.ch'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-114259803220264691</id><published>2006-03-17T13:18:00.000+01:00</published><updated>2006-03-17T13:20:32.216+01:00</updated><title type='text'>A word Google does not know</title><summary type='text'>Cool! I created a word that Google does not find. You probably have to be german-speaking to get it, though: Encephaloman.</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/114259803220264691/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=114259803220264691' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/114259803220264691'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/114259803220264691'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2006/03/word-google-does-not-know.html' title='A word Google does not know'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-113018120977016302</id><published>2005-10-24T21:09:00.000+02:00</published><updated>2005-10-24T21:13:41.906+02:00</updated><title type='text'>Gaming to escape the drudge</title><summary type='text'>The following certainly rings true:"For me, the obsession is sometimes a coping mechanism -- with a job that is boring, or some other life rut. And the obsession seems to end when the boredom ends or the situation I'm avoiding sorts itself out."Greg Sewell, in The End of the Affair</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/113018120977016302/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=113018120977016302' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/113018120977016302'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/113018120977016302'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2005/10/gaming-to-escape-drudge.html' title='Gaming to escape the drudge'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-113013700721328060</id><published>2005-10-24T08:56:00.000+02:00</published><updated>2005-10-24T08:57:41.193+02:00</updated><title type='text'>del.icio.us/peter.arrenbrecht</title><summary type='text'>I have a del.icio.us account now to keep my public bookmarks at. Great stuff, especially due to the nice integration with Flock.</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/113013700721328060/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=113013700721328060' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/113013700721328060'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/113013700721328060'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2005/10/deliciouspeterarrenbrecht.html' title='del.icio.us/peter.arrenbrecht'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-113013426564046157</id><published>2005-10-21T20:29:00.000+02:00</published><updated>2005-10-24T08:20:29.966+02:00</updated><title type='text'>Starring and searching in Flock is great!</title><summary type='text'>Amongst a host of others, Flock realizes an idea I had a while ago and told Google about: a real simple way to remember a site. In Flock, it's called to "star" a site. Very quick. No folder selection. And with full text search. This is exactly right. Because at the moment I am starring the site, I am really ready to move away from it again. I don't want to bother with classification. When, later,</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/113013426564046157/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=113013426564046157' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/113013426564046157'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/113013426564046157'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2005/10/starring-and-searching-in-flock-is.html' title='Starring and searching in Flock is great!'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-112867819222401554</id><published>2005-10-07T11:38:00.000+02:00</published><updated>2005-10-07T11:51:05.690+02:00</updated><title type='text'>Procrastination</title><summary type='text'>So now I know how to call it: procrastination. And now I know I am not alone by far. My own reaction lately was to consciously start thinking and writing more again (as you can see here, at least the latter part), and I implemented a tool that monitors my activity throughout the day so at least I can, at the end of a work day, see what ate the time. Seems someone else had a similar, albeit even </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/112867819222401554/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=112867819222401554' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/112867819222401554'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/112867819222401554'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2005/10/procrastination.html' title='Procrastination'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-112867602643495396</id><published>2005-10-07T11:03:00.000+02:00</published><updated>2005-10-07T11:07:06.440+02:00</updated><title type='text'>StructuredBlogging</title><summary type='text'>Just came across the site StructuredBlogging. This addresses kind of the same problem I want to address with the emergent data entry language. Make it easy for people to add structure. However, it seems that StructuredBlogging requires effort by someone to create the structure in advance of it being used, whereas the emergent approach lets non-technical people add structure of their own.</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/112867602643495396/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=112867602643495396' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/112867602643495396'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/112867602643495396'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2005/10/structuredblogging.html' title='StructuredBlogging'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-112832601767762613</id><published>2005-10-03T09:43:00.000+02:00</published><updated>2005-10-03T13:15:07.346+02:00</updated><title type='text'>Debugging Domain Specific Languages</title><summary type='text'>One of the problems with debugging domain specific languages (DSLs) is that a single DSL construct is often mapped to a multitude of aspects in the generated code or generic implementation. Thus, the classic concept of a breakpoint is difficult to interpret.However, it seems to me that this could be overcome fairly easily. Simply allow users to set breakpoints targeted at specific aspects of the </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/112832601767762613/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=112832601767762613' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/112832601767762613'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/112832601767762613'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2005/10/debugging-domain-specific-languages.html' title='Debugging Domain Specific Languages'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-112807410607950279</id><published>2005-09-30T11:52:00.000+02:00</published><updated>2005-09-30T11:55:06.080+02:00</updated><title type='text'>Emergent Language for Data Entry</title><summary type='text'>Combine a wiki with code assist, templates, syntax checking, relational technology, a query language, semantic mapping and Google Suggest. What do you get?  An emergent language, that's what. A domain specific data entry language uniquely tailored to the information at hand through continued use and extension. The IDE features in the background are there to help in achieving consistency, but the </summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/112807410607950279/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=112807410607950279' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/112807410607950279'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/112807410607950279'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2005/09/emergent-language-for-data-entry.html' title='Emergent Language for Data Entry'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-109817808317997145</id><published>2004-10-19T11:25:00.000+02:00</published><updated>2004-10-19T11:28:03.180+02:00</updated><title type='text'>Open Source killing my idea?</title><summary type='text'>I have an idea for a piece of software that would bring a lot of value to a lot of developers. However, while the idea is quite clever, implementing it does not take that much of an effort. So how am I going to protect myself against the open source community? I could probably make a decent profit from the thing. So there is the real possibility that I can spend some of my working time working on</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/109817808317997145/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=109817808317997145' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/109817808317997145'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/109817808317997145'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2004/10/open-source-killing-my-idea.html' title='Open Source killing my idea?'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-109722486789472616</id><published>2004-10-08T10:37:00.000+02:00</published><updated>2004-10-08T10:41:42.126+02:00</updated><title type='text'>Access 2003 and the DCOM Server Process Launcher</title><summary type='text'>Here's a hint: Don't disable the "DCOM Server Process Launcher" service on XP SP2. It may look like one heck of a vulnerability when you really don't use DCOM at all, but, unfortunately, Microsoft Access 2003 does. It will simply open an instant message box stating "A problem occurred while Microsoft Access was communicating with the OLE server or ActiveX Control." if the service is not running.</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/109722486789472616/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=109722486789472616' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/109722486789472616'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/109722486789472616'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2004/10/access-2003-and-dcom-server-process.html' title='Access 2003 and the DCOM Server Process Launcher'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-108971091766264196</id><published>2004-07-13T11:26:00.000+02:00</published><updated>2004-10-05T18:21:12.843+02:00</updated><title type='text'>The user is just another service</title><summary type='text'>Clemens Vasters recently blogged about one of his epiphanies: "the user is just another service". Same thing here. After one of his sessions about FABRIQ, actually (in Switzerland).</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/108971091766264196/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=108971091766264196' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/108971091766264196'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/108971091766264196'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2004/07/user-is-just-another-service.html' title='The user is just another service'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-108560175109399513</id><published>2004-05-26T20:50:00.000+02:00</published><updated>2004-05-26T22:02:31.093+02:00</updated><title type='text'>Editme customer service</title><summary type='text'>What an amazing experience. I just surfed over to editme.com, prompted by the link generated by this blogger here. While the service sounds exciting, what really knocked me out of my shoes is their sales rep system. You simply log into a chat and within five seconds (!) there was someone online. And that someone was truly helpful. Wow!</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/108560175109399513/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=108560175109399513' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/108560175109399513'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/108560175109399513'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2004/05/editme-customer-service.html' title='Editme customer service'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6927217.post-108419418050281305</id><published>2004-05-10T13:29:00.000+02:00</published><updated>2004-05-26T20:28:59.163+02:00</updated><title type='text'>Nemerle</title><summary type='text'>Just read about Nemerle, a new .NET language. Sounds great to me: C#, ML, and Scheme united in a readable fashion!</summary><link rel='replies' type='application/atom+xml' href='http://peomeint.blogspot.com/feeds/108419418050281305/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6927217&amp;postID=108419418050281305' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/108419418050281305'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6927217/posts/default/108419418050281305'/><link rel='alternate' type='text/html' href='http://peomeint.blogspot.com/2004/05/nemerle.html' title='Nemerle'/><author><name>Peter Arrenbrecht</name><uri>http://www.blogger.com/profile/17041051495984882287</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
