basicprogramming.org


Welcome, Guest. Please login or register.
Did you miss your activation email?
Forum time; Sep 02. 2010, 23:34
Home Help Search Calendar Login Register
News: The forum structure has been changed! Let us know what you think.

+  BASIC programming forum
|-+  Off-topic
| |-+  Coffee table
| | |-+  Easy = True. I think this has implications for BASIC use/non-use
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Reply Print
Author Topic: Easy = True. I think this has implications for BASIC use/non-use  (Read 130 times)
LanceGary
Hero Member
*****
Offline Offline

Posts: 704


« on: Feb 07. 2010, 12:49 » Reply with quote

http://www.boston.com/bostonglobe/ideas/articles/2010/01/31/easy__tru...

Easy = True
How ‘cognitive fluency’ shapes what we believe, how we invest, and who
will become a supermodel

By Drake Bennett
January 31, 2010

Imagine that your stockbroker - or the friend who’s always giving you
stock tips - called and told you he had come up with a new investment
strategy. Price-to-earnings ratios, debt levels, management,
competition, what the company makes, and how well it makes it, all
those considerations go out the window. The new strategy is this:
Invest in companies with names that are very easy to pronounce.

 This would probably not strike you as a great idea. But, if recent
research is to be believed, it might just be brilliant.

One of the hottest topics in psychology today is something called
“cognitive fluency.” Cognitive fluency is simply a measure of how easy
it is to think about something, and it turns out that people prefer
things that are easy to think about to those that are hard. On the
face of it, it’s a rather intuitive idea. But psychologists are only
beginning to uncover the surprising extent to which fluency guides our
thinking, and in situations where we have no idea it is at work.

Psychologists have determined, for example, that shares in companies
with easy-to-pronounce names do indeed significantly outperform those
with hard-to-pronounce names. Other studies have shown that when
presenting people with a factual statement, manipulations that make
the statement easier to mentally process - even totally nonsubstantive
changes like writing it in a cleaner font or making it rhyme or simply
repeating it - can alter people’s judgment of the truth of the
statement, along with their evaluation of the intelligence of the
statement’s author and their confidence in their own judgments and
abilities. Similar manipulations can get subjects to be more
forgiving, more adventurous, and more open about their personal
shortcomings.

Because it shapes our thinking in so many ways, fluency is implicated
in decisions about everything from the products we buy to the people
we find attractive to the candidates we vote for - in short, in any
situation where we weigh information. It’s a key part of the puzzle of
how feelings like attraction and belief and suspicion work, and what
researchers are learning about fluency has ramifications for anyone
interested in eliciting those emotions.

“Every purchase you make, every interaction you have, every judgment
you make can be put along a continuum from fluent to disfluent,” says
Adam Alter, a psychologist at the New York University Stern School who
co-wrote the paper on fluency and stock prices. “If you can understand
how fluency influences judgment, you can understand many, many, many
different kinds of judgments better than we do at the moment.”

A handful of scholars have already started to explore the ways that
advertisers, educators, political campaigners, or anyone else in the
business of persuasion can use these findings. And some of the
implications are surprising. For example, to get people to think
through a question, it may be best to present it less clearly. And to
boost your self-confidence, you may want to set out to write a
dauntingly long list of all the reasons why you’re a failure.

Our sensitivity to - and affinity for - fluency is an adaptive
shortcut. According to psychologists, it helps us apportion limited
mental resources in a world where lots of things clamor for our
attention and we have to quickly figure out which are worth thinking
about.

Most of the time, the shortcut works pretty well. If something feels
notably easy to decipher, whether it’s a piece of text or the shape of
an object or the particulars of a person’s face, there’s a good chance
it’s because we’ve previously done the work of processing it, and that
it’s something we’ve encountered before. Cognitive fluency signals
familiarity - some psychologists argue that the eerie experience of
déjà vu is simply when we’re fooled by the unexpected ease of taking
in a piece of sensory information, and interpret that as a memory of
having been there or seen it before.

An instinctive preference for the familiar made sense in the
prehistoric environment in which our brains developed, psychologists
hypothesize. Unfamiliar things - whether they were large woolly
animals, plants we were thinking of eating, or fellow human beings -
needed to be carefully evaluated to determine whether they were friend
or foe. Familiar objects were those we’d already passed judgment on,
so it made sense not to waste time and energy scrutinizing them.

According to Norbert Schwarz, a leading fluency researcher, the late
psychologist Robert Zajonc used to explain the evolutionary logic
behind this tendency succinctly. “He’d say, ‘If it is familiar, it has
not eaten you yet.’ ”

