G Ragu Review

Updated September 2026: this page previously carried a December 2020 item claiming that Covid-19 could mutate into a dangerous new form under the influence of vaccines based on a chimpanzee adenovirus, attributed to a named virologist and institute, with a link to a petition. We could not verify that the person or the institute exist, and the claims were not supported by evidence. The item has been replaced with this correction. This is general information, not medical advice.

In December 2020, this site published a short item warning that mixing a chimpanzee adenovirus vaccine with Covid-19 could create an unmanageable new virus, comparing it with the 1918 flu pandemic. It quoted a "James Kenwood" of a "Minigan Institute of Bacteriology". We found no record of either. The item should not have been published here.

What is an adenovirus vector vaccine?

It uses a harmless, modified adenovirus to carry instructions for the coronavirus spike protein into cells, so the immune system learns to recognise it. The Oxford-AstraZeneca vaccine, made in India as Covishield, uses a chimpanzee adenovirus that has been altered so it cannot replicate. It does not contain the coronavirus and cannot combine with it to form a new virus.

Where do coronavirus variants come from?

Variants arise as the virus copies itself in infected people. The more it spreads, the more chances it has to change. Vaccination reduces spread and severe illness, which limits those chances. Health authorities have tracked variants closely since 2020.

Why was the original item a problem?

It presented alarming claims as fact, credited them to a source that could not be checked, and encouraged readers to act through a petition. Health misinformation can lead people to avoid vaccination that would protect them. This site does not cover medicine, and the item was outside what it should publish.

Where can you find reliable information?

• India's Ministry of Health and Family Welfare, for national guidance.
• The World Health Organization, for international guidance and evidence summaries.
• Your own doctor, for advice about your health and any vaccine.

What has changed on this site?

The original text and its outbound links have been removed. Any factual error found in an older post is now corrected in place with a note like this one, rather than removed silently.

Keep reading

• Smart TV Tracking Runs Until You Stop It
• Amazon's Vega OS Ends Sideloading On Every New Fire Stick
• Starlink India Plans vs Fibre: The Real Cost

Updated September 2026: in 2020 I wrote about a festive sale where I rushed to buy AirPods Pro, paid before applying a coupon, and then saw the iPhone 11 price I was waiting for never drop. I have rewritten it as a guide to avoiding checkout mistakes during big online sales.

I planned to buy AirPods Pro and an iPhone 11 during the festive season, if both came within my budget. I kept checking shopping sites through the promotional build-up. When the sale opened and I saw the reduced price for the AirPods Pro, I ordered at once and paid in full. A few moments later I realised I had not applied a coupon code and had paid slightly more than necessary. I did not mind too much, since I wanted the product quickly. The bigger disappointment was the iPhone 11: its price did not drop, and that part of my plan fell apart.

Why do people make mistakes at sale checkout?

Time pressure. Countdown timers, limited stock and fast-moving prices push you to pay before checking the details. Coupons, bank card offers and exchange discounts are often applied on different screens, and it is easy to skip one.

What should you check before paying?

• The coupon field, and whether the discount shows in the total.
• Bank and card offers, which may apply only to certain cards or at payment.
• The seller, to make sure it is the one you trust.
• Delivery date and return policy.

What can you do if you forgot the coupon?

Options depend on the site. Some let you cancel before dispatch and reorder with the coupon, if the price and stock are still available. Contacting customer support occasionally helps, though sites are not obliged to apply a coupon after payment. If the difference is small, as mine was, it may not be worth the risk of losing the order.

What if the product you want is not discounted?

Decide your target price before the sale starts. If it is not reached, wait. Phones often drop in price after a new model launches, and there are several sales a year. Buying something else just because it is on offer rarely feels good later.

How do you judge whether a sale price is real?

Compare it with the price a few weeks earlier and with other retailers. Price-tracking tools and browser extensions can show the history, so you know whether the discount is genuine.

Keep reading

• Maximize Savings with Smart Shopping tips & tricks
• Last Year's Apple Watch or Wait? How to Decide
• Amazon's Vega OS Ends Sideloading On Every New Fire Stick

Updated September 2026: in 2020 I wrote about my manager promising leadership a deliverable within two days, over a weekend, without asking whether I was available, then pushing me for a draft before any real information arrived. I have rewritten it as a guide to handling a deadline someone else promised for you.

