In this video Rebecca is speaking why she wants to attend I T.A.K.E. Unconference 2013. Her main reasons are: the conference is focused on code, is not “people waiving their hands and speaking theory”, and open discussions during the open space can create “magical moments”. Enjoy!
Why Rebecca Wirfs-Brock is coming to I T.A.K.E. Unconference Read More »
by Rebecca Wirfs-Brock, republished with permission On agile teams, architects do more than design and implement the interesting tricky bits. They typically balance a wide range of concerns: short-term goals, overall system design integrity, risks versus efforts, design expediency. The successful agile architects I know aren’t ivory tower experts. They take a leadership role
Software Architecture Stewardship Read More »
Rebecca Wirfs-Brock president of Wirfs-Brock Associates and IEEE Software’s Design Columnist, is a well-known and respected object-oriented practitioner. She invented the way of thinking about objects known as Responsibility-Driven Design and is the lead author of Object Design: Roles, Responsibilities, and Collaborations (2003) and the classic Designing Object-Oriented Software (1990). Through her writing, teaching, consulting,
Rebecca Wirfs-Brock — Blending Agile and Lean Practices: Two Quick Stories Read More »
A few months ago we were announcing the launch of a unique technical conference: I T.A.K.E. It’s now time to tell you more about why it’s unique. Speakers are obviously a very important part of a conference. We put a lot of effort into bringing the best development minds from around Europe. They are community
A Technical Conference where Speakers Write Code Read More »
My colleague Nicoleta challenged me to write a blog post about agile that even a non-technical person can understand. I accepted the challenge only to find myself facing a big problem: how can I describe a philosophy that impacts everything about how we work (and even live) in a short post while keeping it easy
Agile for Non-Technical People Read More »
After an initial romance with use cases, the agile community embraced user stories as its de facto standard for documenting requirements. You have probably seen them a lot by now and maybe even wrote a few: As a <user type> I want <action> So that <benefit> To make them more versatile, Mike Cohn introduced two additional
5 tips for better user stories Read More »
Would you like to have better unit testing? We can help with: Attending the “Unit Testing Core Practices” workshop, also available in-company Attending the “Test Driven Development (TDD) ” workshop, also available in-company Attending the “Acceptance Test Driven Development” workshop with Markus Gärtner If the situation is more complex, we would be happy to create a customized package for
How Unit Testing Saved My Holiday (Video) Read More »
In my early years as a programmer I was always afraid to touch existing code. Usually that code was written by someone else. It was so hard for me to understand it. I found out after a while that this kind of code is called “spaghetti code”. Now I am having fun making convoluted code
Yes you can: fix a bug on spaghetti code Read More »
At the time of this post, I have taught unit testing for 5+ years, to a few hundreds of developers, both in classroom and in their own environment, on their own code, be it Java, C#, C++, PHP, Python, Javascript, Objective-C or ActionScript. No matter the technology or the environment, the problems they encountered were
5 Common Unit Testing Problems Read More »
A guest post by Markus Gärtner, republished with permission. Michael Bolton beat me on blogging about it. Though, I still want to throw in my pieces to the structure in Exploratory Testing debate. The source of the conversation was On Twitter, Johan Jonasson reported today that he was about to attend a presentation called “Structured
Structured Exploratory Testing – an oxymoron? Read More »
