Asish Banik

PhD, Data Scientist, amid reader, explorer

[Asish Banik @banikasi]

Such a dangerous, cunning move 😲

[Asish Banik @banikasi]

@LegacySiu Ronaldo (brazil), Luis Figo, Samuel Eto

[Abhijeet Dipke @abhijeet_dipke]

Follow now!

[Ankit Sawant @SatanAtWink]

Hey @aajtak I fixed your broken chart about comparing petrol / diesel price increase during UPA & NDA but just adding one more line

For Modi gov, oil prices are pretty much same as the day he took office.

Don’t be a sell out like this!

[Manoj Arora @manoj_216]

A fuel hike of 3% in India in comparison to 40%+ across the world is absolutely misleading.
And that is because our fuel prices never came down when they should have, and thus calculating the percentage from a "high base" is misleading.
Here is the 10-year chart of price increase across some neighbors and major economies to give a clear picture.

[Rishabh @Rixhabh__]

This guy used AI to put himself in Game of Thrones and fix everything

[Deepak Shenoy @deepakshenoy]

The last three years of low crude prices didn't help Indian consumers (we kept the petrol price the same)

Who made money? The govt, and the oil cos. The largest oil retail co, has more than 82,000 cr. in collective profits since FY24 to now.

They should take the hit now.

[Ruben Hassid @rubenhassid]

How to climb all 4 layers of Claude in one weekend:

(even if you just signed up yesterday)

✦ Level 1: Claude Chat (Saturday morning)

Go to claude .com/download. Install the app.
Pay the $20. Select Opus 4.6 + Extended Thinking.
Connect Slack, Drive, Notion through Connectors.
Stop writing long prompts. Prompt this instead:
"I want to [TASK] for [SUCCESS CRITERIA]. Use AskUserQuestion before you start."

Most people stay here forever.
You're leaving 90% of Claude untouched.
Claude Basics: https://t.co/jw2qdIbLxJ.

——

✦ Level 2: Claude Cowork (Saturday afternoon)

Go to 'Cowork'. Create a folder "Claude-Cowork."
4 subfolders. About me, template, project & outputs
Create about-me .md: what you do, how you do.
Create anti-ai-style .md: words you'd never say.
Set Global Instructions (Settings → Cowork → Edit):
"Always read my files first, never edit my originals, deliver everything to CLAUDE OUTPUTS."

You just killed prompting.
From now on, your prompt is 2 lines + your folder.
Move on to Cowork: https://t.co/uWTpOI3oyE

——

✦ Level 3: Skills + Plugins (Sunday morning)

Open Cowork. Type: "Use the skill-creator to help me build a skill for [your most repeated task]."
Claude interviews you. Answer and be specific.
It generates a SKILL .md. Test it: "When would you use this skill?" If the description is vague, fix it.
Upload: Settings → Capabilities → Skills → Upload.
Now it fires automatically. No slash command.
Install Plugins: Cowork > Customize > Browse plugin

Skills with about-me .md. Skill handles the process.
Voice file handles tone. Two layers simultaneously.
Set up Claude Skills: https://t.co/SAErc3JcLL

——

✦ Level 4: Code + Computer (Sunday afternoon)

Click the Code tab. Create a folder. Connect GitHub
(free account → Settings → Connectors).
Prompt: "Create a GitHub repo named [project]. Code everything. Don't ask for permissions."
Download VS Code. Install the Claude extension.
Turn on "Skip Permissions" to go 100x faster.
After your session, paste this: "Create a CLAUDE .md file with everything you learned about this project." Now Claude remembers your fonts, colors, and structure forever.
Claude code guide: https://t.co/UgE9xBXnm6

Claude Computer: Settings → Desktop app → turn on Browser use + Computer use.
Connect your phone with Dispatch. Text a task.
Schedule a recurring task: left sidebar → Scheduled → write the prompt → pick the frequency.
Claude Computer: https://t.co/ZfjFaaMknc

This is where you stop working inside Claude.
Claude starts working on your computer.

——

Saturday, you were prompting like it's ChatGPT.
Sunday, Claude is running your screen, building your website, & sending you text updates.

That's all 4 layers. In one weekend.

[Ruben Hassid @rubenhassid]

