am starting a new seris of tutorials of how to use keywords for different things, i might have forgot something
tell me if you know more things to do with them :), its my first video in my seris
No offense but making tutorials is sort of a responsibility, and unless you have a solid understanding of the design patterns and OOP in general you shouldn’t be making tutorials on programming because you’ll end up teaching bad habits to newbies.
For example, in your video the way you demonstrated abstract classes was bad and you should have used interfaces instead in that example.
Also a subclass is not something that extends an abstract class but a class that inherits another one in general (the super class doesn’t have to be abstract).
Keywords seem to be simple but they can really change the way variables and methods behave and some of them is not so easy to explain (eg. synchronized or final) so if you plan to continue your series I would recommend you to read through some official Java docs. 
first off that tutorial is for abstract not interface, i will do interface tutorial as well, i know all that, you can do so with out having abstract at all it works alot better am just showing what they are used for
I know the video was about abstract and not interfaces but what I was saying is that the way you presented it in your video was wrong.
If you only have abstract methods and no member variables then there is no point in using abstract, use interfaces instead.
Because of that I’m sure that in your interfaces video your watchers will get confused about the differences between abstract classes and interfaces.
Not trying to be nit picky but this is sort of a “why use arrays when you have collections” attitude. They’re not meant to be for the same purpose.
i will explaind in interface video what the differens is between them and why to use interface, , shud i put a text tutorial in decription where to read what it is?
You shouldn’t be telling people what to use and what not to use anyway. Let the viewer decide whats best because there are times when abstraction is better than an interface and vice versa, but if you tell everyone “x” is a bad way to do something, then they won’t do “x” even if its the best way. Simply teach them the facts and let people figure out when to use what, don’t put opinion into your teaching.
good comment =D, this is true
Moved to Misc. for not meeting the requirements of a General Discussion thread… :emo:
thank you
Your tutorials start at abstract classes? Who is the target audience of these tutorials? “A lot of people don’t start learning keywords before they start to code” Well if I had no idea how to code and i was just starting, your tutorial would completely turn me off to coding. First of all, I would have no idea what a method was, a class was (other than your vague description), not even remotely know what inheritance and other OO design was. Literally 99% of what you said would have made no sense, and be completely useless. If this is targeted at beginners this seems like a tremendously silly way to start.
Sit down, think of a target audience. Think like the target audience. Plan ahead what you are going to do. Pick a pace and a level of detail depending on your target audience. Think of an entire gameplan for the series, and work from there.
For example, If you were to go back and watch a NewBoston tutorial it would feel dreadfully slow, thats because he focuses on very new programmers who have little-no prior experience. If you were to read a book with a higher level target audience, it tends to move faster and get much more in detail.
am just uploading what all keywords do ama do alot tutorials on java not java2D, i will start java2D later
I don’t get it… Coding video tutorials. This kind of stuff needs to be written down.
Maybe I’m biased, I am a technical writer, writing for a developer audience.
Just let him be. Your arguments are not going to make a difference.