MOTIVATIONAL MESSAGES

From the CEO's Desk

Occasionally, our founder and CEO, Tom Murcko, writes exclusive articles
for our newsletter readers. We send these special releases as part of a
new series called, ‘From the CEO's Desk'. Tom hopes that sharing the
insight gained from his career will help you achieve your goals. Cheers!

What I Learned From Steve Jobs

By Tom Murcko
CEO of BusinessDictionary.com, InvestorWords.com & InvestorGuide.com

1

Be bold.

When Steve was just 12, he called the co-founder of electronics giant
Hewlett-Packard to get spare parts for a hobby project. Hewlett was so
impressed in that one conversation that he gave Steve a job that summer
that started him on his career in technology.

2

Question everything.
http://t.ms00.net/s/c?u.qkep.5.w1tt.45x6n

Always ask, why do we do it that way? Often the answer is just inertia:
it's done that way today because it was done that way yesterday, not
because it's the best way. By questioning the way things were, he became
an expert at seeing how things could be better. He envisioned desktop
publishing, the networked office, and the pervasive, transformative
power of the internet long before most others.

3

Make your own rules.

At college he skipped the required classes and instead just took
whatever interested him. (This included a calligraphy class, which
contributed to Apple's leadership on fonts and desktop publishing.)
After a while he decided that school was too expensive for his parents
to pay for, so he stopped paying his tuition, but he was so charismatic
that the dean allowed him to audit classes and stay in a dorm with
friends, effectively going to college without having to pay.

4

Live with intensity.

Life is short. Don't spend it living someone else's life, and don't
spend it on small matters. If something isn't worth doing with
intensity, then it's not worth doing at all.

5

Learn from the best.

Steve wanted to innovate, so he studied the leading innovators. In
Apple's early days, this was Xerox Parc, so he visited their research
labs and saw demonstrations on cutting-edge technologies that changed
the trajectory of his company, including graphical user interfaces,
object oriented programming, and networked computing.

6

Let everything be your teacher.

Apple took the best ideas from all fields. The early Macintosh team
included people with backgrounds in music, poetry, art, history and
other liberal arts, who also happened to be among the best programmers
in the world. If not for computer science, they would've done amazing
things in these other fields. Bringing together diverse expertise made
the products better in countless ways.

Click to Read Lessons 7 - 23
http://t.ms00.net/s/c?u.qkep.6.vucv.45x6n

MANAGE SUBSCRIPTION
http://t.ms00.net/s/c?u.qkep.7.reut.45x6n&email=Ogunwale.abiodun%40yahoo.com
| DISCLAIMER http://t.ms00.net/s/c?u.qkep.8.kggl.45x6n

10201 Fairfax Boulevard, Suite 570 Fairfax, VA 22030


Remove yourself from future email here:
http://i.ms00.net/remove?investor:18:1374246598.73021:Ogunwale.abiodun@yahoo.com:e

This message was sent to Ogunwale.abiodun@yahoo.com
X-PMG-Recipient: Ogunwale.abiodun@yahoo.com





pmguid:u.qkep.45x6n

From the CEO's Desk

Occasionally, our founder and CEO, Tom Murcko, writes exclusive articles
for our newsletter readers. We send these special releases as part of a
new series called, 詮rom the CEO's Desk'. Tom hopes that sharing the
insight gained from his career will help you achieve your goals. Cheers!

What I Learned From Steve Jobs

By Tom Murcko
CEO of BusinessDictionary.com, InvestorWords.com & InvestorGuide.com

1

Be bold.

When Steve was just 12, he called the co-founder of electronics giant
Hewlett-Packard to get spare parts for a hobby project. Hewlett was so
impressed in that one conversation that he gave Steve a job that summer
that started him on his career in technology.

2

Question everything.
http://t.ms00.net/s/c?u.qkep.5.w1tt.45x6n

Always ask, why do we do it that way? Often the answer is just inertia:
it's done that way today because it was done that way yesterday, not
because it's the best way. By questioning the way things were, he became
an expert at seeing how things could be better. He envisioned desktop
publishing, the networked office, and the pervasive, transformative
power of the internet long before most others.

3

Make your own rules.

At college he skipped the required classes and instead just took
whatever interested him. (This included a calligraphy class, which
contributed to Apple's leadership on fonts and desktop publishing.)
After a while he decided that school was too expensive for his parents
to pay for, so he stopped paying his tuition, but he was so charismatic
that the dean allowed him to audit classes and stay in a dorm with
friends, effectively going to college without having to pay.

4

Live with intensity.

Life is short. Don't spend it living someone else's life, and don't
spend it on small matters. If something isn't worth doing with
intensity, then it's not worth doing at all.

5

Learn from the best.

Steve wanted to innovate, so he studied the leading innovators. In
Apple's early days, this was Xerox Parc, so he visited their research
labs and saw demonstrations on cutting-edge technologies that changed
the trajectory of his company, including graphical user interfaces,
object oriented programming, and networked computing.

6

Let everything be your teacher.

Apple took the best ideas from all fields. The early Macintosh team
included people with backgrounds in music, poetry, art, history and
other liberal arts, who also happened to be among the best programmers
in the world. If not for computer science, they would've done amazing
things in these other fields. Bringing together diverse expertise made
the products better in countless ways.

Click to Read Lessons 7 - 23
http://t.ms00.net/s/c?u.qkep.6.vucv.45x6n

MANAGE SUBSCRIPTION
http://t.ms00.net/s/c?u.qkep.7.reut.45x6n&email=Ogunwale.abiodun%40yahoo.com
| DISCLAIMER http://t.ms00.net/s/c?u.qkep.8.kggl.45x6n

10201 Fairfax Boulevard, Suite 570 Fairfax, VA 22030


Remove yourself from future email here:
http://i.ms00.net/remove?investor:18:1374246598.73021:Ogunwale.abiodun@yahoo.com:e

This message was sent to Ogunwale.abiodun@yahoo.com
X-PMG-Recipient: Ogunwale.abiodun@yahoo.com





pmguid:u.qkep.45x6n

From the CEO's Desk         Occasionally, our founder and CEO, Tom Murcko, writes exclusive articles for our newsletter readers. We send these special releases as part of a new series called, 詮rom the CEO's Desk'. Tom hopes that sharing the insight gained from his career will help you achieve your goals. Cheers! What I Learned From Steve Jobs By Tom Murcko CEO of BusinessDictionary.com, InvestorWords.com & InvestorGuide.com 1 Be bold. When Steve was just 12, he called the co-founder of electronics giant Hewlett-Packard to get spare parts for a hobby project. Hewlett was so impressed in that one conversation that he gave Steve a job that summer that started him on his career in technology. 2 Question everything. Always ask, why do we do it that way? Often the answer is just inertia: it's done that way today because it was done that way yesterday, not because it's the best way. By questioning the way things were, he became an expert at seeing how things could be better. He envisioned desktop publishing, the networked office, and the pervasive, transformative power of the internet long before most others. 3 Make your own rules. At college he skipped the required classes and instead just took whatever interested him. (This included a calligraphy class, which contributed to Apple's leadership on fonts and desktop publishing.) After a while he decided that school was too expensive for his parents to pay for, so he stopped paying his tuition, but he was so charismatic that the dean allowed him to audit classes and stay in a dorm with friends, effectively going to college without having to pay. 4 Live with intensity. Life is short. Don't spend it living someone else's life, and don't spend it on small matters. If something isn't worth doing with intensity, then it's not worth doing at all. 5 Learn from the best. Steve wanted to innovate, so he studied the leading innovators. In Apple's early days, this was Xerox Parc, so he visited their research labs and saw demonstrations on cutting-edge technologies that changed the trajectory of his company, including graphical user interfaces, object oriented programming, and networked computing. 6 Let everything be your teacher. Apple took the best ideas from all fields. The early Macintosh team included people with backgrounds in music, poetry, art, history and other liberal arts, who also happened to be among the best programmers in the world. If not for computer science, they would've done amazing things in these other fields. Bringing together diverse expertise made the products better in countless ways. Click to Read Lessons 7 - 23

Here comes a new initiative!!

WISDOM GALLERY COMPUTER INSTITUTE
Arena of displaying talents

watch out for link to the blog, till then start logging.

Fuel starvation

Fuel exhaustion

There are two main ways that an engine can run out of fuel:

• Using all of the fuel. An engine can use all available fuel due to insufficient fuel being loaded for the planned journey or the journey time extended for too long (in the case of an aircraft, due to in-flight delays or problems). Incidents of this type involving aircraft include Air Canada Flight 143,^[1] Avianca Flight 52,^[2] and Ethiopian Airlines Flight 961.^[3]
• Leaking. In some cases, the fuel tank or the supply piping to the engine leaks and fuel is lost. This can cause engines to starve. Cases of this nature involving aircraft include Air Transat Flight 236.^[4]

Fuel starvation

Fuel starvation is slightly different from fuel exhaustion, in that fuel is in the tank but there is a supply problem which either fully or partially prevents the fuel from reaching the engine. Causes may include a blocked fuel filter, problems with fuel tank selection if multiple tanks are installed, or more commonly water-contaminated fuel. Fuel has a lower specific gravity than water which means that any water in the fuel will collect in the bottom of a fuel tank. As fuel is typically drawn from the lowest part of the tank, water is delivered to the engine instead and the engine starves.^[5]


Fuel exhaustion and starvation incidents on aircraft

Many incidents have happened on aircraft where fuel exhaustion or starvation played a role. A partial list of these incidents follows:

• On 19 June 1954, a Convair CV-240 aircraft operated by Swissair registered HR-IBW ran out of fuel over the English Channel near Folkestone. The aircraft ditched in the Channel, killing three passengers. Four crew members and two passengers were found alive after the crash.^[6]
• On 3 August 1954, a Lockheed 1049C Super Constellation of Air France registered F-BGNA was diverted to Boston after being unable to land at New York-Idlewild Airport due to bad weather. It ran out of fuel before reaching Boston and made a belly landing in a field. There were no fatalities.^[7]
• On 21 August 1963, a Tupolev Tu-124 operated by Aeroflot registered SSSR-45021 experienced a landing gear malfunction after taking off from Tallinn Airport. On finding that the nose gear could neither be retracted nor extended, the crew diverted the flight to Leningrad where they prepared for an emergency landing by circling the city burning off fuel. While circling the city the crew made repeated attempts to get the landing gear to lock down; they possibly became over-preoccupied with this and the aircraft ran out of fuel. The crew ditched the aircraft in the Neva River. There were no fatalities.^[8]
• On November 17, 1964 a Dutch F-104 Starfighter crashed into a mountain in Norway when it ran out of fuel following the death of its pilot. The pilot died due to malfunction of the oxygen mask.^[9]
• On June 4, 1967, A British Midland Canadair C-4 Argonaut registered G-ALHG suffered a double engine failure due to a fuel tank selector problem over Stockport, England. The aircraft crashed and 72 of the 84 onboard died.^[10]
• ALM Flight 980 was a Douglas DC-9-33CF flying from John F. Kennedy International Airport in New York City to Princess Juliana International Airport in St. Maarten, in the Netherlands Antilles, on 2 May 1970. Multiple diversions due to severe weather conditions and several unsuccessful landing attempts depleted the aircraft's fuel to the point where the crew believed there was insufficient remaining to reach an alternative airport and decided to ditch the DC-9 in the Caribbean Sea. There were 23 fatalities among the 63 on board.^[11]
• United Airlines Flight 173, a Douglas DC-8-61 en route from Denver, Colorado to Portland, Oregon on 28 December 1978 experienced a landing gear indicator light malfunction while preparing to land. The aircraft continued to circle in the vicinity of Portland while the crew investigated the problem, but it ran out of fuel and crash-landed in a sparsely populated area, killing 10 and seriously injuring 24 of the 181 on board.^[12]
• On 23 July 1983, due to a chain of events and mistakes Air Canada Flight 143 was fuelled using pounds as the unit of measure instead of kilograms, resulting in only half the required amount of fuel being on board. The aircraft used up all available fuel and glided to Gimli Industrial Park Airport where the airliner landed safely. The aircraft is now famously known as the "Gimli Glider."^[13]
• A Cessna 208A Caravan, used for skydiving operations at Jenkinsburg, Georgia, crashed following a loss of engine power just after taking off on 29 September 1985. The aircraft had been refuelled with contaminated fuel; all 17 occupants died.^[14]
• After a string of mistakes and omissions by the pilots, a Boeing 737-200 operating Varig Flight 254 on 3 September 1989 strayed hundreds of miles off-course, ran out of fuel, and crashed in Brazil's Amazon jungle killing 13 of the occupants. Due to the crew's mistake in flying the aircraft west (270°) instead of north-northeast (027°), the aircraft was not found until four survivors walked onto a farm two days later.^[15]
• On 25 January 1990, Avianca Flight 52 was in an extended holding pattern over John F. Kennedy International Airport in New York City due to fog. The Boeing 707-320B was delayed many times before it was given clearance to land. By then, Flight 52 had run out of fuel and crashed into Cove Neck, New York, killing 73.^[16]
• A McDonnell Douglas F/A-18A Hornet of the Royal Australian Air Force, serial number A21-41, was lost on 5 June 1991 after the pilot became incapacitated. The aircraft flew until it ran out of fuel and crashed in a remote part of Queensland. The wreckage was not found until over three years later.^[17][18]
• The crew of Indian Airlines Flight 440, an Airbus A300B2-101, executed a missed approach procedure at Hyderabad-Begumpet Airport on 15 November 1993 due to poor visibility. During the missed approach a problem developed when the flaps would not retract fully. After some time trying to solve the flap problem and find somewhere to land near Hyderabad, the crew diverted the aircraft to Madras but because they had to fly slower due to the extended flaps the aircraft ran out of fuel. It landed in a paddy field near Tirupati; there were no fatalities among the 262 occupants but the aircraft was written-off.^[19]
• On 17 January 2008, ice crystals in the fuel lines of British Airways Flight 38 melted and refroze within the fuel-oil heat exchangers of the Rolls-Royce Trent 800 engines. The ensuing fuel starvation critically reduced engine power on short final into London Heathrow Airport, and the Boeing 777-236 landed just short of the runway. All 152 passengers and crew on board survived, but the aircraft was written off, the first hull loss recorded for the Boeing 7