<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss version="2.0">
  <channel>
    <title>it's a ‹body›building blog</title>
    <description>blog about life, web development and everything</description>
    <link>http://www.itsabodybuildingblog.com</link>
    <generator>Optimus</generator>
    <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/itsabodybuildingblog" type="application/rss+xml" /><item>
      <author>author@example.com (Bartek Szopka)</author>
      <title>Fighting comment spam</title>
      <link>http://www.itsabodybuildingblog.com/fighting-comment-spam/</link>
      <description>Some time ago I released this new version of my blog with very simple comment functionality. It didn't take too long for comment-spam bots to find it and flood me with some very useful links... It's quite obvious that you simply can't build any public comment form without any mean of spam prevention. Read the rest of the 'Fighting comment spam' article...</description>
      <pubDate>2009-05-08</pubDate>
      <guid isPermaLink="false">http://www.itsabodybuildingblog.com/fighting-comment-spam/2009-05-08Fighting-comment-spam</guid>
    </item>
    <item>
      <author>author@example.com (Bartek Szopka)</author>
      <title>Waking up</title>
      <link>http://www.itsabodybuildingblog.com/waking-up/</link>
      <description>It has been a while (months to be precise) since my last post here. And I don't have any good excuse for not writing for such a long time... I was (and I am) kinda busy... but being busy also means lots of quite interesting things to blog about. And that's probably the reason I wanted to wake up this blog. But when I saw it after few months break I didn't like the way it looked and the way it worked... So instead of writing to a blog I started to code the new blog... Is there any simpler web application to create? So I unified the forces of Google App Engine and Django and created my own pure and simple blog implementation... Finally I have the level of flexibility I needed in blogging engines. So, ladies and gentlemen, it's a preview of new &lt;body&gt;building blog... I really hope to launch it quite soon but I'm aware of some IE6 issues (should I care less?) and comments area is still under development... And there are so many little things I'd like to add here and there but don't have time for all of them... As it will probably take ages to get everything as perfect as I'd like, I'll just launch it early and improve in time... What do you think? (If no one cares to answer, just make it a rhetorical question ;)</description>
      <pubDate>2009-03-09</pubDate>
      <guid isPermaLink="false">http://www.itsabodybuildingblog.com/waking-up/2009-03-09Waking-up</guid>
    </item>
    <item>
      <author>author@example.com (Bartek Szopka)</author>
      <title>Automatic Visual Testing of Web Applications</title>
      <link>http://www.itsabodybuildingblog.com/automatic-visual-testing-of-web-applications/</link>
      <description>The topic of automatic visual testing returns to me like a boomerang. There are a lot of tools for automatic testing of the back-end (unit tests, integration tests, etc...) in every programming language you can possibly imagine. They even have the whole methodology of Test Driven Development. For testing the front-end we have Selenium or Ruby based Watir, but still all they test is the functionality of the web application or a website, and not the visual look of it. I'd like a tool, that will automagically tell me, if my web application still looks how it was intended to look. I need to know if my CSS refactoring didn't break the whole thing somewhere on a page I don't even look at, when I'm manually clicking. Is it really possible to automate visual testing? And if it is, will it be useful? Read the rest of the 'Automatic Visual Testing of Web Applications' article...</description>
      <pubDate>2008-07-25</pubDate>
      <guid isPermaLink="false">http://www.itsabodybuildingblog.com/automatic-visual-testing-of-web-applications/2008-07-25Automatic-Visual-Testing-of-Web-Applications</guid>
    </item>
    <item>
      <author>author@example.com (Bartek Szopka)</author>
      <title>Modeling Family Relations</title>
      <link>http://www.itsabodybuildingblog.com/modeling-family-relations/</link>
      <description>Humans are really complicated beings. Relations between humans are even more complicated... A while ago I've written an article about my small genealogy project. After quite fast implementation of data gathering tools (thanks to django admin panel) I got a little stuck with trying to visualize family tree. Read the rest of the 'Modeling Family Relations' article...</description>
      <pubDate>2008-06-26</pubDate>
      <guid isPermaLink="false">http://www.itsabodybuildingblog.com/modeling-family-relations/2008-06-26Modeling-Family-Relations</guid>
    </item>
    <item>
      <author>author@example.com (Bartek Szopka)</author>
      <title>my inline-block "O RLY?" moment</title>
      <link>http://www.itsabodybuildingblog.com/my-inline-block-o-rly-moment/</link>
      <description>Last week Chris Coyier blogged about those CSS “Ah-ha!” moments, when you realise how cool and powerful stylesheets are. On the same day I had one of my CSS "O RLY?" moments. This one was all about inline-block value of the display property. Read the rest of the 'my inline-block "O RLY?" moment' article...</description>
      <pubDate>2008-05-26</pubDate>
      <guid isPermaLink="false">http://www.itsabodybuildingblog.com/my-inline-block-o-rly-moment/2008-05-26my-inline-block-"O-RLY?"-moment</guid>
    </item>
    <item>
      <author>author@example.com (Bartek Szopka)</author>
      <title>Genealogy in the Time of Web 2.0</title>
      <link>http://www.itsabodybuildingblog.com/genealogy-in-the-time-of-web-2.0/</link>
      <description>In every family there is such a time when someone starts to looking into family roots. It seems that it's that time for my family, as my father created lots of paper sheets with quite random pack of names and lines joining them. He asked: Bartek, maybe you will write some app to organize this thing, keep it all together? In few months I'll forget who is who on this papers. What could I answer? Yeay! Why not! Seems like fun. But, as once I was told that good programmer is a lazy programmer. So as a lazy programmer I started with googling some genealogy software and on-line family trees :) Read the rest of the 'Genealogy in the Time of Web 2.0' article...</description>
      <pubDate>2008-05-16</pubDate>
      <guid isPermaLink="false">http://www.itsabodybuildingblog.com/genealogy-in-the-time-of-web-2.0/2008-05-16Genealogy-in-the-Time-of-Web-2.0</guid>
    </item>
    <item>
      <author>author@example.com (Bartek Szopka)</author>
      <title>Showing Up</title>
      <link>http://www.itsabodybuildingblog.com/showing-up/</link>
      <description>That was a busy weekend. It all started with a little inscape play with the blog's logo... When it came to the logo I thought it would be nice to get a cool .com domain for this site but of course such names as bodybuilding.com or even bodybuildingblog.com where already registered. After hours of meditations and throwing far away thoughts like bodybuildinggeek.com I finally came to itsabodybuildingblog.com. Then I added some basic layout... and basic layout quickly turned into typography fun and positioning magic. After another hours of sitting inside styles.css, after being called stupid and maniac by my fiancée for few times I was kinda satisfied with what I see on my screen. It's not surprising that whole satisfaction just burned out when I launched IE6... Another hour or two of debugging and fixing and ... Voilà! I guess I'm not ashamed any more to show this babe to the world.</description>
      <pubDate>2008-05-12</pubDate>
      <guid isPermaLink="false">http://www.itsabodybuildingblog.com/showing-up/2008-05-12Showing-Up</guid>
    </item>
    <item>
      <author>author@example.com (Bartek Szopka)</author>
      <title>Semantic Mark-up of Article Page</title>
      <link>http://www.itsabodybuildingblog.com/semantic-mark-up-of-article-page/</link>
      <description>Last time we where discussing semantic mark-up of blog's home page. With all this knowledge we can smoothly move forward and mark up the page with full article contents and visitors' comments. The process will be very similar to one we used for home page, so if you haven't read previous article, please do it as it will be really helpful. If you already been there don't hesitate and read on :) Read the rest of the 'Semantic Mark-up of Article Page' article...</description>
      <pubDate>2008-05-09</pubDate>
      <guid isPermaLink="false">http://www.itsabodybuildingblog.com/semantic-mark-up-of-article-page/2008-05-09Semantic-Mark-up-of-Article-Page</guid>
    </item>
    <item>
      <author>author@example.com (Bartek Szopka)</author>
      <title>Semantic Mark-up of the Home Page</title>
      <link>http://www.itsabodybuildingblog.com/semantic-mark-up-of-the-home-page/</link>
      <description>When you start to build a website and you have a general idea about content it will contain, you very often move on to designing the visual part of it and later this visualisation gets marked up into (X)HTML styled with CSS. It's not a bad way to do it, but in such process in most cases mark-up gets focused much more on the visual part of the design than on semantic meaning of the content. That's why the process of building a website should be split into clear steps. I'm just testing such iteration approach while creating this blog and I'll document every step in further posts. Marking up the home page is the first one to go. Read the rest of the 'Semantic Mark-up of the Home Page' article...</description>
      <pubDate>2008-04-28</pubDate>
      <guid isPermaLink="false">http://www.itsabodybuildingblog.com/semantic-mark-up-of-the-home-page/2008-04-28Semantic-Mark-up-of-the-Home-Page</guid>
    </item>
    <item>
      <author>author@example.com (Bartek Szopka)</author>
      <title>Arriving at jogger.pl</title>
      <link>http://www.itsabodybuildingblog.com/arriving-at-jogger/</link>
      <description>General concept of this blog was growing in my mind since months and when I finally decided to start writing it I found it really hard to find a place in the web that will give me everything I wanted... Read the rest of the 'Arriving at jogger.pl' article...</description>
      <pubDate>2008-04-25</pubDate>
      <guid isPermaLink="false">http://www.itsabodybuildingblog.com/arriving-at-jogger/2008-04-25Arriving-at-jogger.pl</guid>
    </item>
  </channel>
</rss>
