Hi, My name is Tapio, and I write crappy code.

 

It's been more than a day since a wrote crappy code. Today i didn't. I didn't write a single line of code. I know, I know, it's only an excuse. At 5 PM I almost slipped.  Tomorrow will be a difficult day. How can I avoid slipping?  Maybe I shouldn't write any new code. Just do some simple refactorings. We'll see.

While acknowledging you're a Terrible Programmer may be necessary to becoming a Great Programmer, it's not sufficient.

Thanks to Marc, Ted and Udi. Great posts. Atleast now I know, I'm not alone. 

This has not happened before

 

This can't be happening to me. The system will be in production in two weeks. No panic, no emergency meetings, not even acceptance test defects anymore. We must have forgotten something really important. This has to be a dream. Things like this don't happen in real world. Did we do something differently? Not really. Maybe we paid more attention to testing. It helped a lot but it alone didn't cause this. The most important thing was our team. It's nice to have a bunch of smart people working in the same team. Smart people are not afraid of asking questions. If they have opinions they usually are willing to share them. Good communication gives us a better chance to spot problems in our design and find better solutions. Little by little everybody understands how the system works and how different parts of the system work together.  The system might get a chance to succeed.

Linus Torvalds on Git

Would you like to use this kind of features in your .Net development environment?

 

Anonymous methods and maintainability

Anonymous methods are a cool language feature in C# 2.0. I'm not a big fan of using them but they are certainly useful in many scenarios. After reading some articles (here, here, here and here) I realized that even if you can write very elegant code using them, there is a real danger hiding behind the corner. The code might seem clear and obvious but subtle differences can have a huge effect on behavior. This is not always a problem but in some cases it will be. Somebody else will have to maintain your code. If the new guy is not aware of all those subtleties he will have hard time maintaining your code. A small change could break your code and it might be very difficult to find out why it's broken. Keep those unit tests up to date. Without them you are asking for trouble.  

 

Technorati Tags: .NET