3 ms·
I find interesting that you took the approach of explaining a console application instead of a form app. More interesting from a technical point of view but may
by duiker101 14y ago
I find interesting that you took the approach of explaining a console application instead of a form app. More interesting from a technical point of view but maybe less interesting for a someone who just wants to hack something together to see what happens. When I started using C I always found hard to follow this tutorial because I like to use what I learnt in my own programs but I really did had no ideas of what console apps to make. Instead with server languages (for example) I found it easier because I could create my website and therefore do something "mine". In the end just following the steps of a tutorial I think it's about 30% of the learning process. Making mistakes is a good 50%. And to make them you must try your own things.
- JeremyMorgan 14y agoas I explained in another question it's mostly so the reader can get really "hands on" and write the code out by hand without code completion and other assistance. It may not be for everyone, but for core language stuff I think it's essential. Later in the series I'll definitely be integrating Visual Studio more
- teh_klev 14y agoI think you've made a good choice with keeping VS out of the picture. Understanding the basics of compiling from the command line is where I start with novices. No point blowing their minds with a gazillion IDE knobs and dials. You could take this further and teach some basic command line debugging :)
- andyjohnson0 14y agoI agree with your choice. This is definitely the best way to learn.
- bbotond 14y agoThe mostly linear execution of a console app is IMHO much easier to understand than the event-based paradigm of most GUI frameworks.