@niickjackson: are we cooked?

Nick Jackson
Nick Jackson
Open In TikTok:
Region: US
Monday 21 September 2026 00:40:48 GMT
146143
8881
261
941

Music

Download

Comments

bowenthepickle
Bowenthepickle :
PlayStation pls
2026-10-13 14:36:40
0
ronisme12
Bonnie :
stop making me use my brain or I'm scrolling
2026-09-23 16:56:03
9
thewickedcrystal
ChicWicked :
how do you scroll in an mri machine?
2026-09-21 20:08:22
170
alexandradebono1
Madison :
I was going for almost 2 hours
2026-09-26 13:47:43
5
didoni10
𝓓𝓲𝓭𝓸𝓷𝓲 :
Start telling them the truth
2026-09-21 01:28:45
181
veroz_aep
VEROZ 🇵🇬 :
I'm deleting TikTok
2026-09-21 09:52:50
39
littlemansouls
Andrew :
Gta6 codes tonight plz
2026-09-21 00:41:50
72
fish4518dqf
🫥 :
the ADHD ppl come to the front!
2026-09-21 18:09:51
21
mynameisnotchucknorchess
ChuckandChess :
Nick please do another giveaway soon, I dont have enough money for it and itd be very kind of you to give me a ps5 code and I literally am on your videos within like 30 seconds
2026-09-21 00:42:31
9
gerburke02
GerBurke02 :
I just learned this from a short video. . .
2026-09-22 22:06:51
7
potatutkb4y
Nupid Stigga :
After scrolling TikTok for a few years I can definitely tell you my attention span has gotten way worse
2026-09-22 00:43:28
6
hubertthemighty
HubertTheMighty💚 :
Aren’t MRI’s basically a giant magnet, how do you scroll in that
2026-09-21 22:30:38
10
damtediaz
Mr.ultra :
ohh oops I crolled
2026-09-21 00:46:51
5
dhmmm33
Adam :
I just might be cooked
2026-09-24 03:49:35
5
adam.4450
𝘼𝙙𝙖𝙢 :
I dont have anything funny to say anymore I've done this 3 times now js slide me gta 6 ✌️😭
2026-09-21 00:56:16
39
falynnbristol4
EnchAnted Falynn🌹 :
I've scrolled too many to count 😳
2026-09-21 00:50:24
5
renoander70
RenoAnder :
Who the hell scrolls on their feet?
2026-09-21 20:40:40
7
ballsacks2.0
ツ𝖍𝖔𝖗𝖎𝖟𝖔𝖓メ :
CAN I HAVE GTA 6 PLEASE I HAVE BENN WAITING SINCE YOU ANNOUNCED YOU ARE GIVING THEM OUT PLEASEEEEE
2026-09-21 00:44:47
4
im.cold.help.out
it's cold In here :
don't give me an xbox code
2026-09-21 01:17:59
5
jakovsik
jakov.s :
how much time does bro have on x😭
2026-09-21 00:44:08
5
me4ty1
Me_tyy :
Day 5 until i get gta 6
2026-09-21 01:03:20
9
benzz111l
ㅅ⃝ ㅅ⃝  :
Otp what’s not going to kill us. Ima just live it up to fullest
2026-09-21 19:43:11
11
kevin_cc6
Kevin🇲🇽 :
I wish I could get a free copy of gta 6
2026-09-21 00:47:49
5
littlecaesers12
𝕵𝖔𝖘𝖊𝖕𝖍 :
Omg nick the aliens took have a gta 6 copy but they won’t give it to me can you plz slide me one im on ps5
2026-09-21 00:57:58
5
aaronstandley2
Staminastan :
the fact yall are jucing over gta6 and stopped your outrage over e files shows we are truly cooked
2026-09-21 04:39:58
8
To see more videos from user @niickjackson, please go to the Tikwm homepage.

Other Videos

Comment LOCK and I'll send you the cheat sheet comparing locks, atomic updates, and constraints. One ticket left. Two people click Buy at the same time. Both your screens say you got it. ⚡ The bug isn't in your checkout code, it's the gap between checking and writing. Your server reads the seat, sees available, and then, before it writes sold, does something else entirely ⚡ In that gap Leo's request runs the exact same read. It also sees available. Then both writes land, and you send two confirmation emails for one chair ⚡ This is a race condition: not a rare crash, but the ordinary outcome of two requests arriving at once. Nothing threw. Nothing warned. The database did exactly what it was asked, twice ⚡ The first fix is pessimistic locking. SELECT ... FOR UPDATE takes a row lock, and Leo's request can't even read that row until Maya's transaction commits. The queue behind it stops being optional ⚡ The second fix is better because it removes the gap entirely: fold the check into the write. UPDATE seats SET status='sold' WHERE seat='F12' AND status='available', one statement, one decision ⚡ That runs as a single atomic operation. The check and the update either both succeed or neither happens. There is no
Comment LOCK and I'll send you the cheat sheet comparing locks, atomic updates, and constraints. One ticket left. Two people click Buy at the same time. Both your screens say you got it. ⚡ The bug isn't in your checkout code, it's the gap between checking and writing. Your server reads the seat, sees available, and then, before it writes sold, does something else entirely ⚡ In that gap Leo's request runs the exact same read. It also sees available. Then both writes land, and you send two confirmation emails for one chair ⚡ This is a race condition: not a rare crash, but the ordinary outcome of two requests arriving at once. Nothing threw. Nothing warned. The database did exactly what it was asked, twice ⚡ The first fix is pessimistic locking. SELECT ... FOR UPDATE takes a row lock, and Leo's request can't even read that row until Maya's transaction commits. The queue behind it stops being optional ⚡ The second fix is better because it removes the gap entirely: fold the check into the write. UPDATE seats SET status='sold' WHERE seat='F12' AND status='available', one statement, one decision ⚡ That runs as a single atomic operation. The check and the update either both succeed or neither happens. There is no "between" left for a second request to stand in Even buggy code can't break that rule, because the constraint lives in the database, not in your code. A unique key on the event-and-seat pair means two confirmed tickets for the same seat can't physically exist in the table. The engine refuses the second insert no matter what your application does. The database never really picks a winner by magic. It forces the two requests into a line. One goes first. The other sees the result. Two rules that outlive this specific example: keep your checks inside the write, and keep the final guarantee in the schema. Which has cost you more time, the bug or the incident review after it? Comment LOCK for the full cheat sheet. #databases #concurrency #postgresql #backend #programming

About