“That gut feeling of familiarity determined by ease of processing is a
very effective shorthand,” says Schwarz, a psychologist at the
University of Michigan. “Having to sit down and analyze every time
whether something is familiar would not be a good idea.”

Our bias for the familiar, however, can be triggered in settings where
there’s little purpose to it. In the 1960s, Zajonc did a series of
experiments that uncovered what he dubbed the “mere exposure” effect:
He found that, with stimuli ranging from nonsense words to abstract
geometric patterns to images of faces to Chinese ideographs (the test
subjects, being non-Chinese speakers, didn’t know what the ideographs
meant), all it took to get people to say they liked certain ones more
than others was to present them multiple times.

More recent work suggests that people assign all sorts of specific
characteristics to things that feel familiar. Like beauty.
Psychologists have identified what they call the “beauty-in-
averageness” effect - when asked to identify the most attractive
example of something, people tend to choose the most prototypical
option. For example, when asked to identify the most appealing of a
group of human faces, people choose the one that is a composite of all
the others. And it’s not just faces: Studies have found a similar
tendency when people are asked to identify what makes for an
attractive dog or car or watch. Some psychologists suggest that much
of what we perceive as beauty is just the fact that the most
prototypical faces and dogs and watches are the easiest to process,
because they share the most with all the other faces and dogs and
watches that we’ve seen and stored in our perceptual inventory.

“These faces fit right in there. In effect, you’ve already learned the
facial features, so people like them,” says Piotr Winkielman, a
psychologist at the University of California San Diego who has done
research on fluency and attractiveness.

Winkielman doesn’t claim that beauty is entirely explained by fluency,
but he argues that the effect is powerful, all the more so because
we’re unaware of it. Indeed, the power of the effect, combined with
the ease with which psychologists can fool people into mistaking the
sensation of fluency for actual familiarity, helps explain the current
popularity of research into the phenomenon.

“People are very sensitive to the experience of ease or difficulty,
but very insensitive to where that feeling comes from,” says Schwarz.

One thing that fools us, for example, is font. When people read
something in a difficult-to-read font, they unwittingly transfer that
sense of difficulty onto the topic they’re reading about. Schwarz and
his former student Hyunjin Song have found that when people read about
an exercise regimen or a recipe in a less legible font, they tend to
rate the exercise regimen more difficult and the recipe more
complicated than if they read about them in a clearer font.

Playing with legibility can also change perceptions in subtler, less
predictable ways. Alter and Daniel Oppenheimer, a psychologist at
Princeton University who also co-wrote the stocks and fluency paper,
have found that when a personal questionnaire is presented in a less
legible font, people tend to answer it less honestly than if it is
written in a more legible one. Alter and two other psychologists,
Simon Laham and Geoffrey Goodwin, also found that, when presenting
people with written descriptions of moral transgressions, increasing
the contrast between text and background to make it easier to read the
description made people more forgiving.

To Alter, it’s a demonstration not so much of the power of fluency but
of its opposite, what psychologists call “disfluency.” Even at the
level of a trickier font, the experience of disfluency makes people
wary and uncomfortable. That sensation, Alter argues, is enough to
make them less forthcoming and also less forgiving in their moral
judgments.

“Disfluency functions as a cognitive alarm,” Alter says. “It sets up a
cognitive roadblock and makes people think, and it triggers a sense of
risk and concern.”

It isn’t just visual cues that have this sort of effect. Matthew
McGlone, a psychologist at the University of Texas, has found that
auditory cues can shape people’s perception of truth. McGlone did a
study in which he presented subjects with a series of unfamiliar
aphorisms either in rhyming or nonrhyming form: “Woes unite foes,” for
example, versus “Woes unite enemies.” He found that people tended to
see the rhyming ones as more accurate than the nonrhyming ones,
despite the fact that, substantively, the two were identical. Phrases
that are easier on the ear aren’t just catchy and easy to remember,
McGlone argues, they also feel inherently truer. He calls it “the
rhyme-as-reason effect.”

The persuasive power of repetition, clarity, and simplicity is
something that people who set out to win others’ trust - marketers,
political candidates, speechwriters, suitors, and teachers - already
have an intuitive sense of if they’re good at what they do. What the
fluency research is showing is just how profound the effect can be,
and just how it works.

