@rifat_bhai_7798: বাঞ্ছারামপুর 😇🙌

𝗙𝗽𝘀 ❤️‍🔥📷

Open In TikTok:

Region: BD

Tuesday 06 October 2026 04:07:05 GMT

44719

1947

65

427

Music

Download

No Watermark .mp4 (4.04MB) No Watermark(HD) .mp4 (3.17MB) Watermark .mp4 (0MB) Music .mp3

Comments

I′m^ ba′d bo^y..° :

nice 🥲

2026-10-07 13:27:48

1

🦋⃝🐼➳𝓡𝓾𝓹.𝓴𝓸𝓽𝓱𝓪➳🦋⃝🐼 :

এটা বাঞ্ছারামপুর কোন জায়গায় 🤔

2026-10-06 06:12:13

1

⚡𐙚♡—͞᭡፝֟፝ibrahim⸙ᥫ᭡፝֟፝ꫝ💓 :

এই কফি শপটা আমাদের সুমন ভাইয়ের 🙂

2026-10-06 16:50:26

1

@🦋⃟⃟🌻𝐒?:🦋⃟⃟🌻𝐒𝖎𝐦𝖕𝐥𝖊᭄ :

আমিও আসতাছি দেখা হবে রোজ শুক্রবার [Laugh approved][Laugh approved]

2026-10-07 15:43:27

1

a.L.u _ 🥔 :

এটা বাঞ্ছারামপুর কোথায়

2026-10-06 14:07:11

1

🍁মায়াবতী🍁 :

এটা কোথায় ভাইয়া

2026-10-06 12:25:46

1

--...Zara....-- :

2026-10-06 04:26:56

1

B >🚩 :

লোকেশন

2026-10-06 12:40:39

1

Ruhan") :

বাঞ্ছারামপুর মেয়র রোড 🫥

2026-10-07 06:04:43

1

༻⍣⃝চ্ঁক্ঁলে্ঁট্ঁ পা্ঁগ্ঁলী༻⍣⃝ :

এইবার যাওয়া হলোনা আমার😒

2026-10-07 00:59:03

1

🇸🇦সৌঁদিঁ প্রঁবাঁসীঁরঁ বঁউঁ✈️ :

বান্সারামপুর কোন জায়গা এটা নাম কি

2026-10-07 09:53:38

1

🍒Aaya Tunna Ayat🍒 :

বাঞ্ছারামপুর কোন জায়গায় এটা

2026-10-06 14:06:34

1

👑 M.A.I.J.I.D 👑 :

koi

2026-10-06 17:02:49

1

Hd Hd :

বান্ঞ্ছারামপুর বাজার থেকে কোন দিক দিয়ে যেতে হয় বলবেন প্লিজ

2026-10-06 16:49:37

1

—͞Sᴀʙʙᴜᥫ᭡🕊️🫶 :

2026-10-06 04:13:40

0

❤️MD EMON 💞 :

আপু এটা কোন জায়গা বাঞ্ছারামপুর নাকি 🌸

2026-10-07 15:12:33

0

༒ꜱᴀᴍɪʀ࿐ :

কালকে গিয়ে আসলাম ভালোই 👍❤️‍🩹

2026-10-06 17:27:38

0

𝗥 ! 𝗙𝟰 𝗧 🕷️ :

@

2026-10-06 12:07:38

2

Md, hridoy Ahmed💫🌷 :

অসাধারণ

2026-10-06 12:55:59

1

M H Nahid Neyamot :

Kothai?

2026-10-06 17:04:51

2

🌺কিউট ❤️বালিকা 🌺 :

গেছি

2026-10-08 04:56:55

0

SAYIM YAMAL. LW.7🚩🇪🇸 :

@SuMon MaHmud 🙋‍♂️❤️‍🩹

2026-10-06 14:11:14

2

FO°᭄RHAD࿐ :

❤️

2026-10-06 14:36:26

1

tasmim😌🥰😚 :

😳😳

2026-10-06 11:21:08

1

꧁༒☬𝓐𝓷𝓪𝓻𝓾𝓵𝓵𝓪𝓱☬༒꧂ :

🥰🥰🥰

2026-10-06 14:14:26

1

To see more videos from user @rifat_bhai_7798, please go to the Tikwm homepage.

Other Videos

#fy #opapaiquetanazagachallenge

#fy #opapaiquetanazagachallenge

Bài đăng 28: cháo rây mix thịt heo, khoai tím, mồng tơi. Series 30 ngày ăn dặm cho bé 5 tháng. Trvia em Bo nhà Quỳnh ăn dặm từ 5m15d đến nay là hơn 6m rồi các mẹ cho bé ăn đến đâu rồi .. #mevabe #andam #andamcungbe #thucdonandam #mebimsua

