Thursday, December 25, 2025

Key Teachings of the Bhagavad Gita

 

Key Teachings of the Bhagavad Gita

Understanding Duty and Dharma

  • Dharma: The Gita emphasizes the importance of performing one's duty (dharma) without attachment to the results. Arjuna learns that fulfilling his responsibilities as a warrior is essential, even when faced with moral dilemmas.

  • Karma Yoga: This principle teaches that one should act selflessly, focusing on actions rather than outcomes. "You have a right to perform your prescribed duties, but you are not entitled to the fruits of your actions."

The Nature of the Self

  • Eternal Soul: The Gita distinguishes between the physical body and the eternal soul (ātman). It teaches that the soul is immortal and transcends physical existence, which helps alleviate the fear of death.

  • Mind Control: The text highlights the importance of mastering one's mind. A well-trained mind can lead to liberation, while an uncontrolled mind can lead to bondage.

Balance and Moderation

  • Moderation in Life: The Gita advocates for balance in all aspects of life, including work, rest, and recreation. This balance is crucial for physical and mental well-being.

  • Acceptance of Change: It teaches that change is a constant in life. Embracing change with equanimity fosters resilience and adaptability.

Inner Peace and Contentment

  • Focus on the Present: The Gita encourages individuals to concentrate on their current actions rather than worrying about past failures or future outcomes. This focus can lead to greater satisfaction and peace.

  • Letting Go of Attachments: It advises against attachment to material possessions and outcomes, promoting a mindset of contentment and inner peace.

Universal Principles

  • Unity of Existence: The Gita teaches that all beings are interconnected and part of a greater whole. Recognizing this unity fosters compassion and understanding.

  • Selfless Service: Engaging in acts of kindness and service to others enriches one's life and nurtures meaningful relationships.

These teachings provide timeless wisdom applicable to modern life, guiding individuals toward clarity, purpose, and spiritual growth.

Friday, May 19, 2017

Weight loss is NOT just WHAT you EAT, it is also WHEN you EAT

Weight loss can be tied to when, not just what, you eat

(CNN) - By Lisa Drayer, CNN , May 19, 2017 If you are trying to lose weight and otherwise improve your health, you may already be mindful about what you eat during the day.
You might skip breakfast. At lunch, you may opt for a salad with lots of veggies, no croutons and low-fat dressing -- on the side, of course.
Then, three o'clock hits.
You're incredibly hungry and craving candy, sweets or chips. You finally cave, eating a candy bar or other treat.
By 6 p.m., you're tearing the kitchen apart, snacking on anything you see
Despite your best efforts at cutting carbs at meals, you give in to a large helping of pasta or pizza. And then another. But you're still not satisfied. Dessert is calling, and you want something sweet, again. A scoop or two of ice cream satisfies you for the moment, but you continue to graze into the night until finally, you're so tired, you crash into bed.

So what is the cause of all of this diet drama that keeps occurring, almost according to schedule?
"I started noticing a common pattern where my patients were so good with restricting their calories during the day, but in the late afternoon and evening, they fell apart," said Tamara Duker Freuman, a nutritionist who has helped hundreds of people lose weight over the past decade on a meal-timing based plan she describes as the "circadian-synced diet."
"It was the ongoing grazing into the night. ... That's what kept undermining them. They often thought they were binge eaters ... but in reality, they were just really hungry.
"If they just ate a little more at breakfast and lunch, if they just added a few hundred extra calories in the morning, they would get their eating under control and lose weight," she said.
Despite your best efforts at cutting carbs at meals, you give in to a large helping of pasta or pizza. And then another. But you're still not satisfied. Dessert is calling, and you want something sweet, again. A scoop or two of ice cream satisfies you for the moment, but you continue to graze into the night until finally, you're so tired, you crash into bed.

