<?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:blogger='http://schemas.google.com/blogger/2008' 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-6798371251264429161</id><updated>2025-09-26T15:19:10.986+01:00</updated><category term="gotcha"/><category term="OpenMP"/><category term="algorithmics"/><category term="programming"/><category term="python"/><category term="arithmetics"/><category term="bash"/><category term="bitwiese"/><category term="c++"/><category term="databases"/><category term="distutils"/><category term="floating point"/><category term="machine learning"/><category term="merging"/><category term="optimization"/><category term="parallelism"/><category term="pitfall"/><category term="postgresql"/><category term="probability theory"/><category term="rails"/><category term="sqlite"/><category term="system architecture"/><category term="textmate"/><category term="threads"/><title type='text'>Bitwiese</title><subtitle type='html'>First, computer science is not about computers. Second, computer science is not a science.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://www.bitwiese.de/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default?redirect=false'/><link rel='alternate' type='text/html' href='http://www.bitwiese.de/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>13</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-6798371251264429161.post-1262178048727792070</id><published>2009-04-15T12:53:00.004+01:00</published><updated>2009-04-15T12:58:33.262+01:00</updated><title type='text'>When stochastic search beats direct methods</title><summary type="text">The central problem of reinforcement learning is to fit the parameters of an
agent&#39;s policy in order to make the agent chose &quot;good&quot; decisions according to
some unknown objective.

Let&#39;s consider a very simple case. We have an MDP which is basically stateless.
So to say, all the world is doing is to map the actions of an agent directly to
a reward. Consider this function to be a mixture of two </summary><link rel='replies' type='application/atom+xml' href='http://www.bitwiese.de/feeds/1262178048727792070/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/6798371251264429161/1262178048727792070' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/1262178048727792070'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/1262178048727792070'/><link rel='alternate' type='text/html' href='http://www.bitwiese.de/2009/04/when-stochastic-search-beats-direct.html' title='When stochastic search beats direct methods'/><author><name>Justin</name><uri>http://www.blogger.com/profile/04972102120598633110</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiZ2HpET-1WnXy0XiK_YQSjcM9nFIDQS_AEQV2VD7WpxryOgw5k6eeaXEvxOYN8FSQiEf6Mez0547NDIKGtk3nS1eQpg4tmhmqCyJPYXuyQhLCWSvCpaW8ivk-Ms_thG7XGh088ZGC13bTM/s72-c/gauss.png" height="72" width="72"/><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6798371251264429161.post-4615001301968181548</id><published>2009-02-13T09:01:00.003+00:00</published><updated>2009-02-13T09:20:38.486+00:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="bash"/><category scheme="http://www.blogger.com/atom/ns#" term="gotcha"/><title type='text'>Bash Job Management Essentials</title><summary type="text">Did you ever wish your program had a pause button? I did so regularly.

I regularly have to do lengthy calculations, for example for evaluating some heuristics for an optimization problem such as Maximum Independent Set or Matchings.

A typical program could look like this:

for all benchmark graphs G:
  for all algorithm variants A:
    for k in [2, 4, 8, ..., 128]:
      Execute A on G with the</summary><link rel='replies' type='application/atom+xml' href='http://www.bitwiese.de/feeds/4615001301968181548/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/6798371251264429161/4615001301968181548' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/4615001301968181548'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/4615001301968181548'/><link rel='alternate' type='text/html' href='http://www.bitwiese.de/2009/02/bash-job-management-essentials.html' title='Bash Job Management Essentials'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6798371251264429161.post-3396625733080035153</id><published>2008-12-16T18:15:00.008+00:00</published><updated>2008-12-16T18:33:57.097+00:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="distutils"/><category scheme="http://www.blogger.com/atom/ns#" term="pitfall"/><category scheme="http://www.blogger.com/atom/ns#" term="python"/><title type='text'>Pitfall with distutils + OpenGL on Mac Os X</title><summary type="text">This is mainly here as a reminder to myself and anyone else who might fall into this. The scenario is as follows:

I want to compile a C Python extension that uses OpenGL on Mac Os X. My setup.py file looks something like this:
#!/usr/bin/env python2.5

