... Home Contact

Krzysztof Koźmic's blog

You're doing it wrong.


Show appreciation: My Amazon.com Wish List

Me@Twitter

    Currently reading

    Article Categories

    Archives

    Post Categories

    MyPersonal

    Syndication:

    Agile

    There are 8 entries for the tag Agile

    All your RAM are belong to us

    I’m finishing work on my master’s thesis. As a part of it, I’m evaluating different Agile PM tools. I just installed ThoughtWorks Mingle on my VM and I was amazed that it was veeeery slow. I opened Task Manager and I saw this: I’m pretty sure it shouldn’t be like that. But at least now I understand why my VM is crawling.   Technorati Tags: Agile PM,Agile,Mingle

    Agile in Poland

    I did a little experiment today. I went to biggest job-offering web site in Poland, and searched by keyword: agile. That's all, I didn't specify city, salary, branch nothing, just the keyword. Here's what I got: The grand total of 11 offerings. 5 of them (underlined in green) abroad, 6 in Poland (blue). Out of those 6 only one is in Krakow - the city where I live. I don't know what to think about it, but it makes me sad.   Technorati Tags: Agile, Job

    Simplifying Rhino.Mocks, Round III: kinds of mocks

    My last two posts regarding Rhino.Mocks, attracted quite a lot of attention. Focusing on solution I proposed for limiting complexity around creation different kinds of mocks, one thing was pointed out by few people as not the best solution. Ayende called it "in your face! API design", that is stating the kind of mock you want to create explicitly, via method parameter. I don't think that doing it via method name is any less explicit, but let's not go there. Instead, let's think for a while - why do we need 4 kinds of mocks anyway? All differences boil down...

    Simplifying Rhino.Mocks

    [UPDATE]: Example code is updated. I realized that Kind.Multi is not needed, since you can infer that from passed parameters (when ctorArgs are present, user obviously wants to create MultiMock). I also changed default Kind to Relaxed, since this is the most common one. Ayende wrote today about his ideas for new version of Rhino.Mocks. I like the new syntax (looks similar to what MoQ offers), but there's one more change I'd like to see. Here's the list of all methods of MockRepository, used to create some kind of mock:   public T CreateMock<T>(params object[] argumentsForConstructor);public object CreateMock(Type type, params...

    Agile Toolkit Podcast

    I love reading blogs. I gain so much knowledge from people far smarter than myself. In my previous job it was taking me about 40 minutes to get there, and another 40 to return home. It's quite a lot I guess, wasting over an hour in public communication. Then to make my commute a little bit more productive (ok, I lie here, it was just boring) I decided to use my old Creative Zen Micro mp3 player, and listen to podcasts. That's how it started, and now I have yet another source of knowledge about technology, and what's great about...

    Dr. Venkat Subramaniam on Agile Practices

    There's a great talk (video and slides) up on InfoQ, by Dr. Venkat Subramaniam on Agile Practices. Be sure to check it out. Great stuff, great speaker, great author. Technorati Tags: Agile, Practices, InfoQ

    Mocking with Moq and Rhino.Mocks

    Last week I've read quite a few new blogposts about Moq mocking framework. I had looked at it once, when it was first released, but I didn't find it interesting back then. Now that version 2.0 was released I decided to give it a go once again. Here's very simple model I created: It's a class with one method that uses helper object to obtain a value and possibly raise an event. Here's the whole code: public interface IHelper { int Param { set; } ...

    The true value of TDD (and good design)

    Today I had to tear apart and refactor one of core pieces of tool I'm working on. Oh, and I had to do it fast. At first, I was like: "Hey, you can't change that, it was supposed to stay the way it is now!". Next I started to refactor, changing one by one, all the pieces I needed to change in order to achieve desired effect. I was refactoring, compiling, testing... and again refactoring, compiling, testing.... And ultimately when all tests were once again green - I knew I was done. I felt confident. Thanks to TDD and...