If I have a lot of money, I will spend it by travelling around the world in 10 days with my friends. The country that I plan visit is Australia,Japan,Canada, Singapore. The purpose of this trip is to enjoy and relax our mind.
The first day,I wake up at 7 o'clock in the morning and meet my friend at the KLIA at 8 o'clock. Our flight will be depart at 11 o'clock. We took the plane for 9 hour and finally arrive at the Melbourne Airport, Australia at midnight. After that we search for the hotel that we have booked named Melbourne Hotel get some rest for the day.
The next day we will go to state capital of New South Wales, Sydney. One of the famous place you have to visit in Sydney is the Sydney Opera House. There they got 1000 rooms, 300 corridors and hundreds of tales and secrets. The next day we'll go to the Art Gallery of New South Wales. the Gallery is one of Australia's leading museums of art and a Sydney institution, with five levels presenting a diverse range of art. And that's the end of the second day. The third day, we'll take flight from Australia to Japan also for 9 hours.
There we arrive at the Haneda Airport,Japan. After that we stayed at Hotel Metropolitan Tokyo. The third day, we'll go to the Japan's communications and observation tower,Tokyo Tower. The tower acts as a support structure for an antenna. Originally intended for television broadcasting, radio antennas were installed in 1961, but the tower is now used to broadcast signals for Japanese media outlets. The next day, we go to the Kaminari Gate in Asakusa, Tokyo. The Kaminari Gate was first built in 941 by Taira no Kinmasa a military commander. 2] It was originally located near Komagata, but it was reconstructed in its current location in 1635. The fifth day, we go to the Shinjuku for shopping because the Shinjuku is the center of this large district home to many malls, stores, restaurants. The sixth day, we'll take flight from Japan to Canada for 10 hours and 50 mins.


text:
Avetisyan ist der Familienname folgender Personen:

 Angela Avetisyan (* 1988), armeinisch-russische Jazzmusikerin
 Khachatur Avetisyan (1926–1996), armenischer Komponist
 Liparit Avetisyan (* 1990), armenischer Opernsänger (Tenor)

redpajama_set_name: RedPajamaWikipedia


MAB Funds as Trustee of the MAB Corporation Syndicated Loan Fund raised funds from wholesale investors in May 2016 and made a loan to MAB Corporation Pty Ltd (MAB Corp) for use as working capital.
For an investor who is also a purchaser of an apartment in MAB Corp's Banksia residential development the proceeds upon payment of the final distribution will be applied to reduce the amount payable on the settlement of the purchase of the investor's apartment/s.
MAB Funds expects the loan to repaid in December 2017 upon completion of the Banksia development but no later than 30 June 2020.