Leadership had criticised my manager for collecting irrelevant information and wasting a week. He promised to share everything they wanted within two days, which fell on a weekend, without checking whether I was free. I had no choice but to work the weekend while he chased the account owners. Before any information came back, he pressed me for a draft, and at one point I had to raise my voice and ask him to stop until there was something to work with. By the end of the day the account team sent inputs that were vague and did not fit the context. With the time left, I shared a first version with leadership for review.

Why do managers commit their team's time without asking?

Usually under pressure. After criticism, a quick promise feels like a way to recover. It is rarely personal, but the cost falls on the person doing the work.

What should you do when it has already happened?

• Ask what exactly was promised, and to whom.
• List the inputs you need and who must provide them.
• Agree a realistic first version, such as a draft with gaps clearly marked.
• Set check-in times instead of constant chasing.

How do you push back without an argument?

Name the dependency calmly: "I can build the structure now, but the numbers depend on the account team. I will fill them in as soon as they arrive." That makes the blocker visible without blaming anyone. Raising your voice may feel justified, but it rarely helps next time.

What do you do with vague inputs?

Use what fits and flag the rest. Mark unclear figures in the draft and list the questions for the account team. Leadership would rather see an honest draft with gaps than a polished one built on guesses.

How do you prevent it next time?

Talk to your manager after the deadline, not during it. Ask to be consulted before commitments that need weekend work, and agree how much notice you need. Framing it as avoiding a rushed result usually lands better than a complaint.

Keep reading

• Caught Between Your Manager and the Client Team
• Said Yes Too Fast at Work? How to Weigh a Request
• Assigned to a New Team Overnight: First Steps

Updated September 2026: in 2020 I wrote about returning from a long vacation to an opportunity where my manager's suggestions kept being rejected by the onsite team, there was no offshore support, and the two sides argued over small things. I have rewritten it as a guide to working between a manager and a client-facing team who do not get along.

After my long vacation, my manager put me on an opportunity with the team I found hardest to work with. He shared inputs that did not match the client's requirements. I worked hard to collect the slides he asked for, and the onsite team rejected them all because they conflicted with what the client wanted. The onsite team then shared new direction, with one condition I found hard to accept: no offshore support at all. My manager tended to complicate simple things and suggest ideas the onsite team would throw out, and both sides had strong egos and argued over small points.

Why do you end up in the middle?

Because you do the work both sides review. Your manager directs you, the client-facing team judges the output, and when they disagree your effort is what gets thrown away.

How do you avoid wasted work?

• Confirm requirements with the client-facing team before building, in writing.
• Show your manager the confirmed brief, so their suggestions start from it.
• Build a small draft first, two or three slides, and get both sides to agree the direction.
• Keep a change log of who asked for what, and when.

What if there is no offshore support?

Adjust the scope. Tell both sides what you can deliver alone by the deadline and ask them to agree priorities. It is better to cut sections early than to deliver everything poorly.

Should you take sides?

No. Stay with the client's requirements. When your manager's idea does not fit them, say so privately and suggest how to adapt it. When the onsite team dismisses something useful, ask what the client would need to see for it to work.

When should you raise it higher?

If arguments start delaying the deliverable, ask for a short call with a senior sponsor to agree the direction once. Frame it around the deadline, not the personalities.

Keep reading

• After a Good Kickoff: Keeping Project Scope in Check
• Building Proposal Slides That Reviewers Choose
• Said Yes Too Fast at Work? How to Weigh a Request

Updated September 2026: in 2020 I wrote about setting up early morning calls with an onsite team, only to find on the first day that nobody had opened the document I had sent. I have rewritten it as a guide to getting people to read before the meeting.

I had planned the service request carefully, set out each team member's role and sent a detailed email to the onsite team for confirmation, with a recurring morning meeting. The next day I woke early and opened the call, hoping they had refined the document. They had not touched it, and reviewed it for the first time during the meeting. I was furious. After the review I said, in front of the leadership on the call, that the discussions would be more useful if the onsite team looked at the document beforehand, and I recorded it in the minutes. I only got a mild acknowledgement, and leadership then asked the team to work on the client's review comments.

Why do people come to meetings without reading?

They are busy, the document is long, or they do not know what they are supposed to do with it. A file sent with "please review" gives no reason to open it before the call, especially across time zones.

How do you get a document read before the meeting?

