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

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

Comparators

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

Contents

  Comparators Cai Gengyang <gengyangcai@gmail.com> - 2015-11-21 14:16 -0800
    Re: Comparators Jon Ribbens <jon+usenet@unequivocal.co.uk> - 2015-11-21 22:21 +0000
      Re: Comparators Cai Gengyang <gengyangcai@gmail.com> - 2015-11-21 14:49 -0800
        Re: Comparators Chris Angelico <rosuav@gmail.com> - 2015-11-22 10:00 +1100
          Re: Comparators Quivis <quivis@domain.invalid> - 2015-11-22 22:01 +0000
            Re: Comparators Chris Angelico <rosuav@gmail.com> - 2015-11-23 09:12 +1100

#99222 — Comparators

Comparators, interesting ...

>>> booltwo = (10 + 18) == 3**17
>>> booltwo
False
>>> boolone = (50 - 35) > 35
>>> boolone
False
>>> booltwo = (65 - 35) > 15
>>> booltwo
True
>>> boolalpha = 3 < 6
>>> boolalpha
True
>>> boolbeta = 100 == 10*30
>>> boolbeta
False
>>> 

[toc] | [next] | [standalone]

#99223

On 2015-11-21, Cai Gengyang <gengyangcai@gmail.com> wrote:
> Comparators, interesting ...
>
>>>> booltwo = (10 + 18) == 3**17
>>>> booltwo
> False

What's interesting about that?

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

#99224

Hmm .. I am a slow learner and have poor memory. Sometimes when I see a new programming operator, I have to type it out so that I can remember it and let it sink into my brain 

On Sunday, November 22, 2015 at 6:24:28 AM UTC+8, Jon Ribbens wrote:
> On 2015-11-21, Cai Gengyang <gengyangcai@gmail.com> wrote:
> > Comparators, interesting ...
> >
> >>>> booltwo = (10 + 18) == 3**17
> >>>> booltwo
> > False
> 
> What's interesting about that?

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

#99225

On Sun, Nov 22, 2015 at 9:49 AM, Cai Gengyang <gengyangcai@gmail.com> wrote:
> Hmm .. I am a slow learner and have poor memory. Sometimes when I see a new programming operator, I have to type it out so that I can remember it and let it sink into my brain
>

I recommend creating a text file of notes. Every time you learn
something new, add it to your notes file - and commit the change to
git. Then, when you come back to the file, you'll have one of several
reactions:

1) "Yeah, that's right! Good stuff to remember." - it's done its job
by reminding you.
2) "Wait, what? How does that work?" - add some clarification notes.
3) "Of course it's like that. I know that. Don't need that any more."
- remove it (and commit the change to git).

Every time #3 comes up, you know you're learning - you're becoming a
better programmer. And it will, often. This isn't something just for
"novice" or "beginning" programmers, either; I have a file like that,
although not only about programming. (This week, I added notes about
using iptables to NAT from one IP address to a completely different
one, and change the port number used, which basically let me deploy a
temporary bouncer on a cheap cloud server, getting around a temporary
outage here. Worth doing.) Some stuff will stay there for a long time,
ready for you to look it up whenever you need it. Other stuff will
come and go. All of it is useful.

ChrisA

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

#99243

On Sun, 22 Nov 2015 10:00:51 +1100, Chris Angelico wrote:

> I recommend creating a text file of notes. Every time you learn
> something new, add it to your notes file - and commit the change to git.
> Then, when you come back to the file, you'll have one of several
> reactions:

The git part is good advice. I'd like to build on your idea, though.

Create a directory of small text files, each containing a solution to a 
problem, with comments, and what not.

When you look for something, do:

    grep 'the stuff I look for' *
-- 
  _____  __ __ __ __ __ __   __
 ((   )) || || || \\ // ||  ((
  \\_/X| \\_// ||  \V/  || \_))
   Omnia paratus  *~*~*~*~*~*~*

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

#99244

On Mon, Nov 23, 2015 at 9:01 AM, Quivis <quivis@domain.invalid> wrote:
> On Sun, 22 Nov 2015 10:00:51 +1100, Chris Angelico wrote:
>
>> I recommend creating a text file of notes. Every time you learn
>> something new, add it to your notes file - and commit the change to git.
>> Then, when you come back to the file, you'll have one of several
>> reactions:
>
> The git part is good advice. I'd like to build on your idea, though.
>
> Create a directory of small text files, each containing a solution to a
> problem, with comments, and what not.
>
> When you look for something, do:
>
>     grep 'the stuff I look for' *

I'm not sure the advantage of splitting the files, but yeah, same
difference. Keep notes, one way or another.

ChrisA

[toc] | [prev] | [standalone]

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

csiph-web