is a firm specializing in meeting the software process standards information needs of the professional community particularly concerning the ISO/IEC 12207 standard. SEPT has been in business since 1992. Mr. Magee was one of the principal US delegates to the ISO SC 7 International Plenary meetings from 1986 – 2002.He was a major contributor to the development of ISO/IEC 12207. Mr. Magee signed off the final draft of ISO/IEC 12207 for the United States in Rome, Italy in November 1994. For his diligent work on ISO/IEC 12207, Mr. Magee received an ISO/SC 7 award. Mr. Magee is past convener (1999-2002) of the WG 7 (Life Cycle Management working group for ISO/IEC JTC1 SC 7 Systems and Software Engineering. When he was convener the standard ISO/IEC 15288-System Engineering-System Life Cycle Processes, was developed.
During his working with this standard making group it was apparent that a lay person could become confused in what is required and what is suggested, because sometimes the directions contained in the standards are unclear to a lay person. To reduce this fog surrounding these types of standards SEPT started in 1994 producing checklists for standard. SEPT has produced over 90 released products to date. The checklists lift this fog around a standard and state what is required and suggested by the standard in a clear and concise manner. The SEPT checklists are constructed around a classification scheme of physical evidence comprised of policies, procedures, plans, records, documents, audits, and reviews. SEPT has concentrated on software process safety critical standards. SEPT checklists have been used by companies around the world. SEPT also provides standards information via books, templates, reports and this web site.
In 1995, he was elected to the IEEE Computer Society Golden Core of 500 people who have significantly served the IEEE Society in standards development over its 50-year history. Mr. Magee has over 42 years' experience in the software field and is considered an expert in software and system life cycle methodology.
Mr. Magee is co-author of the books, Guide to Software Engineering Standards and Specifications ISBN 0-89006-919-0 and Guide to Standards and Specifications for Designing Web Software ISBN 0-89006-819-4. He has authored many technical reports relating to software engineering standards issues.
He was active on many governmental, educational and professional boards, and holds BS from the School of Engineering from Oregon State University (1957) and an MBA in International Business from the University of Puget Sound 1980.


text:
package com.esotericsoftware.kryo.serializers;

import static com.esotericsoftware.minlog.Log.*;

import com.esotericsoftware.kryo.Kryo;
import com.esotericsoftware.kryo.io.Input;
import com.esotericsoftware.kryo.io.InputChunked;
import com.esotericsoftware.kryo.io.Output;
import com.esotericsoftware.kryo.io.OutputChunked;
import com.esotericsoftware.kryo.util.ObjectMap;

/** Serializes objects using direct field assignment, providing both forward and backward compatibility. This means fields can be
 * added or removed without invalidating previously serialized bytes. Changing the type of a field is not supported. Like
 * {@link FieldSerializer}, it can serialize most classes without needing annotations. The forward and backward compatibility
 * comes at a cost: the first time the class is encountered in the serialized bytes, a simple schema is written containing the
 * field name strings. Also, during serialization and deserialization buffers are allocated to perform chunked encoding. This is
 * what enables CompatibleFieldSerializer to skip bytes for fields it does not know about.
 *

 * Removing fields when {@link Kryo#setReferences(boolean) references} are enabled can cause compatibility issues. See here.
 *

 * Note that the field data is identified by name. The situation where a super class has a field with the same name as a subclass
 * must be avoided.
 * @author Nathan Sweet <misc@n4te.com> */
public class CompatibleFieldSerializer<T> extends FieldSerializer<T> {
	public CompatibleFieldSerializer (Kryo kryo, Class type) {
		super(kryo, type);
	}

	public void write (Kryo kryo, Output output, T object) {
		CachedField[] fields = getFields();
		ObjectMap context = kryo.getGraphContext();
		if (!context.containsKey(this)) {
			context.put(this, null);
			if (TRACE) trace("kryo", "Write " + fields.length + " field names.");
			output.writeVarInt(fields.length, true);
			for (int i = 0, n = fields.length; i < n; i++)
				output.writeString(fields[i].field.getName());
		}

		OutputChunked outputChunked = new OutputChunked(output, 1024);
		for (int i = 0, n = fields.length; i < n; i++) {
			fields[i].write(outputChunked, object);
			outputChunked.endChunks();
		}
	}

	public T read (Kryo kryo, Input input, Class<T> type) {
		T object = create(kryo, input, type);
		kryo.reference(object);
		ObjectMap context = kryo.getGraphContext();
		CachedField[] fields = (CachedField[])context.get(this);
		if (fields == null) {
			int length = input.readVarInt(true);
			if (TRACE) trace("kryo", "Read " + length + " field names.");
			String[] names = new String[length];
			for (int i = 0; i < length; i++)
				names[i] = input.readString();

			fields = new CachedField[length];
			CachedField[] allFields = getFields();
			outer:
			for (int i = 0, n = names.length; i < n; i++) {
				String schemaName = names[i];
				for (int ii = 0, nn = allFields.length; ii < nn; ii++) {
					if (allFields[ii].field.getName().equals(schemaName)) {
						fields[i] = allFields[ii];
						continue outer;
					}
				}
				if (TRACE) trace("kryo", "Ignore obsolete field: " + schemaName);
			}
			context.put(this, fields);
		}

		InputChunked inputChunked = new InputChunked(input, 1024);
		boolean hasGenerics = getGenerics() != null;
		for (int i = 0, n = fields.length; i < n; i++) {
			CachedField cachedField = fields[i];
			if (cachedField != null && hasGenerics) {
				// Generic type used to instantiate this field could have
				// been changed in the meantime. Therefore take the most
				// up-to-date definition of a field
				cachedField = getField(cachedField.field.getName());
			}
			if (cachedField == null) {
				if (TRACE) trace("kryo", "Skip obsolete field.");
				inputChunked.nextChunks();
				continue;
			}
			cachedField.read(inputChunked, object);
			inputChunked.nextChunks();
		}
		return object;
	}
}

redpajama_set_name: RedPajamaGithub


analysed the search results for millions of keywords throughout 2014 to rank the top ten websites displayed in the two Google ad formats.
The rankings were drawn up according to a PLA Visibility score and a PPC Visibility score which are a measure of how frequently and prominently the sites' ads appear within search results.
In the list of top sites displayed through AdWords, Amazon.com's PPC visibility score of 9,381,597 made it the clear leader. The list was made up of a mix of retail brands and search engines such as wow.com and ask.com .
PLAs, which include a product image, name and price together along with a link to the reseller, became the default way for appearing in Google Shopping in 2013. A Searchmetrics study released earlier this yearindicates that PLAs have experienced rapid adoption, with the number of ads displayed growing by +118% during 2014 alone.
AdWords ads, which have been around for many years, are very widely used and are not growing as rapidly as the relatively new PLA.
The findings of Searchmetrics' study are presented in a whitepaper, "Google Shopping & AdWords: The 10 Most Important Players" which can be downloaded here.


The ACIOA is a non-profit organization governed by the standard covenants of an NPO. These covenants include a Constitution, a Code of Conduct, and Privacy Policies. The ACIOA is governed by a Board of Directors and is led at the organizational level by the President.
So as to insure membership equality, the governance of Chapters and the responsibilities of ACIOA Members are also defined in a codified set of rules. We provide full disclosure of all covenants and governance guidelines upon request.


text:
Hooray for Halloween
Have fun and be safe tonight, peeps, whatever hijinks you're getting up to. And for your Halloweeny pleasure, I offer this delightful exercise in fundamentalist delusion, in case you haven't already caught wind of it from Ed Brayton's blog. It's the kind of thing you simply cannot enhance with further comment, so I won't. (Though the eruption of comments following the article itself are the kind of thing that make the internets so much fun!)
Labels: Halloween, humor
From the mailbag: two for the "unclear on the concept" folder
We often post our wackiest theist emails for your entertainment. But sometimes we get stuff that's just strange all down the line, as in, Did they realize who they were sending this to? And we also sometimes get earnest emails from non-theists, where they need a little help on understanding a thing or two.
Here's something that came out of the blue, which, once we chiseled our way through the odd syntax and comma splices, just made us scratch our heads.
Dear friend ,
I am Sabyesachi contacting you from Culture Unplugged Studios – a global, new age, new media studio focused on enabling networks of socially & spiritually conscious content & its creators, with operations in India, USA, UK and New Zealand.
Bwuh? It goes on.
We are at present in process of launching next online film festival - 'Spirit Enlightened' (to be live from December 09 to July 10), for which we seek your participation. 'Spirit Enlightened', aspires to trace the spirit that has led the humanity through centuries & civilizations and is in the making of our future. The festival hopes to explore with you, 'That' which envelops to infuse & evolve the individual as well as collective being, expands our vision of time as well as place, enlivens our hearts, and enlightens our species to transcend the present state of being for the mystical new – the next state of supramental self. Lets observe & feel this divine/enlightened spirit in the moment of its performance, in the midst of humanity now and forever, through film-media.
Actually, I think it'd be fun as hell to contribute to something like this, if only to read their spluttering reply explaining that what we sent wasn't exactly what they had in mind. They just might go supramental on us!
Second, here's a letter from a self-described agnostic, who's curious about, well, girls. Now, I don't wish to make fun of this fellow, and in fact I've had a nice exchange with him and he seems a decent chap. It's just that...well, read his question. Somehow, I detect a flaw in his thinking.
Im emailing because I dont know where else to ask. I am agnostic (leaning towards atheism) but there is one thing which baffles me, which seriously seems like a product of creationism - the female orgasm.
It has literally no purpose in our survival as a species, its sole purpose is to give the woman pleasure. Why would it exist?
Um...ladies...?
Gosh, when you put it like that, it kinda sounds stupid!
Hat tip to one of our fine Irish viewers, Fergus Russell, for this amusing story.
It transpires that some dimwit named Joe Coleman, who thinks of himself as "a visionary of our Blessed Mother and a spiritual healer under the energy of the Holy Spirit" — which is an awfully big mouthful to say in lieu of simply "kook" — predicted that there would be yet another vision of Mary at a shrine called Knock, a name that is simply begging for jokes. Naturally, thousands of fellow dimwits showed up for this. When nothing happened, Coleman made yet another prediction. Mary, who must have remembered a pressing last-minute appointment to appear in a tamale somewhere last time, has rescheduled for this coming Saturday. Naturally, thousands more dimwits are again expected to turn up, "learning" not exactly being a skill of your garden variety religious dimwit.
Funny enough as all this is, what's funnier is the huffy reaction from the local clergy. The Archbishop of Tuam, one Michael Neary, complains, "Unfortunately, recent events at the Shrine...risk misleading God's people and undermining faith. For this reason such events are to be regretted rather than encouraged."
And of course, it takes an atheist to put all this in its proper perspective, as Liam Meehan does in a letter to the Irish Times.
I'm a little confused that the Archbishop of Tuam, Dr Michael Neary, is discouraging people from gathering at Knock to witness apparitions which he believes "risk misleading God's people and undermining faith".
This is the same "faith" that believes that a cosmic Jew who was his own father by a virgin can enable you to live forever if you symbolically eat his flesh, drink his blood and telepathically tell him you accept him as your master, so he can remove an evil force from something invisible called your soul that is present because a woman made from a rib was convinced by a talking snake to eat an apple from a magical tree.
Har! That's beautiful enough to memorize, Liam. Hope you don't run afoul of those dadburn Irish blasphemy laws or anything!
Continuing AETV issues
So we've been getting another round of complaints that last Sunday's show, the second in the expensively refurbished Access Austin studios, looked and sounded like ass. Hang in there, gang, is all I can say. I suspect these are just teething problems with the new equipment and we'll get up to steam before too many more weekends go by. It is true we don't have quite the level of control over every aspect of the equipment that we did when broadcasting from Matt's place. But while Matt's place worked out spectacularly (to everyone's surprise) from a tech standpoint, there are impracticalities in going back and shooting there forever, which several viewers have pleaded. First off, it's Matt's home, and I imagine he and his lovably cranky parrot Max are thrilled to have it back. One thing that broadcasting from Matt's meant was that, if work or something else prevented him from being available on a given Sunday, then, oh well, there was just no show at all that Sunday. Taping at the Access studios, Russell or any one of us can easily step into the host's shoes in a last minute emergency and the show can go on. Finally, another thing to consider is that, taping at Access, we get to have dinner downtown at Threadgill's again (hooray!), instead of (gag! hack! retch!) Plucker's!
The last sentence is the opinion of the individual blogger and does not necessarily reflect that of the ACA, the Atheist Experience, or its board of directors. Thank you.
Labels: AE TV show
The difficulty in peddling an inferior product
A news item today talks about efforts by Christian evangelists to boost their witnessing in such New England states as Vermont, New Hampshire, Maine and Massachusetts, an area of the country that has become even more secular than the Pacific Northwest. Reportedly, up to 22% of New England residents claim no religious faith of any kind. This is absolutely wonderful news of a trend that I hope continues to spread. But it's sad faces all around for the poor folks at places like Redeemer Fellowship Church.
Several Christian denominations see New England as a "mission field" — a term often associated with unchurched, foreign lands. As they evangelize and work to plant new churches, they speak of possibility, but also frustration. The area's highly educated population is skeptical and often indifferent to their faith.
"About once every hour, I give up. It's tough, man," said a half-joking Joe Souza, a Southern Baptist missionary working north of Boston. "It's like, you found a cure for cancer and you want to give it away and nobody wants it."
That last remark illustrates with blazing clarity why fellows like Souza do not understand their difficulty in winning converts. Read the preceding sentence, Joe, where the people whom you are trying to reach are described as "highly educated" and "skeptical." There's your problem. You are dealing with people who are sufficiently intelligent to realize, much moreso than you, that you emphatically do not have anything to offer that can be remotely likened to a cure for cancer. (For one thing, if Souza's religion really were both true and as good as a cure for cancer, then there would be a cure for cancer. All powerful magic sky deity, remember?)
No, Christianity is in fact peddling an inferior product, one that offers the empty solace of "faith" in response to real-world problems, and then, with staggering arrogance, turns around and threatens people with eternal torture for non-compliance. Maybe there's a placebo effect in Christianity that can, I suppose, be argued to have better benefit than no effect at all. But "it's better than nothing" is not exactly what you'd call a ringing endorsement for a belief system that treats the human intellect as if it's something that can be won over with carrot (Heaven) and stick (Hell) theology.
The work is slow and its fruits can be scarce. Souza said people are generally polite, even interested in talking about spiritual matters. But they don't hesitate to reject invitations. He recalled a man with whom he recently shared his faith at the mall courteously declining to even take a card.
Of course. This man realized that Souza had nothing to offer that he wanted or needed. This is always how people respond to empty sales pitches: with indifference. Oh, it's a telemarketer offering me a limited-time-only deal on subscriptions to magazines I don't even read in the first place? Gee, why am I not clamoring to take advantage of that? Golly, it's a smiling but empty-headed buffoon in the food court telling me all about how much his invisible friend loves me? Sure, great, whatever — can you pass the sugar?
This trend, I think, is a terrific riposte to claims that those who criticize the "New Atheists" often make: that we may as well accommodate religion, because it is such a thoroughly ingrained part of our cultural landscape that we'll never be rid of it. Clearly, as the increasingly educated and skeptical population of New England are demonstrating, that is untrue. It doesn't take much to divest yourself of inferior products in your life. You just need to become a smart shopper.
Labels: belief trends, current events, New England
AETV audio FUBAR
A number of people have been emailing us complaining of a massive audio dropout in the latest AETV podcast, lasting, by some accounts, as long as 15 minutes. Just a note to say we are aware of this, and apologize humbly, deeply, and with abject humility. Frank has committed ritual seppuku. Personally I have no idea how this happened, but these kinds of things can happen, and our fine crew will endeavor to avoid such glitches in future.
Can beliefs be inconsistent?
Last night I listened to the podcast of last week's show with Matt and Don. I am looking forward to being back in the "other" studio again, but not next weekend as scheduled, since I have plans to fly to Pennsylvania.
One of the responses to the callers caught my attention. Matt and Don, beginning at around 42:30 in the audio, were speaking to Gregory in Eugene, Oregon. Gregory first wanted to propose his own uninteresting (IMHO) redefinition of God. Then, later, he claimed that he "considered himself just as much an atheist as I do a theist."
Matt asserted that this was ridiculous -- which it is. To be a theist means that you believe in a god, while to be an atheist means that you do not believe in a god. Obviously these positions are mutually contradictory, and so it makes no sense to hold both of them.
But then Matt went one step further, claiming that Eugene could not hold both of these positions simultaneously, effectively accusing him of either lying or being deluded about his own beliefs. It is this point that I wish to respond to, because -- as an enthusiast of formal logic -- I think one can't make such a blanket statement about other people's beliefs.
Of course, it's perfectly reasonable to assert that people should not hold contradictory beliefs, and to point it out vigorously when they try to slip that sort of thing past. However, it does not follow that one cannot hold contradictory beliefs, and in fact, I think that they do all the time.
Seen in abstract terms, you could say that a person's state of mind is a set of propositions that they assert to be true. "The sky is blue" and "the sky is not green" are two such propositions; "There is a God" is another. Not all propositions need to be definite; they could be probabilistic, as in "There is probably no God" or "There may be intelligent life elsewhere in the universe."
Now, given a particular proposition P, P can be either true or not true; and according to propositional logic it must be one or the other but not both. However, just because a proposition is false in reality does not mean that it is not a part of someone's belief system. Indeed, we know that some people have false beliefs -- just consider that many people are theists and many others are atheists. Either there is a God or there isn't, and therefore one of these groups clearly holds a false proposition to be true, and most likely a host of related propositions as well.
Still, believing a false proposition P does not make your belief system inconsistent; you can easily believe something that is false but does not contradict any other proposition in your universe of beliefs. However, my point is that there is no reason in principle why somebody cannot comfortably believe the assertion P1: "X is true" and P2: "X is false", at the same time.
As a computer geek, I happen to believe (though not entirely backed by affirmative evidence) that the human mind can be represented as a formal system, not entirely unlike a computer could behave in principle if it was outfitted with the right software. I am a believer in the possibility of artificial intelligence, though I definitely do not believe it has been achieved yet, and it may not be achieved within my lifetime, or even the entire span of the human race.
There is a famous theorem formulated by Austrian mathematician Kurt Gödel, which states that all formal systems are either incomplete or inconsistent. In other words, either there is some proposition P for which the system holds P to be both true and not true (inconsistent); or else there is some proposition P which really is true, but the system cannot prove it (incomplete, as P is true but missing).
Some opponents of AI see this as a fundamental limitation of computers, a proof that humans are somehow better than computers because they have intuition which is capable of somehow "jumping outside the system" and directly perceiving truths that cannot be proven formally. I see that as a fallacy. Sure, humans are capable of making logical leaps of intuition, but that doesn't mean the leaps lead exclusively to true beliefs. We know for a fact that brains are often misled into believing things which are not true, and may even be contradictory, which we sometimes call "hypocrisy."
Imagine a person who is completely insane, in the sense that he believes everything that is false and nothing that is true. Such a person must necessarily be inconsistent as well. Why? Well, consider the following untrue statements. P1: 2+2=3. P2: 2+2=5. These statements are contradictory -- they cannot both be true at once. Yet the insane person must believe both, because they are both false.
But you don't have to go so far as complete insanity in order to hold contradictory beliefs. In fact, I would speculate that everyone in the world probably has some beliefs that contradict one another. I do. Matt does. I'm not saying that this is desirable, or that you can't minimize the number of contradictions you believe, but the mind is full of shortcuts and logical leaps and rules of thumb that let us analyze reality without becoming immediately paralyzed by an in-depth comparison of new information against every other single proposition you already believe.
In fact, I once read a beautiful proof by logician Raymond Smullyan that every person must necessarily be either inconsistent or conceited. It goes like this:
The human brain is finite, therefore there are only finitely many propositions which you believe. Let us label these propositions p1, p2, ..., pn, where n is the number of propositions you believe. So you believe each of the propositions p1, p2, ..., pn. Yet, unless you are conceited, you know that you sometimes make mistakes, hence not everything you believe is true. Therefore, if you are not conceited, you know that at least one of the propositions, p1, p2, ..., pn is false. Yet you believe each of the propositions p1, p2, ..., pn. So you believe at least one of these statements to be both true and false; hence you must be inconsistent.
Believing a contradiction does not make you crazy or a liar. Continuing to believe both "there is a god" and "there is no god," even after the contradiction is explicitly pointed out to you, might make you a bit thick. But there's no impossibility there. We know thick people exist, and most of us encounter them on a daily basis.
Labels: AE TV show, epistemology, logic
The Bible Code
Posted by: Anonymous
I think it was Don who once described an apologetic method of debate as something along the lines of coming into a room, dropping a huge pile of feces on the floor, and then leaving the skeptics to sort out the mess.
We were recently hit by such an apologist on our AE TV list who wrote to give us "60 pages" of evidence for god's existence. Not that I'm not interested in giving evidence a fair review—but please have mercy and some sense. We get hit with loads of requests from theists and atheists to "please look at this and tell me what you think about it." Yes, we have a small team of people—but we are all volunteers with real lives outside of AE. And while most people understand and respect that, some seem to think that we're obligated to read (actually in most cases reread) anything they want to dump on us for their god. Fair enough that we should consider claims before dismissing them, but how about doing what Matt sometimes asks: Give me your very best argument or evidence.
This way we can start with what you think is most compelling and examine that first. Then, if I don't find it compelling, there is no reason for me to have to wade through the other 59 pages of crap that you admit isn't quite as compelling. Fair enough? At any rate you'd have to admit it would be a big time-saver that benefits both the apologist and the counter-apologist.
Well, this apologist wrote to some others on the list. Some things I read, some I didn't. But with me, she was very interested in the Bible Code. It had been a few years since I had encountered anyone serious about the Bible Code. In fact, it's so infrequently used by apologists who contact us (and for good reason), that I thought other counter apologists may or may not have ever had any reason to investigate this "code" for themselves. I had read a bit back when I was a theist, but I investigated it just enough to find it utterly uncompelling, and that was that. Since I already believed in god then, it really didn't matter.
So, I was a bit rusty in my responses to the latest claims, and had to do some refresher reading, which I did. And to be fair, I learned some things I didn't recall from my prior reading, which is always nice. To be honest, though, what I learned made me even less inclined to accept this code as anything but hogwash.
Torah Code?
My first complaint about the code is the actually name: Bible Code.
At least in the West, when we see the word "Bible," we think of books that contain basically what is contained in a standard King James anthology or, perhaps, a Catholic version. In fact, while I was dialoguing, I mentioned the New Testament more than once. She never corrected me to let me know that, in fact, the "Bible" Code has nothing to do with the Christian content of the "Bible"—it only applies to restricted portions of the Hebrew holy texts—the Torah (Genesis through Deuteronomy). This means that if there is any reason to think that a book containing codes is the handiwork of any god, nothing in the Christian "scriptures" would be demonstrated as text from god, due to this code. In fact, another name for the Bible Code is "Torah Code"—which I hold to be more honest. When a Christian calls it "Bible Code," that's misleading, unless they also clearly note that none of what has been considered compelling in any of the research—the codes in the main debate over what is generally considered the context of the "Bible Code" issue—applies to what they would usually mean when they use the word "Bible."
Where It All Began and the Koran Code
Although the idea of finding Bible codes goes back a ways, the real hot button came when, Doron Witztum, Eliyahu Rips and Yoav Rosenberg (WRR) published a paper titled: "Equidistant Letter Sequences in the Book of Genesis" in the journal Statistical Science. The main criticism from me is that we have no original manuscripts from which to work. So, we begin any such examination for divine codes with a copy, and with little means of demonstrating that copy's firm adherence to any original version(s).
Ironically, Muslims have noticed this same problem. There is also, not surprisingly, a Koran Code, and one of the reasons given for the superiority of the Koran Code by Muslim proponents is that the Koran text is closer to "original" than any Bible text could ever hope to be. While the Koran does have a history that leaves room for translation "adjustments," the claim that it is closer to "original" is not without a bit of merit. I should note that I do not claim the Koran Code is ELS-type code. It's somewhat variant. But as long as the Torah guys can make up their code rules, why not the Muslims? At any rate, it seems anyone can have some sort of superhuman, magical code in their holy book from god. But here is a link to a Muslim making his case for why the Koran Code beats the pants off any Bible Code:
http://www.submission.org/quran/biblecode.html
And here is a load of info if you're interested in what impresses some Muslims about the Koran Code:
http://www.submission.org/miracle/
And here is an article in the Egypt Daily News, talking about the miracle of the Koran Code, in which Meer Hamza, who has a Ph.D. in software engineering from University of Paisley in Scotland, says it "will be one of the main reasons to make non-Muslims turn to Islam." In fact, the team who "cracked" the code claimed, "no person on earth, not even a computer software is capable of writing even one word abiding with the Quranic mathematical code":
http://www.dailystaregypt.com/printerfriendly.aspx?ArticleID=7314
I include this, not because I find it any more compelling that the Bible Code, but because I was told, by the apologist with whom I was dialoging, that they'd never heard of any such "Koran Code." Not only is it there, but it's hailed as an undeniable "miracle" by the Muslims who subscribe to it. And if you've ever argued with a Muslim, you know they have what can only be called "a thing," for number-play in the Koran.
Forgive me for one sideline. I know I go long. But I've heard people claim the Koran doesn't contain prophecy. (It's funny how many Christians make claims about the Koran, that are hotly disputed by Muslims I encounter.) As I was looking up the code material last night, I found a Koran prophecy for the Apollo Moon mission:
http://www.submission.org/miracle/moon.html
What makes me laugh is how much like Christian prophecy this Koran prophecy works. It predicts so much—after it has already happened. It's very rare to find someone hollering for extra security at some political event because Isaiah or Moby Dick or the Koran or Nostradamus predicted an assassination attempt. How many disasters have been averted by someone recognizing an embedded prophecy before such a prophecy took place? And as I toss this out as rhetorical, watch someone find me an example! It seems there's always someone.
Bible Codes, the Later Years
Believe it or not, there is a guy who came after WRR, Michael Drosnin, who says he found a prophecy in the Torah Code before it happened—the assassination of Yitzhak Rabin. Since Rabin was successfully assassinated, I have to note that this prophecy must not have been very clear, since it was of zero use in averting a tragedy it supposedly foretold. Drosnin claims he tried to report the threat. If so, that would be to his credit. It's too bad there wasn't sufficiently specific information in the prophecy to make a warning more useful. Armed beforehand with a name of the assassin, a specific date and a few more details, and someone in authority could have perhaps helped Rabin avoid being killed. How was this "prophecy" even helpful? And how many future events will be "found" in the text--like the name of Rabin's assassin, said to have been found after he was already identified? That's painting a target around my arrow after I've randomly hit some tree.
But Drosnin was so impressed with himself that he went back looking for other, unhelpful and useless, historic assassination prophecies, and—surprise, surprise—found them. Of course, they were all "encoded" in different ways—it appears there is no set method in this code of expressing that someone will be assassinated. You sort of have to know how to read it in various disguises. But, it's there, says Drosnin—if you know how to look. This sort of sloppy work is a trademark of Drosnin, though. It is examined in sufficient detail in Marvin V. Zelkowitz's research paper, "The Bible Codes," found at the University of Maryland website:
http://www.cs.umd.edu/~mvz/pub/biblecode.pdf
It's slightly painful to read Zelkowitz's responses, because it's hard to accept anyone could be as careless as Drosnin, and still be hailed as a hero by so many gullible followers. Drosnin, to be fair, doesn't claim to be either a scientist or a researcher. He's just a writer—selling books about the Torah Code. Nothing wrong with being a writer, unless your writing about something that rests upon research data, and you don't understand good research methods.
The first thing to understand about research with something like the Torah Code is how data can be bias. Here's a simple example of something you have to understand about numbers and how they impact interpretations of data:
Coin Experiment
I am going to do a study. In my study I have a subject who will flip a silver dollar. I won't tell him why (I want to keep it "blind," so my subject won't skew my results). I also want the coin to land on the floor—I don't want the subject to touch it after he's tossed it—in order to make my results as random as I can. After all, I want to be fair. My hypothesis, known only to me, is that I believe the coin toss experiment will reveal that I get "heads" as a result far more often than "tails." My subject tosses the coin into the air—and it lands, exactly as I predicted! Heads up! I thank my subject and write my paper demonstrating that "not only did I get heads more often than tails, but I actually achieved a much greater result than anticipated: I achieved heads 100% of the time!"
I did nothing to manipulate the data. I blinded the study and removed myself as a potential factor that could bias the data. And I inserted something in my method to make the result random. And I was very honest about the data I gleaned from my research.
I'm guessing you can see the problem with my conclusion that coins, when tossed, will most often (maybe even 100% of the time) land on heads.
Sample size impacts results. How many coin flips did I test? One. And that sample size invalidates my findings. Obviously I need more coin tosses. So, next time I do my research, I do two tosses. And I get heads both times. Have I fixed the problem? No, because we all know that it's possible to get what is called a "run" with things like this. Even though over an extended period of tossing the coin, I should get heads something close to 50% of the time, I could, theoretically, get heads for 100 tosses in a row. It would be funny, but not impossible.
What was the sample size in the original Torah Code experiment? How many books other than the Torah did they test? None. They ran multiple codes, but only on the Torah. They didn't run those codes on other similar samples. And, as we'll discuss, that's more of a problem than just "sample size." But to be fair, there is some debate from what I read about whether the results held up as "statistically significant," after other researchers ran the codes on other, similar books as samples. We'll address that later.
Repeatability, Part I
Beyond increasing sample size, repeatability is also good thing. Instead of doing one experiment where I toss the coin 100 times and calculate the rates, I now decide we'll do ten 100-toss experiments. As I increase my sample size to something more reasonable—100 tosses per experiment, rather than two—I will more and more start getting results closer to 50% heads. But since I recognize it's still realistically possible to get an anomaly like a 100-head-result run in one experiment, it's a good idea to do the experiment more than once. With the Torah Code, if there is demonstrated statistical significance, we still have to understand, this could be our 100-head run. So, I see high results found in one book, as potentially not even relevant. If I run the test on 100 books, I expect to see some hit high, some low, and some closer to center. If we can't explain how one book generated higher rates—the fact that it did so could be nothing more than our 100-head run. The simple fact is: Nobody knows.
The way to demonstrate that the high hit book is significant, and not just a possible anomaly, would begin by offering a plausible explanation for how it hits so much higher than the other books, something for which we could test. "God" could not be offered as a cause in a universe where no gods have yet been demonstrated to exist, since things that do not exist cannot be the cause of other things. To posit god as an explanation, would first require a study to demonstrate there are gods and that those gods would be inclined to produce book codes. A daunting task. But short of any actual plausible explanation available to us, we would be left only with a high hitter and no means demonstrate how it hits so high.
But I will share with you a statement from Robert Aumann. Aumann is a Game Theorist. He was impressed by the codes at the time he said, "for many years I thought that an ironclad case had been made for the codes; I did not see how 'cheating' could have been possible." However, when the research was critiqued by other researchers, Aumann had to admit that "Though this work [in reference to published criticisms of the code methods] did not convince me that the data had been manipulated, it did convince me that it could have been; that manipulation was technically possible."
What Is a Code?
Aumann's statement leads us into our next issue, which requires an understanding of how the codes are generated. A method known as ELS is used—but you could apply loads of different patterns. Any pattern could be a "code." But in ELS, the researcher gets to pick a starting point in the manuscript—which may or may not be the first letter. Then he gets to choose another number (so far the researcher has manipulated two variants) that he then "skips" until the next letter in the manuscript. So, let's say every tenth letter is selected after your chosen start number. The fact you can configure it however you like is a big part of the problem. There is no "prescribed" matrix that we know will work to find secret messages from god in books, so it's up to the researcher to start picking numbers. With no known "correct" matrix for finding secret messages from god in texts, we all have free reign over how we build out favorite matrices.
So, we end up with a string of random letters, which we then go over with a fine-toothed comb looking for words that we get to label as "meaningful" (to us) or not. Obviously we can expect to find loads of "words" or "strands" of words—but only the ones we decide "count" will be selected. So we get to keep and toss whatever we think fits.
As you might imagine, this is a big no-no. In relation to my coin toss experiment, let's say that 25 times out of 100, the coin bounces off a wall before it lands on the floor. Would it be a problem if I said, "anytime the coin bounces off the wall and lands on tails, I am going to say it doesn't count toward the final 100; but anytime it bounces off a wall and lands on heads, we'll count that"? The answer is "yes, it would be a problem." It would skew my results. Each time I hit the wall and don't get my desired heads, I get to do it over again, which increases the chance I'll get heads more often over tails. In these codes, whatever words the researchers find that don't mean anything to them, they don't have to report as a "miss." But whatever they find that they have predetermined will be "meaningful" to them—literally whatever they call meaningful—they get to report as "hits." So you ignore the garbage, and just report the positive findings.
If meaningful phrases are evidence of the existence of a code, then why isn't "noise"—random letters with no discernable meaning found in the code (to a large degree)— counted as evidence against the existence of a code in the text? In other words, if a bit of "not crap" = "coded," then why doesn't "crap" found all over in these codes demonstrate "not coded"? Why does this magical code include any crap at all? What's the crap for? Why doesn't it tell a cohesive story using all the code letters with no noise? I suggest something that starts with "Congratulations, you've cracked my secret god code! I have so much to reveal to you…" and on from there.
In the original study, though, the words that the researchers decided would be counted were words connected with biographical data about famous rabbis. The findings were interesting and the researchers claimed success. In subsequent criticisms, it was demonstrated that by manipulating the matrix settings, you can increase or decrease the level of significance. It would be along the lines of discovering that if you start your coin flip with the coin on tails, you are more likely to get heads as a result. As Aumann says, you may not have intended to start more of your flips on tails, but if you did, however unintentionally, it could still potentially skew your results. Even without meaning to, the moment you select which letters and numbers to use, you have already influenced the results. And this is only one way to subjectively, and problematically, "tune" your results. More later.
Repeatability, Part II and Statistical Significance
For now, let's go back to my Coin Toss experiment and the idea of "repeatability." Most likely I will get some variance if I increase my sample size to 100 tosses within my single experiment. For example, I may get heads 30% and tails 70% in one experiment. So, it's good to "repeat" the experiment. The second time, I get heads 48% and tails 52%. So, I repeat and repeat, and eventually I get 52% heads after 10 experiments of 100 tosses each, plus or minus a few points for error rate—which we would all recognize as a more realistic expectation for a Coin Toss result.
This "plus or minus" consideration is what determines something called "statistical significance." In other words, if we get 52%, that's still in line with results we would expect from random chance for a two-sided coin flip. The two percent is not considered "significant" to us. It is not be impressively outside the range of our expectations. If we had a good sample size, and we did the experiment repeatedly a good number of times, and somehow we kept getting heads "significantly" less than tails, like only 2% of the time, we'd consider something was not in line with "chance." Either our experiment was somehow biased, or there's something else influencing the flips that we must identify. But what is "significant"? Is there a way to determine whether the variance we're seeing is "chance" or something else at 53%? 55%? 60%? In fact, clever researchers have worked out methods of figuring this out. It's not a guess. You don't get to say, "Well I just can't believe we could get these results by chance—so it must be significant!" Your level (or my level, or their level) of credulity is not how statistical significance is measured:
http://www.wikihow.com/Assess-Statistical-Significance
What you find personally significant or impressive, as far as assessing results, is meaningless, because human beings are biased. What can be demonstrated as significant, in research, is something else entirely.
Using Controls
Sometimes you can figure out if something is beyond the norm with what is called a "control." "Controls" are handy. A control would be helpful, for example, in a drug trial. Let's say I make a drug to cure disease X. X kills 5,000 people each year in the U.S. within one year of infection. Nobody who dies from X lives past the first year. And anyone who survives it simply exhibits natural immunity and survives with no further detectible infection. But there is no known effective medical treatment currently for curing X once you contract it.
I take 100 subjects infected with X and give them my drug protocol within the first few days of diagnosed infection. At the end of one year, 50 of my subjects are still alive and show no signs of infection. I announced that of 100 people infected with X, I successfully cured 50 with my treatment.
Should we celebrate that we've made a dent in medical treatment of X? If you think "yes," slap yourself—very hard.
Before we pop the champagne, there's something we forgot to consider: Each year in the U.S. 10,000 people become infected with X. And if I would have used a "control" group—a group of people who weren't treated with my drug—I would have discovered 50 out of 100 subjects alive in that group as well at the end of the year—all with no signs of infection. And the study would have failed to demonstrate my drug helped anyone in that case. It's simply a fact that half the people who become infected with X are able to fight it off successfully through their own natural immunity. The other half die within a year. Unless we get better results in future research, my drug appears to be wholly ineffective.
A "control" in the case of the Torah Code would be using other books—the more the better—to run patterns to see what I get. And in fact, the lack of controls was not ignored by critics. In 1999, in a paper published in Statistical Science (Brendan McKay, Dror Bar-Natan, Gil Kalai, Maya Bar-Hillel [MBKB]) there were a list of criticisms against work done by Code proponents (WRR), that included a control test claim. The claim was that a Hebrew copy of War and Peace had been tested and achieved high levels of statistical significance. I won't lie to you. In this debate—as in all religious debate—there are claims and counter claims and counter-counter-claims. For every person I find claiming "statistically significant" data, I find someone else claiming they have demonstrated that same level somewhere else, or have demonstrated that the first level was achieved using faulty methods. I will let the "experts" hash that one out. All I can say is that the original data did not include controls, which other researchers had to add later. And the initial lack of control in the research should be counted as a demonstration of sloppy method.
How Do We Interpret the Data?
I said at the outset that I had learned this is about the "Torah" Code, and not the "Bible" Code. I was dismissive when the apologist on the list used an Old Testament verse in her examples, because there is something interesting about Old Testament manuscripts that I was already aware of, that, in my mind, makes them extremely suspect—if not entirely useless—in a setting like the code studies. The writing contains no vowels.
Why is this important? Consider this: Let's say we run our code on a regular book and we get a strand that includes these letters: T H E R A P I S T. The codes use no punctuation and you get to decide not only if this set of letters is "meaningful" in your greater context, but how to interpret it. Is it "the rapist" near a set of letters that look like "bundy"? Or is it "therapist" next to a set of letters that look like "freud"? Or if it is in close proximity to "bundy," do you only consider it as "therapist" (and fail to see the "rapist" possibility) and find no link to "bundy" (who was a rapist, but not a therapist) nearby—so you toss it out as a "miss"—instead of a "hit" or even an identified error in your code? If the code says "bundy" was a "therapist"—shouldn't that be reported as an error in the code? Does the code say erroneously that "bundy" was a "therapist"—but you manipulated it and made "bundy" a "rapist" and wrongly attributed a "hit"? What if in 10 years, a famous therapist arises named "Bundy"? Which "bundy" does the code mean? Maybe neither; maybe the "bundy" reference is just noise? How do we tell? Even with benefit of vowels, it's a subjective mess.
Speaking of undesired outcomes of the code—meaningful misses—it's hard to overlook the humorous work of Dr. James D. Price, professor of Hebrew and OT at Temple Baptist Seminary, Chattanooga, TN, who found repetitive "self-contradicting" codes, and "negative codes" with messages like "there is no god" and "Satan is Jehovah":
http://www.nmsr.org/neg-code.htm
But back to the problem of "no vowels." Here's what happens when we don't have to deal with vowels: Using English as an example, let's say we find an "R" in the code. Just an "R" in a strand of letters. Since I get to add the vowels at will, here is a sample of what I can do with just an "R" and my choice of vowels:
And if I add an "S" after the "R" (R and S are, after all, common letters in English):
OR IS
OR AS
I think you get my point. It's incredibly subjective and easy to manipulate. In fact, it isn't just the case that I can manipulate this data. Since there are no vowels, and I am trying to make words from this mess, I must manipulate this data. This is bad, bad, bad. I'm not just interpreting the results now—I'm actually creating the results I want. And this is called "bias," and it's every research paper's worst nightmare. If I can demonstrate reasonable room for bias in your methods, you have seriously compromised your right to label your results "valid."
Believers as Critics
As I wind this down, something interesting I also found was that some of the most damning critics of the Torah Code are religious people or, at least, people who are sympathetic toward it. Remember Zelkowitz, I mentioned earlier? He actually thinks there is something to the work done by WRR. He says in his Bible Code criticism, in fact, that WRR's results had yet to be "satisfactorily explained." But he still went on to shred Drosnin's claims from just about every angle imaginable. Again, I make no claims about WRR—you can read the debate on your own if you find any of this potentially compelling. Zelkowitz published the same year as MBKB's criticism of WRR—so I have no idea if he had a chance to read their criticisms by the time he published or not.
Also, remember Dr. Price, at the Baptist University? Here's a comment posted by him at an online list:
http://lists.ibiblio.org/pipermail/b-hebrew/1999-June/003362.html
"In any segment of Scripture literally thousands of such codes can be found on thousands of words. One may pick and choose among them to imagine any message he desires. The same is true for secular Hebrew literature. Hundreds of false and self contradictory statements have been found. The alleged 'statistical' proof has been seriously challenged by expert mathematicians. In my opinion, the topic is not worthy of serious thought. It is a waste of one's time."
Some other religious folk who take the codes to task include the Web site "bibleonly.org," with their posting of "Does the Bible Code Bear the Signature of God?" by Ed Christian Ph.D., Department of English, Kutztown University, Kutztown, PA. Christian's answer is pretty clearly "no."
And at the scp-inc.org site (Spiritual Counterfeits Project), actually a religious site dedicated to the truth of god's word, they have a multipart shredding of the codes called "Bible Codes, or Matrix of Deception?" Again, after reading a bit of it, I'd say the conclusion I'm supposed to come to is "matrix of deception." Of course, religious people have their own bones to pick with why these types of Bible parlor tricks are blasphemous. I'll leave them to sort that one out as well.
Meanwhile one really uplifting tale I found on the Internet was the story of a current theist, Lori Eldridge. Lori is dedicated to the lord and runs a Bible study site. Lori used to be extremely dedicated to the defense and support of the truth of the Torah (Bible) Codes. At her site today, however, she has only this to say about her past as a defender:
http://www.loriswebs.com/lorispoetry/articles.html
"I used to be the owner of the Tcode mailing list where some of the top notch Torah Code experts in the world discussed the Bible Codes. The majority of us finally came to the conclusion that the codes cannot be of God because they were not statistically relevant and you can even fine 'bible codes' in the daily newspaper. And, most important, even Jesus' name (in Hebrew) was not found in any book of the Bible."
Well, if it doesn't say "Jesus," then it can't be from god, right? In jest, I have to ask, is it possible it doesn't say Jesus as a message from god? I guess what I find hopeful about Lori's statement is that she was finally able to see past a falsehood that would have supported her beliefs about god. She had every biased reason, any other believer would have, to hang on tightly no matter how ridiculous the claim or how sorry the "evidence," but ultimately somebody, somehow got Lori to understand how research works and how the Torah Code fails. While she is still a believer, she changed her mind about at least one piece of evidence when honestly confronted by other compelling evidence to the contrary. And I respect that and applaud her for it. That's a heck of a fine character trait in any human being—theist or not.
Labels: apologetics, bible code, counter-apologetics, research methods, torah code
What's So Good About Being Wrong?
If you're like me, you couldn't wait to see that six-mile plume of debris kicked up on the pole of the moon recently when the NASA rovers dove into the surface of our most famous natural satellite.
And, if you're like me, you were totally disappointed by what you saw on NASA channel, or, I'm told, through your telescopes at home—even with a clear sky.
A brilliant explosion of dust and ice was predicted. It didn't happen.
Again, if you're like me, you immediately thought something along the lines of "What happened?! What went wrong?!"
NASA, however, announced it was a great success. Data began streaming immediately. And they expect to be analyzing it for weeks to come. Maybe it wasn't a glorious sight, but certainly we'll learn something from the voyage. In fact, the failure of our prediction has already taught us something: It taught us that some prediction and some part of the model that NASA attempted and anticipated was wrong. Observably wrong.
When we make a prediction about reality, and our prediction clearly fails, we would do well to go back and rethink our assumptions. I'm sure NASA will be doing just that. It wouldn't surprise me in the least if one of the most burning questions they're asking is why they didn't get that plume they expected (and even computer generated). The truth is, when life goes on as predicted, we learn very little. When life throws us for a loop—if we're so inclined, we have an opportunity to learn a bit more about ourselves, our assumptions, and, most importantly, about the reality around us.
Can you imagine a NASA engineer watching the plume fail to rise, who insists his assumptions cannot be flawed? Don't get me wrong. I don't doubt that even in the sciences, there can be such fools. But generally speaking, most average people, and most scientists as well, understand that when assumptions fail, we have an opportunity to learn something. And we ignore such opportunities, generally, at our peril.
And yet, I can recall time after time in my former fundamentalist life, when I insisted it was simply a mystery when my beliefs, or what I read in the Bible, failed to correspond to reality. Why does the Bible say this if it doesn't make sense? Well, it does make sense, I was taught to insist—it's just that I can't understand it with my human mind. And if you think you can—well, you're just arrogant.
I know that wine doesn't turn to water. I knew it then. I know a man can't survive for days in the belly of a fish. I knew it then. I had never seen such a thing. I had never heard of any such things having ever been verified. And yet, the fact that these stories failed to correspond to reality hindered me not at all from accepting they were true and that reality was not to be trusted in these cases. What I observed in reality didn't matter. This was "different." This was "god"—residing in a compartment in my brain that reality could never taint.
Recently I heard of something called the Correspondence Theory of Truth—which is just a fancy way to say that if I believe I can run through a concrete wall, and I try, and I bust my head and fall on my ass instead, I would do well to question my assumptions, rather than the wall.
All of us use this method of getting by in life all the time. When you sit in a chair, you believe it will hold you. If it does, your belief has been verified. If it doesn't, your belief has been demonstrated to have been wrong. When you fall to the floor, it is nothing more than folly to insist the chair really did hold you, exactly as you said it would. The children's story "The Emperor's New Clothes" is a cautionary tale about Correspondence Theory, in fact, that any child can comprehend: A person who can be separated from reality and reason, is an easy mark.
Undermining our reliance on how reality corresponds to our mental models divorces us from the most basic means we have of testing our beliefs against reality as a means to differentiate true beliefs from false beliefs. It is just one way religion can damage a person's reasoning ability. Getting an adherent to doubt a method of validation he must use day-in and day-out as the basis for how he learns and survives with any modicum of success in this life, is a monumental accomplishment. Shameful—but monumental. The fact that religion accomplishes this on such a grand scale should cause everyone to take notice.
If you've never suffered indoctrination, it probably seems ridiculous to you. How could I ever, for example, get you to believe reality is not what is clearly demonstrated before you? How could I convince you, through unverified claims alone, that I knew a guy who flat-lined for three days, and has recently been brought back to life? How could I convince you that moral knowledge is gained by eating magical fruit? How could I convince you that angels can make donkeys speak? That the planet is 10,000 years old? How could I convince you mass infanticide can be a good thing sometimes?
I understand how easy it is to think Christians are merely stupid. When judged from the perspective of a person who has never suffered the indignity of having his own reasoning skills utterly gutted and discredited as a child, it will probably only ever be understood as "stupid." Honestly, I really can't defend otherwise. I was stupid. But today, at least, I know why.
Some of you will never understand the sick depths of indoctrination and what it can do to the mind of a child. I am sincerely happy for those of you who never knew, and will never know, what it's like to have come to recognize that a group of people, including those you loved and trusted most, convinced you for many years to doubt your own ability to think and reason, and to doubt the most basic, objective reality that surrounds you.
Reintegrating into reality can be a chore, a process that can take, literally, years. I cringe each time I see a letter on our list from someone going through this who writes to ask "When will I stop being afraid? Does it ever go away?" or "When will I stop feeling like I'm so stupid? Will I ever learn to trust myself?"
And where am I going with this? I guess on the one hand, if you're not familiar with anything like this, try to empathize, even if you can't actually sympathize. Consider mercy sometimes when you feel like being sarcastic or cruel. These are abused people. The fact some of them don't yet realize it doesn't alter that fact.
And if you know exactly what I'm describing, know that you're not alone. Know that you will get better. Know that what was done to you was abusive and wrong—even if it was done by misguided people who thought they were doing the right thing. Forgive them for your own peace of mind. And work on getting past this and finding some way to reintegrate with your humanity and to celebrate the fact that imperfection isn't something for which you need to continually denigrate yourself.
Remember that being wrong, and recognizing we're wrong, is nothing to be ashamed of. It's OK to be wrong. It's an opportunity. It's how we learn and grow as human beings.
10/14/09: Addendum
Today we received a letter on the AE TV list. It was from a Christian, imploring us to reconsider our atheism. I wanted to share this quote as a demonstration of the harm caused by childhood indoctrination. It was just such a sterling example of my point:
"So, you are going to live in fear and doubt until you deal with the question of whether Christianity is true or not."
When I was an adolescent, I prayed long and hard for something to help me to believe. The idea that a vengeful god existed and that he required a belief I might fail to provide was terrifying. At the time, I don't think I would have recognized I was in terror, because I was so used to that level of fear. Today I know that there is nothing to be gained by "fearing" ignorance. And the cure for ignorance isn't prayer--it's investigation. While I'm not immune from fear in my life, I can honestly say I no longer fear in the sense that I "doubt" my choices about god and religion. I don't lose any sleep over the thought "what if god exists and I don't believe?" I recall the day I realized that if I researched as much as I could, and honestly concluded there was no god there, god would be an absolute ass to torment me for an honest, heartfelt effort, which his what I gave. And if god is such an ass, I don't want to worship and obey him anyway--even if it means eternity in Hell, in the same way I wouldn't want to follow orders from Hitler, even if it meant firing squad.
Labels: child abuse, epistemology, religious indoctrination, science
Can You Spot the Strawman in this Picture?
Who didn't love Highlights as a kid? It was probably the only positive thing about visiting the dentist that I can recall. Everybody's favorite thing was the Hidden Pictures—but only if the images weren't already circled.
Well, today, I'm giving you an adult atheist version of Highlights Hidden Pictures. In this morning's Austin American-Statesman was a ridiculous opinion piece by Texas Attorney General hopeful Ted Cruz about the cross monument on federal property that has been in the news recently.
Today's assignment: Be the person who spots the most fallacies, errors, omissions or deceptions.
The winner gets full braggin' rights.
The only hint I offer is that whenever a person misrepresents an opponent's stance, the point is to try and wobble them off-base a bit by getting them upset or angry. I find humor, and mocking such a person, has the effect of not giving them what they want, in addition to showing you're above their childish and obvious attempts at manipulation. Should anyone choose to reply to the Statesman directly, I encourage them to bear that in mind.
Labels: church-state separation, fallacies, stupidity, ted cruz
Basava Premanand (1930-2009)
On October 4 of this year Basava Premanand died.
You may never have heard of Premanand, but in addition to physically reminding me a bit of James Randi, Premanand also had his own paranormal challenge and dedicated his life to debunking "godmen" of India. Just days before he died, according to a special release of the e-zine Bangalore Skeptic, he drafted and signed a statement attesting he was of sound mind and still as skeptical as ever. He didn't want any tales of death-bed confessions to haunt his reputation, after his death.
If you haven't ever heard of Premanand, I urge you to look him up and read about him and the sorts of problems Indian skeptics are addressing.
Labels: basava premanand, India, skepticism
A brush with Jehovah's Witnesses
I'm at home all week. I have a new job starting in San Antonio next Monday, but for now I'm just cooling my heels. I've been living in my sister's house for a while, planning to move to an apartment in a couple of months.
Anyway, this is build up to explain why I was enjoying a nice nap today after an exciting round of healing Heroic Oculus on my level 80 priest, when the doorbell rang. I answered it and was confronted by a smiley woman in her forties or fifties, and a twenty-something middle eastern looking young woman.
They were looking for "Katherine," and when I said there was no Katherine here the older lady said that perhaps they had the wrong house. I said "You might be talking about my sister, Keryn." Then she asked if we were believers in God in this house, and I said "No, we're pretty much all atheists." She lit up and said "Well that's great, we love talking to people of all religions and, uh... people of none. I am sure this is the house I was at before, she told me to come back later." At that point I asked if they were Jehovah's Witnesses, they confirmed it, and we were off.
Now, I know some people who would try to get rid of JWs as quickly as possible, but I love them. I've only had one other encounter with them, which I documented here. They are so full of confidence that their book holds all the answers, yet generally pretty ignorant of basic facts. So I decided to pass some time chatting.
I was introduced to the younger woman, who pretty much never spoke the whole time, as a converted Muslim. I had to explain the whole "Jewish atheist" upbringing thing, which the lady interpreted to mean "Oh, so you read the Bible but you never actually got to know the Lord." I told her I didn't see it as getting to know anyone, but rather as not being raised to believe that their god existed.
The woman eager to start reading from the Bible, so I patiently refrained from calling it a book of fairy tales, or a big book of multiple choice, and she proceeded to gush happily about how the Bible is full of stuff that she finds inspirational. She asked me permission to read me one, and I consented.
To be honest, I don't even remember which part she picked. I just remember that at some point shortly after, we were talking about Adam and Eve, the first people, and she brought up how they defied God and ate the apple. So I asked whether they had the knowledge of good and evil at the time when he ordered them not to eat the fruit?
A little evasively, she said that they didn't know good and evil, but they understood that it would be disobeying God. But I persisted, did they really? How did they know that it was wrong to disobey God if they didn't know good and evil? What did they learn from the fruit of knowledge if they had that much understanding about not disobeying God?
She started to read what God said about how the day that Adam and Eve ate the fruit, they would die. So I said "But they didn't die that day. So God was wrong." And she said no, they certainly did die, in the sense that they became mortal. Then we talked about how the word "day" is sometimes a metaphor, and I brought up young earthism, so she said that she dismisses young earthism. "Yes," I said, "but there is no indication in the Bible how long those 'days' of creation actually were. Science had to figure it out first, before you could take credit for her." I also had to fill her in on background history of Bishop Ussher, since she didn't know how widely accepted young earthism once was.
I asked how, with all the non-literal stuff in the Bible, she can tell the difference between what's meant to be taken seriously and what's not? The Bible has no key to interpreting itself -- she pointed out that "in the beginning" from Genesis could be an indeterminate length of time and I pointed out that there is no way, without the insight of scientific examination, to actually determine that this is meant to stand for exactly 14.5 billion years.
But then she said that yes, the Bible has lots of original scientific knowledge, such as the order of creation matching up perfectly with what science says. "Oh reeeeally?" I asked, because this is one of my favorite claims to respond to. "Show me this ordering of creation please, that's fascinating!" So she skipped back to Genesis and started running through the separation of light and darkness, and then plants, and then... "Where was the sun at this point?" I asked.
She had an answer for me: "Oh, this verse doesn't mean that the sun was CREATED there. It just means that the sun was REVEALED at that point." Then she started to explain to me about the vapor canopy hypothesis, where the firmament water that would eventually become the water of Noah's flood, was blocking out the visibility of the sun.
"So," I said, "you believe that when plants came into existence, there was no visible sun on earth." "That's right." "And you believe this is in accordance with what modern science says? Seriously? How do you think plants get their energy? Ever heard of photosynthesis?" She put it to me that plants were getting energy straight from God.
So I said "I'm sorry, but you originally said that you think this information matches up with current scientific data. I know a lot of scientists, and I think it's safe to say that only a very tiny minority would give any credibility whatever to your version of events, including the vapor canopy hypothesis." She insisted that she had all kinds of literature she can bring back proving its scientific accuracy. I replied that I'm well aware that lots of creationists believe in that, but that doesn't make it in agreement with scientific thinking.
"What I'd really like to see is some kind of mainstream, peer reviewed, scientific journal that seriously advances the ideas that you're talking about." She promised that she would do the research and come back with it later. Asked what time would be good for me, and we agreed on Saturday at 11. The whole conversation lasted about 15 minutes, I think.
Personally, I'm betting they won't be back.
Labels: ID/creationism, Jehovah's Witnesses, live debate
What matters is he gets to play the Christian Persecution card
An amusing tale from the world of sports, which I generally regard with absolute indifference. Oakland Raiders cornerback Chris Johnson intercepts a pass in the end zone, celebrates by dropping to his knees and flamboyantly thanking God*, and is promptly penalized. ""I'm just getting on my knees giving my respect to God. I don't see how that's a personal foul or anything like that," he complains. But it appears that religion is not the culprit after all here. It would seem the NFL passed a rule three years ago prohibiting showy end-zone celebrations on general principles. Now the writer of the linked article makes the point that, religion notwithstanding, the problem here is that it's a stupid rule in the first place, and one that the NFL doesn't bother to enforce consistently. But even that misses the point. Christians will run with anything that lets them play the persecuted minority. You can bet that Kirk and Ray and all the fundagelicals who enjoy whipping up fear in the flock by whining about how Christianity is being "criminalized" in America will soon be adding "And the liberals won't even let football players praise Jebus in the end zone!" to their repertoire of repression. Yawn.
* The spectacle of sports stars constantly thanking God for their victories, as if the creator of the universe wouldn't have anything better to do, reminds me of the joke where the coach is talking to his team before the big game, and he warns them, "This is going to be a tough one, boys. God is on their side!"
Labels: Christian "persecution", humor
Conservapedia to form their own schism
Right now, lots and lots of people are emailing us to make absolutely sure that we've heard the exciting news that the geniuses behind Conservapedia want to rewrite the Bible without all the bits that they consider too liberal. To be blunt, it reminds me of trying to rewrite Olsen's Standard Book of British Birds by removing the ones who wet their nests. (And to see opinions I've already rendered on Conservapedia, check out this older post at Kazim's Korner.)
I have to say, when I first saw this at Pharyngula I immediately assumed it was a hoax. Then I saw the actual page on Conservapedia (which at the time of this writing is down, probably flooded by hilarity-seeking atheists). But I still imagined that somebody had punked them. I mean, anyone can edit the site, and their famous objective standards are a bit, hmmmm, what's the word, nonexistent. So clearly some silly person was seeing what he could slip by the censors.
Then I saw the discussion page. It may or may not be a joke, but enough of the regulars there take it seriously that it looks like it's taken on a life of its own.
So, okay. A nontrivial number of Conservapedians really think that their Bible should be improved. After all, if you leave the Bible in its current inferior form, then terrible liberals like E. J. Dionne are free to claim that the book actually supports their point of view, which is clearly ridiculous and unthinkable.
Now, you might say that this is an act of tremendous hubris, but I say, really, what's the big deal? It's not like it is without precedent, for a group of people to write or rewrite some holy text to suit their convenience, and claim the end result to be unchanging eternal truth. I mean, for starters, we've got the original authors of the Bible, unless you accept that they were divinely inspired. Then you've got the Council of Nicea, who went through all the books that were candidates for inclusion at the time and decided which ones did and didn't fit in with their conception of what the Bible should be.
Then you have the big Catholic/Protestant split in the 16th century, which by now has spawned alternate versions of the Bible. You have the Book of Mormon, supposedly dictated by an angel, and you have L. Ron Hubbard who specifically announced his (highly successful) intention to start his own religion.
What I'm saying is that, to borrow a description from the great George Carlin, it's all bullshit anyway. What difference does it make whether you take a 2000 year old book and claim that it is infallible as written literally, or you retranslate it and claim that the translation is infallible, or you make up some entirely new bullshit and claim THAT'S infallible? It's all bullshit, and the beauty of this Conservapedia project is how close they come to flatly admitting that it doesn't matter.
Don't tell me you take any of this stuff seriously anyway.
Labels: Bible translations, Conservapedia, right-wing hysteria
Once again, I've been away from the blog for a few days, this time because I was attending the fantastic Fantastic Fest at the Alamo Drafthouse, and my mind has been in movie mode for a solid, wondrous week. Which means that while ACA'ers were busily batcruising a week ago, I was a few blocks away at the Paramount theater squealing like a little girl while George A. Romero signed my ticket to the premiere screening of Survival of the Dead. Much as I love the gang, I'll have to miss a batcruise for that one, folks. Too bad the movie was crap, though.
Anyway, another incident involving a film legend went down recently, and while it may seem to have nothing to do with atheism, it was an event that gave me lots of food for thought about matters I've often discussed here on the blog and the TV show. I speak, of course, of the arrest of Roman Polanski in Switzerland on a fugitive warrant for his drugging and rape of a 13-year-old girl more than 30 years ago.
Opinions have been divided over Polanski ever since he fled the country upon realizing that the judge handling his case at the time — who, it must be said, has been revealed as something of a publicity hound — was about to renege on a plea deal. On the one hand, there are those who have categorically condemned Polanski as a slimy pedo, and on the other, cineastes who point to Polanski's great films and stature as one of the world's master directors, and the crime as simply some sick aberration that shouldn't tarnish the man's entire life. And besides, the victim, now in her 40's with a family of her own, has forgiven him.
Debates along those lines can and will go on for ages, and they are. Following Polanski's arrest, battle lines were drawn along familiar borders. Many of Polanski's industry pals have rushed to his defense, demanded his release, and offered all manner of apologia for his misdeed. Conversely, read feminist blogs, and it's clear they'll be satisfied with nothing less than Polanski's mutilated corpse dragged down Hollywood Blvd. behind a truck.
For my own part, I would not want to live in a world in which an artist like Polanski wasn't able to create. His best films are landmarks. Repulsion is the great film about psychosexual neurosis. Rosemary's Baby is a horror masterpiece, dealing with religious horror themes in a way the campy and atrociously scripted The Exorcist could never touch. Chinatown is one of the best movies ever to come from a major studio. And even his underrated adaptation of Macbeth, shot while he was still grieving over Sharon Tate's murder, is the darkest and most violent version of Shakespeare ever filmed. So yes, that Polanski is a great artist ought to be beyond dispute.
He also drugged and raped a 13-year-old girl.
This is a bad thing.
In deciding where I should draw my own conclusions here, I had to consider the way in which I like my atheism and overall fondness for rationalism to inform my thinking. The key factor is moral and intellectual integrity. By that. I certainly don't mean adopting inflexible dogmatic views and attitudes, but I do mean being consistent and not a hypocrite.
Repeatedly, on this blog and the TV show, I have been ruthless in my condemnation of religious pedophiles. Tony Alamo, Warren Jeffs, adult Muslims in the Middle East who enter into arranged marriages with girls as young as eight or nine — I've seen no reason to cut them slack. And so I cannot cut Polanski any either. Certainly, I do and will always revere him as an artist. But the crime is a crime is a crime. Time doesn't make it go away. Nor does the minor detail that the difference between Polanksi's rape and those committed by the likes of Alamo and Jeffs is that Polanski never tried to justify it on religious grounds. Do I plan to denude my DVD collection of Polanski's films? No. Why? They're great films, that's why. But just as O.J. Simpson's double murders don't diminish his accomplishments as a football star, neither can his football accomplishments be waved around as if they diminish the murders.
So if I cannot cut Warren Jeffs, Tony Alamo, and whoever-the-frak-else among religious wackaloons any slack when they victimize kids, nor can I cut Polanski slack. As an atheist, I think it's an important factor in retaining my own integrity that I do not allow personal anti-religious bias to influence my opinion, and make me treat crimes by the religious more harshly than the same crime committed in a context where religion had no role. It's hard for people to free themselves of biases, and those of us who pride ourselves on reason must be doubly diligent that we don't make excuses and plunge into the same hypocrisy we see from the religious.
I think the arrest needed to happen, if only so that the whole affair can now play out as it must, and neither Polanski nor his victim have to go on living with it as some sort of Sword of Damocles hanging over their lives. Polanski will always be a great filmmaker. But he drugged and raped a kid. At 76, it's past time for him to man up and face the consequences. If the court is harsh, so be it. If it's lenient, so be it. But it must be faced. And Polanski's defenders ought to know better than to embrace the casual insouciance of that last line in Polanski's greatest movie: "Forget it, Jake, it's Chinatown."
Labels: biases, current events, pedophilia, personal integrity, rape
From the mailbag: two for the "unclear on the conc...
Gosh, when you put it like that, it kinda sounds s...
What matters is he gets to play the Christian Pers...

redpajama_set_name: RedPajamaCommonCrawl


text:
package yanagishima.controller;

import static yanagishima.util.DownloadUtil.downloadCsv;
import static yanagishima.util.DownloadUtil.downloadTsv;
import static yanagishima.util.HistoryUtil.createHistoryResult;
import static yanagishima.util.PublishUtil.canAccessPublishedPage;

import java.util.HashMap;
import java.util.List;
import java.util.Map;
import java.util.Optional;

import javax.servlet.http.HttpServletResponse;

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.PostMapping;
import org.springframework.web.bind.annotation.RequestParam;
import org.springframework.web.bind.annotation.RestController;

import io.swagger.annotations.Api;
import lombok.RequiredArgsConstructor;
import lombok.extern.slf4j.Slf4j;
import yanagishima.client.fluentd.FluencyClient;
import yanagishima.config.YanagishimaConfig;
import yanagishima.model.User;
import yanagishima.model.db.Comment;
import yanagishima.model.db.Publish;
import yanagishima.model.db.Query;
import yanagishima.model.db.SessionProperty;
import yanagishima.service.CommentService;
import yanagishima.service.PublishService;
import yanagishima.service.QueryService;
import yanagishima.service.SessionPropertyService;
import yanagishima.util.AccessControlUtil;

@Slf4j
@Api(tags = "download")
@RestController
@RequiredArgsConstructor
public class ShareController {
  private final PublishService publishService;
  private final QueryService queryService;
  private final SessionPropertyService sessionPropertyService;
  private final CommentService commentService;
  private final YanagishimaConfig config;
  private final FluencyClient fluencyClient;

  @GetMapping("share/csvdownload")
  public void get(@RequestParam(name = "publish_id", required = false) String publishId,
                  @RequestParam(defaultValue = "UTF-8") String encode,
                  @RequestParam(defaultValue = "true") boolean header,
                  @RequestParam(defaultValue = "true") boolean bom,
                  User user,
                  HttpServletResponse response) {
    if (publishId == null) {
      return;
    }

    publishService.get(publishId).ifPresent(publish -> {
      String publishUser = publish.getUser();
      String requestUser = user.getId();
      String viewers = publish.getViewers();
      if (!canAccessPublishedPage(publishUser, requestUser, viewers)) {
        AccessControlUtil.sendForbiddenError(response);
        return;
      }
      String fileName = publishId + ".csv";
      downloadCsv(response, fileName, publish.getDatasource(), publish.getQueryId(), encode, header, bom);
    });
  }

  @GetMapping("share/download")
  public void download(@RequestParam(name = "publish_id", required = false) String publishId,
                       @RequestParam(defaultValue = "UTF-8") String encode,
                       @RequestParam(defaultValue = "true") boolean header,
                       @RequestParam(defaultValue = "true") boolean bom,
                       User user,
                       HttpServletResponse response) {
    if (publishId == null) {
      return;
    }

    publishService.get(publishId).ifPresent(publish -> {
      String publishUser = publish.getUser();
      String requestUser = user.getId();
      String viewers = publish.getViewers();
      if (!canAccessPublishedPage(publishUser, requestUser, viewers)) {
        AccessControlUtil.sendForbiddenError(response);
        return;
      }
      String fileName = publishId + ".tsv";
      downloadTsv(response, fileName, publish.getDatasource(), publish.getQueryId(), encode, header, bom);
    });
  }

  @GetMapping("share/shareHistory")
  public Map<String, Object> get(@RequestParam(name = "publish_id") String publishId, User user,
                                 HttpServletResponse response) {
    Map<String, Object> body = new HashMap<>();
    try {
      publishService.get(publishId).ifPresent(publish -> {
        String publishUser = publish.getUser();
        String requestUser = user.getId();
        String viewers = publish.getViewers();
        if (!canAccessPublishedPage(publishUser, requestUser, viewers)) {
          body.put("publishUser", publishUser);
          body.put("accessDeniedFlag", true);
          return;
        }
        if (publishUser != null && publishUser.equals(requestUser)) {
          body.put("publisherFlag", true);
          body.put("viewers", viewers);
        }
        String datasource = publish.getDatasource();
        body.put("datasource", datasource);
        String queryId = publish.getQueryId();
        body.put("queryid", queryId);
        Query query = queryService.get(queryId, datasource).get();
        body.put("engine", query.getEngine());
        List<SessionProperty> sessionPropertyList = sessionPropertyService.getAll(datasource, query.getEngine(),
                                                                                queryId);
        createHistoryResult(body, config.getSelectLimit(), datasource, query, true, sessionPropertyList);
        Optional<Comment> comment = commentService.get(datasource, query.getEngine(), queryId);
        body.put("comment", comment.orElse(null));
      });
    } catch (Throwable e) {
      log.error(e.getMessage(), e);
      body.put("error", e.getMessage());
    }
    return body;
  }

  @PostMapping("share/updateViewers")
  public Map<String, Object> updateViewers(@RequestParam(name = "publish_id") String publishId,
                                           @RequestParam String viewers,
                                           User user,
                                           HttpServletResponse response) {
    Map<String, Object> body = new HashMap<>();
    try {
      publishService.get(publishId).ifPresent(publish -> {
        String publishUser = publish.getUser();
        String requestUser = user.getId();
        if (publishUser != null && publishUser.equals(requestUser)) {
          String lowerViewers = viewers.toLowerCase();
          publishService.update(publish, lowerViewers);
          body.put("viewers", lowerViewers);
          emitPublishEvent(publish, lowerViewers, "share/updateViewers");
        } else {
          AccessControlUtil.sendForbiddenError(response);
          return;
        }
      });
    } catch (Throwable e) {
      log.error(e.getMessage(), e);
      body.put("error", e.getMessage());
    }
    return body;
  }

  private void emitPublishEvent(Publish publish, String viewers, String path) {
    Map<String, Object> event = new HashMap<>();
    event.put("publish_id", publish.getPublishId());
    event.put("datasource", publish.getDatasource());
    event.put("engine", publish.getEngine());
    event.put("query_id", publish.getQueryId());
    event.put("user", publish.getUser());
    event.put("viewers", viewers);
    event.put("path", path);
    fluencyClient.emitPublish(event);
  }
}


A layoff can be an unpleasant experience and probably not one you want to relive over and over during interviews. The way you handle this topic can make or break an opportunity to move forward with your career and leave the past behind.
• DO be the first one to bring up your layoff. Many times a recruiter starts off with, "Tell me about yourself". Tell them about your career achievements and goals first, and then take the opportunity to explain your recent layoff. You can explain it on your own terms, instead of letting the interviewer formulate questions about it. Avoiding or hiding the issue only makes your interviewer think you did not take the layoff well or that you have more to hide.
• DO mention if it is related to the recession. Today, even though layoffs can be embarrassing, many recruiters are not surprised when candidates mention a layoff resulting from the poor economy.
• DO mention if you were part of a mass layoff (one of many or your whole department). A mass layoff takes the attention off why you, personally were laid off. A single person getting laid off makes a recruiter wonder. A good way to describe a mass layoff is, "There was a staff decrease. Two hundred positions were eliminated, including mine."
• DO tell them what you have been doing in your time away from work. Be prepared because they do ask about this. Always tell them that job-searching and networking has become your number one priority! Tell them if you took a month to relax. Tell them if you have been doing consulting and freelance work. Be honest.
• DO NOT make it a complex story. If you are still upset about your layoff, do not let it show or ramble on about why you were let go. Telling a complicated story (there was reorganization, and your boss told you not to worry, but they kept your co-worker instead because she had more experience...) indicates that there was more reasoning behind your layoff. Simply say, "There was reorganization and unfortunately my position was eliminated." Move on to the next question.
• DO NOT speak negatively of your last employer, co-workers or the job itself. This is very unprofessional, and again, makes your interviewer think twice about why you were laid off.
• DO NOT forget that you can tell them if you are uncomfortable answering. If your interviewer keeps asking about it, tell them you prefer not discussing it. This does not affect whether you get the job or not.


Meaning: Amethyst is a great all round healing stone. It's a great stone for people new to working with crystals and children. It helps awaken the intuition and spiritual connections, along with trusting in ones' gifts / wisdom. Great for working on opening / strengthening the third eye chakra and useful during meditation.