2 ms·
My background: C# pays for my family, my wife is constantly jumping on and off random tutorials to learn some programming (interested in C# because of my dayjob
by darklajid 14y ago
My background: C# pays for my family, my wife is constantly jumping on and off random tutorials to learn some programming (interested in C# because of my dayjob and Python as a nice beginner's language with lots of learning resources).
If I look at this article I feel that the flow is missing. It is well written, has nice screen shots and explains a lot. But it seems to hop around a lot. I don't quite know who you're targeting, but I'm reasonably sure you'd confuse the hell out of my (intelligent, brilliant) wife.
The style is more documentation slash dissection of stuff, less introduction with a purpose. I miss a global "why", you provide more like "This is something we can do, let's walk through it together". Unless you're already a programmer or really into case studies like this, I think this way to present something is less accessible.
Don't want to bash on your work. I think what you did here looks nice. Just sharing why I don't think I'd subscribe or why I cannot recommend the series to my so.
- JeremyMorgan 14y agoI don't take it as bashing, I appreciate honest feedback. If everyone only contacted me telling me how great I am or how bad I am neither would help, so I prefer a good mix. My aim here is for the serious beginner. By that I mean someone starting out who may have tinkered with a language or two but really wants to learn C# in depth. That's why it's so verbose and I try to cover the topics. A hacker who wants to learn the basics should probably go elsewhere. I'm honest enough with myself to have already thought this through, and I may throw in some quick hacky stuff specific for what someone is searching for, but for the most part I want these to be a very thorough introduction to the language.