@nastyhih: Эдиторы, почему спим?((( #jujutsukaisen #магическаябитва #наоязенин #naoyazenin #стеклянный

nastyhi
nastyhi
Open In TikTok:
Region: RO
Tuesday 06 October 2026 08:05:18 GMT
56106
11526
32
1841

Music

Download

Comments

prusi_inv
🫖 ᚢᚹᚴᛈᛋ_Invincible 🫖 :
Есть подозрения что это женщина
2026-10-06 11:24:14
245
skaramuh1
꧁ ༒ 𝑴𝒊𝒔𝒂𝒌𝒊 ༒ ꧂ :
ВЫ МЕНЯ ПРЕСЛЕДУЕТЕ В РЕКАХ😭😭😭
2026-10-06 09:23:35
138
reall_loll
Skepper :
20 минут назад 200 просмотров Потеряла свой прайм
2026-10-06 08:23:11
664
grandmasterburmaldi
Бурмалдень :
2026-10-06 16:26:37
1
adammagomadov92
adam mgm :
перепутал с сибуэ
2026-10-06 17:06:34
2
nagets_negr
дикий Витте :
ты не дверь!
2026-10-06 10:07:04
26
hot_bane
Maytchina :
2026-10-06 12:59:06
3
shyt1820
ShyT-Яро :
2026-10-06 09:05:51
14
gandonicgamer
Gandonicgamer :
Ты не тоджи
2026-10-06 08:14:08
6
zombie.pubg3
ZOMBIE zm :
Да ну
2026-10-06 09:44:31
3
mauvestringer
pinkmeanie :
2026-10-06 17:07:46
0
leleleleele17
xb :
2026-10-06 16:09:27
0
elrin166
Gojo:bf :
5
2026-10-06 08:16:34
0
yuji_itadorioriginal
[| yuji # itadori °^° |] :
емаа
2026-10-06 08:10:50
0
carvens375
Кирито :
жду взаимную подписку - коммент 62
2026-10-06 08:14:40
0
gmmqm1
Naoya Zenin :
я один на неё подписан завидуйте 😝😝😝😝
2026-10-06 12:42:14
0
the.chrome0
𝕮𝖍𝖗𝖔𝖒𝖊 :
2026-10-06 15:30:12
0
avenvip
алихан :
@Айгюн только ты можешь успокоить его 🥀🥀
2026-10-06 11:05:10
2
lastcherryyy
. ≏ cჩЗ𐑾ׂ𐑾ׂ𝙮˚ ⸝⸝ ⌗ ༘ :
@Наоя бро эьо ты
2026-10-06 13:30:07
1
xxxxanax4
xxxxanax :
@nastyhi
2026-10-06 08:16:03
1
jangwoojian
Mark :
@Разумовская
2026-10-06 08:42:37
2
4o._.nad0_
Рокады Бульба бананы казино :
@Anohina 🛐
2026-10-06 12:55:20
0
To see more videos from user @nastyhih, please go to the Tikwm homepage.

Other Videos

How to build an entire app with AI, the kind a developer charges $10,000 for You don't need to know how to code to build a real app. You need one idea first: every app has two halves. The restaurant: Front end = the dining room. Everything the customer sees and touches: the menu, the buttons, the booking form. In your app, that's the screens. Back end = the kitchen. The customer never walks in, but that's where the work happens: check the time slot is free, take the payment, save the booking, send the text. Database = the pantry. It stores every customer, every dog, every booking. Close the app, come back next week, and it's all still there. API = the waiter carrying orders between them. The screen asks, the back end answers. Most people only describe the dining room when they ask AI to build something. They get a beautiful app that forgets everything the second they hit refresh. The build, in Claude Code (a dog groomer's booking app): Plan: who it's for, the screens, what the kitchen does and what goes in the pantry, written to a plan file before any code. Front end: the booking page and owner dashboard, previewed in your browser. Point at what's off and it fixes it in seconds. Back end: a free Supabase project gives you two things, a web address for your database and a key. Keys go in one private file called .env: the key drawer in your back office. Then Claude Code connects the booking form and builds the tables. Log-in: email and Google, with Supabase handling the passwords. One rule, row level security: every customer only sees their own bookings. Test it by logging in as two different people. Getting paid: Stripe in test mode (play money). Copy the secret key into the drawer, ask for a $25 deposit with Stripe Checkout, test with 4242 4242 4242 4242. A webhook is Stripe calling your kitchen back to say
How to build an entire app with AI, the kind a developer charges $10,000 for You don't need to know how to code to build a real app. You need one idea first: every app has two halves. The restaurant: Front end = the dining room. Everything the customer sees and touches: the menu, the buttons, the booking form. In your app, that's the screens. Back end = the kitchen. The customer never walks in, but that's where the work happens: check the time slot is free, take the payment, save the booking, send the text. Database = the pantry. It stores every customer, every dog, every booking. Close the app, come back next week, and it's all still there. API = the waiter carrying orders between them. The screen asks, the back end answers. Most people only describe the dining room when they ask AI to build something. They get a beautiful app that forgets everything the second they hit refresh. The build, in Claude Code (a dog groomer's booking app): Plan: who it's for, the screens, what the kitchen does and what goes in the pantry, written to a plan file before any code. Front end: the booking page and owner dashboard, previewed in your browser. Point at what's off and it fixes it in seconds. Back end: a free Supabase project gives you two things, a web address for your database and a key. Keys go in one private file called .env: the key drawer in your back office. Then Claude Code connects the booking form and builds the tables. Log-in: email and Google, with Supabase handling the passwords. One rule, row level security: every customer only sees their own bookings. Test it by logging in as two different people. Getting paid: Stripe in test mode (play money). Copy the secret key into the drawer, ask for a $25 deposit with Stripe Checkout, test with 4242 4242 4242 4242. A webhook is Stripe calling your kitchen back to say "paid". The text reminder plugs in the same way with Twilio. Every outside service connects like this: account, key, drawer, sentence. Go live: push to GitHub, import into Vercel, paste the same keys into its settings, deploy. Buy your domain, add it in Vercel, copy two DNS lines into your domain company, and it's live on your own name with the padlock. Before real customers: point the webhook at the new address and swap test keys for live keys. After that, adding more is one sentence: Google Calendar sync, a loyalty card, review requests, or an automation that drops every new booking into your CRM. Your job becomes the owner who tests every button like a customer would. #buildwithai #claudecode #aiagent

About