• Put a short summary in the email, so the main points are read even if the file is not.
• Ask for something specific, such as "confirm your owners in section 2 by 6pm".
• Keep the document short, with the decisions near the top.
• Send it early enough for the other time zone to have a working day with it.
• Use the meeting for decisions, not first reading.

Should you call it out in front of leadership?

Carefully. Raising it with leaders present can work, but it can also make people defensive. A better first step is a private message to the onsite lead. If the pattern continues, mention it neutrally in the minutes, as a fact about preparation rather than a complaint.

What if the meeting is wasted anyway?

Cut it short. Suggest ending early so everyone can read, and meeting again later the same day. People quickly learn that coming unprepared costs them time.

Are early morning calls worth it?

Only if they produce decisions. If they turn into reading sessions, move them to a time when both sides can prepare.

Keep reading

• Caught Between Your Manager and the Client Team
• After a Good Kickoff: Keeping Project Scope in Check
• Helping Your Old Team? Tell Your Manager First

Updated September 2026: in 2020 I wrote about being asked to help my old team with a service request and walking to my manager's cabin to explain it, only to learn he was about to send a rejection email to everyone. I have rewritten it as a guide to getting your manager's support before helping another team.

After a long discussion with my old delivery contact, I understood the request would take very little of my day for the next few days. I had two options. I could simply do the work, since I knew the project and nobody else could step in quickly. But my manager was on the email trail, and doing it without telling him could backfire later if he asked why he had not been told. So I went to his cabin to explain. He told me he was about to send a rejection email to my old team, saying I was tied up with new work and could not support the request. I stopped him in time and explained what was needed and how much effort it would take.

Why should you tell your manager before helping another team?

Because your time is theirs to plan. Even small side work can clash with their priorities, and if they learn about it from someone else, it can look like you went around them. A short conversation avoids that.

What should you say?

• What the request is, in one or two sentences.
• How much time it needs, for example an hour a day for a week.
• Why you are the right person, such as knowledge nobody else has.
• What will not be affected, naming your current priorities.

Why talk in person rather than email?

Speed and tone. In my case an email would have crossed with his rejection. A quick conversation lets your manager ask questions and decide on the spot, and it is harder to misread.

What if your manager says no?

Accept it and help find another option. Offer to hand over notes or join one short call so the other team is not left stuck. That keeps both relationships intact.

How do you keep your manager informed afterwards?

Send a brief update when the work is done and mention any time it took beyond the estimate. It builds trust for the next request.

Keep reading

• Assigned to a New Team Overnight: First Steps
• Said Yes Too Fast at Work? How to Weigh a Request
• When Your Manager Does Not Back You in Public

Updated September 2026: in 2020 I wrote about setting up a kickoff call with an onsite team and an offshore lead I had struggled with before, feeling relieved afterwards, and then wondering whether the work would stay simple. I have rewritten it as a guide to keeping scope under control after a good kickoff.

I was back with the same onsite team and the same offshore delivery lead whose way of working had caused problems before. I owned setting up the call. It began with introductions and the service request details, and afterwards I felt relieved: I already had most of the standard slides, and only a few needed rebuilding. Until the next day's call, I only had to gather slides from the repository and leave blank ones for the onsite team. I still wondered whether it would stay simple or grow every day with new client requirements. As usual, my expectations changed in the calls that followed.

Why does scope grow after a kickoff?

Kickoff calls cover the known requirements. The unknown ones arrive later, as the client answers questions, the onsite team talks to the account and people spot gaps. Each addition seems small, so nobody stops to check the total.

What should you send right after the kickoff?

• A short summary of what was agreed, in plain words.
• A slide list showing which exist, which need rebuilding and who fills each blank one.
• Owners and dates for every open item.
• A line on change: new requirements will be added to the list and may move dates.

How do you handle new requirements as they arrive?

Add each one to the list you sent, with its owner and effect on the timeline. Share the updated list at the next call. When people can see the list growing, they are more willing to drop low-value items or extend the deadline.

What if you have a difficult history with someone on the team?

Start fresh but write things down. Clear owners and dates in writing reduce the room for the misunderstandings that caused trouble last time. Keep the tone neutral and focus on the work.

Is relief after a kickoff a bad sign?

No. It usually means you are well prepared. Just treat the first plan as a draft and check it against each new request.

Keep reading

• Caught Between Your Manager and the Client Team
• Building Proposal Slides That Reviewers Choose
• Said Yes Too Fast at Work? How to Weigh a Request