Been really poor in programming at school. Java and ASP.net 2.0 I know its practice makes perfect but is there any way i can improve it? Cant seem to graps the concepts well.
Try different languages and you'll soon realise how much they have in common and that for the most part syntax mastery will be all that you need in the end, the rest will come naturally.
Learn good database design, because these days most programming is object orientated. And try to solve problems more than once. You can solve a problem with 12 lines of code, or 3.
Understand how to call procedures and write your own, without using any of the inbuilt functions of asp.net and see how you go.
Learn good database design, because these days most programming is object orientated. And try to solve problems more than once. You can solve a problem with 12 lines of code, or 3.
Understand how to call procedures and write your own, without using any of the inbuilt functions of asp.net and see how you go.
Go through online tutorials, use the API (It's your bible), try creating little programs to do everyday tasks.
Assuming this is for java btw.
Assuming this is for java btw.
Focus on learning what you're doing and why you're doing specifically that before you set out to do it. If you don't know what you're doing, and why you're doing it when you write your code, you'll never be a good programmer. It's a bitch, and takes a lot of reading without much practical implementation, but it's the only way to success. There are way too many people teaching programming who fail to build things up from the very bottom, and start off with a "Hello World", which is only good for demonstrating syntax and typing diciplines, and not at all good for teaching fundamentals.
Practice, as boring as coding is that's the only way. You gotta just write lots of code until everything just makes sense to you.
There are hundreds of ways you could make the same OO program but only a handful will actually be any good. You need to learn to understand why doing OO design certain ways is better than others. Normally that revolves around making your program accessible to expansion.
There are hundreds of ways you could make the same OO program but only a handful will actually be any good. You need to learn to understand why doing OO design certain ways is better than others. Normally that revolves around making your program accessible to expansion.
The best I always found was to make some useful. Identify something you would actually like to make, then use tutorials and examples to reach that goal.
i.e. set a goal
Assuming you care about this beyond school
i.e. set a goal
Assuming you care about this beyond school
Last edited by jsnipy (2009-01-19 08:26:15)
Best resource to learn a language from scratch: http://www.w3schools.com/
Also learn how to read specifications from http://www.w3c.org/
Don't be too keen on any particular language. Whenever there's a problem each language/platform/OS will have its advantages and disadvantages. Weigh them and then decide.
Depending on how you learn, like the guy before me said, get down and dirty. Google search some beginner guides and start by making something simple. If you try something too hard you'll get frustrated.
Each time you build something, use what you've learn previously.
Programming, by its very nature, is taking something very complex and making one decision at a time.
Also learn how to read specifications from http://www.w3c.org/
Don't be too keen on any particular language. Whenever there's a problem each language/platform/OS will have its advantages and disadvantages. Weigh them and then decide.
Depending on how you learn, like the guy before me said, get down and dirty. Google search some beginner guides and start by making something simple. If you try something too hard you'll get frustrated.
Each time you build something, use what you've learn previously.
Programming, by its very nature, is taking something very complex and making one decision at a time.
You have to be interested in it... are you?
It's possible to learn something you don't enjoy obviously... but if you are into learning programming... you won't care how long it takes... you'll have a thirst for learning it... hope that made sense...
It's possible to learn something you don't enjoy obviously... but if you are into learning programming... you won't care how long it takes... you'll have a thirst for learning it... hope that made sense...
Love is the answer
Just cheat off someone else.
It really depends on where you're struggling.Ayumiz wrote:
Been really poor in programming at school. Java and ASP.net 2.0 I know its practice makes perfect but is there any way i can improve it? Cant seem to graps the concepts well.
If it's the pure OO concepts, that's a toughy, you have to think in a certain way to be a good programmer, but don't ask me what that 'way' is - I've never been able to put it into words.
But, if it's something like that you keep on forgetting the syntax and grammar of the language, then, as others have said, practice is the only way to learn - the more code you write the more you get to know the syntax and grammar.
Maybe give some examples of things you're finding difficult, and we'll talk you through them (though, CrazeD's recent thread seems to suggest there aren't many (if any) really good Java coders on the forum, so if it's a question about say why a specific chunk of code isn't working, we might not be able to help much, but I think there are enough coders here to help you with any OO concepts you're struggling with).
Finally, unless you know it's going to be in an exam, don't get too hung-up on trying to memorise long lists of classes and function names - there's way to many of them for anybody to remember them all and all good programmers keep a language reference book to hand.
Last edited by Scorpion0x17 (2009-01-19 20:49:10)
Shouldnt this be in tech?
Probably.GodFather wrote:
Shouldnt this be in tech?
Might explain why the OP's finding programming difficult, too...
I'll tutor you personally if you can get me a job in Singapore.
Study Object Oriented development. And that doesn't mean learn database design because the principles of OO have nothing to do with that. If you can grasp those concepts, the syntax will fall into place pretty easily.
What always helped me learn a lot was when I had to do something I'd never done before. You learn a lot that way. Don't be afraid to use google either. I can tell you first hand that pretty much every developer I know uses google every single day. I've been doing this for 12 years and I still do.
No disrespect to Aussie, but I disagree with most of what he said. Yeah, you should learn different languages and try to do things different ways, but DB design isn't OO. Syntax mastery isn't half as important as grasping concepts, especially with Intellisense. And the native .NET functions are super-handy to know. It will save you a lot of time and grief if you get familiar with those.
Study Object Oriented development. And that doesn't mean learn database design because the principles of OO have nothing to do with that. If you can grasp those concepts, the syntax will fall into place pretty easily.
What always helped me learn a lot was when I had to do something I'd never done before. You learn a lot that way. Don't be afraid to use google either. I can tell you first hand that pretty much every developer I know uses google every single day. I've been doing this for 12 years and I still do.
No disrespect to Aussie, but I disagree with most of what he said. Yeah, you should learn different languages and try to do things different ways, but DB design isn't OO. Syntax mastery isn't half as important as grasping concepts, especially with Intellisense. And the native .NET functions are super-handy to know. It will save you a lot of time and grief if you get familiar with those.
I noticed that in Reapers post and was likechittydog wrote:
the principles of OO have nothing to do with [database design]
However, I think I may know what he meant - relational database design becomes a whole lot easier if you start thinking of table schemas as being something like class definitions - it's more 'object based design' than 'object oriented design'.
don't think linear,think outside the box
It's more like:blah wrote:
don't think linear,think outside the box
Think inside the box, outside the box, what the box is made from, what makes the box 'box-like', how the box behaves in a 'box-like' manner, and what can be done with the box.
thatScorpion0x17 wrote:
It's more like:blah wrote:
don't think linear,think outside the box
Think inside the box, outside the box, what the box is made from, what makes the box 'box-like', how the box behaves in a 'box-like' manner, and what can be done with the box.
I did forget one thing - think under the box, too.blah wrote:
thatScorpion0x17 wrote:
It's more like:blah wrote:
don't think linear,think outside the box
Think inside the box, outside the box, what the box is made from, what makes the box 'box-like', how the box behaves in a 'box-like' manner, and what can be done with the box.
Yeah I did. I was going over all the stuff I've learned through uni and a lot of it is cross disciplined. Learning database design helps when you code in SQL commands, which you can use in web programming, which is a language that when you learn will also prob start with your first web page saying Hello World. lolScorpion0x17 wrote:
I noticed that in Reapers post and was likechittydog wrote:
the principles of OO have nothing to do with [database design]
However, I think I may know what he meant - relational database design becomes a whole lot easier if you start thinking of table schemas as being something like class definitions - it's more 'object based design' than 'object oriented design'.
Do printf("Hello world!")\n 50 times over.
The idea of any hi-fi system is to reproduce the source material as faithfully as possible, and to deliberately add distortion to everything you hear (due to amplifier deficiencies) because it sounds 'nice' is simply not high fidelity. If that is what you want to hear then there is no problem with that, but by adding so much additional material (by way of harmonics and intermodulation) you have a tailored sound system, not a hi-fi. - Rod Elliot, ESP
Freezer:
rand=(200,99)
rand=(200,99)
Reaps
nerdtalklol=(over9000)
nerdtalklol=(over9000)
Indeed that is how I perceived what he meant.Scorpion0x17 wrote:
I noticed that in Reapers post and was likechittydog wrote:
the principles of OO have nothing to do with [database design]
However, I think I may know what he meant - relational database design becomes a whole lot easier if you start thinking of table schemas as being something like class definitions - it's more 'object based design' than 'object oriented design'.