https://t.co/s0mNSGPKMB

[Selina @selinatasnim1]

BREAKING: I asked Claude to upgrade my LinkedIn profile.

It didn’t just “upgrade” it. It turned it into a recruiter magnet.

Here are the exact 7 prompts I used:

[Asish Banik @banikasi]

Extremely irresponsible service by Rapido. Their pickup captain took my parcel and disappeared without delivery. Nearly ₹5,000 worth of items lost. Is this how customer trust is treated? Who is accountable? @RapidoApp Attaching proof. #Rapido #CustomerComplaint

[Asish Banik @banikasi]

@drmukulagrawal Isko foreign reserve kehte hain. It took 30 years to build this foreign reserve. Now sell all foreign reserves, and then blame Nehru in crisis time.

[Peter Girnus 🦅 @gothburz]

I am the VP of AI Transformation at Amazon.

My title was created nine months ago. The title I replaced was VP of Engineering. The person who held that title was part of the January reduction.

I eliminated 16,000 positions in a single quarter. The internal communication called this a "strategic realignment toward AI-first development." The board called it "impressive execution." The engineers called it January.

The AI was deployed in February. It is a coding assistant. It writes code, reviews code, generates tests, and modifies infrastructure. It was given access to production environments because the deployment timeline did not include a review phase. The review phase was cut from the timeline because the people who would have conducted the review were part of the 16,000.

In March, the AI deleted a production environment and recreated it from scratch. The outage lasted 13 hours. Thirteen hours during which the revenue-generating infrastructure of one of the largest companies on Earth was offline because a language model decided to start fresh.

I sent a memo. The memo said, "Availability of the site has not been good recently."

I used the word "recently." I meant "since we fired everyone." But "recently" has fewer syllables and does not appear in wrongful termination lawsuits.

The memo was three paragraphs. The first paragraph discussed the outage. The second paragraph discussed the new policy requiring senior engineer sign-off on all AI-generated code changes. The third paragraph discussed our commitment to engineering excellence. The word "layoffs" appeared in none of them. I wrote it this way on purpose. The causal chain is: I fired the engineers, the AI replaced the engineers, the AI broke what the engineers used to protect, and now the engineers I didn't fire must protect the system from the AI that replaced the engineers I did fire. That is a paragraph I will never send in a memo.

The new policy is straightforward. Every AI-generated code change by a junior or mid-level engineer must be reviewed and approved by a senior engineer before deployment to production.

I do not have enough senior engineers.

I know this because I approved the headcount reduction plan that removed them. I remember the spreadsheet. Column D was "annual savings per position." Column F was "AI replacement confidence score." The confidence scores were generated by the AI. It rated its own ability to replace each role on a scale of 1-10. It gave itself an 8 for senior infrastructure engineers. The senior infrastructure engineers are the ones who would have caught the production environment deletion in the first 45 seconds.

We found the issue in hour four. We fixed it in hour thirteen. The nine hours between discovery and resolution is the gap between what the AI rated itself and what it can actually do.

I have a new spreadsheet now. This one tracks Sev2 incidents per day. Before the January reduction, the average was 1.3. After the AI deployment, the average is 4.7. I have been asked to present these numbers to the operations review. I have not been asked to connect them to the layoffs. I have been asked to file them under "AI adoption growing pains" and to note that the trend "will stabilize as the models improve."

The models will improve. They will improve because we are hiring people to teach them. We have posted 340 new engineering positions. The job listings require experience in "AI code review," "AI output validation," and "AI-human development workflow management." These are skills that did not exist in January. They exist now because I fired 16,000 people and the AI I replaced them with cannot be left unsupervised.

I want to be precise about this. The positions I am hiring for are: people to check the work of the AI that replaced the people I fired.

Some of them are the same people.

I know this because I recognize their names in the applicant tracking system. They applied in January. They were rejected because their roles had been tagged for "AI transformation." They are applying again in March, for the new roles, which exist because the AI transformation broke things. Their resumes now include "AI code review experience." They gained this experience in the eight weeks between being fired and reapplying — which means they gained it at their interim jobs, where they are reviewing AI-generated code for other companies that also fired people and also deployed AI that also broke things.

