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

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

Re: request for guidance

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: request for guidance David Hutto <dwightdhutto@gmail.com> - 2013-12-14 00:11 -0500
    Re: request for guidance rusi <rustompmody@gmail.com> - 2013-12-13 21:36 -0800
      Re: request for guidance Chris Angelico <rosuav@gmail.com> - 2013-12-14 16:43 +1100
    Re: request for guidance rusi <rustompmody@gmail.com> - 2013-12-14 23:54 -0800

#61881 — Re: request for guidance

[Multipart message — attachments visible in raw view] — view raw

Don't get me wrong, I didn't mean reinventing the wheel is a bad thing,
just that once you get the hang of things, you need to display some
creativity in your work to set yourself apart from the rest.

Nowadays, everyone's a programmer.

If it weren't for reinventing the wheel, then we wouldn't have abs(antilock
breaking systems), or new materials, or different treading for water
displacement or hydroplaning.

The point was just to try something in python, and to 'boldly go where no
'man' has gone before'.


Just to remind her that it's not just about python, but what you can
accomplish with it, and distinguish yourself from others.


On Fri, Dec 13, 2013 at 11:56 PM, Chris Angelico <rosuav@gmail.com> wrote:

> On Sat, Dec 14, 2013 at 3:48 PM, David Hutto <dwightdhutto@gmail.com>
> wrote:
> > In my opinion, a novice always tries to reinvent the wheel. Take for
> example
> > a simple text editor.
>
> Which isn't a bad thing. Especially in that particular case, it's good
> to try your hand at writing a text editor - most of the hard
> grunt-work is done for you (just plop down an edit control - in some
> toolkits you can even deploy a control with full source code
> highlighting), so you can focus on figuring out what it is that makes
> yours different. And then you'll appreciate other editors more :) But
> along the way, you'll learn so much about what feels right and what
> feels wrong. And maybe you can incorporate some of your own special
> unique features into whatever editor you end up using... quite a few
> are scriptable.
>
> ChrisA
> --
> https://mail.python.org/mailman/listinfo/python-list
>



-- 
Best Regards,
David Hutto
*CEO:* *http://www.hitwebdevelopment.com <http://www.hitwebdevelopment.com>*

[toc] | [next] | [standalone]

#61882

On Saturday, December 14, 2013 10:41:09 AM UTC+5:30, David Hutto wrote:
> Don't get me wrong, I didn't mean reinventing the wheel is a bad thing, just that once you get the hang of things, you need to display some creativity in your work to set yourself apart from the rest.
> Nowadays, everyone's a programmer.
> If it weren't for reinventing the wheel, then we wouldn't have abs(antilock breaking systems), or new materials, or different treading for water displacement or hydroplaning. 
> The point was just to try something in python, and to 'boldly go where no 'man' has gone before'.
> Just to remind her that it's not just about python, but what you can accomplish with it, and distinguish yourself from others.

> On Fri, Dec 13, 2013 at 11:56 PM, Chris Angelico <ros...@gmail.com> wrote:
> On Sat, Dec 14, 2013 at 3:48 PM, David Hutto <dwight...@gmail.com> wrote:
> > In my opinion, a novice always tries to reinvent the wheel. Take for example
> > a simple text editor.

> Which isn't a bad thing. Especially in that particular case, it's good
> to try your hand at writing a text editor - most of the hard
> grunt-work is done for you (just plop down an edit control - in some
> toolkits you can even deploy a control with full source code
> highlighting), so you can focus on figuring out what it is that makes
> yours different. And then you'll appreciate other editors more :) But
> along the way, you'll learn so much about what feels right and what
> feels wrong. And maybe you can incorporate some of your own special
> unique features into whatever editor you end up using... quite a few
> are scriptable.


For the young-n-enthu "Make haste slowly!" is usually good advice

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

#61883

On Sat, Dec 14, 2013 at 4:36 PM, rusi <rustompmody@gmail.com> wrote:
> For the young-n-enthu "Make haste slowly!" is usually good advice

As the Ancient Romans said, "festina lente".

ChrisA
[1] http://math.boisestate.edu/gas/iolanthe/web_op/iol13.html

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

#61940

On Saturday, December 14, 2013 10:41:09 AM UTC+5:30, David Hutto wrote:

> Don't get me wrong, I didn't mean reinventing the wheel is a bad
> thing, just that once you get the hang of things, you need to
> display some creativity in your work to set yourself apart from the
> rest.

> Nowadays, everyone's a programmer.

> If it weren't for reinventing the wheel, then we wouldn't have
> abs(antilock breaking systems), or new materials, or different
> treading for water displacement or hydroplaning.

> The point was just to try something in python, and to 'boldly go
> where no 'man' has gone before'.  Just to remind her that it's not
> just about python, but what you can accomplish with it, and
> distinguish yourself from others.

To complement what David is saying, programmers need to know
programming but a lot else besides in order to become even minimally
productive. eg

Primary Development tools/aids

   1. Help
   2. Interpreter-CLI
   3. Interpreter-Introspection
   4. Editor
   5. Completion ('intellisense')
   6. Tags (navigation)
   7. Refactoring
   8. Integration with 'non-programming' below


Other Development Tools
   1. Debugger
   2. Profiler
   3. Heap Profiler
   4. Coverage

Non-Programming

 Area             | Tool(s)              
------------------+----------------------
 packaging        | distutils, setuptools
                  | pip        
                  | Native tools (eg apt)
 versioning       | hg, git, bzr         
 multiple pythons | virtualenv           
 automation       | tox                  
 testing          | unittest, nose, pytest
 build            | scons, make...       
 deployment       | fabric               

Yeah I know this can sound a bit intimidating :-)

In actual practice most active developers need to know about 30% of the above

But you need to know which is your 30% ;-)

PS. Yeah you can say Im just a teacher trying to justify my job!!  On
the other side, for years I argued with the authorities that a 3 year
CS degree could be reduced to 6 months.

But I dont think it could be reduced to 6 days... or even 6 weeks

[toc] | [prev] | [standalone]

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

csiph-web