So what is the cause of all of this diet drama that keeps occurring, almost according to schedule?
"I started noticing a common pattern where my patients were so good with restricting their calories during the day, but in the late afternoon and evening, they fell apart," said Tamara Duker Freuman, a nutritionist who has helped hundreds of people lose weight over the past decade on a meal-timing based plan she describes as the "circadian-synced diet."
"It was the ongoing grazing into the night. ... That's what kept undermining them. They often thought they were binge eaters ... but in reality, they were just really hungry.
"If they just ate a little more at breakfast and lunch, if they just added a few hundred extra calories in the morning, they would get their eating under control and lose weight," she said.
At the end of the 20-week study period, the late eaters lost less weight compared with the earlier eaters (17 vs. 22 pounds on average, respectively) and lost their weight more slowly, despite the fact that both groups ate approximately 1,400 calories per day and consumed similar amounts of fat, protein and carbohydrates.

Another study followed two groups of overweight women with metabolic syndrome on identical 1,400-calorie weight loss diets for 12 weeks. The only difference between the groups was that their calories were distributed differently throughout the day: Both groups consumed 500 calories at lunch, but one group consumed 700 calories for breakfast and a 200-calorie dinner (the "big breakfast" group), while the other group ate 200 calories at breakfast and 700 calories at dinner (the "big dinner" group).

The nutrient content of the meals was exactly the same for both groups, the only difference being that the breakfast and dinner meals were swapped. After 12 weeks, the big breakfast group lost about 2½ times more weight than big dinner group (8.7 pounds for big breakfast group vs. 3.6 pounds for big dinner group) and lost over 4 more inches around their waist.
The big breakfast group experienced a 33% drop in triglyceride levels -- a marker associated with heart disease risk -- while the group that ate the higher-calorie dinner experienced a 14.6% increase. The bigger breakfast group also experienced greater reductions in fasting glucose, insulin and insulin resistance scores, all of which indicate decreased risk for type 2 diabetes, according to the study's authors.

So front-loading calories and carbohydrates is not only favorable in terms of weight loss, it had beneficial effects on other indicators of overall health, including decreased risk for type 2 diabetes and cardiovascular disease.

That second study "opened my eyes," Freuman said. "It wasn't just that people were less hungry and eating less at night, but it pointed to the fact that there might be some sort of underlying metabolic magic going on, where the timing of calories and carbs mattered more than the total amount of calories and carbs eaten in a day. It helped me understand what I was intuitively seeing in my patients."

Circadian rhythms: the 'metabolic magic'
More and more research is suggesting that when you eat may be just as important as what you eat. And it is very closely tied to the complex science of circadian rhythms.
According to the National Institute of General Medical Sciences, circadian rhythms are physical, mental and behavioral changes that follow a roughly 24-hour cycle, responding primarily to light and darkness in an organism's environment.

Circadian rhythms are driven by biological clocks inside our bodies. The brain has a master biological clock, influenced mainly by light, which tells "peripheral" clocks in the muscles and organs what time of day it is. Because of these clocks, many of the metabolic processes that take place inside us operate at different rates over the course of a 24-hour period.

Because of circadian rhythms, there are variations in certain hormone levels, enzyme levels and glucose transporters at different parts of the day, which differentially affect how calories, carbohydrates and fat are metabolized," said Freuman, who presented case studies of patients who improved their weight and health by eating in sync with circadian rhythms at the New York State Academy of Nutrition and Dietetics annual meeting in May 2016.
Circadian rhythms can help explain why eating late at night increases the likelihood of weight gain and decreases the rate at which we lose weight, compared with eating earlier in the day.
For example, research suggests that the calories we burn from digesting, absorbing and metabolizing the nutrients in the food we eat -- known as diet-induced thermogenesis -- is influenced by our circadian system and is lower at 8 p.m. than 8 a.m., according to Frank A.J.L. Scheer, director of the Medical Chronobiology Program in the Division of Sleep and Circadian Disorders at Brigham and Women's Hospital in Boston.
Other metabolic processes involving insulin sensitivity and fat storage also operate according to circadian rhythms and can greatly influence the likelihood of weight gain or weight loss at different times of the day.
"These different metabolic processes ebb and flow at different times of the day, and they play a role in how your body metabolizes food energy, which ultimately affects your weight, cholesterol levels and blood sugar control -- and so it has tremendous implications for what is considered optimal times for eating," Freuman said.

