@derrickphones1: @NTONGO SNACKS visits Derrick phones #derrickphones #newstock #ntongosnacks #foryoupage #fypシ゚viral @Goodlyfe Eddy

DERRICK MASIMU(phones)
DERRICK MASIMU(phones)
Open In TikTok:
Region: UG
Saturday 04 July 2026 11:07:34 GMT
214437
12737
562
79

Music

Download

Comments

shamttm
Shamirah Ttd 🤞 :
Few moments later nazala alumye spoon 😂😂😂😂😂
2026-07-08 18:10:22
290
blessed2250
Her calmness 💞🩵💞 :
who's from the future 🤣🤣🤣
2026-07-08 13:30:08
332
user8368291503165
DAISY. Namubiru :
who is here after seeing mama flower's video😂😂😂😂😂😂😂
2026-07-09 07:25:12
3
mumzonlygal0
MUMZ ONLY GAL💕❤️💜 :
naye mummy flower anamusima oyo😂😂😂😂
2026-07-04 11:15:56
459
marycloset25
mary sky💋 :
sm from future nae maama flower 🌼 kyakoze ntongo
2026-07-08 10:54:19
154
triciakintu3
🤍Tricia🖤 :
Me after seeing maama flower's live
2026-07-09 05:27:18
21
sawiyam123
Sawiyam123 :
Nyazala ojamuwulira
2026-07-04 17:40:58
206
kirabo.mackline6
Kirabo Mackline :
Who is from the future we go back together 😳😳
2026-07-09 06:28:13
11
callieprillar
callie prillar :
am frm mummy flowers page naye kika 🤣🤣🤣🤣🤣
2026-07-08 16:50:29
24
user5296961131456
Mrs kirumira 🌹🦋🌹 :
Saba nnyo maama flower asiime
2026-07-04 19:09:35
91
tasha.bella.94
LONER💜🦋 :
Mama flower right nw
2026-07-04 11:54:25
81
momoshidah200
Taisha :
Nazaala teyasimye muntu 😩😩
2026-07-08 16:15:09
31
user19414450465935
user19414450465935Carix the Qu :
Who's from the future😂😂😂😂
2026-07-08 17:51:24
1
dijjah921
🎀Black pearl 🤍🧕. :
So you guys didn't notice Derrick's hand moving😁
2026-07-08 20:13:54
2
tricia20128
Tinahtwofivesix :
tiktok in-laws tetuyina buzibu naye nazaala🤔🤔
2026-07-06 12:28:19
22
ingabirenovence
Hec98 :
let's go back ba dia🤣🤣🤣we finish the video
2026-07-08 18:30:14
10
kachainajuliet1
Kachaina juliet :
good luck ayagala kweetega bruno k, ate temunjasamira good luck juuuuuu
2026-07-08 17:56:19
13
bukirwa.bettina
Bukie Betty B² :
Abawala omoyimo banange amangu ago
2026-07-04 12:12:27
48
user6198678130126
Really :
Ntongo is the full meaning of highjump
2026-07-08 18:58:41
9
monikaunique4
Talika256 :
Derrick ands ntongo must shine 🥰
2026-07-04 11:33:48
18
depearl.28
🫵🫵🪱🪱🌳🐆🐉🦚 :
Abana abobuwala namwe mwesawonyo banange
2026-07-08 15:48:56
9
To see more videos from user @derrickphones1, please go to the Tikwm homepage.

Other Videos

The N+1 Problem — and How to Kill It You write a loop. It looks clean. The tests pass. Then production slows to a crawl under real data. The culprit? N+1. Here's what's happening: your app loads a list of 100 orders. Then, for each order, it fires a separate query to get the customer. That's 1 + 100 = 101 queries. With 500 orders it's 501. Under 10 concurrent users, that's 5,010 database round-trips for one page load. Each query carries overhead: network latency, connection acquisition, query parsing, and execution plan lookup. Individually they're fast. Multiplied across N records under real load, they drain your connection pool and tank your response times. The fix is straightforward once you see it. In Entity Framework Core, Include() tells the ORM to JOIN the related table in a single query instead of querying lazily per record. If you only need specific fields, Select() into a DTO is even better — it avoids loading full entity graphs and produces a leaner SQL query. The key rule: never access a navigation property inside a loop without explicitly loading it first. To detect it: enable EF Core SQL logging in development. If you see the same query repeating with different IDs, you have an N+1. Tools like MiniProfiler make this visible at a glance. In interviews, when you hear
The N+1 Problem — and How to Kill It You write a loop. It looks clean. The tests pass. Then production slows to a crawl under real data. The culprit? N+1. Here's what's happening: your app loads a list of 100 orders. Then, for each order, it fires a separate query to get the customer. That's 1 + 100 = 101 queries. With 500 orders it's 501. Under 10 concurrent users, that's 5,010 database round-trips for one page load. Each query carries overhead: network latency, connection acquisition, query parsing, and execution plan lookup. Individually they're fast. Multiplied across N records under real load, they drain your connection pool and tank your response times. The fix is straightforward once you see it. In Entity Framework Core, Include() tells the ORM to JOIN the related table in a single query instead of querying lazily per record. If you only need specific fields, Select() into a DTO is even better — it avoids loading full entity graphs and produces a leaner SQL query. The key rule: never access a navigation property inside a loop without explicitly loading it first. To detect it: enable EF Core SQL logging in development. If you see the same query repeating with different IDs, you have an N+1. Tools like MiniProfiler make this visible at a glance. In interviews, when you hear "it slows down as data grows," think N+1 first. Follow @capacitadev on Instagram and TikTok for interview prep content across Junior, Intermediate, Senior, and Staff levels. There's a free PDF with 20 interview questions waiting for you in the link on the profile. #dotnet #csharp #entityframework #efcore #softwareengineering

About