214 karma · joined April 25, 2008
That is what this placebo situation demonstrates, more than anything. YOU are responsible for YOUR condition.
Nitrates exist in fertilizer - and thats what folks make bombs out of.
Weed is often fertilized with nitrates, and trace amounts of these elements are present in your sweat, in your pee, and so on. When you go through a bomb detector after a heavy weed weekend or so, you're going to be flagged for closer inspection.
This was explained to me by a security agent at an airport I was travelling through after a heavy week in Amsterdam.
Darn. What a shame. Guess I'm not gonna learn Ruby now.
On a lighter side, for some reason Ruby reminds me of "The Mighty Boosh" .. its supposed to be great, amazing, and all the younger kids are into it, but when I actually sit down and try to comprehend "why?" (no pun intended), its just a big fat meh.
I work on SIL-4 rated systems for life-protection applications. Absolutely ZERO TOLERANCE for warnings is a requirement in this job, and every single time it has been addressed, the warning gave us a clue how to fix something. Whether it was the code that needed fixing, or the compiler - either way, the alert is there. Ignore at your own peril.
WARNINGS := -Wall -W -Wunused-parameter -Wmissing-declarations
WARNINGS += -Wstrict-prototypes -Wmissing-prototypes -Wsign-compare
WARNINGS += -Wconversion -Wshadow -Wcast-align -Wparentheses
WARNINGS += -Wsequence-point -Wdeclaration-after-statement -Wundef
WARNINGS += -Wpointer-arith -Wnested-externs -Wredundant-decls
WARNINGS += -Werror -Wdisabled-optimization -pedantic
CFLAGS += $(WARNINGS)
Note: -pedantic is pretty good if you really wanna learn how to write code that will work properly.
Also: Treating Warnings as Errors is a good thing. You'll learn a lot, and the most important thing will be: handle all warnings. Do not release code until it builds clean.
For example for a music-editing software project (internal, not publically released) I once used SVG as the primary User interface description language, with nodes named according to the verbs and objects in the UI paradigm, with the DOM structure being modified from a C++ application as needed depending on realtime input from the user.
It works fabulously for this .. All I had to do was provide a dictionary of key node names to a UI designer, tell them "whatever you call a 'dial' has to have a 'needle', and then it will work for all controls that are using your dial skin", and hey-presto: instant UI appeal! Without any major coding changes it was possible to have very fresh, very appealing user interfaces built up by artists overnight .. and another thing I found interesting was that those artists I worked with that understood that the Node Editor was the primary interface to my program, were able to get really nice stuff done, fast, and with enthusiasm.. whereas those who complained that SVG wasn't Illustrator and that they were /never/ going to learn Inkscape to build the GUI and that I had to learn to use 'the real tools .. like Illustrator' .. well, that was just a waste of time.
So my personal experience with SVG has been superb .. I really think its an excellent data form for design user interfaces and, given the appropriate strategy for how to lay out SVG nodes in a manner that makes sense (hint: group), it can be very fun for artistic/creative hats to participate directly in the skinning of an application ..
My how far we've come.
It sure is fun to dive into Android, for example, and get some context, and then another week spend some time with the AVR compiler.. then the Beagleboard, etc.
Once he gets older, I want to move us to somewhere in Asia, perhaps India, and give him another language to speak, which we will learn together. I can't think of a greater gift to give your child than another language, personally. It really truly opens the world to him.
Of course, I'm a programmer. Language is my bread and butter. To be truthful, I'm a bit ashamed that I haven't learned as many human languages as computer languages, but there is still time for that.. ;)
A pity, because they sure are shiny.
Better that it just remains curious, and that we don't use AGC Version 1.0 for future launch attempts ..
Thats why, its good code. ;)
Palestine: Our children are dying in the streets, we live in a ghetto of Israeli design, we will fight you with whatever we have.
Israel: We have nukes. We will use them on innocents at our own whim.
It holds its nuclear arsenal in conditions guaranteed to instill fear in governments around the world, and if indeed the Israeli state holds the key to diminishing the threat of radiation sickness as a result of the use of these weapons, then the threat level just increased.
It depends, also, on the hardware integration. Hey, good thing there is a VM around to handle this issue.
One thing that I think we all have to take into account is the fact that the rules for Cell Network access are a lot different than what we're used to for general purpose computing networks. The fact remains that these networks are extremely, rigorously, monopolized and maintained by groups that are not going to give them up without a fight.
Its an underlooked fact that cell networks are considered a military asset. Every single cell tower, its location, and its operational condition are monitored by the Pentagon on a realtime basis. You do not get access to these towers without permission.
It should come as no surprise that stringent control is being applied to the terminals used to gain access to these networks. For sure, we have a consumer mentality about it - freedom of choice, freedom to buy, freedom not to use, etc.
But the raw hardware on the backend: it does not belong to you. You are being granted permission to access it by the military-industrial complex which controls the means and resources by which the asset is maintained, stringently.
This is bleeding through, all the way through, and Apple are doing a pretty good job of picking up the attitude. Seriously.
The nail on the head issue is this: Apple are making buck$ from all this. They don't care a damn. Android, well .. Google may have its nefarious plans for us all, data-wise, but at least I have a lot more control, as a developer, over what happens. And frankly, I think the feedback cycle with Android users has been a much more positive one than with the iPhone crowd.
I sure hope Apple loosen up a little, though I won't be counting on it. I'll just focus on Android as my primary platform for now. Its better for me, and better for my users: and thats what really matters.
Thus, its not a Linux distribution. They could just as easily have chosen ChorusOS or vxWorks or some other kernel .. the only advantage they have in using Linux is the fact that Linux runs on tons more hardware than anything else ..
Reading about how to stop being un-productive is .. well .. unproductive. Not getting shit done? Go do something!