Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #74404 > unrolled thread

What Next After Python Basics

Started byOrochi <kartikjagdale11@gmail.com>
First post2014-07-13 13:16 -0700
Last post2014-07-22 23:52 -0700
Articles 6 — 5 participants

Back to article view | Back to comp.lang.python


Contents

  What Next After Python Basics Orochi <kartikjagdale11@gmail.com> - 2014-07-13 13:16 -0700
    Re: What Next After Python Basics Dan Stromberg <drsalists@gmail.com> - 2014-07-13 17:38 -0700
    Re: What Next After Python Basics "C.D. Reimer" <chris@cdreimer.com> - 2014-07-13 14:46 -0700
    Re: What Next After Python Basics mathias.moe@gmail.com - 2014-07-19 13:26 -0700
      Re: What Next After Python Basics Chris Angelico <rosuav@gmail.com> - 2014-07-20 11:29 +1000
    Re: What Next After Python Basics Orochi <kartikjagdale11@gmail.com> - 2014-07-22 23:52 -0700

#74404 — What Next After Python Basics

FromOrochi <kartikjagdale11@gmail.com>
Date2014-07-13 13:16 -0700
SubjectWhat Next After Python Basics
Message-ID<ca4c09ca-49a8-4177-80cd-016f3748612c@googlegroups.com>
Hi,
I am beginner in Python
I have Completed Basic Python Course from Codecademy.com .
Now that I have a hands on the basics what is the next thing I should do.
I mean should I learn more or start a small Project(Any Ideas are Welcomed) or any Other suggestions.
Where to Start?

Thank You,
Orochi

[toc] | [next] | [standalone]


#74409

FromDan Stromberg <drsalists@gmail.com>
Date2014-07-13 17:38 -0700
Message-ID<mailman.11793.1405298319.18130.python-list@python.org>
In reply to#74404
On Sun, Jul 13, 2014 at 1:16 PM, Orochi <kartikjagdale11@gmail.com> wrote:
> Hi,
> I am beginner in Python
> I have Completed Basic Python Course from Codecademy.com .
> Now that I have a hands on the basics what is the next thing I should do.
> I mean should I learn more or start a small Project(Any Ideas are Welcomed) or any Other suggestions.
> Where to Start?

That really depends on how quickly (or slowly) you get frustrated.

If you're able to say "I don't understand this yet, but I'll tuck it
in the back of my mind for later" a lot, and google for answers as
needed, I'd dive into a project.

If not, maybe try another course and/or monitor this group and Stackoverflow.

The best kind of project to pick, now or later, is the kind that you
will actually use yourself.

[toc] | [prev] | [next] | [standalone]


#74410

From"C.D. Reimer" <chris@cdreimer.com>
Date2014-07-13 14:46 -0700
Message-ID<mailman.11794.1405300338.18130.python-list@python.org>
In reply to#74404
On 7/13/2014 1:16 PM, Orochi wrote:
> Hi,
> I am beginner in Python
> I have Completed Basic Python Course from Codecademy.com .
> Now that I have a hands on the basics what is the next thing I should do.
> I mean should I learn more or start a small Project(Any Ideas are Welcomed) or any Other suggestions.
> Where to Start?
>
> Thank You,
> Orochi

My first project after barely learning the basics of Python was reading 
a spreadsheet with 600+ website URLs, taking a screenshot of each 
website, and building a HTML webpage to display the 600+ screenshots. If 
I was to do this manually (i.e., clicking and looking at each website), 
this would take two weeks of my spare time. By automating this task into 
a Python script (which took two weeks of my spare time), the script runs 
for two hours in the background and I take 15 minutes to glance at the 
HTML pages with screenshots. If I find something wrong with a particular 
screenshot, I can click on the website URL to investigate further.

Chris Reimer

[toc] | [prev] | [next] | [standalone]


#74834

Frommathias.moe@gmail.com
Date2014-07-19 13:26 -0700
Message-ID<08d0e743-004b-41c2-a760-a062c7a7d12c@googlegroups.com>
In reply to#74404
On Sunday, July 13, 2014 10:16:47 PM UTC+2, Orochi wrote:
> Hi,
> I am beginner in Python
> I have Completed Basic Python Course from Codecademy.com .
> Now that I have a hands on the basics what is the next thing I should do.
> I mean should I learn more or start a small Project(Any Ideas are Welcomed) or any Other suggestions.
> Where to Start?
> 
> Thank You,
> Orochi