Breakfast-skippers beware
Circadian rhythms may help explain why breakfast skipping is associated with increased risk of weight gain, even among those who consume comparable amounts of calories in a day.
"The link between breakfast skipping and obesity had once been thought to be due to overcompensation of calories at subsequent meals due to excess hunger ... but the research does not consistently show differences in total energy intake among breakfast-skippers," Freuman said.
"Something else about skipping breakfast -- aside from potentially eating more calories later in the day -- must explain the greater risk of weight gain among breakfast skippers," she said. A more likely answer: Eating more calories in the later part of the day is out of sync with metabolic circadian rhythms.
"We get less metabolically robust as we age," she explained. "So even if you've gotten away with skipping breakfast and eating out of sync in your 20s or 30s, it may eventually catch up with you."
Night shift workers can also benefit from eating in sync with their circadian rhythms. They may modify meal timing to sync up with metabolic circadian rhythms by eating breakfast at the end of their workday, at 7 or 8 a.m., and then eating their heaviest meal when they wake up, about 3 or 4 p.m.
Freuman discourages her night shift patients from eating during the night. "We don't want them eating many calories, so we'll have them sip on tea or have a Thermos of miso soup or, if need be, something small like an apple in order to minimize overnight calories.
"Your metabolism is working in a certain way, whether you are awake or asleep -- so even if you are awake during most of the night, you still want to be eating most of your calories during daylight. Sleep has little to do with it," Freuman said.
Tips for eating in sync with circadian rhythms
So how do we eat in sync with our circadian rhythms? They key is to front-load your calories and carbs. Freuman suggests the following, which she advises to her patients:

1. Don't skip breakfast
Ideally, breakfast should be satiating enough to preclude the need for a midmorning snack, and it should have a minimum of 300 calories, according to Freuman. It should always include high-fiber carbohydrates, which are more slowly digested than refined carbs, and it should include protein, which helps keep hunger in check.
Good breakfasts include a cup of cooked oatmeal with low-fat milk and a small handful of nuts, two slices of Ezekiel or whole-grain bread with mashed avocado and sliced tomato, or a two-egg omelet with veggies, fruit and a slice of whole-wheat toast.
If you are not hungry when you wake up, you can defer breakfast for a few hours -- but it should not be skipped, according to Freuman.

2. Have the "blue plate special" for lunch
"Lunch should be like that blue plate special ... the main meal of the day," Freuman said.
For a simple lunch strategy, Freuman suggests filling half of your plate with non-starchy vegetables and then dividing the second half into protein (like grilled fish or chicken) and slowly digested high-fiber carbohydrates (like beans or quinoa). "A salad with grilled chicken is fine, but try adding a baked sweet potato, a heaping scoop of chickpeas or even a thick, hearty lentil soup," she said.
If you prefer a sandwich for lunch, pair it with fiber-rich vegetables. "A turkey sandwich is part of a good lunch, but it's not a whole lunch." Try adding butternut squash soup or carrots with hummus.
Other good lunches that Freuman recommends include baked salmon with lentils and cooked green veggies or a Mexican quinoa bowl with quinoa, black beans, chicken, avocado and salsa, along with a pile of greens.
The easiest way to plan for lunch may be to use last night's leftovers. "I cook dinner at home and bring in my leftovers for lunch the next day. When I get home from work, I'm not tearing the house apart."