And some of the more interesting ramifications of the new work come
from the suggestion that disfluency, rather than fluency, can
sometimes be what’s called for. Work on product marketing by Schwarz
and Hyejeung Cho has found, for example, that while creating a sense
of disfluency in potential consumers is likely to make them see a
product as less familiar, it also makes them see it as more
innovative.

And a few studies suggest that disfluency works well as a prompt to
get people to think carefully and catch mistakes. Alter and
Oppenheimer found that using a more difficult font can get students to
do better on the Cognitive Reaction Test, a three-question test that
usually trips up people answering intuitively. In another study, they
found that disfluency also led people to think more abstractly.
Schwarz and Song found that a difficult font can dramatically increase
the number of people who correctly respond to the question, “How many
animals of each kind did Moses take on the Ark?” (The answer is “none”
- Moses wasn’t on the Ark.)

In other words, to get people to think carefully and to prevent them
from making silly mistakes, make them work to process the question:
make the font hard to read, the cadence awkward, and the wording
unfamiliar.

Some researchers are also starting to look at the question of how to
change people’s responses to cognitive fluency. Winkielman is part of
a team of researchers who, in a forthcoming study, looked at the
relationship between mood and the desire for fluency. They found that
happy people are less interested in familiar, fluent stimuli - in this
case abstract visual patterns - than sad people. According to
Winkielman, this makes sense: When we’re unhappy, we seek out
stability and a sense of safety; when we’re happy, we’re more open to
the unfamiliar.

“Fluent things are familiar, but also boring and comfortable,” he
says. “Disfluency is intriguing and novel. Sometimes you like comfort
food, like when you’re sick. And usually you want to try something new
when you’re more comfortable.”

It may be possible to tactically use disfluency to improve our own
everyday lives, as well. Schwarz has found that the ease or difficulty
of thinking something can sometimes neutralize the actual content of
the thoughts themselves. Along with Lawrence Sanna of the University
of North Carolina, Schwarz has looked at fluency and self-confidence.
The two found that, if the goal was to boost college students’
confidence before an exam, getting them to list a few reasons why they
were going to succeed was more effective than getting them to list
many reasons. Because it was harder, the students who were asked to
think of more ways to succeed were actually less confident, even
though they ended up with longer lists.

And Schwarz and Sanna found a converse effect when they asked students
to think of reasons they would not do well: Students asked to come up
with a longer list of reasons they would fail reported feeling more
confident than those asked for a shorter list. Indeed, they reported
feeling as confident as the students who had been asked to come up
with the short list of ways to succeed - by the authors’ calculation,
thinking of 12 ways to fail had the same effect as thinking of three
ways to succeed.

In unpublished research, Schwarz has found a similar effect with
marital happiness: Couples asked to come up with a short list of good
qualities about each other reported higher levels of marital happiness
than the other couples in the study - but so did those couples asked
to come up with a long list of each other’s bad qualities.

“Having to come up with many good things about your spouse is
terrible, because it becomes difficult and then you think she’s
obviously not that wonderful,” Schwarz says. “Coming up with a few bad
things about your spouse, that’s bad because it’s not that hard.
Having to come up with a lot of bad things, since it’s hard, it means
she’s not that bad at all. The difficulty that you have tells you that
there are not many such things.”

Results like these suggest that feeling good about yourself may in
part be a matter of having a hard time feeling bad, and that
confidence and even success might be triggered by interventions that
do nothing but make failure seem the more intimidating possibility.
The human brain, for all its power, is suspicious of difficulty, but
perhaps we can learn to use that.

Drake Bennett is the staff writer for Ideas. E-mail
drbenn...@globe.com.

© Copyright 2010 Globe Newspaper Company.
Report to moderator   Logged
gp1628
Staff Member
Full Member
*
Offline Offline

Posts: 195



« Reply #1 on: Feb 08. 2010, 09:16 » Reply with quote

Very interesting.
And very useful information.

One of the things it brings to mind as far as BASIC is the combat we face with other languages. Read the article. Then dwell on the fact that they talk about C, C+, Java, Perl, Python, etc. And we talk about YaBasic, GFA Basic, SmallBasic, Visual Basic, etc etc etc. The fracturing of the topic might in itself be part of our doom.

Come to think of it, any language which has fractured like that has tended to fall to the side. True of operating systems also. *slap head* WOW.

Maybe, as a podium for the subject of BASIC, this site should make more of an effort to talk about BASIC trying to avoid getting too much into versions.
Just a wild thought because of the article.
Report to moderator   Logged
syzygy
Full Member
***
Offline Offline

Posts: 232



