From my experience, I always kick myself every time I do something like the following:
<TextBlock Text="Bogus Text" />
The reason I kick myself is that I find by closing a tag like this, I’m essentially shooting myself in the foot before I get very far. If I close a tag now, within the same line as I open it, I run the risk of having to break it out, and then do a </TextBlock> later.
Yes, this is just an additional step, but if I have a whole lot of conditions within this, I’ll find myself losing my place very quickly. Instead, I’ll seperate the command – for just in case. It sets up the markup for future additions.
<TextBlock Text="Bogus Text">
Preparing for the future saves you on time later. Oh – reasons I mention this – again, from Victor’s book. He’s having you create, just to test the application to verify that Visual Studios created it without flaws, a simple Text Block with “FOO” as the text. Yes, it’s there just to test the application and verify that its functional. However, if you’re in the habit of always always creating things for the future, you hardly ever have to think about what you’re doing when performing something as simple as the creation of a textblock. Those habits tend to pay off in the long run. If you do things “the lazy way” most of the time, and properly only when the time calls for it, you’re likely to accidentally slip into your lazy mode and have to correct yourself every single time you put the fingers to the keyboard.
Need I mention this “right way now” mindset applies to every other aspect of life?
Leave a Reply