3. Pack a snack
An afternoon snack may be necessary if lunch and dinner are more than five hours apart. However, it should be no more than 200 calories, and it should be high in protein and fiber. "This will prevent you from arriving at dinner feeling 'starving,' " Freuman said.
Snacks that will satisfy include an apple with a tablespoon of peanut butter, grape tomatoes with string cheese, a hard-boiled egg or plain Greek yogurt with fruit.

4. Go low-carb for dinner
Dinner should be light and low in carbohydrates. "The more you can go low-carb for dinner, the more it will mitigate the effects of distorted calories at night," Freuman said.
Dinners might include fish and a cooked vegetable, lettuce-wrapped tacos or a turkey burger (minus the bun) and a salad with light dressing.
"I'll make turkey meatballs for my kids, and I'll give them pasta too, but I'll have mine on a bed of spinach -- and the next day, I'll bring the pasta for lunch."
And when dining out, Freuman suggests ordering two appetizers, like a salad and a shrimp cocktail or grilled calamari.


Wednesday, December 28, 2016

Leadership

Leadership is NOT about you, It's about making other people better as a result of your presence and making sure that impact it lasts in your absence and making sure systems and culture is are place to set other people to succeed even when you are not in the room.

Anne Morriss, managing director of the Concire Leadership Institute.

Monday, May 16, 2016

AWS : The Software Division of Amazon


Cool lyrics by Pharell Williams

Happy - Lyrics by Pharell Williams
It might seem crazy what I'm about to say
Sunshine she's here, you can take a break
I'm a hot air balloon, I could go to space
With the air, like I don't care baby by the way
Because I'm happy
Clap along if you feel like a room without a roof
Because I'm happy
Clap along if you feel like happiness is the truth
Because I'm happy
Clap along if you know what happiness is to you
Because I'm happy
Clap along if you feel like that's what you wanna do
Here come bad news talking this and that
Yeah, give me all you got, don't hold back
Yeah, well I should probably warn you I'll be just fine
Yeah, no offense to you don't waste your time
Here's why
Because I'm happy
Clap along if you feel like a room without a roof
Because I'm happy

Stats on the place we LIVE !!!

About 71% of the Earths surface is covered by water;29% of it is land. The oceans hold about 96.5% of all Earths water. Earth water is a total volume of 1.332 billion cubic kilometers (351 quintillion US gallons)

There are 196 countries in the world today. Taiwan is not considered an official country by many, which would bring the count down to 195 countries. Although Taiwan operates as an independent country, many countries (including the U.S.) do not officially recognize it as one

7 Continents
Asia
Africa
North America
South America
Antartica
Europe
Australia

5 Oceans:
Artic
Atlantic
Indian
Pacific
Southern

Friday, April 1, 2016

Great Architecture Links


Great Architecture Links


Key Principles of Software Architecture
https://msdn.microsoft.com/en-us/library/ee658124.aspx

Architectural Patterns and Styles
https://msdn.microsoft.com/en-us/library/ee658117.aspx
Crosscutting Concerns
https://msdn.microsoft.com/en-us/library/ee658105.aspx

A Technique for Architecture and Design
https://msdn.microsoft.com/en-us/library/ee658084.aspx



10 Lessons from 10 Years of Amazon Web Services - By Werner Vogels