« Reply #2 on: Feb 09. 2010, 03:21 » Reply with quote

One of the defining characteristics of BASIC is certainly the fact that BASIC is poorly defined.

I mean, lately we had the discussion whether the inclusion of GOTO constitutes good BASIC or au contraire bad BASIC, and you could find good arguments for both sides.

As opposed to all the major languages -- "C", Python, Fortran or whatever --, there is no hard definition, no single reference document for BASIC*), nor even a reference implementation as for Ruby. BASIC is more of a philosophy or a paradigm than a language, and most features are poorly defined.

This, of course, leads to two effects. First, if you don't like a feature of BASIC, you tend to implement your own dialect and still may call it BASIC with a clean conscience, so this is programmer's heaven, as opposed to, say "C", where your liberties in designing your own compiler are... limited.

On the downside, anybody who wants to start programming with BASIC will be mostly in the dark as to what he can expect, since this will largely depend on the particular interpreter he choses. Even worse, even if you have mastered one dialect, you'll experience your pitfalls and trapdoors when you move to a different dialect, even if it's running on the same OS. So, this will certainly lead to the perception of BASIC as a poorly-defined, "squishy" language, and hence to the reservations people have programming with it.

I don't know if there is such a thing, but BASIC seems to be more of an "interpreter programmer's" language than an "application programmer's".

Cheers,

syzygy

*) Okay, there's ANSI BASIC, but to my knowledge there never has been a complete implementation of this, which would support my point here. ;-)
Report to moderator   Logged
aurelB
Hero Member
*****
Offline Offline

Posts: 769



WWW
« Reply #3 on: Feb 09. 2010, 06:24 » Reply with quote

Quote
Even worse, even if you have mastered one dialect, you'll experience your pitfalls and trapdoors when you move to a different dialect, even if it's running on the same OS.

This simply is NOT true!
Why?
I start from my own expirience.
I can say that i know 90% of Creative Basic and when i use some other
basic like FreeBasic,Pure Basic etc...etc...
I imidietly understand 50% of this other basic language(especialy on windows).
All things look familiar only syntax is little bit different .
By the way BASIC is only programming language which evolved from
very simple userfriendly language to very powerfull programming
languages today.He use best thingss from other so called "big languages".
Report to moderator   Logged

syzygy
Full Member
***
Offline Offline

Posts: 232



« Reply #4 on: Feb 09. 2010, 06:33 » Reply with quote

Quote
I imidietly understand 50% of this other basic language

Yes, but if you move from, say one "C" compiler to another, you should be able to understand 99% of the code. (I'm talking about the language core, not libraries etc.)

It may be good or bad, but there is no "standard BASIC" in the way K&R defines a standard "C".

Cheers,

syzygy
Report to moderator   Logged
LanceGary
Hero Member
*****
Offline Offline

Posts: 704


« Reply #5 on: Feb 09. 2010, 08:01 » Reply with quote

This simply is NOT true!
Why?
I start from my own expirience.
I can say that i know 90% of Creative Basic and when i use some other
basic like FreeBasic,Pure Basic etc...etc...
I imidietly understand 50% of this other basic language(especialy on windows).
All things look familiar only syntax is little bit different .
By the way BASIC is only programming language which evolved from
very simple userfriendly language to very powerfull programming
languages today.He use best thingss from other so called "big languages".

Some BASICs use the same commands/statements/functions in very different ways.

For example compare rnd() and randomize in Liberty and MS BASICs. In MS BASIC rnd() will generate a repetitive stream of random numbers if the randomize statement is used. if the randomize statement is used then a pseudo non repeating random sequence is generated. But the opposite is true of Liberty BASIC.

Liberty BASICs method of creating windows by borrowing file creation statements is also very different from that found in other BASICs.

Similar confusion reigns over local and global variables (many BASICs require you to declare a variable as local even within subs (e.g., Small BASIC) but some make all variables in SUBs local by default and you have to specially declare any global variables (e.g., Liberty BASIC).

Data typing also differs considerably across BASICs. Some MS BASICs assume all variables are "variant" others require specif declarations of types.

The use of upper and lower case is not always consistent. I think True BASIC requires all key words to be in ipper case letters...

But despite confusion this I agree with Aurel to some extent. Learning one BASIC does help you when learning another...

Lance
Report to moderator   Logged
syzygy
Full Member
***
Offline Offline

Posts: 232



« Reply #6 on: Feb 09. 2010, 08:13 » Reply with quote

OTOH, there is only one "C" you'll ever need to learn... ;-)

Don't get me wrong, the wide variety in BASIC interpreters is not necessarily a bad thing IMHO. The upside is, you can chose the interpreter which best fits your taste: "You don't want mandatory variable declarations? Here, take this one! Case-sensitivity for you, Sir? This one might be for you. You need OO features? Have you tried that one?"

But it is something which sets BASIC apart from virtually all other languages.*)

Cheers,

syzygy

*) Is there another programming language with as many different dialects as BASIC? I know of none...
Report to moderator   Logged
gp1628
Staff Member
Full Member
*
Offline Offline