Bài đăng 28: cháo rây mix thịt heo, khoai tím, mồng tơi. Series 30 ngày ăn dặm cho bé 5 tháng. Trvia em Bo nhà Quỳnh ăn dặm từ 5m15d đến nay là hơn 6m rồi các mẹ cho bé ăn đến đâu rồi .. #mevabe #andam #andamcungbe #thucdonandam #mebimsua

simple leg day for sculpted legs 🤝

simple leg day for sculpted legs 🤝

#CapCut

A repo called “superpowers” has 265,000 stars on GitHub. What it actually installs is discipline. Four of its fourteen skills have a section titled, literally, “The Iron Law”. Here they are, word for word: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE NO SKILL WITHOUT A FAILING TEST FIRST Every single one makes Claude slower. That is the point, and it’s why the repo is good. 01 - brainstorming: Nine gates before it writes a line of code — explore the context, ask clarifying questions one at a time, propose two or three approaches with trade-offs, write a spec, get you to approve it. Step nine is the first one that touches code. Its own line: “Simple” projects are where unexamined assumptions cause the most wasted work. 02 - test-driven-development: The test comes first and you watch it fail. If you didn’t watch the test fail, you don’t know if it tests the right thing. I used this one to write the code that formats the star counts in this very post — the slide shows the real run, six failing then six passing. It fixes a rounding bug I’d actually shipped: 1,598 stars going out as “1.6k” when the honest direction is down. 03 - systematic-debugging: Five things it has to do before it may propose a single fix: read the error properly, reproduce it, check what changed, instrument the boundaries, trace the data. Symptom fixes are failure. This is what you want the third time the same bug comes back. 04 - verification-before-completion: The most useful and least exciting skill in the repo. It bans “should work”. A claim needs the command, run now, output read. Its own table is brutal: “tests pass” requires test output with zero failures — a previous run is not sufficient. And the line that earns the whole post: Skip any step = lying, not verifying. 05 - writing-skills: The meta one. Writing skills IS Test-Driven Development applied to process documentation — you watch an agent fail without the skill, write the skill, then watch it comply. So a skill isn’t a doc you wrote; it’s a doc that provably changed how an agent behaves. Free, MIT, and not Claude-only — the repo ships plugin manifests for Codex, Cursor, Copilot, Gemini CLI, Kimi and OpenCode too. The honest read: none of this makes the model cleverer. It makes it show its work. If you’ve ever been told “done” by something that hadn’t run the tests, that’s the one to install first. Slide 7 has both install lines and all fourteen skills. Follow for more no-hype AI & tech. #ai #claudecode #softwareengineering #tdd #nohype

A repo called “superpowers” has 265,000 stars on GitHub. What it actually installs is discipline. Four of its fourteen skills have a section titled, literally, “The Iron Law”. Here they are, word for word: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE NO SKILL WITHOUT A FAILING TEST FIRST Every single one makes Claude slower. That is the point, and it’s why the repo is good. 01 - brainstorming: Nine gates before it writes a line of code — explore the context, ask clarifying questions one at a time, propose two or three approaches with trade-offs, write a spec, get you to approve it. Step nine is the first one that touches code. Its own line: “Simple” projects are where unexamined assumptions cause the most wasted work. 02 - test-driven-development: The test comes first and you watch it fail. If you didn’t watch the test fail, you don’t know if it tests the right thing. I used this one to write the code that formats the star counts in this very post — the slide shows the real run, six failing then six passing. It fixes a rounding bug I’d actually shipped: 1,598 stars going out as “1.6k” when the honest direction is down. 03 - systematic-debugging: Five things it has to do before it may propose a single fix: read the error properly, reproduce it, check what changed, instrument the boundaries, trace the data. Symptom fixes are failure. This is what you want the third time the same bug comes back. 04 - verification-before-completion: The most useful and least exciting skill in the repo. It bans “should work”. A claim needs the command, run now, output read. Its own table is brutal: “tests pass” requires test output with zero failures — a previous run is not sufficient. And the line that earns the whole post: Skip any step = lying, not verifying. 05 - writing-skills: The meta one. Writing skills IS Test-Driven Development applied to process documentation — you watch an agent fail without the skill, write the skill, then watch it comply. So a skill isn’t a doc you wrote; it’s a doc that provably changed how an agent behaves. Free, MIT, and not Claude-only — the repo ships plugin manifests for Codex, Cursor, Copilot, Gemini CLI, Kimi and OpenCode too. The honest read: none of this makes the model cleverer. It makes it show its work. If you’ve ever been told “done” by something that hadn’t run the tests, that’s the one to install first. Slide 7 has both install lines and all fourteen skills. Follow for more no-hype AI & tech. #ai #claudecode #softwareengineering #tdd #nohype

About

Robot
API

Legal

Privacy Policy