from distutils.core import setup, Extension

module1 = Extension(&#39;foo&#39;,
sources=[&#39;foo.c&#39;],
extra_link_args=[&#39;-framework OpenGL&#39;])

setup(
name=&#39;</summary><link rel='replies' type='application/atom+xml' href='http://www.bitwiese.de/feeds/3396625733080035153/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/6798371251264429161/3396625733080035153' title='7 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/3396625733080035153'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/3396625733080035153'/><link rel='alternate' type='text/html' href='http://www.bitwiese.de/2008/12/pitfall-with-distutils-opengl-on-mac-os.html' title='Pitfall with distutils + OpenGL on Mac Os X'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>7</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6798371251264429161.post-5160690963875043687</id><published>2008-02-13T10:26:00.009+00:00</published><updated>2008-02-13T12:54:24.942+00:00</updated><title type='text'>Gaining speed with Weave</title><summary type="text">Python is slow in terms of execution speed. Period. It is fast enough for most tasks out there, but when it comes to number crunching or manipulation of lots of objects, you can hear the interpreter grind its teeth.

Python advocates have a lot to say on how to handle these situations. The most common is &quot;you can always rewrite that particular part of code in C&quot;. There are other recommendations: </summary><link rel='replies' type='application/atom+xml' href='http://www.bitwiese.de/feeds/5160690963875043687/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/6798371251264429161/5160690963875043687' title='7 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/5160690963875043687'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/5160690963875043687'/><link rel='alternate' type='text/html' href='http://www.bitwiese.de/2008/02/gaining-speed-with-weave.html' title='Gaining speed with Weave'/><author><name>Justin</name><uri>http://www.blogger.com/profile/04972102120598633110</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>7</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6798371251264429161.post-2608104458176870787</id><published>2007-09-30T22:09:00.000+01:00</published><updated>2007-09-30T22:35:49.776+01:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="c++"/><category scheme="http://www.blogger.com/atom/ns#" term="OpenMP"/><title type='text'>C++ - Beware What Lurks Beneath The Surface</title><summary type="text">
C++ is a great programming language. It allows you to mix the most important programming paradigms like object orientation as well as generic, functional and structured programming. Another nice aspect is that the compilers are efficient and with some black template magick, you get some of these things for almost free at run time.



However, one of the greatest features of C++ can hurt you: </summary><link rel='replies' type='application/atom+xml' href='http://www.bitwiese.de/feeds/2608104458176870787/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/6798371251264429161/2608104458176870787' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/2608104458176870787'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/2608104458176870787'/><link rel='alternate' type='text/html' href='http://www.bitwiese.de/2007/09/c-beware-what-lurks-beneath-surface.html' title='C++ - Beware What Lurks Beneath The Surface'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6798371251264429161.post-3305309862993415514</id><published>2007-09-26T15:46:00.000+01:00</published><updated>2007-09-27T08:24:52.015+01:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="parallelism"/><category scheme="http://www.blogger.com/atom/ns#" term="programming"/><category scheme="http://www.blogger.com/atom/ns#" term="threads"/><title type='text'>Ruby&#39;s Multithreading: On Processes And Threads</title><summary type="text">Note that I made a grave error of thinking before writing this article: I forgot the copy-on-write page sharing of modern Unices. I added two paragraphs to this article that should clarify the point. Thanks for your comment, Alex.

Please note that I do not want to critizize Jason here. I am simply picking up this point from his presentation as a motivation of a topic that I wanted to write about</summary><link rel='replies' type='application/atom+xml' href='http://www.bitwiese.de/feeds/3305309862993415514/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/6798371251264429161/3305309862993415514' title='13 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/3305309862993415514'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/3305309862993415514'/><link rel='alternate' type='text/html' href='http://www.bitwiese.de/2007/09/on-processes-and-threads.html' title='Ruby&#39;s Multithreading: On Processes And Threads'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>13</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6798371251264429161.post-3382377832596364886</id><published>2007-08-07T22:08:00.003+01:00</published><updated>2011-11-21T12:53:10.271+00:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="algorithmics"/><category scheme="http://www.blogger.com/atom/ns#" term="OpenMP"/><category scheme="http://www.blogger.com/atom/ns#" term="programming"/><category scheme="http://www.blogger.com/atom/ns#" term="system architecture"/><title type='text'>Hitting The Memory Wall</title><summary type="text">Acknowledgement (2011-11-21): You should search Google for your blog titles before hitting &quot;publish&quot;. When I wrote this article some years back, &quot;hitting the memory wall&quot; was just a term I had read some time earlier and internalized for myself as a standing term, like folklore. This was wrong. There is a paper from 1995 by WA Wulf and SA McKee with the same title: Hitting the memory wall that I </summary><link rel='replies' type='application/atom+xml' href='http://www.bitwiese.de/feeds/3382377832596364886/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/6798371251264429161/3382377832596364886' title='9 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/3382377832596364886'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/3382377832596364886'/><link rel='alternate' type='text/html' href='http://www.bitwiese.de/2007/08/hitting-memory-wall.html' title='Hitting The Memory Wall'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>9</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6798371251264429161.post-1542378030178280978</id><published>2007-06-03T23:01:00.000+01:00</published><updated>2007-09-26T15:41:19.338+01:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="algorithmics"/><category scheme="http://www.blogger.com/atom/ns#" term="merging"/><category scheme="http://www.blogger.com/atom/ns#" term="optimization"/><title type='text'>Highly Efficient 4 Way Merging</title><summary type="text">Acknowledgements: This article is based on the work of Peter Sanders and Roman Dementiev. You can find the full source code presented here in their STXXL library (STL library for large data structures), Peter Sanders&#39; paper and the accompanying source code.

Warning: If you are of sensitive nature either regarding


  computer science theory
  highly practical program optimization


then I </summary><link rel='replies' type='application/atom+xml' href='http://www.bitwiese.de/feeds/1542378030178280978/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/6798371251264429161/1542378030178280978' title='11 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/1542378030178280978'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/1542378030178280978'/><link rel='alternate' type='text/html' href='http://www.bitwiese.de/2007/06/highly-efficient-4-way-merging.html' title='Highly Efficient 4 Way Merging'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>11</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6798371251264429161.post-3536150194950877024</id><published>2007-05-17T15:46:00.000+01:00</published><updated>2007-05-25T12:08:02.387+01:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="machine learning"/><category scheme="http://www.blogger.com/atom/ns#" term="probability theory"/><category scheme="http://www.blogger.com/atom/ns#" term="python"/><title type='text'>Simulation of Markov Decision Processes with enhanced generators in Python (with blood)</title><summary type="text">The language war will always go on and I consider myself as someone who has to promote the Python programming language no matter what happens (even though I know that there is no silver bullet.) Thus, I do have to use every opportunity to show the world how easy it is to connect formalisms of high scientific importance with not-so-important-but-still-cool language features.

Whatever.

Markov </summary><link rel='replies' type='application/atom+xml' href='http://www.bitwiese.de/feeds/3536150194950877024/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/6798371251264429161/3536150194950877024' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/3536150194950877024'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/3536150194950877024'/><link rel='alternate' type='text/html' href='http://www.bitwiese.de/2007/05/simulation-of-markov-decision-processes.html' title='Simulation of Markov Decision Processes with enhanced generators in Python (with blood)'/><author><name>Justin</name><uri>http://www.blogger.com/profile/04972102120598633110</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6798371251264429161.post-9000369498453122376</id><published>2007-04-19T22:24:00.000+01:00</published><updated>2007-04-19T22:51:57.113+01:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="rails"/><category scheme="http://www.blogger.com/atom/ns#" term="textmate"/><title type='text'>Ignoring folders with TODO Bundle in TextMate</title><summary type="text">TextMate&#39;s TODO bundle lets you keep track of the TODOs in your projects. You can mark a line to show up in the TODO list with FIXME, TODO or CHANGED. The following two images show a text file with these keywords and the resulting TODO list.





The only problem is that if you keep a copy of Rails in vendor/, then the TODO plugin will also show the items in Rails (or any other external libraries</summary><link rel='replies' type='application/atom+xml' href='http://www.bitwiese.de/feeds/9000369498453122376/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/6798371251264429161/9000369498453122376' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/9000369498453122376'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/9000369498453122376'/><link rel='alternate' type='text/html' href='http://www.bitwiese.de/2007/04/ignoring-folders-with-todo-bundle-in.html' title='Ignoring folders with TODO Bundle in TextMate'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6TJt8f3K1zaNeFn_1GkBf80X9RsCMUYOlH4fuoSibkeed5EQKMNpx_au9zpYDhAy_tNApFFm_vwd_Me7kXQ7bPgIXhPYgc8URoBcLOCmuXN-Rum3LHsqhSSpP1BLKbTR7LOm4SRzNmso/s72-c/TodoFile.png" height="72" width="72"/><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6798371251264429161.post-1772175143221037390</id><published>2007-04-11T18:53:00.000+01:00</published><updated>2007-04-11T19:30:10.075+01:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="arithmetics"/><category scheme="http://www.blogger.com/atom/ns#" term="floating point"/><category scheme="http://www.blogger.com/atom/ns#" term="gotcha"/><title type='text'>The Joys Of Floating Point Numbers</title><summary type="text">Sometimes, floating point numbers are the thing that futile hours of programming are made of. Whether they come as 32, 64 or any other precision you want, they can truly give you unnecessary and unexpected work if you do not use them correctly. 

The problem I stumbled over yesterday was the problem of rounding errors.

Consider the following C snippet

double pi = </summary><link rel='replies' type='application/atom+xml' href='http://www.bitwiese.de/feeds/1772175143221037390/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/6798371251264429161/1772175143221037390' title='6 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/1772175143221037390'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/1772175143221037390'/><link rel='alternate' type='text/html' href='http://www.bitwiese.de/2007/04/joys-of-floating-point-numbers.html' title='The Joys Of Floating Point Numbers'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>6</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6798371251264429161.post-8768744272022577089</id><published>2007-04-07T15:34:00.000+01:00</published><updated>2007-04-11T18:55:13.027+01:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="databases"/><category scheme="http://www.blogger.com/atom/ns#" term="gotcha"/><category scheme="http://www.blogger.com/atom/ns#" term="postgresql"/><category scheme="http://www.blogger.com/atom/ns#" term="sqlite"/><title type='text'>SQLite gotcha</title><summary type="text">SQLite is great. No, really, I do mean it. If you ever need to work on structured data and editing it from the outside is a must, then SQLite is worth checking out and might be a superior choice to XML and will be a superior choice to your own proprietary format.

I cannot speak about performance - there are some outdated claims that SQLite is faster than postgres and mysql for the most common </summary><link rel='replies' type='application/atom+xml' href='http://www.bitwiese.de/feeds/8768744272022577089/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/6798371251264429161/8768744272022577089' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/8768744272022577089'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/8768744272022577089'/><link rel='alternate' type='text/html' href='http://www.bitwiese.de/2007/04/sqlite-trapdoor.html' title='SQLite gotcha'/><author><name>Justin</name><uri>http://www.blogger.com/profile/04972102120598633110</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6798371251264429161.post-56703279495771049</id><published>2007-04-06T20:38:00.000+01:00</published><updated>2007-04-06T20:47:20.506+01:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="bitwiese"/><title type='text'>First Post</title><summary type="text">Obviously, this is the first entry of the shining new Bitwiese Weblog. Feel warmly welcomed by these few bytes which propably travelled kilometre over kilometre from here to Blogger&#39;s servers and back again to you.

This weblog is brought to you by Justin and me, Manuel. We hope to publish information related to the following
programmingcomputers in the widest sensecomputer science (prepare for </summary><link rel='replies' type='application/atom+xml' href='http://www.bitwiese.de/feeds/56703279495771049/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/6798371251264429161/56703279495771049' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/56703279495771049'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6798371251264429161/posts/default/56703279495771049'/><link rel='alternate' type='text/html' href='http://www.bitwiese.de/2007/04/first-post.html' title='First Post'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry></feed>