Posts: 195



« Reply #7 on: Feb 09. 2010, 10:03 » Reply with quote

There is not one C. Ive often had to specify that I would only accept ANSI-C code or maybe ANSI-C+. Not C, C+, C++, or C#, etc.

There are standards for most languages and protocols. Arguments about the way things "should be done" should always fall back to a standards document. The Internet would have been far messier without such things. In the early net I refused all of the "use this its better" offers involving a language unless it started with ANSI, ISO, IEC, maybe ECMA or at least RFC (american/international/european or Internet standards). And in languages that dont have a standard yet, you can usually find a discussion about the need for having one.

BUT keep in mind that THIS discussion is not about the facts of such languages. Its about the impressions, and the affects of those. Whether or not its TRUE that a language is fractured or not means little if the IMPRESSION is that its fractured. I think that the article makes this clear and points out something important about the life/death of things we know about including programming languages, services, and OSs
Report to moderator   Logged
aurelB
Hero Member
*****
Offline Offline

Posts: 769



WWW
« Reply #8 on: Feb 09. 2010, 10:34 » Reply with quote

Quote
*) Is there another programming language with as many different dialects as BASIC? I know of none...

Hey this is really TRUE.... Grin

Also like Gandalf say there is no only one C or Ruby or Python or Fortran or Pascal
or assembler.
This languages have dialects to.

@Lance you mention Liberty basic .
heh Liberty is weird becose is build in SmalTalk and build windows as predefined
classes (i guess)- ( SmallTalk is very weird language for me - strange then C++) Roll Eyes
Report to moderator   Logged

gp1628
Staff Member
Full Member
*
Offline Offline

Posts: 195



« Reply #9 on: Feb 09. 2010, 10:58 » Reply with quote

Hey this is really TRUE.... Grin

Also like Gandalf say there is no only one C or Ruby or Python or Fortran or Pascal
or assembler.
This languages have dialects to.
Right, but they also have a standard to refer to.
I tend to see ANSI-C or ISO-Fortran referred to as a common ground more than ANSI-BASIC which is a shame.
Report to moderator   Logged
menn
Hero Member
*****
Offline Offline

Posts: 571


« Reply #10 on: Feb 09. 2010, 15:12 » Reply with quote

i don't think that basic is poorly defined. i think that people eager to extend its capabilities often know very little about the language and its history, or about what's good programming and what's hype. even the best programmers write about the hype of the latest programming templates and practices as the nuisance it sometimes is.

programming is not one-size-fits-all, and what's good for c or pascal is not necessarily good for basic. but that doesn't stop people from taking one of the greatest languages ever and turning it into something else. sometimes, they do a good job. often, the best things become overcomplicated or removed because someone who doesn't know better thinks it's a good idea.

for example, if you say the only reason to leave goto in is "historical reasons," you're not getting it. that's not basic's fault, it's the definition in conflict with the personal ambitions of people who want to make "basic, only better." if people ignore what it is, and change it, it can either change in a way that keeps all the advantages of basic, or in a way that sacrifices them.

it's like saying we need "standards." sometimes the de facto standard is superior to the suggested, formal standard. what's lacking is not a formal standard but better (not even perfect) compliance with the de facto standard. and sometimes the de facto definition is superior to the formal defintion. but, if it goes ignored, the definition is irrelevant. it's not that we -can't- know what basic is. most people just don't care what it is, only what they think it should turn into. no definition will solve that.
« Last Edit: Feb 09. 2010, 15:13 by menn » Report to moderator   Logged

an "all purpose" language calls for- as much as can possibly be reasonable- an "all purpose" forum. the worst thing happening to modern basic? too many pointless rules and painting everything into corners. most modern basic forums are like that too.
Pages: [1] Go Up Reply Print 
« previous next »
Jump to:  
Atom RDF RSS 0.91 RSS 2.0


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2008, Simple Machines LLC Valid XHTML 1.0! Valid CSS!