Lately I've been discussing estimation a lot with both colleagues and friends so I guess it is time to go at it again. As I've mentioned several times before; I'm not a believer in estimates. The process of estimating is good in order to understand and break down complex problems but the estimate itself as limited (if any) value in my opinion.
Don't let your constructor create the world around it
I recently listened to a developer podcast about the async/await feature in .Net. And I was terrified when the host asked about using those key words in the constructor.
Posted by cellfish at 05:23 No comments:
I try to live by the motto; starting the debugger is a failure when it comes to code I write. That means that through logging and just reading the code it should be possible to figure out what is going on in my code. However quite often I have to work with code I did not write and then some advanced breakpoint tricks come in handy.
Posted by cellfish at 05:04 1 comment:
Proper collection implementation in .net
Most people I've worked with that needed a collection of some sort have implemented the collection by inheriting from one of the standard collection classes. This is however typically not the right thing to do since you expose more functionality than you really want in many cases.
Why refactoring user stories is a bad idea
There is this old article that I wanted to discuss for a while and now is the time. If you'd rather say technical dept user story instead of refactoring that is ok. The logic applies to both.
Subscribe to: Posts (Atom)