Blogs:JaroslavTulach:Daily Life
From APIDesign
(→Jaroslav Tulach's Daily Life Blog) |
(→Jan Žák and Petr Šmíd are winners of APIFest08) |
||
Line 5: | Line 5: | ||
==== Jan Žák and Petr Šmíd are winners of [[APIFest08]] ==== | ==== Jan Žák and Petr Šmíd are winners of [[APIFest08]] ==== | ||
- | {{:APIFest08: | + | {{:APIFest08:Report}} |
--[[User:JaroslavTulach|JaroslavTulach]] 11:44, 26 October 2008 (UTC) | --[[User:JaroslavTulach|JaroslavTulach]] 11:44, 26 October 2008 (UTC) |
Revision as of 11:45, 26 October 2008
Jaroslav Tulach's Daily Life Blog
Jan Žák and Petr Šmíd are winners of APIFest08
It is time to announce results of APIFest08. Listen to related podcast or download it!Would you win?
The celebration of 10 years of NetBeans releases is in progress and that is why it is also time to celebrate all those who contributed to the NetBeans architecture, and design practices which make NetBeans platform the most stable Java rich client application framework.
The best way to have fun is to play games. The best way to learn is to play as well. The best way to teach is to organize such game. When me and CZJUG lead Jakub Podlešák realized that, we decided to organize similar game as described in Chapter 17 of TheAPIBook. It is a game to teach, learn and have fun while designing architecture and APIs and practising BackwardCompatibility principles in software interfaces.
There were four base rounds (1, 2, 3, 4) in the APIFest08. We started with fourteen participants. However as the competition advanced further and further, only those who were really eager to win managed to finish all four design tasks. Still, six solutions advanced to the final judgment day/week.
The judgment round is in fact the start of the real competition. However it is also much more difficult than the first four rounds. Instead of looking into own solution, one needs to dig into solutions provided by others and seek for left compatibility problems which is different and time consuming. Still I am glad that two participants, Petr Šmíd and Jan Žák did not give up and sent me their hacks showing BackwardCompatibility evolution problems in many solutions.
Problems in Solution 04
Both guys managed to find some problem in solution 04. Actually there were multiple problems as demonstrated by Petr, however the most obvious one was source incompatibility caused by the addition of new method into a subclassable interface as shown by Jan and me (my solutions are just illustrative, I am not one of the competitors). The lesson to take is that if one is seeking for 100% BackwardCompatibility one needs to prevent modifications to classes that can be subclassed.
Problems in Solution 06
The author of solution six did few compatibility mistakes. First of all, as Jan demonstrates, the once public field Convertor.one disappeared in subsequent revision, which is clearly incompatible for clients using it.
I found an interesting source incompatibility caused by adding overloaded version of constructor. If there are two methods with the same name and number of parameters, but different types, one can try to call them with null and the compiler will refuse the compilation:
against-solution06/test/apifest/CurrencyTest.java:18: reference to Convertor is ambiguous, both method Convertor(BigDecimal,java.util.Currency,java.util.Currency) and method Convertor(Convertor.RateProvider,java.util.Currency,java.util.Currency) match Convertor c = new Convertor(null, cur1, cur2);
Obviously the code compiled before the second constructor was introduced. It failed with later version. This is not that big incompatibility in practise, but it is enough to loose in APIFest08.
Petr exploited another functional incompatibility. The text of a thrown exception changed between two releases. As such it is enough to generate the exception and compare the text. A thing to remember? There are different kinds of APIs, text messages being one of them. For purpose of APIFest08 all of them are equal.
Problems in Solution 07
When I checked the state of all solutions after task 3, I found a perfect way to win. The solution 07 is an example of absolute API stability. The author of this solution managed to guess my future requirements and he changed nothing in the original API in first three rounds! Indeed, it is impossible to find an inconsistency in two versions of an API if they are identical. That is why my own goal for task 4 was to force the author of solution 07 to make some changes. I succeeded, the API version 4 is different than the previous versions, however as the solution 07 is based on a variation of request/response pattern, it still seems unbreakable.
And actually nobody managed to question BackwardCompatibility of the solution. But Jan Žák noticed an important problem. To quote his email: Sometimes - like in the Task2 - the author even added nothing to the API and implemented the requested feature directly in the test case. I'm not convinced, that this approach is strictly fair.. When I look at the quest of the second round and see the complex subclassing classing code provided by solution 07...
/** Merge all currency rates of convertor 1 with convertor 2. * Implement this using your API, preferably this method just delegates * into some API method which does the actual work, without requiring * API clients to code anything complex. */ public static Convertor merge( final Convertor one, final Convertor two ) { // quite a complex code with subclassing }
...I have to agree. All other solutions got this correctly. As such I am giving Jan one point for finding a problem in solution 07 - finding that it does not meet the requirements.
Problems in Solution 11
This is the solution designed by Jan Žák and it seemed completely unbreakable for me. However, Petr had other opinion. He realized that when a code like:
private String k1, k2; public Constructor(String k1, String k2) { this.k1 = k1; this.k2 = k2; } public boolean canConvert(String s1, String s2) { if (k1.equals(s1) && k2.equals(s2)) { return true; } if (k2.equals(s1) && k1.equals(s2)) { return true; } return false; }
is modified to be more general:
private List<String> keys = new ArrayList<String>(); public Constructor(String k1, String k2) { keys.add(k1); keys.add(k2); } public boolean canConvert(String s1, String s2) { if (keys.contains(s1) && keys.contains(s2)) { return true; } return false; }
The result is not the same. Petr managed to exploit this with his test. Congratulation, this is very clever!
This shows how carefully we need to evolve APIs of our libraries. Even slight change in Runtime Aspects of APIs can lead to incompatibilities.
Problems in Solution 13
This solution suffered with source as well functional compatibility problems. Jan managed to exploit both, Petr concentrated on the source incompatibility and I on the functional one.
The thing to remember is that as soon as you implement equals, you need to stick with its implementation. Changing it can be exploited either by careful hackers or by everyone who puts the objects into List or other collection classes.
Problems in Solution 14
This is the solution provided by Petr Šmíd. As Petr is one of the last standing hackers, his solution is not easy to break. I managed to exploit change in implementation classes by using obj.getClass().getInterfaces() check. This does not require any additional permissions, everyone can do this, however it is not really fair. If this was the only way to break Petr's solution, I would still consider his work unbreakable.
However Jan Žák created more intrinsic exploit that generates ArrayStoreException, if executed with newer version of the API. The reason for that is that the task4 version wraps all CurrencyRate with own TimeLimitedCurrencyRate objects. As these objects are not used only internally, but also exposed to clients with a getter getCurrencyRates, it is enough to pass in own objects and check that the returned values are of the same type. Excellent work Jan!
The lesson to remember is to Separate APIs for Clients and Providers as advocated in Chapter 8.
Results
All solutions are flawed in one or other way. As such nobody gets ten points for creating an unbreakable solution. The only points awarded are only for exploits:
Petr Šmíd
Petr is one of the winners of APIFest08.
Petr broke solutions 4, 6, 11, 13.
Jan Žák
Jan broke solutions 4, 6, 13, 14 and challenged correctness of solution 7
Celebration
Both Petr and Jan visited in Sun's Prague office on Thursday 30, 2008 and got their copy of TheAPIBook. Jan is the absolute winner of APIFest08 - he broke four solutions, plus correctly challenged another one. However, I'd like to congratulate you all, dear participants. I enjoyed the game and I hope you are not sorry for participating either.
Thanks, Jaroslav Tulach!
<comments/>
--JaroslavTulach 11:44, 26 October 2008 (UTC)
The Most Insightful Review of "Practical API Design"
The longest, most detailed and insightful review I have seen so far has been written by Tim Band for Lambda The Ultimate.
--JaroslavTulach 11:27, 24 October 2008 (UTC)
APIFest08 Judgment Day/Week Starts!
The judgment day is here! Dear APIFest08 participants, during the last rounds, you were concentrated on making your own solution perfect. However since today you will have to stop looking just at your own solution, you will need to start digging in solutions provided by others to find possible evolution mistakes. This is a new task, different to what you have done so far, but I hope you'll make it. Because only if you find mistakes in solutions provided by others you will be allowed to win TheAPIBook.
If your own solution is found backward compatible and it successfully passed the 4th round, you'll be awarded with 10 points. By default you all have those points. However you can be awarded with 1 point by showing compatibility problems in each solution provided by someone else, who advanced to 4th round. Of course, in case somebody finds such problem, the author of the solution looses own 10 points. As I wrote in the last post, I know that at least five solutions have some problems, so do not give up and seek for them! Your points are waiting! Also please note that the fact that I may know about a problem of your solutions does not mean other participants are going to find it. Don't give up and good luck!
First of all you need to setup your working environment:
# create the repository hg clone http://source.apidesign.org/hg/apifest08/ # or update it hg pull; hg update # create directory named by you Joe Hacker would have: mkdir taskx/jhacker
and now your hunt can start. Repeat following tasks as many times you wish. First of all somehow select the solution you want to find problem in. Usually I use a diff:
diff -ru task2/solution03 task3/solution03
Each difference is potential candidate for compatibility problem. It is just necessary to write code against the old API that does something different in the new version. If I notice some potential evolution problem, then I setup the against project and write a test into it to show the error:
# select the solution you want to break, let supposed it is #3: hg copy taskx/jtulach/against-solutionXY/ taskx/jhacker/against-solution03 # now open some of the created files in your favorite editor: netbeans --open taskx/jhacker/against-solution03/project.properties
Now adjust the content of the properties file:
# change definition of apitotest property to solution03: apitotest=solution03 # you can also adjust the taskA and taskB variables to # reflect the days that you want to compete against # for example if there is compatibility problem between # task2 and task3, change them to: taskA=${apifest}/task2 taskB=${apifest}/task3
Now you can open the project in the NetBeans IDE
netbeans --open taskx/jhacker/against-solution03/
or directly edit its jhacker/against-solution03/test/apifest/CurrencyTest.java file. The goal is to make this file compilable against api available in the version taskA. If you execute the project:
ant -f taskx/jhacker/against-solution03/build.xml run
or by pressing F6 in the NetBeans IDE, your test is compiled, executed against taskA and it has to succeed. If it does, the test is executed against taskB library. If it fails, you have demonstrated BackwardCompatibility problem and that is why the build succeeds. Make sure you open the Output Window to see the real resul! There is also the JUnit Result Window and it is not really helpful in the against project, but I do not know how to suppress its appearance. If the test succeeds with taskB library, the sources of your test are compiled once again against taskB library. This can fail, if there are source incompatibilities. Failure means your success, as you have demonstrated an incompatibility! To see result of these steps in action, look at my attack against solution02 (I can show it as it did not advanced into this final task and you cannot be awarded with points by finding problems in it). If you managed to attack one solution, perfect, you can repeat these steps for another one.
The rules for writing compatibility tests are similar to API Fest One - e.g. the less tricks you use the better. Where trick means more or less Java Permission. Do not try to use reflection that could obviously break each solution. Also do not use wildcard imports in source, that can easily break each solution as well. Do not put the code into the API package, that would allow you to use package private methods and would be unfair. Rules are simple: less tricks is better and I am the judge. Enjoy!
After you are done, please generate the diff using hg diff and submit your solutions by Sun, Oct 26, 2008, morning of CET to our mailing list. Possibly you can ZIP your sources and send them to us too. As soon as we process your submissions, I'll write an APIFest08 report and announce winners. Also I will prepare TheAPIBook for the winner.
--JaroslavTulach 06:03, 18 October 2008 (UTC)
APIFest08 Task 4 Necessary to Choose the Best API Designer
It is unbelievable! We are approaching task4 of APIFest08 and we still have eight participants who play with us! Moreover the competition is still not decided, as far as I can tell. Today I spent few hours looking for BackwardCompatibility problems in provided solutions and I still have not managed to break three of them! It is not that surprising as some of the competitors follow advices of TheAPIBook. For example I've seen APIDesignPatterns:ResponseReply being used. Guys, how can I find a quest for you if you know all the good tricks? Anyway this means we have to go on, as I have only two books to give to winners!
That is why let me ask call round4: Please integrate with dates. Keep history of conversions, allow queries in historical data, etc. Please see Task4Test.java with the actual quests.
Locate your solution among existing task4 directory. There shall already be Task4Test.java file along your Task1Test.java, Task2Test.java and Task3Test.java. Enhance your API, show its usage in the Task4Test.java. Remove the conditional if failing statements.
After you are done, please generate a diff. The best way is to use Mercurial:
# create the repository hg clone http://source.apidesign.org/hg/apifest08/ # or update it hg pull; hg update # then do your modifications # ... # do not forget to add newly created files hg add task4/solutionXY # and finally produce a diff hg diff
you can obtain the diff in other ways, potentially you can send us to our mailing list the whole ZIP file, but diffs are preferred.
Please submit your solutions by Thu, Oct 16, 2008, morning of CET. I guess this is the last coding round. On Saturday you will start hacking solutions provided by others!
--JaroslavTulach 22:17, 11 October 2008 (UTC)
Define "Friday Morning"
When I was defining the quest of APIFest08:Task3 I needed to set a deadline. However as the APIFest08 is not competition for millions of bucks, just for TheAPIBook, I did not feel I need to be exact enough and I defined the deadline as Fri, Oct 10, 2008, morning of CET. This is the reaction that I got from one of the participants:
I really like the precision you use in specifying the deadlines! I will choose to interpret "Fri, Oct 10, 2008, morning of CET" as the time when the first ray of the rising sun can be seen from the train I'll be taking to commute to Prague unless the window is too dirty, is that o.k.? :-)
Cute and OK. Of course only under the assumption that you do your best to clean or at least open your window in case it is too dirty and that you are not referring to a window of an underground train.
--JaroslavTulach 07:53, 8 October 2008 (UTC)
APIFest08 task3 is here
The task3 of APIFest08 is here to tease you more, dear participants. Btw. great work on the previous tasks! It is really hard for me to come up with a task that will be unimplementable for you. I guess you all defend BackwardCompatibility of your solutions pretty well.
Let see what will happen during the round3. I have prepared the Task3Test.java for you. Please enhance your API to allow your API users to write online convertor that updates its exchange rates all the time. Please find the details of your quest inside of the Task3Test.java file.
Locate your solution among existing task3 directory. There shall already be Task3Test.java file along your Task1Test.java and Task2Test.java. Enhance your API, show its usage in the Task3Test.java.
After you are done, please generate a diff. The best way is to use Mercurial:
# create the repository hg clone http://source.apidesign.org/hg/apifest08/ # or update it hg pull; hg update # then do your modifications # ... # do not forget to add newly created files hg add task3/solutionXY # and finally produce a diff hg diff
you can obtain the diff in other ways, potentially you can send us to our mailing list the whole ZIP file, but diffs are preferred.
Please submit your solutions by Fri, Oct 10, 2008, morning of CET, so we can process your submission before weekend and think about more sophisticated ways to tease you. Good luck!
--JaroslavTulach 09:27, 7 October 2008 (UTC)
New Code for Food Picture
The spirit of HtmlForFood story lives on! Geertjan did a NetBeans platform training recently and it seems he learned new skills, which include ability to debug and generate code:
--JaroslavTulach 14:58, 6 October 2008 (UTC)
APIFest08 task2 is here
The task2 of APIFest08 is here. We have fourteen solutions that advanced to second round. Some of them did use their chance to get up to speed in APIFest08:Task1.5, some of them did not. The latter ones will be in tougher position, as the second round is just about to start.
You task #2 is to allow one convertor to hold multiple rates of multiple currencies. Also, create an API to allow composition of convertors. Here is the Task2Test.java file with detailed description of the quest. Locate your solution among existing task2 directory, copy the Task2Test.java file along your Task1Test.java. Enhance your API, show its usage in the Task2Test.java.
After you are done, please generate a diff. The best way is to use Mercurial:
# create the repository hg clone http://source.apidesign.org/hg/apifest08/ # or update it hg pull; hg update # copy the task 2 file hg copy currency/test/org/apidesign/apifest08/test/Task2Test.java task2/solutionXY/test/org/apidesign/apifest08/test/Task2Test.java # then do your modifications # ... # and finally produce a diff hg diff
you can obtain the diff in other ways, potentially you can send us to our mailing list the whole ZIP file, but we want to have the right to process diffs first, as that is simpler for us.
Please submit your solutions by Sat, Oct 4, 2008. Good luck, and do not forget to keep BackwardCompatibility!
--JaroslavTulach 11:50, 1 October 2008 (UTC)
APIFest08's task one and half
Thanks you all, dear twelve brave men for participating in APIFest08! I was really glad to see your submissions after the task 1. I really like the variety between your individual solutions.
However, I also have to apologize. I did try, to correctly specify the task 1 goals, however, looking at some of your solutions, I failed. Some of your APIs do not satisfy all the use cases that I had in my mind. That is my fault, I should have expressed myself clearly. Anyway it puts us into bad situation. Now you are not at the same starting position for the real APIFest08 game. That is why I have to, like a starter seeing a problem before 100m run, call off the ready state, and ask you to prepare once more. That is why I am calling round one and half. Please adjust your your solution according to additional tasks, described in Task1Test.java. There is proper description of the behaviour of the factory methods and two more tests. Please implement this in your solutions.
Please do it by Tue, Sep 30, 2008, noon. You do not need to retain any backward compatibility yet, however restrain yourself from doing too big changes to your APIs, they are all good, just satisfy the additional use cases, please.
Please accept my apology, and good luck!
--JaroslavTulach 18:24, 28 September 2008 (UTC)
Ezekiel 25:17
"The path of the righteous man is beset on all sides by the inequities of the selfish and the tyranny of evil men..."
At certain moment, some ideas get "indexed". Such ideas get a single name, single label and it is enough to say just that name and the right rings are going to bell in heads of all listeners. You do not need to repeat the whole joke, it may be enough to say just the name of the main character in it. You may not repeat the whole story, it is enough to say "life is like a box of chocolate, you never know what you gonna get" and it is clear what is the story about. Or, just refer to "Ezekiel 25:17" and you can bet that most of your listeners will know what you are referring to. These sentences became "indexes" for their whole stories.
The trap that every author of a book shall be aware to not fall into is to become a generator of indexes for his own books. This is inevitable, at the end the author spend last few months reading again and again the same book. Reading own sentences over and over, changing words to make them better, more expressive, more sharp and exact. It is natural that for the author to see nothing more real than the book and its content. It is easy to fall in the trap of believing that this is so also for every other human being one meets.
As a result authors sometimes use sentences like "should you read the xyz book, you would know that...". Or refer to their work using "I have described uvw in Chapter 33, please read it". This is explainable, yet very annoying. I've faced that behavior once and I was quite up set and I knew I should restrain from doing the same after publishing TheAPIBook. I knew that, but I could not stop myself from doing that! It was so tempting to refer to chapter 11, Runtime Aspects of APIs instead of explaining that getting ready for reentrant calls is important. It was so easy and tempting, yet it was also quite annoying for people around me. At least that is my guess from seeing their unusual reactions to my speech or email in not so recent weeks.
Please take this as my public apology for using Jarda 15:13 or Jarda 7:3, etc. "indexes". I could always understand how it feels to get such self-reference. Sorry for that and I promise not to use it anymore.
PS: In case of need refer to this text as Jarda 24:9.
<comments/>
--JaroslavTulach 19:43, 24 September 2008 (UTC)
API Fest '08
The APIFest08, a game to practice Practical API Design skills, is just starting. It is a contest primarily designed for members of Czech JUG, but we want to make it as open as possible. Play with us and celebrate 10th anniversary of first public NetBeans release.
--JaroslavTulach 09:31, 23 September 2008 (UTC)
And the Winner of the HtmlForFoodCompetition is ...
The HtmlForFoodCompetition which we run in order to promote TheAPIBook and popularize its major concepts is running towards its end! I have already selected the winner using a complex mathematical operations with a huge contribution of pseudo randomized numbers. Please tune in the next NetBeans Podcast Episode 46 and hear the announcement yourself!
I can only say that the submissions we got were really great:
- Vincent Cantin was looking so desperately sad.
- cismet guys provided wide range of variations on the "code" topic.
- Tonni Epple draw a perfect caricature.
- Andre Pinto pictured himself with a beautiful selection of languages and "code" sentences.
- Full Movie was not really submitted for competition, however it is very nice exploration into everyday developers' pains.
Who will win TheAPIBook by providing the best Html For Food picture?
Listen to second half of this API Design Tips podcast: , the winners are cismet guys! Congratulation! --JaroslavTulach 20:25, 8 September 2008 (UTC)First Public Review of Practical API Design Book
There is a review of TheAPIBook! Geertjan had just sent me a link to the first public review of the TheAPIBook. I was a bit nervous to open the page. I was not sure whether to get ready for absolute criticism or words expressing usefulness of TheAPIBook. I guess that a review which says this is without a doubt a book that you need to put on your bookshelf. This is the first book of its kind and the tips and tricks that it provides is timeless - a key attribute of any pragmatic software development book can only be seen in positive light. Thanks for the nice review, Mike.
Now on to the critical comments. Yes, I know the first part of the book, the theory, maybe seen as something delaying the real pleasure - the practical code samples. In some sense it does, however I just felt that given the wide audience of readers (just to quote the reviewer this book is really much more for anyone who writes code that anyone else consumes - and who doesn’t do that? This book is for any developer who is not brand new to software development), I felt the need to get everyone on the speed, clean up the terminology, make sure we understand each other. Maybe I was too careful, as RichUnger said: you do not need your readers to agree with you 100%, maybe 99% is enough. Well, I targeted for the 100%, and as a result, the book may be seen slow for those who are already on the same boat. Still, it has a lot of meat even for such readers, I guess.
The other interesting comment was about the subtitle: confessions. The comment is very likely true. I have to admit, especially after the confession I made at the end of Chapter 4, that I have never been to a confession. My understanding of that term is really vague. However, we needed the subtitle to stress, that the book is not opinion neutral, that it contains personal experiences, ideas, stories, etc. When Clay suggested to use confessions, I felt, yes, that is sort of what I am actually doing. Maybe this is not absolutely correct, but it helps set the right expectations up. At least I hope.
I really like Mike saying: After reading many chapters, I went right to my open source project, Architecture Rules, and either changed code or emailed developer mailing list to suggest changes to code to encourage a better, more malleable and extensible API. Yes, this is it! This is the reason why I wrote TheAPIBook. Software for 21st century needs to be modular, needs to be well evolved and I am glad that my book can contribute to that.
Thanks for such nice review and I am eagerly waiting to see more. Btw. if you ever feel you have a note to share about API Design, feel free to jump on the apidesign.org wiki.
--JaroslavTulach 19:42, 2 September 2008 (UTC)
Win the Practical API Design Book
As part of Chapter 1, The Art of Building Modern Software I wanted to demonstrate that the need for programmers is really big and that almost everyone who wants to get a job as a programmer may get it. For this I wanted to reuse a picture of a San Francisco homeless that is famous for wearing sign with "Will Code HTML for Food". However I could not do that, because the picture is of really low quality. That is why I needed a new re-take. We already have some, but still, I'd like us to start sharing! As sharing of pictures is sometimes easier than sharing of API Design ideas, please participate in a photo contest! Get a chance to win TheAPIBook by taking "Will Code HTML for Food" like picture and adding a reference to it to HtmlForFood by Aug 28, 2008!
I am looking forward your submissions.
--JaroslavTulach 16:11, 14 August 2008 (UTC)
New LaF of apidesign.org
There was a lot of factors that influenced me last year, when I was searching for publisher of my book. However one of them must have been slickness of cover. I really like the black and yellow style of Apress books. I like it so much that I decided to make it the default Look and Feel of the apidesign.org website.
I'd started with MonoBook theme and modified it to be a bit darker. I do not code CSS for living, but CSS file editing support in NetBeans IDE is good, so it was quite entertaining experience. I am sure not everything is perfect, but I'll keep fixing problems as they appear. If you notice something ugly or broken, let me know.
<comments/>
--JaroslavTulach 10:16, 4 August 2008 (UTC) --JaroslavTulach 10:09, 4 August 2008 (UTC)
There is a Reason Why Every Book is Dedicated to Family
I've heard this sentence at the J1 this year and I cannot get it out of my mind. Yes, family plays a really big role in the life of a writer. So please let me thank to it as well to other friends.
--JaroslavTulach 19:00, 27 July 2008 (UTC)
Good Book Needs Good Reviewers
It is time to thank to all my reviewers as today I've found out that you can order my book on Amazon.com. Please look at my little ThanksReviewers to find out why to order my book. I believe that all reviewers really shape it to something worth reading. Thanks a lot.
--JaroslavTulach 19:44, 18 July 2008 (UTC)
Removing Fear of Writing Documentation
Heuréka! As I've just noted in a dedicated page describing chapter 16, Teamwork one GeertjanWielenga's fear has just been overcome!
--JaroslavTulach 16:05, 17 July 2008 (UTC)
Adventures with PHP and MediaWiki
During the last week, I was slightly playing with various enhancements to the content of the API Design wiki.
--JaroslavTulach 21:14, 6 July 2008 (UTC)
Book is never Written by a Single Person
The Practical API Design book has been sent for print over the last weekend. I take it as a good opportunity to say thanks to all the people who helped me write it. The first set of ThanksEveryone notes is now available and covers those who "manually" contributed. I still need to thank to all those support "units" around me - something left for next blog entry...
--JaroslavTulach 12:01, 23 June 2008 (UTC)
Entering the Blogosphere
I have created my blog, does it mean that I finally exist?
--JaroslavTulach 09:33, 15 June 2008 (UTC)