AJAX isn't Microsoft's nightmare.
Check up on Atlas, http://weblogs.asp.net/scottgu/archive/2005/06/28/ 416185.aspx, a neat addition to the.NET Framework that I will surely use once it's ready. Another addition to the Framework I will be using is LINQ, but that's another story...
Tightly integrated that is with SQL Server for example. Need to debug a stored procedure? Set a break point in it using VS and step through it, adding watches and such like if you were debugging C# code for example. Now that is the shiztnizz.
Oh how I wish my company would upgrade both VS and SQL Server, guess I'm stuck with VS 2003 for a while. Sigh...;)
A great IDE that I swear by is none other than Visual Studio.NET. Why you ask?
So many great tools that come with it. No, I do not drag and drop to code, I write everything myself. But...
...one tool I love is the debugger. I can actually set a break point inside a STORED PROCEDURE and step through it inside VS.NET. Makes like so much easier when you have complicated/delicate queries to write.
There's no such thing as a good vs average programmer. There's only those who follow the algorythm and the lucky artists.
But you are missing the bigger picture, the framework.
Yes it all comes down to an algorithm of some sort, but usually software is a bunch of algorithms all tied in together, working together now.....and in the future.
You have to think of the future, and how your code will adapt and respond to new algorithms.
The average programmer will patch up his code until he reaches a point where nothing works and he will need to re-write it (time, money and frustrations).
The good programmer will devise a beautiful (fully commented) framework that will allow for future expansion which won't need re-writes or clutter.
Well I for one have been coding professionally in C# for a solid year now and let me tell you I've enjoyed every day of it.
I've also taken on the monumental task of re-creating our company namespace with some of the items from this book (which is great by the way if you overlook some english semantics).
I would recommend this book, as it has helped me fine-tune my game if I can call it like that.
Slashdot Mirror
AJAX isn't Microsoft's nightmare. Check up on Atlas, http://weblogs.asp.net/scottgu/archive/2005/06/28/ 416185.aspx, a neat addition to the .NET Framework that I will surely use once it's ready. Another addition to the Framework I will be using is LINQ, but that's another story...
"Red Book" reminds me of the "Dragon Book". Anyone know what I'm talking about? :)
Tightly integrated that is with SQL Server for example. Need to debug a stored procedure? Set a break point in it using VS and step through it, adding watches and such like if you were debugging C# code for example. Now that is the shiztnizz.
Oh how I wish my company would upgrade both VS and SQL Server, guess I'm stuck with VS 2003 for a while. Sigh... ;)
A great IDE that I swear by is none other than Visual Studio .NET. Why you ask?
So many great tools that come with it. No, I do not drag and drop to code, I write everything myself. But...
I didn't know that the enter key didn't really work for paragraphing.
I must still be looking for the any key.
There's no such thing as a good vs average programmer. There's only those who follow the algorythm and the lucky artists. But you are missing the bigger picture, the framework. Yes it all comes down to an algorithm of some sort, but usually software is a bunch of algorithms all tied in together, working together now.....and in the future. You have to think of the future, and how your code will adapt and respond to new algorithms. The average programmer will patch up his code until he reaches a point where nothing works and he will need to re-write it (time, money and frustrations). The good programmer will devise a beautiful (fully commented) framework that will allow for future expansion which won't need re-writes or clutter.
Well I for one have been coding professionally in C# for a solid year now and let me tell you I've enjoyed every day of it. I've also taken on the monumental task of re-creating our company namespace with some of the items from this book (which is great by the way if you overlook some english semantics). I would recommend this book, as it has helped me fine-tune my game if I can call it like that.