Excellent experience of Werner Vogels from Amazon
The epoch of AWS is the launch of Amazon S3 on March 14, 2006, now almost 10 years ago. Looking back over the past 10 years, there are hundreds of lessons that we’ve learned about building and operating services that need to be secure, reliable, scalable, with predictable performance at the lowest possible cost. Given that AWS is a pioneer in building and operating these services world-wide, these lessons have been of crucial importance to our business. As we’ve said many times before, “There is no compression algorithm for experience.” With over a million active customers per month, who in turn may serve hundreds of millions of their own customers, there is no lack of opportunities to gain more experience and perhaps no better environment for continuous improvement in the way we serve our customers.
I have picked a few of these lessons to share with you in the hope that they may be of use for you as well.
1. Build evolvable systems
Almost from day one, we knew that the software we were building would not be the software that would be running a year later. The expectation was that with each order or two of magnitude, we would need to revisit and revise the architecture to make sure we could address the issues of scale.
But we couldn’t adopt the old style approach of upgrading systems through a maintenance outage, as many businesses around the world are relying on our platform for 24/7 availability. We needed to build such an architecture that we could introduce new software components without taking the service down. Marvin Theimer, Amazon Distinguished Engineer, once jokingly said that the evolution of Amazon S3 could best be described as starting off as a single engine Cessna plane, but over time the plane was upgraded to a 737, then a group of 747s, all the way to the large fleet of Airbus 380s that it is now. All the while, we were refueling in midair and moving customers from plane to plane without them even realizing it.
2. Expect the unexpected
Failures are a given and everything will eventually fail over time: from routers to hard disks, from operating systems to memory units corrupting TCP packets, from transient errors to permanent failures. This is a given, whether you are using the highest quality hardware or lowest cost components.
This becomes an even more important lesson at scale: for example, as S3 processes trillions and trillions of storage transactions, anything that has even the slightest probability of error will become realistic. Many of those failure scenarios can be anticipated beforehand, but many more are unknown at design and build time.
We needed to build systems that embrace failure as a natural occurrence even if we did not know what the failure might be. Systems need to keep running even if the “house is on fire.” It is important to be able to manage pieces that are impacted without the need to take the overall system down. We’ve developed the fundamental skill of managing the “blast radius” of a failure occurrence such that the overall health of the system can be maintained.
3. Primitives not frameworks
Pretty quickly, we started to realize that the way customers would like to use our services was a work in progress. When customers left the constraining, old world of IT hardware and datacenters behind, they started to develop systems with new and interesting usage patterns that no one had ever seen before. As such, we needed to be ultra-agile to make sure we were catering to our customers’ needs.
One of the most important mechanisms we provided was to offer customers a collection of primitives and tools, where they could pick and choose their preferred way to engage with the AWS cloud, instead of only providing one framework that they are forced to use, which includes everything and the kitchen sink. This approach has enabled our customers to become so successful, that even later generations of AWS services make use of exactly the same primitive services our customers have become accustomed to.
It is also important to realize that it is hard to predict what certain priorities are for your customers until they have the service in their hands and actually start building with it. This is why we deliver new services often with a minimal feature set and allow our customers to help drive the roadmap for extending the service with new features.
4. Automation is key
Developing software services that need to be operated is radically different from building software that needs to be shipped to customers. Managing systems at scale requires a very different mindset to ensure that we meet the reliability, performance, and scalability expectations of our customers.
A key mechanism to achieve this is to automate the management as much as possible, removing error prone, manual operations. To do this, we needed to build management APIs that control the key functionality of our operations. AWS helps its customers do this too. By decomposing your applications into essential building blocks, each with a management API, you can apply automation rules to maintain reliable and predictable performance at scale. A good litmus test has been that if you need to SSH into a server or an instance, you still have more to automate.
5. APIs are forever
This was a lesson we had already learned from our experiences with Amazon retail, but it became even more important for AWS’s API-centric business. Once customers started building their applications and systems using our APIs, changing those APIs becomes impossible, as we would be impacting our customer’s business operations if we would do so. We knew that designing APIs was a very important task as we’d only have one chance to get it right.
6. Know your resource usage
When building a financial model for a service to identify the appropriate charging model, be sure to have good data about the cost of the service and its operations, especially for running a high volume – low margin business. AWS needed to be very conscious as a service provider about our costs so that we could afford to offer our services to customers and identify areas where we could drive operational efficiencies to cut costs further, and then offer those savings back to our customers in the form of lower prices.
An example in the early days where we did not know the resources required to serve certain usage patterns was with S3: We had assumed that the storage and bandwidth were the resources we should charge for; after running for a while, we realized that the number of requests was an equally important resource. If customers have many tiny files, then storage and bandwidth don’t amount to much even if they are making millions of requests. We had to adjust our model to account for the all the dimensions of resource usage so that AWS could be a sustainable business.
7. Build security in from the ground up
Protecting your customers should always be your number one priority, and it certainly has been for AWS… from both an operational perspective as well as tools and mechanisms; it will forever be our number one investment area.
One approach that we learned quickly is that to build secure services, it is necessary to integrate security at the very beginning of service design. The security team is not a group that does validation after something has been built. They must be partners on day one to make sure that security is fundamentally rock solid from the ground up. There is no compromise when it comes to security.
8. Encryption is a first-class citizen
Encryption is a key mechanism for customers to ensure that they are in full control over who has access to their data. Ten years ago, tools and services for encryption were hard to use and it wasn’t until a few years into our operations that we learned how to best integrate encryption into our services.
It started by providing server-side encryption in S3 for compliance use cases. If you would inspect any disks in our datacenters, none of the data would be accessible. But with the launch of Amazon CloudHSM (for hardware security models) and later Amazon Key Management Service, customers could use their own keys for encryption, which removed the need for AWS to manage their keys.
For some time now, support for encryption has been integrated at the design phase of each new service. For example, in Amazon Redshift, each of the data blocks is encrypted by default with a random key and the collection of these random keys is again encrypted with a master key. The master key can be provided by customers, ensuring that they are the only ones who can decrypt and have access to their critical business data or personal identifiable information.
Encryption continues to be a high priority for our business. We will continue to make it even easier for our customers to make use of encryption so they can better protect themselves and their customers.
9. The importance of the network
AWS has come to support many different workloads; from high-volume transaction processing to video transcoding at scale, from high-performance parallel computing to massive web site traffic. Each of those workloads have unique requirements when it comes to the network.
AWS has developed a unique skill to innovate datacenter layout and operations, such that we can have flexible network infrastructure that can be adapted to meet the needs of our customers’ workloads, whatever they may be. We have learned over time that we should not be afraid to develop our own hardware solutions to ensure our customers can achieve their goals. This enables us to meet our very specific requirements, such as the ability to isolate AWS customers from each other on the network to achieve the highest levels of security.
Another successful example of how AWS-designed networking hardware and software enabled us to further improve performance for our customers was in addressing the virtualization tax on network access from virtual machines. Because network access is a shared resource, customers previously could experience significant jitter on the network at times. Developing a NIC that supported single root IO virtualization allowed us to give each VM its own hardware virtualized NIC. This lowered latency more than 2x and delivered more than 10x improvement in latency variability on the network.
10. No gatekeepers
The AWS team has delivered many services and features over time to create a very broad and deep platform for our customers. But AWS is so much more than the services that we built in-house: a very rich ecosystem exists of services delivered by our partners that extends the platform into many new directions.
For example, we have partners like Stripe offering payment services to Twilio making telephony programmable on AWS. Many of our customers are also building platforms themselves on top of AWS to serve specific vertical needs: Philips is building their Healthsuite Digital Platform for managing healthcare data, Ohpen has built a platform for retail banking on AWS, Eagle Genomics has built a genomics processing platform, and many more. What’s essential is that there are no gatekeepers on the AWS platform that tell our partners what they can and cannot do. “No gatekeepers” liberates the innovative processes and opens the door for many unexpected inventions, which are sure to follow.
I am looking forward to seeing what we learn – and AWS customers accomplish – over the next 10 years. And remember, it is still Day One ...

Saturday, February 27, 2016

Quotes by Khalil Gibran

Quotes by Khalil Gibran 

"May there be such a Oneness between us that when one weeps the other tastes salt."

"Out of suffering have emerged the strongest souls; the most massive characters are seared with scars."


You talk when you cease to be at peace with your Thoughts.


"A truth can walk naked...but a lie always needs to be dressed..."


"Be yourself. Not your idea of what you think somebody else's idea of yourself should be".

Monday, January 25, 2016