Skip to content


Protected: XML Framework episode 2: The POST data

This post is password protected. To view it please enter your password below:


Posted in Software architecture.


Protected: XML Framework episode 3: The view description format

This post is password protected. To view it please enter your password below:


Posted in Uncategorized.


Protected: XML Framework episode 1: The URL

This post is password protected. To view it please enter your password below:


Posted in Uncategorized.


The efficient team structure in web projects

Sorry, this entry is only available in Polish.

Posted in Development process, Software architecture.


The programming language implementations benchmarks

I’ve found benchmark of languages at http://shootout.alioth.debian.org/. The conclusions were simple: every language is good in what it was designed for and as far as the main costs are generated by programmers, it’s more important to pick easier language than faster. Every scripting language can have C/C++ based extensions speeding up programs where it is relevant, so why bother? Continued…

Posted in Optimization.


(Polish) JavaScript – konwencje kodowania

Sorry, this entry is only available in Polish.

Posted in Development process.


The prototype-based object-oriented paradigm

Sorry, this entry is only available in Polish.

Posted in Development process.


Web design thoughts

I’m certainly not a web designer (or at least I don’t want to be) but I can’t left some of current design patterns without notice, so here is article. I have experienced web user and developer, and I’m spending most of my time on searching better solutions for different types of sites. Back in the 2003-2006 I made several sites which weren’t best, because of lack of good design patterns available in these times. There weren’t JavaScript libraries that makes cross-browser programing easy, or support for CSS 2.1 in IE. That wasn’t long ago. Things started to change  in 2006, I think, when JS libraries became stable. The huge step forward was IE 7 in terms of CSS support. Despite that, almost all things possible now, were also possible since 1998. The difference is in simplicity of implementation. You can, for example, build your site using mash-ups – you just have to get the example code and it’ll simply work. Continued…

Posted in Uncategorized.


The “report mistake on this page” button

I’m using web since 2001 and I’ve never seen good feedback feature on sites. If I’m on page and I actually see bug or mistake I should have option to report it. There should be “report mistake on this page” function in bottom of page. It’s behavior should be as follows:

  1. user clicks button
  2. new overlay (in YUI terms) appears with:
    1. “is it visible right now?” question
    2. if yes then there is no need to other questions; just leave description textarea
    3. if no you can ask questions related to specific behavior of your site and “when this bug is visible?”
  3. user clicks on “submit” or “cancel” button
  4. component should then save whole page (the current state is easy to obtain from browser) and send it to developers with answers from user and user agent information
  5. user should see the confirmation and “thank you” text

Is it really that hard to do? I don’t think so. You can handle every feedback, contact, product questions etc. in this way. Users will thank you for that! Continued…

Posted in usability.


(Polish) Szacowanie kosztów w przedsiemwzięciach programistycznych

Sorry, this entry is only available in Polish.

Posted in Optimization.