Printable View
I've been trying to teach myself python over the last couple of weeks. I have read various e-books and tutorials and feel that I have a basic understanding(though I still do not fully understand the whole OOP end, which I know is extremely important).
My question is, where to go next? My goal is to eventually do some free lance work and just create private scripts for myself. I don't know how to start going about project at this point, but that is what I would like to do. Any suggestions?
Glad you're learning some programming. Post some stuff about it when you get the time.
I'd say the OOP element isn't really that important to the degree where it's imperative but since Python is an object oriented programming language it's a core aspect.
OOP on the surface is only a programming paradigm which is the model of which the language in question is structured around. OOP as you probably know is the orientation around objects/classes. It's a programming technique based around data & methods being encapsulated in objects or classes usually for facilitation and organization purposes. There are procedural programming languages which are more linear and procedure-based, and there are functional and more.
You'll likely learn about these somewhere down the road in your programming conquest.
--
Anyway, I'd say the logical next step is to keep learning Python because in programming when you think you have something down you usually don't. It'll take a lot of trial and error, practice and time. But more importantly, it'll take a lot of coding. When you feel completely comfortable with Python and have everything down (which should take a bit of time) then you should move on to your next language if necessary. While you are learning these languages pick up on general programming concepts and techniques such as the use of version control (you should try Git. Overall it's a great VCS suited for most if not all of your organizational needs).
You have a long road ahead of you. Good luck and feel free to post any programming related questions any time.
Rather that continuing to build on your theoretical knowledge, get in and get your hands dirty (if you don't transfer that knowledge from theoretical to practical information you're going to eventually forget it all). Pick a project, and build it. You're going to run in to a lot of problems along the way, and it'll probably take quite a lot of time, research and energy to build. Having said that though, you'll learn a lot, and your next project will run more smoothly (although you should still run in to problems).
I've always found that (particularly in CS), taking a lot of information in in a short time period for a subject I'm not too familiar with generally doesn't fare too well. For instance, if I'd never touched Python, it'd be more practical to read through a book chapter by chapter, applying and reinforcing what I've learnt from that chapter in some sort of practical exercise. Reading through 500+ pages without applying it practically is never going to bode well (even if you do read it all, chances are you're not understanding what you're reading).
Thank you both for commenting. Both of you had some really good points.
I have had little experience constructing my own scripts. The only practice I've had is coping down someone's code and trying to make sense of it. If you were to tell me to go make such and such I would have no idea where to begin.
Could either of you suggest something feasible to code that would give me some solid practice?
Make anything that comes to mind. Technically anything you think of can be administered from an idea into something concrete and existent (from small games, macros, utilities, and more).
Code as often as possible. Read a lot of various source code to get the idea of how certain things would work (i.e. an application you're using that hypothetically has the source code available for it).
As Artificial said, go through lessons and such to apply your theoretical knowledge into practice. The best way to learn is to simply get your feet wet early and often. A few people here (including me) learned from creating programs for Gaia. That was just our choice for our platform of practice. Maybe you could try something similar.
I or someone else here would be glad to help you out with any issues or questions you have. And in case I haven't mentioned this already, asking plenty of questions in regard to programming is another way to learn. Don't feel frightened and don't be afraid of failure - it's pretty natural in programming in general.
I think that that is a good plan. Artificial's video on the gaia login does all the dirty work for me so I'll just try to add onto that.
Once again, thank you for the help. I am sure that I will have some more questions in the near future.