Welcome to TiddlyWiki created by Jeremy Ruston, Copyright © 2007 UnaMesa Association
[[source|http://www.foodnetwork.com/food/recipes/recipe/0,,FOOD_9936_11125,00.html]]
!!Ingredients
#2 whole slabs baby back ribs
''Dry Rub''
#8 parts tightly packed brown sugar
#3 parts kosher salt
#1 part chili powder
#1 part something else
**example - (equal parts) group black peper, cayenne pepper, jalepeno seasoning, Old Bay seasoning, rubbed thyme, onion powder
''Braising Liquid''
#1 C white wine
#2 T white wine vinegar (or any other vinegar)
#2 T Worcestershire sauce
#1 T honey
#2 cloves garlic, chopped
!!Directions
#Combine dry rub, mix well
#Place each slab on heavy duty aluminum foil, shiny side down
#Sprinkle each side of slab with dry rub and pat into meat
#Seal aluminum foil, refrigerate for at least 1 hour (or overnight)
#Pre-heat oven to 250º F
#Combine braising liquid, microwave 1 min
#Place ribs (still in aluminum foil) on baking sheet
#Open one end of aluminum foil on each slab and pour half of braising liquid into each
#Tilt baking sheet to equally distribute braising liquid
#Braise ribs in oven for 2.5 hours
#Transfer braising liquid to medium saucepan
#Bring liquid to simmer, reduce until thick syrupy consistency (reduced about half, about 5 minutes)
#Brush glaze on ribs
#Broil until glaze caramelizes, ''do not leave unattended!''
#Slice each slab into 2 rib portions
#Toss with remaining glaze
[[recommended levels for auto insurance|http://ezinearticles.com/?Recommended-Levels-for--Your-Auto--Insurance&id=112121]]
!!Ingredients
*Country style ribs
*Marinade sauce
**Equal parts soy sauce, sugar, rice wine
**1/3 part hoisin sauce
!!Directions
#Mix sauce together
#Stir in cornstarch
#Place ribs in pan along with marinade
#Let sit 30 min
#Pre-heat oven to 400º F
#Bake until inside temperature is 170º F, ~60 min depending on size of ribs
#Pour sauce into pot, bring to boil
#Thicken with mixture of cornstarch and water
#Slice pork with thickened sauce
!Ingredients:
*4 lb beef short ribs
*1 c. onion (chopped)
*1 t salt
*1/2 t pepper
*2 T oil
*sauce:
**3/4 c. ketchup
**3 T Worcestershire sauce
**2 T prepared mustard
**1 T soy sauce
**2 T sugar
**1 T lemon juice (optional)
!Directions
#Place ribs, salt, pepper in 4 Qt dutch oven. Cover with water. Bring to boil. Cover and simmer 1.5-2 hours
**this can be done the night before
#Drain ribs
#Heat oil. Cook onions until tender
#Add ribs, onions, and sauce. Simmer for 0.5-1 hour or until ribs are tender, turning the meat so that it is covered by the sauce (and does not dry out or burn)
#Serve as is or grill
##Place on rack 6 in. above hot coals
##Grill 10 min
##Baste ribs with sauce, turning occasionally
Provides ''3-4'' servings
!!Directions
#Clean chicken pieces (e.g. thighs, leg quarters)
#Marinade with sauce (e.g. Lawry's Marinade) for 30-60 min
#Pre-heat oven to 350º F
#Place chicken on a slotted pan (to allow fat to drip)
#Bake chicken, skin down for 20 min
#Remove chicken from oven, cover with any leftover marinade, and flip
#Bake chicken, skin up for 20 min
#Remove and let rest
#Ensure chicken is cooked
**Poke chicken at thickest part
**Liquid will run clear when fully cooked
!!Ingredients
*7 bone roast
*onion
*carrots
*potatoes
*celery
*frozen peas
*corn starch
*seasoning
**salt
**pepper
**soy sauce
**thyme
**bay leaf
**whatever else you want
!!Directions
#Boil meat and sliced onion for 3 hours
**Can be done the night before
#Remove meat from stew
#Add sliced carrots and celery to simmering stew, cook for 30 min
#Peel, cut, and boil potatoes separately for 15 min
#Remove fat and cut meat into bite-sized pieces
#Season simmering stew to taste
#Add meat to stew
#Bring stew to boil
#Thicken if desired
##Thoroughly mix corn starch with cold water
##While stirring boiling stew, slowly pour corn starch mixture
##Allow to re-boil, repeat if desired
#Reduce to simmer
#Add cooked potatoes
#Add frozen peas
!!Ingredients
*1 lb egg noodle
*1 T butter or margarine
*3/4 cup onion, chopped
*3/4 lb boneless beef sirloin or flank steak, cut into thin strips
*1 t beef buillon or 1 cube dissolved in 2/3 c hot water
*3/4 c milk
*1-1/2 T flour
*1-1/2 T Worcestershire sauce
*8 oz cans mushrooms, drained
*1 c sour cream
*Salt and pepper
*Parsley (optional)
!!Directions
#Melt butter in large skillet over medium heat
#Add onion, cook until tender
#Add beef, cook until tender
#Stir bouillon, milk, flour, Worcestershire sauce, and mushrooms together
#Add mixture to skillet
#Heat to boil, reduce heat to low
#Cook noodles according to package directions
#Stir sour cream into beef mixture
#Season to taste with salt and pepper
#Spoon over hot noodles
#Sprinkle with parsley, if desired
''Serves 6-8''
''Cook time: ~30 minutes''
[[Binary Trees|http://cslibrary.stanford.edu/110/BinaryTrees.html]] - on Section 2 problems
!!Directions
#Fill pot with enough water to cover chicken
#Clean chicken
##Remove neck from body cavity, lay aside
##Remove viscera (kidneys, liver, etc), lay aside
##Remove any remaining feathers
#Bring water to boil
#Dip chicken into boiling water so that boiling water enters body cavity
#Remove chicken from boiling water after dipping
#Re-boil water
#Place chicken into boiling water
#Remove chicken after 20 min*
#Cut off chicken breast
#Place chicken back into boiling water
#Remove chicken after 20 min*
#Remove all remaining meat
#Serve with sauce
**e.g. Oyster sauce, (Flying Horse brand) Sweet Chili Sauce
''* - 20 min for a 4 lb chicken''
Also check out what I know about [[Boiled Chicken Experientially]]
!!Directions for chicken broth
#Place viscera, neck, and remaining carcass into boiling water
#Bring to boil
#Simmer for 1-2 hours
#Refrigerate overnight
#Remove solidified fat
#Re-boil broth
#Simmer for 2 hours
#Remove bones, etc
''2008-05-13''
Boiled 4.5 lb chicken for 28 min, then 22 min. White meat a little dry, dark meat fine. But this chicken was a little bit frozen
''2008-06-11''
4.93 lb chicken for 21 min, then 20 min. White meat pretty good, but a tiny bit overdone. Dark meat fine. Chicken was nearly thawed.
!!Ingredients
*Onion, chopped and grilled
*Chicken, cooked (can be leftover)
*Corn tortillas
*Shredded cheese
*Enchilada sauce, green (28 oz)
*Olives, sliced (optional)
*Jalapeños (optional)
!!Directions
#Pre-heat oven to 350º
#Create layers of all ingredients (except enchilada sauce) in pan
#Pour enchilada sauce over top
#Bake 30 min
!!Ingredients
*Flank steak
*Wide rice noodles ("fun" in Chinese)
*Bean sprouts (and/or some other vegetable)
*Olive oil
*Garlic
*Dark soy sauce
*Regular soy sauce
*Corn starch
!!Directions
#Slice flank steak diagonally and place in pan
#Cover with regular soy sauce and corn starch, rub in with fingers
#Heat oil in wok
#Add steak and partially cook (i.e., leave some parts rare)
#Remove from wok
#Heat more oil in wok
#Add chopped garlic
#Immediately place separated noodles into wok
#Color and moisten with dark soy sauce while cooking
#Mix in bean sprouts
#When almost ready, mix in steak
''Theology''
[[Sermon References]]
[[Christianity In Science]]
''Christian Living''
[[Dating Articles]]
[[Article on Greed|The Stench of Dead Presidents]]
''Other religions''
[[Christianity vs Islam]]
[[Creation articles|http://www.creationontheweb.com/content/view/3547/]]
[[Skeptical Christian blog: Gap in theistic arguments|http://www.skepticalchristian.com/t_episode14.htm]]
[[Faith facts|http://www.faithfacts.org/islam.html]]
[[Diffie Hellman|http://en.wikipedia.org/wiki/Diffie-Hellman_key_exchange]]
[[Sorting algorithms|http://en.wikipedia.org/wiki/Sorting_algorithms]]
[[SSH|http://en.wikipedia.org/wiki/Ssh]]
Changed tiddlers:
[[PageTemplate]]
[[contentFooter]]
[[StyleSheet]]
[[Customize Aquamacs|http://www.emacswiki.org/cgi-bin/wiki/CustomizeAquamacs]]
[[dance like Michael Jackson|http://www.tess-impersonates-mj.com/school.htm]]
''Gender Specific''
[[Single Guy References]]
[[Single Girl References]]
''Gender Neutral''
[[Love & Marriage: Luther Style]]
[[Theology of Sexuality|http://www.pureintimacy.org/gr/theology/]]
!!Love & Dating Series
''originally on Focus On The Family's blog [[boundlessline|http://www.boundlessline.org]]:
[[Love & Dating 7: Love]]
[[Love & Dating 6: Managing Expectations]]
[[Love & Dating 5: Being Proactive]]
[[Love & Dating 4: Moving Toward Clarity]]
[[Love & Dating 3: The Harm In Hanging Out]]
[[Love & Dating 2: Holding Out]]
[[Love & Dating 1: Be Realistic]]
A great guy. Haha this is his so he can think and write whatever he wants.
Yeah he's an [[INTP]]
[[Google tutorial|http://code.google.com/edu/parallel/dsd-tutorial.html]]
Does not necessarily apply to computer program, but it actually is a reference to mathematical programming.
Basically it is:
#Overlapping subproblems - Multiple problems that are similar
#Optimal substructure - Optimal solutions to subproblems can be used in order to find the optimal solution to the overall problem
#Memoization - Term that has a special computer science meaning. Similar to memorize, but it means to store or reuse solutions to previously calculated problems so that they don't have to be reused. [[source|http://en.wikipedia.org/wiki/Memoization]]
[[source|http://en.wikipedia.org/wiki/Dynamic_programming]]
[[read this|http://www.topcoder.com/tc?module=Static&d1=tutorials&d2=dynProg]]
[[Who Needs Sit Ups?|http://www.armytimes.com/offduty/health/ONLINE.MUSCLE.SITUPS/]]
[[Body weight exercises|http://www.fightingarts.com/ubbthreads/showflat.php?Cat=0&Number=15833023&an=0&page=0#Post15833023]]
[[Argument for body weight exercises (from a gymnast)|http://www.t-nation.com/readTopic.do?id=512003]]
[[Barefoot running - sportsci.org|http://www.sportsci.org/jour/0103/mw.htm]]
!!Ingredients
*1 1/4 cup whole milk (I used low fat milk + cream)
*4 egg yolks
*3/4 cup granulated sugar (I would use 1/2 cup next time), divided in half
*2 cups Greek yogurt (I would suggest Fage or Trader Joe's Greek Style, full fat or 2%)
*1 tablespoon vanilla extract
!!Directions
#Melt half the sugar in the milk and heat over low heat until steam rises from the milk. Do not boil, but don't panic if you get it to the point of bubbling a bit.
#Meanwhile, whisk the egg yolks with the remaining sugar until pale yellow and fluffy.
#Slowly, by dribbles, add half a cup of milk to the egg yolk mixture, whisking continuously to prevent curdling.
#When the egg yolks are thinned out, pour it slowly back into the milk, whisking continuously.
#Cook the custard over medium low heat, stirring often.
#You'll need to cook until the mixture is somewhere between 175 and 180 degrees, or until you can coat the back of a spoon with it and the custard will hold a line if you run your finger through it. I find the spoon test more effective than my thermometer.
#Cool the custard in an ice bath or uncovered until it's room temperature. Whisk in the vanilla and yogurt, then chill overnight.
#Churn in ice cream machine
#Put in freezer
!!!More Notes
It's not as decadent as homemade ice cream, but people who like the tang of good yogurt will probably enjoy this. I personally think it goes better with fruit than real ice cream does. And if you use low fat ingredients, less sugar, and a ton of fruit it's an incredibly delicious frozen treat that's as healthy for you as a bowl of yogurt, half an egg yolk, and no more sugar than you'd get out of a tablespoon of jam or honey. Much tastier than flavored yogurts (bleh!), and probably less sugary too.
[[source|http://www.chezpei.com/2006/09/frozen-yogurt.html]]
!!Ingredients
*2 cups Greek Style yogurt
*2/3 cup Sugar
*1 Tablespoon Vanilla
!!Directions
#Mix together
#Chill 1-3 hrs
#Put in the ice cream maker for 20 mins
[[source|http://www.chowhound.com/topics/376016#3463806]]
also very similar to [[this recipe|http://www.101cookbooks.com/archives/a-frozen-yogurt-recipe-to-rival-pinkberrys-recipe.html]]
!!Ingredients
*6 thin pork chops
*Marinade
**1 t rice wine
**2 T soy sauce
**1 T sugar
**1 t vinegar
**1/2 t black pepper
**1/2 t sesame oil
**2 T cornstarch
**5 cloves garlic, minced
!!Directions
#Pierce chops several times with fork
#Marinate porks chops for 1 hour, turning 2 or 3 times
#Heat skillet and add 1 T vegetable oil
#Cook pork chops, about 3-4 min
##Sear on high 10 sec,
##Cook on medium the rest of the time
*[[Mac Links]]
*[[Virtual Machine|http://virtualbox.org/]]
*[[Picture to PDF converter|http://bmeps.sourceforge.net/]]
*[[Rsnapshot backup|http://www.rsnapshot.org/]]
[[Quality, Quantity or A Fast Time on the Stopwatch]]
[[Exercise Links]]
[[Measure Body Fat Percentage]]
[[Recipes|recipe]]
[[Home Solutions|http://www.dumblittleman.com/2007/08/tons-of-homemade-solutions-for-house.html]]
[[Perfectly cook vegetables|http://www.realsimple.com/realsimple/gallery/0,21863,1108703,00.html?]]
''Buying a home''
[[home-buying mistakes|http://www.boundless.org/2005/articles/a0001745.cfm]]
[[INTP relationships|http://www.personalitypage.com/INTP_rel.html]]
[[INTP profile|http://www.intp.org/intprofile.html]]
An Introduction to Computer Bits for the Newbie ([[original link|http://pubs.logicalexpressions.com/Pub0009/LPMArticle.asp?ID=247]])
I once heard someone describe a bit as the smallest particle inside a computer, so let's get something straight, right from the start. A bit is not a particle. A bit is "no-thing". A bit is a digit - derived from the words, ''BI''nary digi''T''. Binary means 2. The binary number system contains only two digits, 0 and 1. Those digits are what we call bits. One bit, a 0 or a 1, is the smallest unit of data a computer can work with. 0's and 1's are ALL your computer can work with.. A computer does not understand our language.
Any data you input into your computer, whether it be numbers, documents, graphics, sound, or video, has to be translated into a language the computer understands which is the binary "language" - base 2 arithmetic - nothing but zeros and ones. Your computer is a number cruncher that is constantly doing binary calculations whenever you use it. The binary system is the native language of your computer, often referred to as machine language..
The idea to use binary in computers dates back to the mid 1930's, but the idea for that idea dates back to the mid 1800's to the time of English mathematician George Boole who developed Boolean algebra, a system of logic that could be applied to elaborate expressions (statements), proving them true or false and that fit perfectly with the binary system. It took about 85 years before anyone got the idea to apply the logic to circuits - that true or false could be replaced by on and off and 1 and 0. i.e. “when A = 0, not A = 1, when A = 1, not A = 0”.
The first prototype computing device using binary with Boolean logic was demonstrated in 1940 (by Professor John Atanasoff and student Clifford Berry at Iowa State University) At that time, transistors hadn't been invented yet, vacuum tubes were still being used but Boolean algebra became a major guide in the development of every electronic computer we know today. The outstanding feature of Boolean algebra that sets it apart from other types of mathematics, is that it deals with expressions(statements), not numbers or equations. Today, using Boolean is common in searching the internet (and – not – or) which most computer users know, but less know the important role Boolean played in the actual development of the computer. Good old George, he was a brilliant self taught mathematician, but poor old George too—he had an early and unfortunate death.
So, why binary? Why just zeros and ones? To understand that you need to realize that a bit is a visual assignment to an electrical state. At its core, your computer is nothing more than a vast collection of transistor switches—millions of them compose your processor—your Central Processing Unit (CPU). For example a Pentium 4 can have 42 million transistors. These micro transistors are constantly being switched off and on, at incredible speeds, whenever you use your computer .What determines how they are switched, is whatever software you are using. Your program provides the set of instructions for the CPU to fetch and decode.
Now what does that have to do with bits? EVERYTHING.
Transistors are what give us our bits! A single transistor can be in one of two electrical states. It can be off (open) or it can on (closed). When current is flowing through it(voltage high) it is ON. When current isn't flowing through it (voltage low), it is OFF. We use 0 to represent OFF and 1 to represent ON. 0 = switch OFF , 1 = switch ON . i.e:, off-on-off-on-off-on-on-off = 01010110 (the letter V) = 8 bits. It's a perfect match for the binary system - simple and fast, since there's only 2 values to switch between, as opposed to 10 (which was used in the early days of computing).
So, as you can see, a bit really is just an assignment to an electrical or voltage condition and that a single bit can be in one of two conditions (off or on). This represents the minimum the computer can process or store and is what we mean when we define a bit as the smallest unit of data a computer can work with.
!!!Still a bit confused?
Let's use a simple analogy to make the concept a "bit" more clear.
Think of the light switch on your wall. Like a single transistor, it can only be in one of two states. On or off. When you turn the switch on, current flows and the light turns ON. When you flip the switch off, the current stops flowing and the light turns OFF. You can think of those on and off states as bits. LIGHT ON=1 LIGHT OFF=0
Now imagine a huge billboard filled with rows and rows of little lights each one having a separate switch and you have a master switchbox to control them all. Each switch on the switchbox is labeled 1 for ON and 0 for OFF. It's not hard to visualize that by turning some switches on and some off, you might figure a combination to display your name in lights. It would just be a light pattern you formed by using off and on light switches which you represented by 0s and 1's. You might then save that pattern—you could see what combination of 0's and 1's formed your name—and perhaps make some shortcut combo switch that would recall that light pattern with just one flip. Depending on your intelligence, logic and electronics skills, there would be a number of ways you could probably improve the functioning.
In the very crudest sense, you made a computer (the worst computer ever built <lol>).
You can think of your keyboard as the switch box, the switches themselves the transistors (your processor) and the billboard your monitor. And working on any changes or improvements would make you a computer programmer—your set of instructions telling the machine what to do.
Also imagine if that was base 10 instead of base 2. Having to put each light through 10 different settings to find the right setting, surely would make the computer slower.
In a real computer, typing my name VIC would have this bit pattern:
010101100100100101000011
That represents 24 bits—count them. However, the only way the computer sees them is as electrical conditions.
off on off on off on on off off on off off on off off on off on off off off off on on
In the light switch analogy, the 0's and 1's would represent the off and on positions needed to form VIC in lights.
A lot of bits for just 3 letters you might be thinking.
But think about this—those 24 bits can be rearranged to form a multitude of different patterns.
It might not seem apparent, but in fact, there are 16,777,216 unique possibilities with 24 bits! If that were a lottery ticket, your odds of winning (getting the right combo of 24 digits) would be 1 in 16,777,216 (that's 16 MILLION....).
Obviously, the more bits you have the more unique patterns you can form or the more instructions the computer can process.
Let's start with a single bit. One bit can't do very much.
As we already know, one bit can represent only two values, 0 or 1
1. The bit can be off
2. The bit can be on
One transistor can perform a 2 bit function. The light switch on your wall would be like one bit. It can turn the light on or it can turn the light off. Nothing else.
With two bits, it would be like having two light switches on your wall. Two bits can have 4 different values.
1. The first bit can be off and the second bit on. (01)
2. The first bit can be on and the second bit off. (10)
3. Both bits can be on. (11)
4. Both bits can be off. (00)
The number of possible unique values DOUBLES with EACH bit you add. (2 to the power)
It's an amazing exponential growth as you will see.
Therefore, 3 bits = 8 values. Now the possibilities are:
1. Off Off Off (000)
2. Off Off On (001)
3. Off On Off ( 010)
4. Off On On ( 011)
5. On Off Off (100)
6. On Off On (101)
7. On On Off (110)
8. On On On (111)
4 bits = 16 values
5 bits = 32 values
6 bits = 64 values
7 bits = 128 values
8 bits = 256 values
We call a collection of 8 bits a byte and it takes one byte to form one plain character(a number, letter or symbol).
If you count all the common printable characters on your keyboard—26 lower case letters, 26 upper case letters, 10 numbers, and 32 punctuation keys—you come up with 94 keys. As you can see from the bit values in the sample list above, 7 bits can have 128 unique values. This is more than enough to display all those characters and others, and in fact, 7 bits are enough to identify each character.
I.e., A= 1000001 (in your computer, however, A is stored as 01000001 since 8 bits per character is the standard—read on).
The binary values of all those keyboard characters have been standardized into what is known as the ASCII code (pronounced askey) which stands for American Standard Code for Information Exchange, and each character has been assigned a decimal value to make it easier for us to deal with the long binary values.
For example, A = 65 B=66, C=67, D=68, and so on. Try it—open a text document and press ALT + 65 on the number pad of your keyboard (make sure to have the num lock on). It should display the letter A. Of course, your computer only sees the binary value, regardless if you press A directly or Alt + 65.
There are 128 characters( the complete number of possibilities for 7 bits) in the Standard ASCII code (numbered 0 to 127). The first 32 codes represent non printable characters, many of which are obsolete and no longer used. They date back to the days of teletype terminals. ASCII was finalized in 1968, and in case you are not aware, ASCII means plain text. When you hear the term "ASCII" file, it just means a text file—plain and unformatted. ASCII is most commonly used for transmitting data— as when you send a plain text email—and was actually developed as a telecommunication standard.
Here's a chart I made to show you the Standard (0 -127) ASCII character set, with their binary, hex and decimal equivalents.
http://www.personal-computer-tutor.com/ascii.html
If you're observant, you will notice that the chart shows 8, not 7 bits for each character. The reason for this is that the ASCII code was later updated to an extended 8 bit set which is enough for 256 characters. So a 0 value is usually added as the 8th bit.
For example, the character A in original ASCII is 1000001, but you'll usually see it listed as 01000001. And all the characters are stored in 8 bit (one byte) format in your computer.
You can see that too—open up Notepad, type a single character and save. Then look at the File size in Properties.
That 0 bit also serves a function as an error checking or parity bit during transmissions.
Now a bit more about this Extended ASCII Set. As I said, it's an 8 bit code which is enough to encode 256, 8 bit characters—enough for the previous Standard 7 bit set with the extra 0 bit, and the extended characters which consist of 128 special symbol characters that require the full 8 bits to identify. So in total, there are 256 characters in the ASCII code (0 to 255).
However, the extended set is usually shown separately. In other words we have the Standard set covering character numbers 0 to 127 and an Extended set which covers character numbers 128 to 255. Also, the extended ASCII code is not a true standard in the sense that different extended sets exist (using the same codes can give you different characters depending on your computer), but the original was created for the IBM PC and that's the most commonly known set. Here are a few of them, most of which you can get in Windows by pressing Alt + the code or if that doesn't work, use the code at an MS-Dos prompt.
128 = Ç 129 = ü 130 = é 131 = â 132 = ä 133 = à 134 = å 135 = ç 136 = ê 137 = ë 138 = ê 139 = ï 140 = î 141 =ì 142 = Ä 143 = Å 144 = É 145 = æ 146 = Æ 147 = ô 148 = ö 149 = ò 150 = û 151 = ù 152 = ÿ 153 = Ö 154 = Ü 155 = ¢ 156 = £ 157 = ¥
To see the entire extended character set along with decimal, hex and binary equivalents, see my extended ASCII page here:
http://www.personal-computer-tutor.com/extended.htm
!!!Hexadecimal Number System
Though the Decimal system is used for the ascii code, it is not the best number system to represent binary values in a computer. The hexadecimal system is much better and in fact, the most widely used number system to represent binary values. Hex values are used not only for characters, but for specifying colors, memory addresses, and in programming. Also, If you play in the Windows registry at all, you are probably familiar with class id (clsid) keys that follow this alpha numeric format—{441E9D47-9F52-11D6-9672-0080C88B3613}—which are actually hex values. The source of program files are also commonly viewed with in hex format with hex editors.
Hex stands for 6 and decimal stands for 10. Hexadecimal counts 0 to 9, and then A B C D E F Why hex you might be asking? Because it's a compact and more logical and compatible number system to use with binary. It's also easier to use than decimal for mental math (but you would have to become fluent in it as you are in decimal to know). Two hexadecimal digits neatly represent 8 bits:
Example:
00000010 = 41
01000010 = 42
01000011 = 43
One hexadecimal digit represents one decimal digit.
A = 10
B = 11
You can easily confirm this:
Decimal ..... 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Hexadecimal 0 1 2 3 4 5 6 7 8 9 A B C D E F
As you've learned, the highest number of possibilities for 8 bits is 256 in DECIMAL (0 to 255)
In hex, this would translate to 00 to FF.
But still, whether you use 0 to 255, or 00 to FF, to your computer it's only binary bits: 00000000 to 11111111.
All conversions are just man's attempt to make the binary system easier to work with.
As already mentioned, the ASCII code only applies to plain unformatted text. It's what you use when you type a plain text email or inside a notepad document. The one byte per character does not apply to formatted characters such as rich text or html with different font styles, colors and sizes. Such characters would naturally require more than 8 bits and much more than 256 possibilities to show all the variations possible with formatting. But, as we know, each single bit added DOUBLES the unique values possible.
By just adding one more byte, which is made up of 8 bits, the number of unique values jumps to 65,536!
That makes a character standard like the 16 bit Unicode possible which can encode over 65,000 different characters - enough to support almost every language. What a difference a byte can make, eh?
So:
16 bits = unique values = 2 bytes
32 bits = 4,294,967,296 unique values = 4 bytes
64 bits = 8,496,527,156,231,722 unique values = 8 bytes
Even 64 bits doesn't sound like much—only 8 bytes—the ASCII equivalent of ABCDEFGH, but the possible unique values are mind boggling.
Because of this, computers are limited to the number of bits they can handle at one time - 64 bits is the max, currently.
In binary that 64 bits making up the string ABCDEFGH translates to:
0100000101000010010000110100010001000101010001100100011101001000
That shows the maximum number of bits that can be processed at one time to calculate 8,496,527,156,231,722 possible unique results.
And that's basically what is meant when you hear of computers being referred to as 16 bit, 32 bit or 64 bit. The number refers to how many bits the CPU can manipulate at one time or the amount of data it can process per clock cycle.
If in a 32 bit processor, more than 32 bits are needed for a job, the computer needs to do more math work breaking down the numbers and recombining them.
For example, a 32 bit processor can add two 32 bit numbers at one time. For a 16 bit processor to do the same would require two instructions instead of just one to come up with the same answer.
So that means the 32 bit processor can process double the amount of data than a 16 bit processor can, in the same time ( twice as fast). Likewise, a 64 bit processor has the potential to do the job twice as fast as a 32 bit one. The Apple Power Mac G-5 was the first widely available 64 bit system for consumers. However, the majority of home PC's today, are 32 bit, though it shouldn't be long before 64 bit becomes common.
Image quality is also measured by bit—by bit depth—the number of bits used for one pixel.
The more bits per pixel, the higher the image quality. To make this easy to understand, let's again begin with a single bit.
You now know that one bit can only be in one of two states. But it's important to realize that the computer doesn't care what you use to associate those off and on electrical states with. 0's and 1's.can be Yes or No, True or False, Open or Close, Black and White or whatever else. So with a one bit image, we can use Black or White, Red or Blue, or any two colors, which means, all you can expect with a one bit image is a monochrome image—a single solid color. But add 7 more bits, and you have an 8 bit image—and as you've seen in the ASCII section, 8 bits = 256 values. Again those values can be applied to anything logical. So with an 8 bit image, we have an image capable of displaying 256 different colors.
A 16 bit image can have 65,536 color variations.
A 24 bit image can have 16, 777,216 color variations (my name VIC, remember?)
Bit depth is also often specified with video cards, i.e., 32 bit graphics which equates to
4,294,967,296 values and more than enough for realistic 3D rendering.
More bits per anything always equals better quality or performance. Same applies to sound bits—when you hear of sound being referred to as 8 bit or 16 bit, it refers to the sampling size. With 8 bits you can have 256 levels but with 16 bits you can have 65,536 levels. 16 bits also gives you double the dynamic range of 8 bits. 16 bit is the CD standard. Even higher quality is DVD audio which play 24 bit samples.
With sound cards, the bit specification does not refer to sample size. For example, a 32 bit sound card does not mean 32 bit sound quality!
Your CD quality remains 16 bits. 32 bits refers more to the performance of the card—the bit size of the data path—how many bits can travel through at one time. For a 32 bit card it's 4,294,967,296 bits (again, the maximum possibilities for 32 bits). For a 16 bit sound card, the path is 65,536 bits wide. In general, this means the 32 bit card will play your music and sounds more smoothly.
What about bits in relation to memory and hard drives?
In a nutshell, bits—0's and 1's can be recorded (tape drives make this obvious). With RAM, the recording is electrical and, as you know, when you turn off the power, the electricity is gone, and thus so is the data in the RAM chips.
A hard drive on the other hand uses magnetism to permanently record 0's and 1's. So the data remains.
With memory and hard drives, we are dealing with holding and storage capacities only and we measure them in bytes.
1024 bytes = 1 kilobyte
Many hard drive makers misrepresent the capacity of their hard drives by using the decimal system to calculate size which means you can be losing out on several gigs when you buy a new hard drive.
[[Mango languages|http://www.mangolanguages.com/application]]
[[Device Drivers|http://www.freesoftwaremagazine.com/articles/drivers_linux?page=0,3]]
[[Independent Software Vendors|http://live.gnome.org/GuideForISVs]]
[[example|http://www.gigamonkeys.com/book/practical-a-simple-database.html]]
[[lisp book|http://www.gigamonkeys.com/book/]]
[[set up debian lisp/scheme server|http://www.lisperati.com/quick.html]]
[[why lisp is great|http://www.paulgraham.com/avg.html]] (from yahoo! stores creator Paul Graham)
Let's Talk About Dating, Part 1: Be Realistic
by Denise Morris on Mar 10, 2008 at 3:24 PM
So Suzanne and I have decided to do a series on The Line in which we impart all of our wisdom about dating and relationships. (It'll be a short series.)
I'll cover the first issue, so here goes: be realistic.
Because of our culture and the romanticized version of relationships we see in the movies, I think it's easy to get caught up in an unrealistic idea of what love and romance should look like. Girls get accused of having these false expectations a lot-- and they do -- but guys are guilty of it as well.
Because of Hollywood's influence, it's easy for me to believe that the perfect guy will fall into my lap at any moment. He will be gorgeous, smart, funny, well-educated, entertaining and enjoy all the same things I do. He will love me perfectly and bring out the best in me every single day. I think the danger in this attitude is being on the lookout for this person and ignoring anyone who doesn't fit each of these qualifications. This attitude, I believe, will only set me up for disappointment.
First of all, people are people. No one -– including me and you -- is all that great. We all fail and we all have shortcomings. Honestly, I'm never going to find someone who is completely perfect. I do want to be with someone who I work well with and whom I love, but it's important to be realistic when it comes to what I can live with and live without.
Secondly, I think it's important to give people the benefit of the doubt. Most of my girl friends and I are willing to go on at least one date with a guy if he asks (as long as he meets the basic expectations -- loves the Lord, doesn't eat bugs, and so on). We do this because 1) the guy had the guts to actually ask us out, which is awesome. It seems to be rare among lots of guys these days, so we should give them credit when they go for it. 2) You never know what you'll find out when you give someone a chance. He just may surprise you.
Guys, I think you should do the same. Be willing to ask a girl out even if she doesn't meet every expectation you've set up in your mind. Does she want to be more like Jesus? Is she kind? Is she enjoyable to be around? All of these are great reasons to consider getting to know this girl better. It may be scary, but it's worth doing.
Most importantly, I've realized that I need be realistic about love. Those romantic feelings will come and go, which is why much of true love is a choice I have to make. The Bible reinforces this idea in the picture we see of love between God and the chosen nation of Israel. The people of Israel were always running around being unlovable, but God did it anyway -- He kept His promise and loved her even when they didn't deserve it. I think we should work on approaching dating and marriage the same way -- we should choose to love one another because we want to be more like Jesus -- no matter what the other person is doing.
I recently began to pray for God to bring me the man He wants me to love unconditionally -- whatever that may look like. It's a scary prayer. I don't like it. But I realized that so much of my prayers for a husband had to do with someone who would love me, who would make me happy, who would fulfill me. Yes, I hope God brings me someone who will do all those things, but my attitude should be more about how I can serve and love someone, not what they can do for me.
Anyway, Suzanne will follow up later this week with another tidbit of advice. Until then, discuss away.
Let's Talk About Dating, Part 2: Holding Out
by Suzanne Hadley on Mar 11, 2008 at 5:04 PM
I had an interesting conversation on a plane the other day. ([[No rudeness occurred|http://www.boundlessline.org/2008/03/rude-people.html]], thankfully.) I was sitting next to a single, Christian guy (I know, how often does that happen?), and we began discussing the Christian dating scene. "It seems like the majority of Christian singles are holding out for something," my new friend said. "Like the guys are waiting for a pastor's daughter/cheerleader that just popped out of Bible college, and girls are looking for...I don't know, a guy who just returned from a four-year missions trip to Peru."
I smiled at that analysis. I'm sure each single could generate his or her own similar "fantasy." And true, this notion that something better (or cuter or funnier) may be just around the corner, has the tendency to paralyze us in the "choosing" process.
Candice considers this very topic in her article "[[When to Settle|http://www.boundless.org/2005/articles/a0001699.cfm]]." She explains that when she began dating Steve, a friend questioned whether she might be "settling," because Steve planned to use his degree to be a small town principal. Candice writes:
<<<
My friend was a believer in the notion that to marry a man without certain traits or ambitions would be settling. And in her mind, settling was bad. No longer just a guideline, not settling was itself a goal. Something worth striving for. As in: Finish that report for work, lose 20 pounds, get a boyfriend, don't settle.
And so we find ourselves in the midst of a massive shift in marriage trends: women waiting longer than ever to marry, all the while holding out for their soul mate -- "the one." When a nice guy asks a woman out, if the sparks of attraction aren't hot from the start, she turns him down, reasoning, sure, I want to get married someday, but I'm not about to ... settle.
<<<
But this kind of "holding out" may be hurting us in the end. As my new friend observed," It creates this weird vibe. People are always evaluating each other like, 'Are you it? Will you meet the criteria? " That, plus the fear of settling may drive us to pass by perfectly good options. Candice explains:
<<<
Have you ever known a man that you've thought about dating, but in the end, ruled him out because to do otherwise would be settling? If you're holding out for perfection, or have a long list of must-haves, it's possible you're overlooking some good men who are already in your life. Knowing what about a potential mate is worth appreciating and what's just eye candy has everything to do with when you should "settle."
Choosing to marry a man — whomever he is — inevitably involves compromise (on his part, and yours). That's why it's not truly settling. It's just making a decision. Something we do every time we pick one thing over another. In most areas, it's called being decisive. For some reason we've made indecision noble when it comes to dating.
<<<
And that's the crux of this issue. We've spiritualized "holding out." And yet is there even one biblical character who passed up perfectly good marriage options in the name of not settling? No. Read Candice's article. She provides a great list to evaluate whether a person has the potential to be God's best for you. Then move forward with confidence!
Let's Talk About Dating, Part 3: The Harm in Hanging Out
by Denise Morris on Mar 13, 2008 at 12:01 PM
In case you haven't heard, "group dating" has become the spiritual way to date for Christian singles. This method involves guys and girls hanging out in platonic groups. It is supposed to help people build friendships that eventually become "something more." However, the reality is that this group dating mentality has morphed into coed packs of friends who never actually get around to dating. Consider Anna and Cody:
Anna and Cody are part of a group of coed friends hanging out at someone's house. Anna sits down on the couch, strategically leaving a wide open space next to her. Cody wanders over and casually takes a seat next to Anna. They ignore one another.
After about a year and a half of pretending to watch TV, Cody turns and asks Anna how things are going. She answers. They turn back to the TV.
The group of friends decides to hang out this weekend to go hiking. Cody and Anna are pleased that they'll see one another again, but do not let on. They are no fools -- they can't let anyone know that they are interested in one another! Besides, this type of group dating is ideal. There is no commitment and no fear of rejection. Perfect!
------
The whole "guys and girls hanging out all of the time but never actually dating" is somewhat popular in Christian culture. Sometime these group get-togethers are wonderful -- they allow you to meet new people, have fun and spend time with good friends. But, in my opinion, these group outings are not always good, for the following reasons:
For one thing, if you want to be in a relationship with someone, you eventually have to get to know them at a deeper level. Group dating can be great in the beginning -- it's a non-threatening way to figure out who someone is. But groups have a lot of people, a lot of interruptions and a lot of surface-level conversation.
[[An article|http://www.christianitytoday.com/singles/newsletter/mind61011.html]] by Jason Illian talks about why group dating has become popular in Christian culture, but adds that, when it goes on for too long, it can become hurtful:
<<<
The church devised the group dating concept because it recognized the futility and dangers of how most people date in American culture. With pregnancies, diseases, and divorces on the rise, they wanted to protect their flock from having similar heart-wrenching results. I can appreciate their intentions, but going from one extreme to another has not alleviated our problems. It has just given most singles a whole new set of issues to deal with—loneliness, despair, and confusion ranking at the top of the list.
<<<
I think that possible problems that can arise from co-ed groups just "hanging out" for all eternity is that it allows for a lack of commitment on both sides. Girls and guys get a lot of the emotional support that they would be getting from a boyfriend/girlfriend without having to take the risk of possibly getting hurt. Illian thinks this is a bigger issue for the guys:
<<<
One of the biggest problems with group dating is that it allows men to be passive. In a group setting, men can shun accountability and responsibility. They don't have to make any plans because someone else will. They don't have to be responsible for anything because it is easy to disperse ownership with others involved. And they don't have to ask any one girl out because they can enjoy all of them at the same time! Men don't have to be proactive leaders—they can simply be pack hunters.
<<<
Illian points out that marriage is not a group outing. Eventually it has to be two people figuring out how they're going to live life together. In Illian's opinion, one-on-one dating is a great way for men to learn how to lead in a society where they have not been taught what leadership looks like.
As for women, hanging out with guys in groups sometimes feel more emotionally safe. Dating and commitment can be scary because it's possible that your heart can get broken. We've been taught to "guard our hearts" (something we'll address in another post), and group dating seems like a safe way to do that. However, we girls often end up getting emotionally involved even without commitment -- group dating doesn't always protect us from heartbreak. And, when we're constantly willing to hang out with guys without requiring any commitment, we're encouraging behavior that allows for tedious, non-relationship relationships. No bueno.
So, in the end, I think it's great to hang out with friends -- guys and girls. However, as singles who want to move toward marriage, I think we need to be wise and intentional with our time -- including the time we spend just "hanging out."
Let's Talk About Dating, Part 4: Moving Toward Clarity
by Suzanne Hadley on Mar 17, 2008 at 4:32 PM
So I like you. You like me. We're spending time together. But we're not dating.
I'm going to avoid terminology we've used in the past simply because I'm tired of it. Relationships are complex and each one is different. I wrote an article called "[[Not Your Buddy|http://www.boundless.org/2005/articles/a0001200.cfm]]" to address the frustration many Christian singles feel when they have a special friend that seems to stay just that. The person obviously has the potential to be more -- otherwise he or she would be "special."
But how do you move from that ambiguous "we've got a connection" to something more intentional? It's not easy for either the guy or the girl. From the [[article by Jason Illian|http://www.christianitytoday.com/singles/newsletter/mind61011.html]] that Denise referenced in [[her last post|http://www.boundlessline.org/2008/03/lets-talk-abo-2.html]], the author makes this observation:
<<<
The normal model of male-female relationships is quite simple -- you are either dating or you are not dating. But the current Christian model is quite different. Perhaps we got held underwater a little too long during baptism, but our model looks like this: become friends, hang out, get to know one another, see where it goes, talk about possibly getting involved, discuss the north wind and how it may affect the relationship, talk to the youth pastor about it, pray about it, fast over it, court (which may mean dating), date (which may mean courting), and finally, date. Instead of having or not having a romance, we add a million meaningless micro-steps which muddy the already difficult waters.
<<<
So is the problem a lack of decisiveness (as discussed in the post "[[Holding Out|http://www.boundlessline.org/2008/03/lets-talk-abo-1.html]]")? Is it an unwillingness or lack of desire to commit to one option, even if it seems promising? Or is it general confusion about how to navigate the process when it seems so much is resting on it?
The last time I was getting to know a Christian guy, I almost felt paralyzed by all the dating and courtship advice I've absorbed over the years. I had a strong desire to do it just right. And I think that's the point Illian was making. We've made it more complicated than it needs to be. Just commit to it. Like any process in life -- getting a job, making a move, choosing a major, selecting a church -- courtship and dating require a certain degree of commitment to the process. And answers to big questions are revealed through that commitment -- not apart from it. Sometimes the answer will be yes, sometimes it will be no. Everything doesn't need to be decided before engaging in the process.
If you're wondering about the viability of a relationship with someone, take a few simple, intentional steps to test your theory. Being direct and seeking clarity will provide more answers -- and satisfaction -- than hanging on in a relationship shrouded in mystery. And if you've made things complicated for yourself, start afresh ... the simple answer is often the right answer.
Let's Talk About Dating, Part 5: Being Proactive
by Denise Morris on Mar 19, 2008 at 1:30 PM
As [[I mentioned before|http://www.boundlessline.org/2008/03/lets-talk-about.html]], our romanticized ideas of dating, love and marriage sometimes cause us to sit back and wait for that perfect someone to fall right into our laps. The Christian version of this sentiment usually involves [[Bible verses plucked from their context|http://www.biblegateway.com/passage/?search=Psalm 37:4;&version=31;]] and inserted into conversations about relationships.
So, just in case that guy/girl doesn't just magically appear before you one day, this post is about some proactive ways to pursue relationships.
Being proactive can sometimes be more difficult for women -- especially for those who believe that men should be the initiators in relationships. But that doesn't excuse us from being actively involved in the road to marriage. One thing every girl can do is to make herself available to the guy she's interested in. Go to events he'll be at, make an effort to talk to him, let him get to know who you really are.
And sometimes women need to take matters into their own hands. We see this in [[Ruth's situation|http://www.boundless.org/2005/articles/a0001352.cfm]], but hers was unusual. For today's women, sometimes being proactive means pulling away from relationships that aren't going anywhere. If the guy you've been hanging out with hasn't "made a move" then it might be necessary to end whatever sort of pseudo relationship you're involved in. The guy is either 1) not interested or 2) too comfortable with the way things are to define things. Either way, you're going nowhere. Although it may be painful and a difficult transition, sometimes the most healthy thing to do is to let it go.
For guys who are interested in pursuing a girl, Nike would tell you to "just do it." I agree. Take the steps to get to know a girl, ask her out and see where it goes. Be intentional about moving forward in the relationship. Be careful with your words and actions, but don't be paralyzed by the fear of something that might not work out in the end.
One thing that I think both sexes can work on when it comes to proactively pursuing dating is communication. We wrote about this on TrueU awhile back, for both [[the guys|http://www.trueu.org/dorms/menshall/A000000432.cfm]] and [[the girls|http://www.trueu.org/dorms/womenshall/A000000431.cfm]]. Talking things out with the person you're interested in can be very helpful, even if it is awkward or uncomfortable. All of this will help you move toward the [[clarity|http://www.boundlessline.org/2008/03/lets-talk-abo-3.html]] that Suzanne talked about.
But what if there's just no one to pursue?! I feel ya. Finding the right guy/girl can be a challenge. But what can I do (besides complain) to change the situation?
Well, if I'm invited to hang out with a group of people I don't know very well, I should go. It might be uncomfortable to hang out with strangers, but if I do it, they won't be strangers for long. I could volunteer somewhere, do some social networking, get to know people at my church. Put up signs around my neighborhood (totally kidding!!).
Finally, both men and women need to be proactive in praying for their future spouses. For some reason, this one is difficult for me -- I either forget to do it, or I don't see automatic results so it feels useless. But it's obviously not. The Bible tells us to present our requests to God, and relationships should be no different. Pray for God to prepare you and your spouse for one another. Ask Him to give you wisdom and to bring that right guy/girl along.
Even if being proactive in one situation doesn't result in marrying the guy/girl of your dreams, it doesn't mean it wasn't worth it. If we approach things with the right attitude, God can and does use the relationships in our lives to make us more like Himself.
And, hey, at least no one can say you didn't try.
Let's Talk About Dating, Part 6: Managing Expectations
by Suzanne Hadley on Mar 20, 2008 at 4:35 PM
A friend once told me: "Expectations are stupid." I think he meant that since we can't control outcomes, expectations -- particularly unreasonable ones -- often lead to disappointment. I'm not sure I'd go that far. After all, expectations can create a framework that helps you see if you're wandering off course. But when it comes to romantic relationships, too many expectations at the onset can be stifling.
There are two main ways I think singles can combat relationship-squelching expectations:
1. Be open to someone who isn't what you've always had in mind. In "[[7 Myths Single Women Believe|http://www.boundless.org/2005/articles/a0001480.cfm]]," I addressed the expectations some singles have about meeting "the one."
<<<
Just as my junior high mind projected who I would recognize as "the one," my grown-up self entertains expectations of how I'll feel when my "soul mate" arrives on the scene. The truth is, God knows best the kind of man who will inspire me to greater devotion to Him. As I seek the Lord, I can trust Him to reveal that person to me in whatever way He sees fit.
<<<
Basically, throw out expectations that aren't related to the essentials -- essentials being character, godliness and connection. You may be surprised by the type of person who is good for you and brings out your best. There's a country song that goes: "She's not at all what I was looking for. She's more." Be open to God showing you "more."
2. Leave some room for a budding relationship to grow without the expectations that come later. Mark responded to [[my post on clarity|http://www.boundlessline.org/2008/03/lets-talk-abo-3.html]] with this comment:
<<<
I feel pretty overwhelmed with all of the dos and don'ts of dating. In order to undertake all of the above-mentioned items at the outset, I'd have to be pretty blown away by the woman. Of course, it's not entirely likely that I'm going to feel that way immediately so I'd have to spend some time getting to know the girl.
Personally, I have no problem asking a girl out. It's the second or third date that perlplexes me. How do you get to know someone without giving off the signal "we're in a relationship" and not acting clingy?
<<<
Many of my guy friends have expressed this same frustration. It seems after a date or two, the woman may be already thinking about marriage, children and their future life together. I talk about this in "[[Not Your Buddy|http://www.boundless.org/2005/articles/a0001200.cfm]]:"
<<<
Song of Songs puts it this way, "Do not awaken love before it so desires." As a generation of women drunk on chick flicks, we want romance to happen so badly we allow ourselves to fantasize about relationships that have no founding.
<<<
In short, girls need to cool it (and guys, if they're expecting a woman to decide for or against them after one or two dates). If a guy asks you out, don't immediately fixate on him as your future husband. Allow a period of time to simply get to know who he is, without forcing him to state his intentions. There is a time for that -- I'm not condoning the lingering limbo relationship -- but don't send him into a panic after the second or third date by demanding clarity he's not ready to give.
Give lots of grace. Don't assume he's a villain if he decides not to pursue further after a few dates. Being gracious and giving the person in whom your interested the benefit of the doubt also makes acquaintance less awkward if the relationship doesn't work out and you have to part ways. Expectations may not be stupid, but letting them take control may be.
Let's Talk About Dating, Part 7: Love
by Denise Morris on Mar 25, 2008 at 1:59 PM
This is the last post in Suzanne's and my dating series. We're all out of wisdom and/or unwanted advice.
I thought it would be fitting to end with what I deem to be the most important aspect in any relationship -- the two greatest commandments:
<<<
"Teacher, which is the greatest commandment in the Law?" Jesus replied: "'Love the Lord your God with all your heart and with all your soul and with all your mind.' This is the first and greatest commandment. And the second is like it: 'Love your neighbor as yourself.' All the Law and the Prophets hang on these two commandments." (Matthew 22:36-40, NIV)
<<<
As Christians, our goal should be to spend our lives fulfilling these commandments. We'll obviously mess up, but our desire should be to get better at loving God and loving those around us. Dating relationships are no different. If we focus on these things, I believe that our relationships will be healthier and more glorifying to God.
First of all, if we're attempting to love God with all that we are, our hearts and minds will be in the right place. We'll have our priorities straight and our energies will be focused on doing the simple things that God has asked us to do. Secondly, if we love our neighbor/girlfriend/boyfriend as ourselves, we'll have much healthier relationships. We won't be so caught up in our own needs or wants or preferences -- instead we'll be focused on serving and loving whomever we're in relationship with. [[We won't just be looking out for our own interests, instead we'll be concerned with the needs of others|http://www.biblegateway.com/passage/?search=phillipians 2:4&version=31]].
And as [[I've mentioned before|http://www.boundlessline.org/2007/08/when-it-comes-t.html]], I believe that much of this "love" we're talking about is a choice we make. It's not based on [[romanticized notions of love|http://www.boundlessline.org/2007/08/when-it-comes-t.html]] or [[unrealistic expectations|http://www.boundlessline.org/2008/03/lets-talk-abo-5.html]]. It's based on finding someone with whom you serve the Lord well and then choosing to love that person in the good times and the bad, when you feel giddy about them and when you don't. Our love should be based on the sacrificial example we see of Christ and His bride.
Friendships, dating, courting, marriage -- all of them are difficult. All of them require risk. But we cannot be so concerned with [[guarding our hearts|http://www.trueu.org/dorms/womenshall/A000000435.cfm]] that we avoid relationships that God has called us to. God's triune nature reveals that He is a relational being. He created us to be in relationship with Him and one another. And as we can see through His relationship with us, the type of community we're supposed to foster with one another is loving, sacrificial and servant-hearted. In order to succeed in the "dating game" we must have the same attitude.
Finally, trust the Lord. He is good and His love endures forever. As you navigate the DTRs, the difficult conversations, the up-and-down feelings and the breakups, remember that you're not alone. Ask God to bring you wisdom and guidance. Practice love and apply it to your dating relationships. And pray that God will be glorified.
Love and Marriage: Luther Style
by Justin Taylor (originally posted [[here|http://www.boundless.org/2005/articles/a0001696.cfm]])
My 3-year-old daughter recently accompanied my wife to a wedding while I stayed home with our toddler. When they got home, I asked my little girl about the wedding. She talked, of course, about the beautiful flowers and the wedding dresses. I told her that maybe she too would grow up and get married someday.
A look of despair crossed her face as she delivered her melodramatic response: "Yes, but it takes //so// long to grow up! ... I'm //never// going to get married!"
Many of us can identify! Some of us are born practically ready to get married. But not Martin Luther. He would have fit in better with the guys at my college who proudly proclaimed, "Bachelor to the Rapture!"
Luther definitely fit the Christian bachelor lifestyle. He once went a whole year without airing out his straw bed. (I don't know exactly what sweaty straw smells like, but I suspect it was quite unpleasant!) Luther also used to boast, "If I break wind in Wittenberg they smell it in Rome." He would have fit right in with my college buddies — and was obviously not preparing himself to find a wife!
But we're getting ahead of ourselves. Let's start back at the beginning in order to learn a little more about this unlikely candidate to change marriage as we know it.
!!!Martin Luther
Luther was born in 1483. His dad wanted him to be a lawyer, so he ended up in law school. On a trip home to see his parents, the 22-year-old Luther got caught in a frightening thunderstorm. He was so frightened that he said a prayer to a saint: If she saved him, he'd become a monk. He survived the storm — and much to his father's displeasure, entered the monastery. He ended up getting his doctorate in theology and becoming a professor.
The Protestant Reformation eventually resulted from him nailing his 95 Theses against the Wittenberg Door in 1517. Four years later, the Emperor demanded that Luther recant his teachings. Luther asked for 24 hours to think it over. The next day, he delivered his famous speech: "Unless I am persuaded by the testimony of scripture or by clear reason, then I will not recant because it is neither safe nor wise to act against conscience. Here I stand. I can do nothing else. God help me. Amen."
Most of us have at least heard about this side of Luther and the Reformation associated with his name. But few know about another reformation he brought about — in the way people thought about marriage.
!!!Katherine von Bora
When Luther was 16, something happened about 120 miles away (unbeknownst to him) that would forever change his life: Katherine von Borra was born. Her mom died when she was only five, her father remarried, and Katherine was sent off to a convent to be educated and to become a nun. She would stay in such cloisters for the next 20 years.
In the 1520s, Luther was about 40 years old and still single himself. For an unmarried man, he sure wrote a lot about marriage, arguing that it was not only helpful and honorable, but //necessary// (except for the very small minority of people gifted and called to singleness). He wrote, "As it is not within my power not to be a man, so it is not my prerogative to be without a woman. Again, as it is not in your power not to be a woman, so it is not your prerogative to be without a man."
Being a nun at that time was not something voluntary. They were bound by their oaths to remain in the convents. But then the nuns — including Katherine — began to catch wind of Luther's liberating writings. He was writing things like, "your vow is contrary to God and has no validity" — don't delay but "get married." Much to the chagrin of church leaders, his vision caught on. Nuns began to escape the nunneries (nuns on the run!), seeking husbands and getting married!
Now the guys who are reading this may have a slight smile on their face at this point. Here is Luther — a 40-year-old man who has never been married. He figures out a place where they are scores of young eligible bachelorettes, and he makes an impassioned plea for them to go and find husbands? How selfless! How noble! How ... //convenient//!
If you're thinking maybe Luther had a hidden motive here, you're not the first to have thought that! The rumor mill was alive and well in the 1500s. A number of people thought Luther was creatively angling for a wife. But Luther honestly did not desire or plan on marriage. He didn't pretend that he was free from sexual temptation — after all, he wrote, "I am neither wood nor stone." But on the other hand, he wrote that his "mind is far removed from marriage."
The reason was a sobering one — a situation most of us will never have to face. Luther was persuaded that he didn't have much longer to live because he would be killed for his beliefs and for his faith. He recognized that being on the verge of martyrdom didn't exactly make him courtship material.
Luther was seeking to free these nuns //not// so that he could find a wife, but because he truly believed it was wrong for women to make a vow of singleness, not based on gifting and personal conviction but rather due to external pressures and unbiblical teaching. Luther's understanding of the Bible and of grace permeated through many aspects of his worldview, including marriage.
After Katherine and her fellow nuns became convinced by Luther's writings, they were able to secretly contact him, requesting his help to escape. Luther set in motion an ingenious plan devised with the delivery man for the convent.
Early on Easter morning of 1523, Leonard Kopp stopped by the convent to make his weekly delivery of herring. After unloading the fish from his barrels, his covered wagon slowly pulled away — no one realizing that the just-emptied barrels now contained 12 fugitive nuns!
!!!Martin and Katherine
Each of the nuns was quite poor and in terrible shape. Luther diligently worked to return them to relatives for support or to find them husbands. But Katherine's family didn't want her back, so Luther arranged for her to live with some friends of his. Katherine and Luther became friends — though he thought she was quite prideful!
Luther was determined to help Katherine find a husband. He tried setting her up with one of his professor-colleagues in his 60s. But feisty Katherine, in her 20s, made it abundantly clear she wasn't interested!
We don't know exactly how it happened. In 1525 we have a letter from Luther to his friend Spalatin, saying, "I urge matrimony on others with so many arguments that I am myself almost moved to marry...." A week later Luther took a trip to visit his parents. Perhaps in a joking manner he mentioned to them the idea of getting married. His dad became very excited at the idea of passing on the family name and enthusiastically encouraged Luther to get going on it! A few weeks later Luther wrote, "If I can manage it, before I die I will still marry my Katie to spite the devil." Perhaps not the most romantic line in history, but Luther was well on his way to turning in his membership card to the "Bachelor to the Rapture" Club!
Luther didn't believe in long engagements. In fact, he had one of the shortest engagements in history — he proposed to Katherine and they were married that very same day (June 13, 1523). Their marriage not only shocked their friends, but eventually led to the transformation of church and culture. One scholar writes, "Little did the sixteenth-century world realize the tremendous significance — both religious and social — of this simple and reverent ceremony in the backwoods of rural Germany.... Luther's marriage remains to this day the central evangelical symbol of the Reformation's liberation and transformation of the Christian daily life."
Katie bore six children (three boys and three girls), and she and Martin were married for just over two decades. He died at the age of 62. Katie would live another seven difficult years, till she went to be with the Lord at the age of 53. Among her final recorded words reveal the gospel-shaped desire of her heart, which was to "cling to Christ like a burr to a dress."
!!!The Luthers' Legacy of Love and Marriage
I wish I could recount here the many details of their fascinating life together, but space permits me only to draw a few lessons that we can learn from their union:
#//Martin and Katie didn't put their hope in marriage; they put their hope in God.// Martin was in his 40s, convinced he would never be married and would soon suffer a martyr's death. Katie had lived in a convent since the age of five, convinced she would never be married and would remain a nun until she died. Their difference in age and circumstance, along with their feisty personalities, meant that on paper, they were probably not a good match. But God had other plans; they were faithful; and God made them into an example for many to emulate.
#//Martin and Katie didn't marry each other because they were infatuated with each other; instead they grew to love each other because they were married.// In a handwritten invitation to the public ceremony for their wedding, Luther wrote to a friend, "I feel neither passionate love nor burning for my spouse, but I cherish her." Now it's important to keep in mind here that Luther is coming off a world-record short engagement (marriage happened on the same day!). There wasn't a lot of time for a full-fledged, deeply rooted romance to ensue. Luther was well aware that very often "In the beginning of a relationship love is glowing hot, it intoxicates and blinds us, and we rush forth and embrace one another. But once married, we tend to grow tired of one another...." His experience was the opposite; he cherished her, but they did not start off in passionate love — though that quickly grew as they were marriage. Luther wrote, "The first love is drunken. When the intoxication wears off, then comes the real marriage love."
#//Martin and Katie viewed marriage as a school for growing in godliness.// Both of them took God seriously; and both knew how to correct the other when one of them was ignoring God and taking life too seriously. One day Luther was depressed and despairing. So Katie decided to put on a black dress for the day. Luther asked, "Are you going to a funeral?" "No," she responded, "but since you act as though God is dead, I wanted to join you in the mourning!" Exactly what Luther needed to hear.
#//Martin and Katie enjoyed the God-given gifts of life and marriage unto the glory of God.// Scripture teaches that "everything created by God is good, and nothing is to be rejected if it is received with thanksgiving, for it is made holy by the word of God and prayer" ([[1 Tim. 4:4-5|http://www.biblegateway.com/passage/?search=1 Tim. 4:4-5;&version=47;]]). One Luther scholar explains how this was lived out in his life: "Luther's faith was simple enough to trust that after a conscientious day's labor, a Christian father could come home and eat his sausage, drink his beer, play his flute, sing with his children, and make love to his wife — all to the glory of God!"
!!!Conclusion
Whether you're single, engaged or married, there is no shortage of books to read regarding the state you are currently in. But few of us think to look outside of our own century to peer into the Christian-centered marriage of a couple from hundreds of years ago. They have many more lessons to teach us.
So the next time my daughter complains that life is just taking too long before she's married — or the next time I run into one of those "Bachelor to the Rapture" guys — I might just recommend that they learn a little bit about Luther.
!!Ingredients
#2 squares bean curd
#Part 1
##1 t chopped garlic
##1 T chopped green onion
##1 t chopped ginger root
#2 oz chopped pork
#1 T hot bean paste ("la do ban jiang")
#Part 2
##1 T rice wine
##1 C water
##.5 t MSG (not necessary)
##.25 t salt
##1.5 T soy sauce
#Part 3
##1.5 t cornstarch
##1 T water
#2 T .5-inch sections green onion or garlic stalk
#.25 t Szechuan peppercorn powder (not necessary)
!!Directions
#Remove hard edges, dice bean curd
#Heat pan and 3 T oil
#Stir fry ''Part 1'' and chopped pork until fragrant
#Add ''Part 2'' and bean curd, cover and cook 3 min over low heat
#Mix ''Part 3'', add along with .5 T fried oil, toss ingredients lightly
#Remove to serving plate, sprinkle green onion or garlic sections and peppercorn powder on top
[[Get Back To Your Mac w/o paying for it|http://lifehacker.com/365673/get-back-to-your-mac-without-paying-for-it]]
[[Home|Welcome]]
[[Blog|http://www.goingthewongway.com]]
[[Editing Shortcuts|TiddlyWiki Shortcuts]]
[[google map|http://maps.google.com/maps?f=d&hl=en&geocode=999802989413177060,33.669885,-117.859000;4355767686695278212,33.663256,-117.874268;5985982791277153002,33.735419,-117.993100&saddr=18191+Von+Karman+Ave,+Irvine,+CA+92612&daddr=Von+Karman+Ave+@33.669885,+-117.859000+to:Campus+Dr+@33.663256,+-117.874268+to:33.672069,-117.947845+to:I-405+N+@33.735419,+-117.993100+to:942+Yale+St,+Los+Angeles,+CA+90012&mra=dpe&mrcr=0&mrsp=3&sz=13&via=1,2,3,4&sll=33.672354,-117.930508&sspn=0.087716,0.156555&ie=UTF8&z=13]]
81 miles work -> church -> home
!!Ingredients
*5 lb potatoes
*1 stick butter
*Seasoning
**Salt
**Pepper
**Garlic Salt
*1 C milk
!!Directions
#Peel potatoes
#Slice potatoes
#Put potatoes in water, bring to boil
#Simmer 30 min until tender
#Drain most of the water
#Add butter
#Add salt, white pepper, garlic salt
#Mash
#Add milk
!!For Men
Before you use the formulas, there are two measurements that are required:
''Measurements''
#Bodyweight
#Waist Girth (measured at the belly button)
''Procedure'':
#Multiply your bodyweight by 1.082. Add the result to 94.42. Once your calculation is complete, save the number. (Bodyweight x 1.082) + 94.42=Result 1
#Multiply your waist girth by 4.15. Once you get this result, subtract it from the number obtained in step 1 (i.e. Step 1 result-Step 2 result). The result obtained after the subtraction is done is your lean bodyweight (your weight if you had no fat in your body at all). Result 1 - (Waist Girth x 4.15)= Lean Body Weight
#Finally, subtract your lean bodyweight from your total bodyweight (Total weight-Lean Bodyweight). Once you get the result, multiply that number by 100. Once you get the result divide it by your total bodyweight. This final result is your percentage of body fat. ((Total Bodyweight - Lean Bodyweight) x 100) divided by (Your Body Weight) = Your Percentage of Body Fat.
''Example'':
I weigh 190 and I have a 30.5inch waist. Therefore, step 1 is (190 x 1.082) + 94.42 = 300. Step 2 says that my lean body weight equals 300-(30.5 x 4.15)=173.425. Finally, Step 3 says that my body fat percentage is ((190-173.425) x 100) divided by 190= 8.72%.
!!For Women
Before you use the formulas, there are five measurements that are required (not fair, I know):
''Measurements''
#Bodyweight.
#Wrist Circumference (measured at the widest point).
#Waist Circumference (measured at your belly button).
#Hip Circumference (measured at the widest point).
#Forearm Circumference (measured at the widest point).
''Procedure'':
#Multiply your bodyweight by 0.732. Bodyweight x .0732 = Result 1.
#Add the result above to 8.987. Result 1 + 8.987= Result 2.
#Divide your wrist circumference by 3.14. Wrist divided by 3.14 = Result 3.
#Multiply your waist measurement by 0.157. Waist x 0.157 = Result 4.
#Multiply your hip measurement by 0.249. Hip x 0.249 = Result 5.
#Multiply your forearm measurement by 0.434. Forearm x 0.434 = Result 6.
#Add results 2 & 3. Result 2 + Result 3 = Result 7.
#Subtract Result 4 from Result 7. Result 7 - Result 4 = Result 8.
#Subtract Result 5 from Result 8. Result 8 - Result 5 = Result 9.
#Add Result 6 and Result 9. The result is your lean body mass (your fat free weight) Result 6 + Result 9 = Lean Body Mass.
#Subtract your lean body mass from your bodyweight. Once you get the result, multiply that number by 100. Once you get this result, divide it by your bodyweight. ((Bodyweight - Lean Body Mass) x 100) divided by your bodyweight.
''Example'':
A woman that weighs 125, and has a wrist measurement of 6.0, a waist measurement of 24, a hip measurement of 38, and a forearm measurement of 9.5 would calculate her body fat percentage in the following manner. Step 1: 125 x 0.732=91.5. Step 2: 91.5 + 8.987=100.487. Step 3: 6 divided by 3.14=1.91. Step 4: 24 x 0.157=3.768. Step 5: 38 x 0.249=9.462. Step 6: 9.5 x 0.434=4.123. Step 7: 100.487+1.91=102.397. Step 8: 102.397-3.768=98.629. Step 9: 98.629-9.462=89.167. Step 10: 4.123+89.167=93.29 (Lean Body Weight: Fat Free Weight). Step 11: ((125-93.29) x 100) divided by 125 = (31.37 x 100) divided by 125 = 3171 divided by 125= 25.368 (Body Fat Percentage).
---------
Notes: The formulas above are just approximations. The goal here is to have a point of reference from which to work. I recommend that you measure your body fat every three weeks. If you see a pattern where you see yourself gaining muscle and losing fat, then you know your program is right on track. If not, examine which part of your program is not optimal. Assuming that you are following an effective training routine, look at the things that could be going wrong such as you are not getting enough rest at night or more likely you are not following your nutrition plan to the letter.
Since I like to measure my progress, and that of others, in the shortest amount of time possible, I created a computer program that once you enter the required inputs, it calculates in a microsecond your lean body mass, fat mass, and body fat percentage. It sure beats using the calculator, the pen or pencil and the piece of paper.
[[source|http://www.davedraper.com/bodyfat-calculation.html]]
[[Interop|http://msdn2.microsoft.com/en-us/library/ms173184.aspx]]
208.67.222.222
208.67.220.220
<!--{{{-->
<div id='header' class='header'>
<div id='title'>
<div id='topMenu' refresh='content' tiddler='MainMenu'></div>
<span class='siteTitle' refresh='content' tiddler='SiteTitle'></span>
<span class='siteSubtitle' refresh='content' tiddler='SiteSubtitle'></span>
</div>
</div>
<div id='sidebar'>
<div id='sidebarOptions' refresh='content' tiddler='SideBarOptions'></div>
<div id='sidebarTabs' refresh='content' force='true' tiddler='SideBarTabs'></div>
</div>
<div id='displayArea'>
<div id='messageArea'></div>
<div id='tiddlerDisplay'></div>
<div class='clearAll'></div>
</div>
<div id='contentFooter' refresh='content' tiddler='contentFooter'></div>
<!--}}}-->
!!Ingredients
*Seasoning
**Salt
**Pepper
**Lawry's seasoning salt
**Soy sauce
**Garlic salt
*Prime rib (small end w/ plenty of marbling, ~4 lbs)
!!Directions
#Season outside of prime rib
#Pre-heat oven to 350º
#Insert meat thermometer
#Cook until thermometer registers 120º, ~1.5 hours
#Remove from oven, let rest 10 min before cutting
Programming Languages
[[Lisp References]]
[[Python References]]
Computer Science
[[Binary Trees]]
[[Distributed Systems]]
[[Intro To Bits]]
Mac
[[Learning Cocoa|http://en.wikibooks.org/wiki/Programming_Mac_OS_X_with_Cocoa_for_beginners/A_more_ambitious_application]]
[[PyObjC intro|http://pyobjc.sourceforge.net/documentation/pyobjc-core/intro.html]]
Microsoft
[[Microsoft Related Programming]]
Linux
[[Linux Related]]
Editors
[[Customizing Emacs]]
''TODO''
[[Computer Science To Read]]
[[Python tutorial|http://docs.python.org/tut/node5.html]]
[[Python tutorial classes|http://docs.python.org/tut/node11.html#SECTION0011900000000000000000]] - Iterators
[[PyObjC intro|http://developer.apple.com/cocoa/pyobjc.html]] - at Python advantages
BY MARK TWIGHT
(originally published [[here|http://www.gymjones.com/knowledge.php?id=20]])
<<<
"You could get through workouts a lot faster if you didn't actually have to do them."
<<<
Some "fitness" folks like to quote the Henry Rollins phrase, "two hundred pounds is always two hundred pounds." At Gym Jones we say that, to ensure valid measurement a yardstick must be one yard long and two hundred pounds is only that when moved through a complete range of motion -- regardless of the speed at which it moves.
Fresh from quoting the man whose music they probably hate those same folks mouth off about ideal range of movement and quality of work but unless those ideals manifest as action they are meaningless. No matter how hopeful the words if the chin does not rise significantly higher than the bar then it is not a pull-up -- kipping or otherwise -- because the weight has not been moved through its maximum possible trajectory; the potential energy has not been fully expressed.
As our training group grew during the last year we noticed that, in the quest for faster times work quality was easily sacrificed. Such may be unconscious behavior but I like to call it cheating. When movement quality declined we couldn't use the stopwatch to monitor improvements because other parameters must be fixed for the time to be relevant: if the load is fixed, and the movement is always the same then posting a faster or slower time is useful knowledge. If the load is fixed but the range of motion (ROM) is shortened a second variable has been introduced and knowing the time is no longer useful.
Some argue that movements executed quickly lead to a higher power output and that if ROM is sacrificed along the way the trade-off is worth it. Yes, power output will be greater but the athlete who cuts ROM short and finishes faster is not doing the same workout as the athlete who pulls and pushes through complete ROM. If two athletes aren't playing the same game by the same rules any comparison of the results lacks meaning. And there is no reason NOT to execute movements completely even when doing multiple reps for time. Putting a full kip on the pull-up, still not getting the head above the bar and calling it good is about as lame as it gets.
Understand that I am not arguing against kipping or wiggling or squirming to get a rep done, I am simply stating that in our gym we do not count incomplete reps no matter how good the athlete's intention. Athletes shortcut reps because it's easier to do less than it is to do more and that's cheating or at best, lazy. If we accept "chicken necking" instead of a proper pull-up (because it is 90% complete and more reps can be done faster thus increasing the power requirement) the natural conclusion is accepting speedily executed but partial squats. What we allow ourselves to settle for is largely dependent on our goals and the strength of our character. It is up to the individual to figure out why he/she is doing something and to accept responsibility for those choices and actions. Figure it out.
By nature mankind is comparative. We like to see where we fit into the scheme of things. If fitness is important then timed or scored workouts are a lens through which we may see ourselves in a larger context. For this comparison to be meaningful we all have to be doing the same thing. Track events are simple that way: run a fixed distance. In the realm of gym fitness rowing on the Concept II fills a similar role, there is no way to cheat it: 5000 meters is 5000 meters no matter how you get there. But when it comes to couplets, triplets and chippers requiring a variety of movements, the execution of which may be "interpreted" valid comparison among individuals is contingent on a fixed set of parameters. At Gym Jones we use the following rules to ensure work quality:
*Pull-ups: elbows must pass behind centerline of the body, if this happens the entire head rises above the bar, active shoulder position at bottom (as opposed to full dead hang)
*Push-ups: chest touches the floor first, active shoulder and full extension at the top, body held as a solid plank, the hips do not move
*Squats: thighs must be parallel to floor (at minimum) in the bottom position, full extension at the top of the movement
*Lunges: trailing knee must "kiss" the ground but may not support any weight
*~Push-Press and Thruster: arms must lock out overhead, hips displace horizontally to the rear to initiate recovery of the weight, Thruster includes all attributes of a proper squat
*Kettlebell or Dumbell Swing: weight must be raised higher than the head (arms about 45 degrees)
*Box Jump: once established on the box the athlete must stand up completely, whether jumping for reps or max height taking steps to gain momentum is not permitted
*Ball Slam: full extension at the top with hips forward, ball must actually be slammed (imagine that), catching it on the bounce is better style, rounded back not permitted during recovery
*Burpees: includes a proper push-up, explosive finish (jump), overhead clap, and feet remain together throughout movement to ensure maximum hip displacement
*Wall Ball: full squat required, ball must hit target
*Dips: upper arm must be parallel to the floor (at minimum) in the bottom position, arms lock out in full extension at the top
When everyone agrees on the rules the outcomes may be compared and relevant conclusions drawn. For the sake of meaningful knowledge and honest communication we only post results on the Gym Jones site that were achieved in accordance with our standards for full ROM (unless otherwise noted). From now on we will detail the types of exercises used e.g. whether push-ups were done on the floor, on parallettes, on the rings, with feet higher or lower than hands, etc. Strict standards prevent misrepresentation and the speculation that follows. I've seen "Jonesworthy" done properly and I've seen it done with partial reps, and then read both times posted on the web as if they were comparable efforts.
We train in preparation for sport-specific tests or work-related challenges, we do not train for the sake of it or because conditioning is our sport or hobby. We don't do this because we want to look a certain way or to lose weight (these are consequences). We suffer during training to improve ourselves physically and psychologically and we measure those improvements on mountains, on frozen waterfalls, in burning buildings, facing cunning adversaries, on the battlefield, on the mat and in the cage. Because these tests occur outside the gym we don't compete in the gym, we work hard, and we work together to make the sum greater than its individual parts. Cheating here won't help us get where we are going so we enforce all quality all of the time.
That's our yardstick, how long is yours?
[img[pull up|http://www.gymjones.com/images/knowledge/know_20_1.jpg]]
Johnny with his entire head (and then some) above the bar
[img[push up|http://www.gymjones.com/images/knowledge/know_20_2.jpg]]
Stephane going deep between the parallettes
[img[squat|http://www.gymjones.com/images/knowledge/know_20_7.jpg]]
Stephane with his thighs parallel to the floor, holding during a Bottom-to-Bottom Tabata Squat set
[img[press|http://www.gymjones.com/images/knowledge/know_20_9.jpg]]
Jim nearing the end of Thruster & Pull-up couplet and still going to full extension
[img[kettlebell swing|http://www.gymjones.com/images/knowledge/know_20_5.jpg]]
Logan swinging a bit higher than required, which shows stronger character than if he'd swung lower than required
[img[ball slam|http://www.gymjones.com/images/knowledge/know_20_10.jpg]]
AJ at full extension during a Ball Slam and it's obvious that he's not just going to drop it ...
[img[burpee|http://www.gymjones.com/images/knowledge/know_20_4.jpg]]
James airborne coming out of a Burpee and clapping hard
[img[dip|http://www.gymjones.com/images/knowledge/know_20_6.jpg]]
Mathieu showing good shoulder flexibility and strength ... this is proper dip depth
[img[push up on rings|http://www.gymjones.com/images/knowledge/know_20_8.jpg]]
MFT (on the right) going about as deep as the shoulders allow
[img[kettlebell squat|http://www.gymjones.com/images/knowledge/know_20_11.jpg]]
Dylan getting appropriately low though most people would try to get away with less
[img[medicine ball squat|http://www.gymjones.com/images/knowledge/know_20_12.jpg]]
Ricky pushing to full extension and using the medicine ball to ensure proper squat depth
!!Directions
#Pre-heat oven to 350º F
#Clean chicken
##Pluck any remaining feathers
##Remove viscera (kidneys, liver, etc)
#Cover with marinade. Marinade consists of:
##soy sauce
##garlic powder
##small amount of sugar
#Insert whole green onion inside
#Place chicken onto rack (breast down)
#Bake in pre-heated oven
**Approximately 30 min. for a 4 lb chicken
#Place any remaining marinade while turning chicken (breast side up)
#Cook until juices run clear and there is no more pink
**Approximately 30 min. for a 4 lb chicken
Can feed ''4-5'' people (for a 4 lb chicken)
[[Chase|https://chaseonline.chase.com/chaseonline/logon/sso_logon.jsp?fromLoc=ALL&LOB=COLLogon]]
[[Chase 2|https://chaseonline.chase.com/online/home/sso_co_home.jsp]]
[[WaMu|https://online.wamu.com/IdentityManagement/Logon.aspx]]
[[Dr Lin articles|http://www.bsmi.org/lin.htm]]
[[John Wesley - What Is An Arminian?|http://new.gbgm-umc.org/umhistory/wesley/arminian/]]
[[Price Protectr|http://www.priceprotectr.com/index.jsp]]
!!Ingredients
*Ribs
*Onion (chopped into wedges)
*BBQ Sauce
*Seasoning
**1 T Garlic Powder
**2 T Salt
**1 T Black Pepper
**1/2 C Soy Sauce
!!Directions
#Rinse ribs of gristle
#Place ribs in water along with seasoning
#Bring to boil
#Simmer for 2 hours
**This can be done the night before
#Pre-heat oven to 325º F
#Place ribs in aluminum foil-covered pan
#Cover ribs with BBQ sauce
#Cook ribs in oven for 1 hour
[[when to settle|http://www.boundless.org/2005/articles/a0001699.cfm]]
[[weight issues|http://www.boundless.org/2005/answers/a0001693.cfm]]
[[7 myths single women believe|http://www.boundless.org/2005/articles/a0001480.cfm]]
[[i'm just not attracted to her|http://www.boundless.org/2005/articles/a0001640.cfm]]
!!Ingredients
#Steak (any kind but Ribeye preferred)
**Look for marbling (fat running throughout) when shopping for steak
#Oil
#Salt
#Pepper
#Garlic Salt
!!Instructions
#Wash gristle
#Pat dry
#Sprinkle side with salt, garlic salt, and pepper
#Heat enough oil to cover bottom of flat cast iron pan
#Place steak in pan
#Cook 4 min or until blood pools on top
#Sprinkle top with salt, garlic salt, and pepper
#Flip steak
#Cook 4 min or until cooked as much as desired
**[[Tips on doneness|http://www.menshealth.com/cda/article.do?site=MensHealth&channel=guy.wisdom&category=howto.guides&conitem=cbab54968cc1d010VgnVCM10000013281eac____]]
/*{{{*/
/*Bleach Theme for TiddlyWiki*/
/*Design and CSS by Saq Imtiaz*/
/*Version 1.0*/
/*}}}*/
/***
!General
***/
/*{{{*/
body {
background: #fff;
}
#contentWrapper{
margin: 2.5em auto;
width:759px;
line-height: 1.6em;
border:1px solid #999;
font-size: 11px;
font-family: Lucida Grande, Tahoma, Arial, Helvetica, sans-serif;
color: #555;height:1%;
}
.clearAll {clear:both;}
.tagClear {clear:none;}
/*}}}*/
/***
!Header
***/
/*{{{*/
#header {background:#fff; border-bottom:1px solid #999;padding: 2.5em 2em 1.6em 2em; height:1%;
}
.siteTitle {
font-family: 'Trebuchet MS' sans-serif;
font-weight: bold;
font-size: 32px;
color: #EF680E;
background-color: #FFF;
}
.siteSubtitle {
font-size: 1.0em;
display:block;
color: #999999; margin-top:0.5em !important; margin-top:1em; margin-left:3em;
}
#topMenu { positon:relative; float:right; display:inline; margin-right:2em;}
#topMenu br {display:none; }
#topMenu { background: #fff; color:#000;padding: 1em 1em;}
#topMenu a, #topMenu .tiddlyLink, #topMenu .button {margin:0 0.5em; color:#666;}
/*}}}*/
/***
!displayArea
***/
/*{{{*/
#displayArea {margin-left:1.35em; margin-right:16.3em; margin-top:0; padding-top:1em; padding-bottom:10px;}
/*}}}*/
/***
!Sidebar
***/
/*{{{*/
#sidebar {position:relative;float:right; line-height: 1.4em; border-left:0px solid#000; display:inline; background:#fff; right:0;
width: 16em;}
/*}}}*/
/***
!SidebarOptions
***/
/*{{{*/
#sidebarOptions {padding-left:0.5em; border-left:1px solid #999;padding-top:1em;}
#sidebarOptions a {
color:#999;
text-decoration: none;}
#sidebarOptions a:hover, #sidebarOptions .button:active {
color:#333;
background-color: #fff;border:1px solid #fff;
}
#sidebarOptions input {border:1px solid #999; width:10em;}
/*}}}*/
/***
!SidebarTabs
***/
/*{{{*/
#sidebarTabs {border-left:1px solid #999;}
#sidebarTabs .tabContents {background:#fff;}
#sidebarTabs .tabContents .tiddlyLink, #sidebarTabs .tabContents .button{color:#999;}
#sidebarTabs .tabContents .tiddlyLink:hover,#sidebarTabs .tabContents .button:hover{color:#333;background:#fff;border:none;}
#sidebarTabs .tabContents .button:hover, #sidebarTabs .tabContents .highlight, #sidebarTabs .tabContents .marked, #sidebarTabs .tabContents a.button:active{color:#333;background:#fff}
.tabSelected{color:#fff; background:#999;}
.tabUnselected {
background: #ccc;
}
.tabSelected, .tabSelected:hover {
color: #fff;
background: #999;
border: solid 1px #999;
padding-bottom:1px;
}
#sidebarTabs .tabUnselected:hover { border-bottom: none;padding-bottom:3px;color:#4F4B45}
.tabUnselected {
color: #999;
background: #eee;
border: solid 1px #ccc;
padding-bottom:1px;
}
#sidebarTabs .tabUnselected { border-bottom: none;padding-bottom:3px;}
#sidebarTabs .tabSelected{padding-bottom:3px;}
#sidebarOptions .sliderPanel {
background: #fff; border:none;
font-size: .9em;
}
#sidebarOptions .sliderPanel a {font-weight:normal; }
#sidebarOptions .sliderPanel input {border:1px solid #999;width:auto;}
#sidebarOptions .sliderPanel .txtOptionInput {border:1px solid #999;width:9em;}
#sidebarTabs .tabContents {border-right:0; border-left:0; border-bottom:1px solid#999; padding-left:4px;}
.listLink,#sidebarTabs .tabContents {line-height:1.5em;}
.listTitle {color:#666;}
#sidebarTabs .tabUnselected:hover { border-bottom: none;padding-bottom:3px;color:#4F4B45}
#sidebarTabs .txtMoreTab .tabContents {border-left:1px solid #999;}
#sidebarTabs .txtMainTab .tabContents li a{font-weight:bold;}
/*}}}*/
/***
!Main
***/
/*{{{*/
.title {color:#EF680E;}
.subtitle, .subtitle a { color: #999999; font-size: 1em;margin:0.2em; /*font-variant: small-caps; changed 080417, no small caps*/}
.shadow .title{color:#999;}
.selected .toolbar a {color:#999999;}
.selected .toolbar a:hover {color:#333; background:transparent;border:1px solid #fff;}
.toolbar .button:hover, .toolbar .highlight, .toolbar .marked, .toolbar a.button:active{color:#333; background:transparent;border:1px solid #fff;}
* html .viewer pre {
margin-left: 0em;
}
* html .editor textarea, * html .editor input {
width: 98%;
}
a,#sidebarOptions .sliderPanel a{
color:#EF680E;
text-decoration: none;
}
a:hover,#sidebarOptions .sliderPanel a:hover {
color:#EF680E;
background-color: #fff;
border-bottom:1px dotted #EF680E;
}
.viewer .button, .editorFooter .button{
color: #555;
border: 1px solid #EF680E;
}
.viewer .button:hover,
.editorFooter .button:hover{
color: #fff;
background: #EF680E;
border-color: #EF680E;
}
.viewer .button:active, .viewer .highlight, .editorFooter .button:active, .editorFooter .highlight{color:#fff; background:#DF691B;border-color:#DF691B;}
#topMenu a, #topMenu .button {
padding: 20px 10px; border:none; font-weight:bold;
}
#topMenu a:link{
text-decoration: none;
}
#topMenu a:hover, #topMenu .button:hover {
background-color: #fff;
color:#EF680E;
border:none;
}
.tagging, .tagged {
border: 1px solid #eee;
background-color: #F7F7F7;
}
.selected .tagging, .selected .tagged {
background-color: #eee;
border: 1px solid #BFBAB3;
}
.tagging .listTitle, .tagged .listTitle {
color: #bbb;
}
.selected .tagging .listTitle, .selected .tagged .listTitle {
color: #666;
}
.tagging .button, .tagged .button {
color:#aaa;
}
.selected .tagging .button, .selected .tagged .button {
color:#BFBAB3;
}
/*.highlight, .marked {background:transparent; color:#111; border:none; text-decoration:underline;} changed 080417 to show color*/
.tagging .button:hover, .tagged .button:hover, .tagging .button:active, .tagged .button:active {
border: none; background:transparent; text-decoration:underline; color:#333;
}
.popup {
background: #999;
border: 1px solid #999;
}
.popup li.disabled {
color: #000;
}
.popup li a, .popup li a:visited {
color: #eee;
border: none;
}
.popup li a:hover {
background: #6F6A68;
color: #fff;
border: none;
}
.tiddler {
padding-bottom: 40px;
/*border-bottom: 1px solid #999; */
}
#messageArea {
border: 4px solid #999;
background: #f5f5f5;
color: #999;
font-size:90%;
}
#messageArea a:hover { background:#f5f5f5; border:none;}
#messageArea .button{
color: #666;
border: 1px solid #CC6714;
}
#messageArea .button:hover {
color: #fff;
background: #999;
border-color: #999;
}
.viewer blockquote {
border-left: 5px solid #888;
}
.viewer table {
border: 2px solid #888;
}
.viewer th, thead td {
background: #888;