Be careful where you get your information
The internet is rife with misinformation.
As a developer you tend to depend heavily on searching for examples of how to solve a particular problem such as code snippets, and patterns and practices. There is very little ground breaking work and it is almost certain that someone has been there, done that, and blogged the solution to your problem already.
Problems arise when you choose the wrong source to trust. For example, today I was trying to figure out how to get ASP.NET not to render a name attribute for the form element as we are starting to target XHTML 1.1 compliance for BeforeYouBuy. A quick google came up with this.
Certainly the answer that is proposed is "a solution", but it's certainly not "the solution". A slight modification to my search turned up this how to on the msdn site.
It's really down to knowing where to look.
As a developer you tend to depend heavily on searching for examples of how to solve a particular problem such as code snippets, and patterns and practices. There is very little ground breaking work and it is almost certain that someone has been there, done that, and blogged the solution to your problem already.
Problems arise when you choose the wrong source to trust. For example, today I was trying to figure out how to get ASP.NET not to render a name attribute for the form element as we are starting to target XHTML 1.1 compliance for BeforeYouBuy. A quick google came up with this.
Certainly the answer that is proposed is "a solution", but it's certainly not "the solution". A slight modification to my search turned up this how to on the msdn site.
It's really down to knowing where to look.
posted by James Fitzsimons at 3:00 pm
0 Comments:
Post a Comment
<< Home