The 30 Day "No IDE" Challenge
-
If you've ever watched this show[^], you've probably seen people depriving themselves from the most common things that they take for granted. Now, aside from your day job, what would happen if you forced yourself to use only command-line build tools (such as NAnt, NUnit, and MSbuild) for your personal projects at home? At the end of thirty days, how would that change the way you write code? Here are the rules: -You cannot use any IDE to build your personal code (that means no VS2008, SharpDevelop, MonoDevelop, or any other IDE out there). "Personal code" is any code that you write as a hobby. * -You *can* use graphical text editors with syntax highlighting, but they CANNOT have any form of Intellisense or code completion. -You must use either NAnt or MSBuild, or the command line compiler for your favorite language to build your projects. *You can, of course, use any tool you wish if it is a work-related task. Everyone here has to make a living, somehow. :) Right now, this idea is just on the drawing board, but I figured that I'd post the basic rules for the challenge to the CP community and see if I can get it refined before I take the challenge myself. Depending on the feedback, I'll either blog about it or put up a series of articles on CP regarding "Kicking the IDE Habit". So what do you guys think? Do the rules seem fair enough? Anyone else want to take the challenge with me?
Do you know...LinFu?
-
If you've ever watched this show[^], you've probably seen people depriving themselves from the most common things that they take for granted. Now, aside from your day job, what would happen if you forced yourself to use only command-line build tools (such as NAnt, NUnit, and MSbuild) for your personal projects at home? At the end of thirty days, how would that change the way you write code? Here are the rules: -You cannot use any IDE to build your personal code (that means no VS2008, SharpDevelop, MonoDevelop, or any other IDE out there). "Personal code" is any code that you write as a hobby. * -You *can* use graphical text editors with syntax highlighting, but they CANNOT have any form of Intellisense or code completion. -You must use either NAnt or MSBuild, or the command line compiler for your favorite language to build your projects. *You can, of course, use any tool you wish if it is a work-related task. Everyone here has to make a living, somehow. :) Right now, this idea is just on the drawing board, but I figured that I'd post the basic rules for the challenge to the CP community and see if I can get it refined before I take the challenge myself. Depending on the feedback, I'll either blog about it or put up a series of articles on CP regarding "Kicking the IDE Habit". So what do you guys think? Do the rules seem fair enough? Anyone else want to take the challenge with me?
Do you know...LinFu?
-
If it's pain you want, there are far easier ways to achieve it. Stabbing yourself is a good start.
dighn wrote:
If it's pain you want, there are far easier ways to achieve it. Stabbing yourself is a good start.
Like I said, it wouldn't be challenge if it was easy. :)
Do you know...LinFu?
-
If you've ever watched this show[^], you've probably seen people depriving themselves from the most common things that they take for granted. Now, aside from your day job, what would happen if you forced yourself to use only command-line build tools (such as NAnt, NUnit, and MSbuild) for your personal projects at home? At the end of thirty days, how would that change the way you write code? Here are the rules: -You cannot use any IDE to build your personal code (that means no VS2008, SharpDevelop, MonoDevelop, or any other IDE out there). "Personal code" is any code that you write as a hobby. * -You *can* use graphical text editors with syntax highlighting, but they CANNOT have any form of Intellisense or code completion. -You must use either NAnt or MSBuild, or the command line compiler for your favorite language to build your projects. *You can, of course, use any tool you wish if it is a work-related task. Everyone here has to make a living, somehow. :) Right now, this idea is just on the drawing board, but I figured that I'd post the basic rules for the challenge to the CP community and see if I can get it refined before I take the challenge myself. Depending on the feedback, I'll either blog about it or put up a series of articles on CP regarding "Kicking the IDE Habit". So what do you guys think? Do the rules seem fair enough? Anyone else want to take the challenge with me?
Do you know...LinFu?
as I have explained to the command line kid, I am fully capable going without advanced tools. On the other hand I have written editors rapid design and code completion systems even compilers. I think I have earned the right to use the latest tools to make my life easier. :) go for it, but I will pass.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
-
If you've ever watched this show[^], you've probably seen people depriving themselves from the most common things that they take for granted. Now, aside from your day job, what would happen if you forced yourself to use only command-line build tools (such as NAnt, NUnit, and MSbuild) for your personal projects at home? At the end of thirty days, how would that change the way you write code? Here are the rules: -You cannot use any IDE to build your personal code (that means no VS2008, SharpDevelop, MonoDevelop, or any other IDE out there). "Personal code" is any code that you write as a hobby. * -You *can* use graphical text editors with syntax highlighting, but they CANNOT have any form of Intellisense or code completion. -You must use either NAnt or MSBuild, or the command line compiler for your favorite language to build your projects. *You can, of course, use any tool you wish if it is a work-related task. Everyone here has to make a living, somehow. :) Right now, this idea is just on the drawing board, but I figured that I'd post the basic rules for the challenge to the CP community and see if I can get it refined before I take the challenge myself. Depending on the feedback, I'll either blog about it or put up a series of articles on CP regarding "Kicking the IDE Habit". So what do you guys think? Do the rules seem fair enough? Anyone else want to take the challenge with me?
Do you know...LinFu?
Well I would just use VBScript for the month :laugh:. Or maybe VRML, I've been doing a bit of that recently. That doesn't need compilers and sure as hell doesn't have any Intellisense when using Notepad++. That's a thing, is code colouring allowed?
Ninja (the Nerd)
Confused? You will be... -
dighn wrote:
If it's pain you want, there are far easier ways to achieve it. Stabbing yourself is a good start.
Like I said, it wouldn't be challenge if it was easy. :)
Do you know...LinFu?
That point is there in useless unpleasant pointless challenges?
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
-
If you've ever watched this show[^], you've probably seen people depriving themselves from the most common things that they take for granted. Now, aside from your day job, what would happen if you forced yourself to use only command-line build tools (such as NAnt, NUnit, and MSbuild) for your personal projects at home? At the end of thirty days, how would that change the way you write code? Here are the rules: -You cannot use any IDE to build your personal code (that means no VS2008, SharpDevelop, MonoDevelop, or any other IDE out there). "Personal code" is any code that you write as a hobby. * -You *can* use graphical text editors with syntax highlighting, but they CANNOT have any form of Intellisense or code completion. -You must use either NAnt or MSBuild, or the command line compiler for your favorite language to build your projects. *You can, of course, use any tool you wish if it is a work-related task. Everyone here has to make a living, somehow. :) Right now, this idea is just on the drawing board, but I figured that I'd post the basic rules for the challenge to the CP community and see if I can get it refined before I take the challenge myself. Depending on the feedback, I'll either blog about it or put up a series of articles on CP regarding "Kicking the IDE Habit". So what do you guys think? Do the rules seem fair enough? Anyone else want to take the challenge with me?
Do you know...LinFu?
If I had a decent text editor I wouldn't mind manually typing all of my code. I don't really rely on wizards. The only thing I really get from an IDE besides the incredible features of the modern debugger is the use of intellisense as a spelling tool. Depending on which .NET library you use or which third-party tool you use it is impossible to tell just which naming convention is in use. I can guarantee one thing however, if we all developed with a text editor instead of an IDE that crap called properties would have never been introduced.
Need software developed? Offering C# development all over the United States, ERL GLOBAL, Inc is the only call you will have to make.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway
Most of this sig is for Google, not ego. -
Well I would just use VBScript for the month :laugh:. Or maybe VRML, I've been doing a bit of that recently. That doesn't need compilers and sure as hell doesn't have any Intellisense when using Notepad++. That's a thing, is code colouring allowed?
Ninja (the Nerd)
Confused? You will be...Ninja-the-Nerd wrote:
Well I would just use VBScript for the month Laugh. Or maybe VRML, I've been doing a bit of that recently. That doesn't need compilers and sure as hell doesn't have any Intellisense when using Notepad++. That's a thing, is code colouring allowed?
Yep. You can use an editor with syntax highlighting features, but you cannot use it to build your projects or generate the project source files for you. The whole point of this exercise is to learn what the IDE does for you (in detail) so that you'll be able to do it on your own without relying on an IDE at all. Then again, I suppose if I sat around and did nothing with my projects for a month, I'd win the challenge 'by default', but then again, that's not too fun, now is it? :)
Do you know...LinFu?
-
If I had a decent text editor I wouldn't mind manually typing all of my code. I don't really rely on wizards. The only thing I really get from an IDE besides the incredible features of the modern debugger is the use of intellisense as a spelling tool. Depending on which .NET library you use or which third-party tool you use it is impossible to tell just which naming convention is in use. I can guarantee one thing however, if we all developed with a text editor instead of an IDE that crap called properties would have never been introduced.
Need software developed? Offering C# development all over the United States, ERL GLOBAL, Inc is the only call you will have to make.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway
Most of this sig is for Google, not ego.Ennis Ray Lynch, Jr. wrote:
If I had a decent text editor I wouldn't mind manually typing all of my code. I don't really rely on wizards. The only thing I really get from an IDE besides the incredible features of the modern debugger is the use of intellisense as a spelling tool. Depending on which .NET library you use or which third-party tool you use it is impossible to tell just which naming convention is in use. I can guarantee one thing however, if we all developed with a text editor instead of an IDE that crap called properties would have never been introduced.
I suspect that a lot of more experienced devs like yourself wouldn't even call it a challenge, but there's a whole new generation of people (like myself) who haven't quite left the comfortable bounds of the VS200x IDE. Okay, I admit it. I'm VS2008 addict, and I'm looking to break this addiction. Mono on Linux looks tempting right now, but it's too easy to fall back to VS2008 because of all it's features. There has to be a better alternative than just to jump to another IDE and start the addiction cycle all over again...
Do you know...LinFu?
-
Ennis Ray Lynch, Jr. wrote:
If I had a decent text editor I wouldn't mind manually typing all of my code. I don't really rely on wizards. The only thing I really get from an IDE besides the incredible features of the modern debugger is the use of intellisense as a spelling tool. Depending on which .NET library you use or which third-party tool you use it is impossible to tell just which naming convention is in use. I can guarantee one thing however, if we all developed with a text editor instead of an IDE that crap called properties would have never been introduced.
I suspect that a lot of more experienced devs like yourself wouldn't even call it a challenge, but there's a whole new generation of people (like myself) who haven't quite left the comfortable bounds of the VS200x IDE. Okay, I admit it. I'm VS2008 addict, and I'm looking to break this addiction. Mono on Linux looks tempting right now, but it's too easy to fall back to VS2008 because of all it's features. There has to be a better alternative than just to jump to another IDE and start the addiction cycle all over again...
Do you know...LinFu?
Most of my CS classes required text only. While the C++ we could use the MS IDE as the University has a license for all students for Visual Studio all of the work was on Linux so we still had to use gcc and javac for most of it typing code in vi. Then the prof's would through a curve and just pick random languages, comparative languages was a real PITA. What you will find when leaving the IDE you will quickly learn a lot more of the API by memory. Combine that with faster typing skills and you will really pound some code out. However, I would suggest Java for breaking the IDE habit and not C#. The I have found Java documentation to be so much better. You will need a lot of documentation right at your fingertips.
Need software developed? Offering C# development all over the United States, ERL GLOBAL, Inc is the only call you will have to make.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway
Most of this sig is for Google, not ego. -
If you've ever watched this show[^], you've probably seen people depriving themselves from the most common things that they take for granted. Now, aside from your day job, what would happen if you forced yourself to use only command-line build tools (such as NAnt, NUnit, and MSbuild) for your personal projects at home? At the end of thirty days, how would that change the way you write code? Here are the rules: -You cannot use any IDE to build your personal code (that means no VS2008, SharpDevelop, MonoDevelop, or any other IDE out there). "Personal code" is any code that you write as a hobby. * -You *can* use graphical text editors with syntax highlighting, but they CANNOT have any form of Intellisense or code completion. -You must use either NAnt or MSBuild, or the command line compiler for your favorite language to build your projects. *You can, of course, use any tool you wish if it is a work-related task. Everyone here has to make a living, somehow. :) Right now, this idea is just on the drawing board, but I figured that I'd post the basic rules for the challenge to the CP community and see if I can get it refined before I take the challenge myself. Depending on the feedback, I'll either blog about it or put up a series of articles on CP regarding "Kicking the IDE Habit". So what do you guys think? Do the rules seem fair enough? Anyone else want to take the challenge with me?
Do you know...LinFu?
-
If you've ever watched this show[^], you've probably seen people depriving themselves from the most common things that they take for granted. Now, aside from your day job, what would happen if you forced yourself to use only command-line build tools (such as NAnt, NUnit, and MSbuild) for your personal projects at home? At the end of thirty days, how would that change the way you write code? Here are the rules: -You cannot use any IDE to build your personal code (that means no VS2008, SharpDevelop, MonoDevelop, or any other IDE out there). "Personal code" is any code that you write as a hobby. * -You *can* use graphical text editors with syntax highlighting, but they CANNOT have any form of Intellisense or code completion. -You must use either NAnt or MSBuild, or the command line compiler for your favorite language to build your projects. *You can, of course, use any tool you wish if it is a work-related task. Everyone here has to make a living, somehow. :) Right now, this idea is just on the drawing board, but I figured that I'd post the basic rules for the challenge to the CP community and see if I can get it refined before I take the challenge myself. Depending on the feedback, I'll either blog about it or put up a series of articles on CP regarding "Kicking the IDE Habit". So what do you guys think? Do the rules seem fair enough? Anyone else want to take the challenge with me?
Do you know...LinFu?
I actually don't use any IDE on my job. vim + windbg + SourceInsight + command-line build system + command-line based SCM system.
-
If you've ever watched this show[^], you've probably seen people depriving themselves from the most common things that they take for granted. Now, aside from your day job, what would happen if you forced yourself to use only command-line build tools (such as NAnt, NUnit, and MSbuild) for your personal projects at home? At the end of thirty days, how would that change the way you write code? Here are the rules: -You cannot use any IDE to build your personal code (that means no VS2008, SharpDevelop, MonoDevelop, or any other IDE out there). "Personal code" is any code that you write as a hobby. * -You *can* use graphical text editors with syntax highlighting, but they CANNOT have any form of Intellisense or code completion. -You must use either NAnt or MSBuild, or the command line compiler for your favorite language to build your projects. *You can, of course, use any tool you wish if it is a work-related task. Everyone here has to make a living, somehow. :) Right now, this idea is just on the drawing board, but I figured that I'd post the basic rules for the challenge to the CP community and see if I can get it refined before I take the challenge myself. Depending on the feedback, I'll either blog about it or put up a series of articles on CP regarding "Kicking the IDE Habit". So what do you guys think? Do the rules seem fair enough? Anyone else want to take the challenge with me?
Do you know...LinFu?
I don't use a full featured IDE anymore.
Sovereign ingredient for a happy marriage: Pay cash or do without. Interest charges not only eat up a household budget; awareness of debt eats up domestic felicity. --Lazarus Long
-
That point is there in useless unpleasant pointless challenges?
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
Super Lloyd wrote:
That point is there in useless unpleasant pointless challenges?
It's not as useless as you think--there's a lot to be learned by stripping away some of the things that the IDE does for you, and learning how to do it yourself.
Do you know...LinFu?
-
Super Lloyd wrote:
That point is there in useless unpleasant pointless challenges?
It's not as useless as you think--there's a lot to be learned by stripping away some of the things that the IDE does for you, and learning how to do it yourself.
Do you know...LinFu?
I started with Notepad long ago. I worked with Notepad for a long time. Well not notepad, JFE[^] actually. One day I tried VS, never look back! (also #develop) Why walk when you can fly? You don't want to work without the IDE, nothing to learn here. But maybe you can try to learn how to compile with the command line tool. That would be a more worthy / teaching challenge....
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
-
I started with Notepad long ago. I worked with Notepad for a long time. Well not notepad, JFE[^] actually. One day I tried VS, never look back! (also #develop) Why walk when you can fly? You don't want to work without the IDE, nothing to learn here. But maybe you can try to learn how to compile with the command line tool. That would be a more worthy / teaching challenge....
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
Super Lloyd wrote:
I started with Notepad long ago. I worked with Notepad for a long time. Well not notepad, JFE[^] actually. One day I tried VS, never look back! (also #develop) Why walk when you can fly?
You've got a point there--the problem is that I don't have the luxury of using VS2008 in a non-windows environment, and I need to learn how to do without the IDE and learn how to build apps with the command line tool (which is probably going to be nant, in this case). I realize that there are platform-independent IDEs as well, but I want the build process to be consistent despite whatever platform I use.
Do you know...LinFu?
-
If you've ever watched this show[^], you've probably seen people depriving themselves from the most common things that they take for granted. Now, aside from your day job, what would happen if you forced yourself to use only command-line build tools (such as NAnt, NUnit, and MSbuild) for your personal projects at home? At the end of thirty days, how would that change the way you write code? Here are the rules: -You cannot use any IDE to build your personal code (that means no VS2008, SharpDevelop, MonoDevelop, or any other IDE out there). "Personal code" is any code that you write as a hobby. * -You *can* use graphical text editors with syntax highlighting, but they CANNOT have any form of Intellisense or code completion. -You must use either NAnt or MSBuild, or the command line compiler for your favorite language to build your projects. *You can, of course, use any tool you wish if it is a work-related task. Everyone here has to make a living, somehow. :) Right now, this idea is just on the drawing board, but I figured that I'd post the basic rules for the challenge to the CP community and see if I can get it refined before I take the challenge myself. Depending on the feedback, I'll either blog about it or put up a series of articles on CP regarding "Kicking the IDE Habit". So what do you guys think? Do the rules seem fair enough? Anyone else want to take the challenge with me?
Do you know...LinFu?
You mean everyone hear doesn't do that already? I was under the impression that the sissies used notepad and the real men... Well the real mean use the command line. I gyet ner ideer whuctch yoo beeein dreekin' but if'n yu dunt myind sheerin' I be mutch abliged! ;P
-
A development environment with templates as part of the language? Nice!
Do you know...LinFu?
-
You mean everyone hear doesn't do that already? I was under the impression that the sissies used notepad and the real men... Well the real mean use the command line. I gyet ner ideer whuctch yoo beeein dreekin' but if'n yu dunt myind sheerin' I be mutch abliged! ;P
code-frog wrote:
You mean everyone hear doesn't do that already? I was under the impression that the sissies used notepad and the real men... Well the real mean use the command line. I gyet ner ideer whuctch yoo beeein dreekin' but if'n yu dunt myind sheerin' I be mutch abliged! ;P
Haha :) Real men code in binary, I suppose. After all, it can't be THAT hard now, can't it? :P I mean it's only just a bunch of 1s and 0s...
Do you know...LinFu?
-
Super Lloyd wrote:
I started with Notepad long ago. I worked with Notepad for a long time. Well not notepad, JFE[^] actually. One day I tried VS, never look back! (also #develop) Why walk when you can fly?
You've got a point there--the problem is that I don't have the luxury of using VS2008 in a non-windows environment, and I need to learn how to do without the IDE and learn how to build apps with the command line tool (which is probably going to be nant, in this case). I realize that there are platform-independent IDEs as well, but I want the build process to be consistent despite whatever platform I use.
Do you know...LinFu?
Philip Laureano wrote:
You've got a point there--the problem is that I don't have the luxury of using VS2008 in a non-windows environment, and I need to learn how to do without the IDE and learn how to build apps with the command line tool (which is probably going to be nant, in this case). I realize that there are platform-independent IDEs as well, but I want the build process to be consistent despite whatever platform I use.
MonoDevelop support MsBuild file. csproj are MsBuild file! Solution: work with VS on Windows and #develop / Mono on other platform and maintain your project with MsBuild, it's all good!
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.