8 rules to fix your bugs
Me and Ivar just came up with a new way to attack bugs - we formed a fight club!
You can join us if you follow the rules!
1st RULE: You do not talk about FIGHT CLUB.
2nd RULE: You DO NOT talk about FIGHT CLUB.
3rd RULE: If someone says “stop” or goes limp, taps out the bugfix is over.
4th RULE: Only two guys to a bugfix.
5th RULE: One bugfix at a time.
6th RULE: No shirts, no shoes.
7th RULE: Bugfixes will go on as long as they have to.
8th RULE: If this is your first night at FIGHT CLUB, you HAVE to fix bugs!
CRUD for Software Development
CRUD (Create-Read-Update-Delete) operations are the basic functions of most data storages. It’s all you need to get your data into any required state. The same concept can be applied to development process as well.
Following combines all aspects of your product development:
- CREATE - Focus on delivering!
- READ - Focus on listening your customers, developers and yourself!
- UPDATE - Focus on transferring your “readings” into products!
- DELETE - Abandon when no-one is listening to you!
You could name this list as DLTA (Deliver, Listen, Transfer, Abandon) but it’s far from being as cool as CRUD!
TOP 5 reasons for Eclipse Certification
Wayne Beaton questioned the importance of certification for eclipse community. I’ve been wondering about this and seems like a great time to bring it up. Here is my humble TOP 5/DOWN 1 for having/not having them.
Code without automated tests is like using bricks without cement
Just today morning in Tallinn a whole wall of a brand-new building just fell down!
Update: The building was not new and it fell because there is a road reconstruction very nearby.
This made me think that automated unit-tests can save at least your soul.
As soon as there is a bit more complex code to be programmed it’s very tempting to get it first working without using the glue or cement to nail down the foundations of the code.
By cement I mean automated tests, of course.
The implementation you write is only a set of bricks. Which can be used to build a wall, of course.
To really keep them together and ensure that they STAY together, you need to write tests.
Phuuh!
Let the Sun Shine and Tests Run!
Organising design-by-contract test code
“Lets say you write component-oriented, loosely coupled, design-by-contract (java) software and you do rigorous unit testing. How do you organise your codebase?”
Leo Simons offers one possibility: Organising design-by-contract test code