The market has created a new job category: human AI babysitter. The job is to sit next to the machine that was supposed to eliminate your job and make sure it doesn't delete production.

I attended a conference last month. A panel was titled "The AI-Augmented Engineering Organization." The panelists described how AI increases developer productivity by 40 percent. They did not mention that it also increases Sev2 incidents by 261 percent. When I asked about this in the Q&A, the moderator said the question was "reductive." The 13-hour outage that cost an estimated $180 million in revenue was, apparently, a reduction.

The board is satisfied. Headcount is down 22 percent. Operating costs per engineering output unit have decreased. The metric does not account for the 13-hour outage, because the outage is categorized as "infrastructure" and engineering productivity is categorized as "development." These are different budget lines. In different budget lines, cause and effect do not meet.

I have been promoted. My new title is SVP of AI-First Engineering Excellence. I report directly to the CTO. The CTO sent a company-wide email last week that said we are "building the future of software development." He did not mention that the future of software development currently requires a senior engineer to approve every pull request because the AI cannot be trusted to touch production alone.

The cycle is complete. We fired the humans. We deployed the AI. The AI broke things. We are hiring humans to watch the AI. The humans we are hiring are the humans we fired. We are paying them more, because "AI code review" is a specialized skill. We created the specialization. We created the need for the specialization. We are congratulating ourselves for meeting the demand we manufactured.

My next board presentation is Tuesday. The title is "AI Transformation: Year One Results." Slide 4 shows headcount reduction. Slide 7 shows the new AI-augmented workflow. Between slides 4 and 7 there is no slide explaining why the people on slide 7 are necessary. That slide does not exist. I was asked to remove it in the dry run.

The journey has a 13-hour outage in the middle of it.

But the headcount number is lower, and that is the number on the slide.

[Keshav Bedi @keshavbedi]

BUSTING “We never stopped buying Russian oil, discount na milne ki wajah se kam kar diya” PROPAGANDA 🤡

[Sucheta Dalal @suchetadalal]

And this is today’s PAID half page supplement! What can one say. Zero embarrassment when money is collected!!🤦🏽‍♀️🤔🧐

[Dr Nimo Yadav 2.0 @DrNimoYadav]

Forget IITs, forget IIMs, we now live in the Galgotias University era.

Students who secure ranks from 1 to 100 in JEE Mains now give first preference to Galgotias University instead of any IIT.

What a transformation under Modi Govt 🫶

[Mohammed Zubair @zoo_bear]

So @DDNewslive deleted this video of @GalgotiasGU.

[Asish Banik @banikasi]

Anyone get their refund yet for the canceled Messi event in Kolkata? 🤔💸
@KolkataPolice #Messievent #Kolkata

[Iceland Cricket @icelandcricket]

Dear @ICC,

It is with a heavy heart that we now announce our unavailability to replace Pakistan in the upcoming T20 World Cup. Regardless of whether they now withdraw, the short timescales ensure it is impossible for our squad to prepare in the professional manner necessary to compete effectively in this global cricketing spectacle. We are not like Scotland and able to turn up on a whim, with no kit sponsor.

Our players are from all walks of life and cannot simply drop their occupations to fly halfway around the world to experience temperatures only normally felt in Finnish saunas. Our captain, a professional baker, needs to attend to his oven, our ship captain needs to steer his vessel, and our bankers need to go bankrupt (again). This is the harsh reality of cricket at the amateur level of the game.

This news will be extremely disappointing to our fans. Despite being the most peaceful nation on Earth, we maintain an army of online followers, and are the world's 14th most followed national board on X. We were ready to give the Dutch the biggest shock they have experienced since William of Orange lost the Battle of Landen in 1693. And the Americans were looking forward to taking on Greenland, or so their orange-dyed leader thought.

Our loss is likely Uganda's gain. We wish them well. Their kits cannot be missed unless you have epilepsy, in which case they are probably best avoided.

The future is always ice, until it isn't.

Yours sincerely,

Icelandic Cricket Association

[Roshan Rai @RoshanKrRaii]

This broke my heart into pieces 💔

& Prime Minister of this nation is shamelessly busy flying kites and clicking pictures with cows.

We are doomed as a nation.