>
I started up going through a few problems on projecteuler.net, and then casually escalated to look through codegolf.stackexchange.com for fun code to study, and even some problem to mimic. So, there's *an* idea. (mind you, might not be the best of ideas). If you're up for it, there's even rosettacode.org, with crazy code which I found fun to study.

But mostly, just code. Anything. For my studies, I get assignments to go through large bodies of text and sort them for some criteria, and while I'm given tools to do it, I try to make my own tools to get the job done. That is to say, if there's something in your day that you use in some way, and it's fairly simple, or its essential functionality can be copied, then that's something to copy.


I apologize for the raving suggestions.

Mathias H. M.

[toc] | [prev] | [next] | [standalone]


#74852

FromChris Angelico <rosuav@gmail.com>
Date2014-07-20 11:29 +1000
Message-ID<mailman.12076.1405819787.18130.python-list@python.org>
In reply to#74834
On Sun, Jul 20, 2014 at 6:26 AM,  <mathias.moe@gmail.com> wrote:
> But mostly, just code. Anything. For my studies, I get assignments to go through large bodies of text and sort them for some criteria, and while I'm given tools to do it, I try to make my own tools to get the job done. That is to say, if there's something in your day that you use in some way, and it's fairly simple, or its essential functionality can be copied, then that's something to copy.
>
>
> I apologize for the raving suggestions.

No, that's not raving. The way to get good at something is to do it,
and do it a lot. That's why I don't play lasertag, that's why I don't
butcher my own meat, that's why I don't write optimizing C compilers.
I don't have time to get good at any of those things. (Not that I have
a philosophical objection to any. If my circumstances change, I might
take one of them up at some point, but for the moment, I don't.) To
become a programmer, you need to write programs.

As a student programmer, you get very specific tasks: Write a program
that, given this input, produces this output; and use exactly these
tools (language statements, library functions, etc) to do so. There's
a definite "right answer" and a whole lot of "wrong answers". (And
it's really obvious when someone asks for help. When the problem's
that specific, it's bound to be homework.)

As a novice, you generally have fairly specific goals, but now you
have flexibility in how you implement it. Import this CSV file into an
SQL database, converting "25 Mar 01" into "2001-03-25" as it goes
through. You could do that with a preparse script, or you could import
into a temporary table and convert it in the database, or you could
parse and import in one step. It's fairly straight-forward to figure
out whether you've accomplished the goal or made a mess of it, but
there's no longer a "right way to do it".

An expert programmer has to cope with much vaguer requirements. Reduce
the number of data entry errors in invoicing. Adding something to a UI
that helps people notice errors earlier may not clearly and
demonstrably be working, until they've had a chance to get accustomed
to it and you start seeing that the error average per week is lower
than it was before the feature went in. (And even then, you can't be
sure; something else might have caused the improvement.)

(An expert will also sometimes get really clear goals. These are good
days. These are luxuries. These are the times when you profusely thank
the previous programmer for putting in such comprehensive unit tests
that the porting process is reduced to "make sure all tests pass, then
we're done". These are rarities, sadly, but they definitely do exist.)

Before you can handle the complex and less-clear jobs, you have to get
enough experience to know what you're doing. That means doing jobs
that have really clear requirements. Will they be boring? Maybe.
Derivative? Almost certainly. But pointless? Absolutely not. And maybe
you'll recreate something in almost the same way, but with one little
tweak that makes it now absolutely perfect for you. Or recreate
something in a different language, just because it's better that way.
(I did that myself recently - see http://rosuav.com/1/?id=1009 - even
though the old one was working fine.) Never useless, because of what
it does for you, the programmer.

It takes ten thousand hours of practice to achieve competence.
Fortunately, those hours will be enjoyable, if spent programming. :)

ChrisA

[toc] | [prev] | [next] | [standalone]


#75062

FromOrochi <kartikjagdale11@gmail.com>
Date2014-07-22 23:52 -0700
Message-ID<3209756f-37ef-4fb6-92e8-73382c00eac9@googlegroups.com>
In reply to#74404
Ok 
Thank You Guys for the suggestions.
I am starting with simple Data Structures and Algorithm studied in College,trying to code them in python.
Besides I am also trying to use Python in competitive programming.(codechef.com)
Its fun.

Thank you all !

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web