Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
kescherRant26264293dDon't do tutorials, just try it out and read up on it. Tutorials are often full of wrong info.
Also, why didn't you attend your online classes?
LotsOfCaffeine2659293dDon't really have tutorials but a bit of advice:
Start with the basics before jumping into OOP.
Learn your if, while, for and functions, before messing with inheritance, etc.
Hazarth2798293dThis is a list of steps I created to learn any language
1: print hello world
2: print a number from a variable
3: print a string from a variable
4: concatenate strings from variables with some default text
5: get input from the user as a string
6: get input from the user as a number
7: make an If statement that responds to the users input using some kind of string comparison in one way or another
8: make an infinite echo loop that can be exited by writting "quit"
9: make a finite counting loop with a "for" cycle or similar
10: build a simple text game!
at step 10 you should be comfortable with the syntax enough to start going deeper and making your own projects. The rest is up to google and the language docs. For C# microsoft has excelent documentation (for the most part).
buglesscoder43293dLol I am too CS student and would be starting to prepare for c++ finals that's on 28th by today.
Yggdrasil168293dTo be a CS student includes being a programmer. But maybe it's just me
To learn C# from 0 take dotnetcore and read their documentation. Also if you have a syllabus read it.
Codex40417890293d@Yggdrasil not right of the bat. If you've never had to write a line of code you ain't a programmer. The curriculum of CS differs per Uni and also the order it's been taught. I know unis where they have the first year just doing design (database and architectural) before they start programming in the second year. There is also CS unis where programming is an optional course.
C# in depth hasn't been updated in quite a while. It's missing a fair amount and had some fundamental bits (especially around string processing) that are now factually inaccurate. Only reason I don't put it on the reading list.
Yeah, love the skeets, but the changes in 8+ were watershed in terms of a lot of fundamental assumptions.
Codex40417890293d@sk23ll John skeet indeed does know all about C#, everytime I look up things his answers are always top rated. On stack overflow.
0x5d0121185d@Hazarth Kinda needs further steps right in the list instead of vague notion of "going deeper". If the language is based on some VM, it's imperative to learn its inner workings. If you target a particular compiler, you're better off knowing its pros and cons, some of its bugs even. Being familiar with the majority of standard library is also a minimum you're going to need in a day-to-day practice. Just hacking together some simple stuff just isn't enough to "learn" a language. Sure, you feel comfortable using some basic parts of the tool but you still don't *know* it.
Hazarth2798185d@0x5d0 I agree, but those are rather advanced topics. If say you're a student (like OP), the first thing you want to hear from your prof isn't "this is going to take forever and you need to learn the minute details of compilers to truly understand everything"
I think the better first step is to enjoy using it, and to enjoy using something you have to make it your own... thus learn basics first and understand that you can create stuff with it!
the list isn't comprehensive because that would feel overwhelming, I feel like simple 10 steps that point you into creating something managable as your first first project or two is what can spark a deeper interest in the language, and then you can start looking into it deeper as you need to with your growing goals (not to mention OP is a student, he's going to have his hand held here and there through more difficult topics too)
does that explain my intention or do you still disagree?
0x5d0121185d@Hazarth The point about it not appearing overwhelming for a newbie is valid. Though I'd still hold my ground just a bit by saying that some types of people are more effective when they have the full picture. After all, the journey is sometimes more about the joy of milestones that we hit along the way, right?