However, I recommend everyone go back to the old-fashioned world of Notepad and the command line once in a while. The ability to navigate code efficiently and use autocomplete features, source control support, an integrated debugging experience, and so on-all these make the use of a professional editor like Visual Studio 2010 invaluable. But more important, the uncooperative editor forces me into a coding mode, where thinking precedes typing a single character.įor any decent-sized project, this approach becomes much less attractive. For one, it helps me memorize commonly used APIs for the more specialized ones, I keep MSDN online open. True, colleagues think I endure a lot of unnecessary pain because of this approach, but I'm a true believer.īut why? For a couple of reasons, really. Any text editor, the good old command-line interpreter, and the C# compiler suffice to get the job done. Personally, I'm a huge fan of coding with the bare minimum tools required. The Power of Notepad and the Command Line
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |