@podcastpshow: LeBron will have a few statues when it's all said & done, but Vince Staples is hesitant when it comes to one in LA.

Podcast P Show
Podcast P Show
Open In TikTok:
Region: US
Wednesday 14 February 2024 18:05:10 GMT
639703
63882
547
126

Music

Download

Comments

ca6ey
Casey :
I don't think Bron gets a Lakers statue but Miami and Cleveland for sure
2024-02-14 20:02:00
4557
f3yzl
F3👨🏾‍🦯 :
Lebron won a ring in la broke the all time scoring record in la won a assist title in la and been there for 6 years 😭 bro might actually get one
2024-02-14 20:49:13
1
sheen_scott
Sheen :
They really need to retire his jersey in Toronto and Boston too
2024-02-14 19:24:46
1566
la.marr_
La-marr :
Bron don’t need a statue in crypto
2024-02-14 18:07:43
2451
_enzo_1521
Enzo :
One championship does not equal statutes
2024-02-14 21:00:19
323
godfirst1j
god first :
If he gets one more ring in La he should get one
2024-02-14 18:13:41
577
nwti55
T55 :
Who’s here after Bron just got a statue in LA
2026-04-06 12:10:10
1
ggvazquezzz
Gerardo :
I love Lebron and I’m a lakers fan 🤷🏽‍♂️
2024-02-14 18:16:04
42
shlimon2x
Lyndon Limon :
Bron brought a chip he’s getting three statues no cap
2024-02-14 18:45:51
4
texasfool32
Texas fool :
He needs one in Toronto
2024-02-14 21:00:30
2
desiro24
Desiro :
if u think about it he came to LA past his prime but he's been in LA for awhile now and still put up big numbers
2024-02-14 18:45:37
2
tylerchristopher824
tylerchristopher824 :
I’m a lakers fan and I loved watching Lebron the last 6 years on the team. I never want it to go back to how it was before he joined
2024-02-14 21:45:04
1
jaylit02
jaylit02 :
I’ll say if bron can win one more ring in LA then he could get a statue but with one ring ehhhhhh
2024-02-14 20:44:50
1
flamingtamales
:0 :
Vince don’t speak for all Lakers fans , I love Lebron and I’m grateful he’s stuck it out with the Lakers for so long when he didn’t have to
2024-02-14 20:10:49
3
1lortayy__
🌟 :
he's getting a statue for every team, and they're all gonna retire his jersey
2024-02-15 06:53:30
2
feedgotcha
Daniel :
It’s cause you don’t think LA when someone brings up Bron. But they do for Kobe,Shaq,Magic and all
2024-02-14 22:09:47
2
javisalome17
Javi Salome :
Lakers not giving Bron a statue
2024-02-14 20:28:28
73
roningrewal
roningrewal :
Keldon Johnson and pg that’s random lol
2025-03-26 07:32:59
2
jimmytalksball__
JimsBallTalk :
LeBron deserves Cleveland and Miami that’s it
2024-02-15 01:30:55
1
truefleeligion
3 :
Said it perfectly laker fans def not gon rock with bron there kobe d riders and bron haters for no reason 🤦🏾‍♂️
2024-02-25 22:48:46
1
_4theloveofmoney
_1babyju :
with out lebron lakers would be like the raptors lets kiab
2024-02-16 16:41:18
1
carl102306
cloud123 :
it's not about the championship tho. lebron brings so much in LA in terms of popularity and money. LA was so much declining before lebron joins.
2024-02-15 01:37:09
1
ernsinkdex
ernsinkdex :
He ain't getting one in Miami but sure to cleavland. Kobe was the face of the lakers. Same for mj in Chicago. Bron is the face of the nba. I agree there.
2024-02-14 23:19:59
1
wdfisthataaaaaaaaaaaaaa
wdfisthataaaaaaaaaaaaaa :
Lebron broke the all time record in their stadium and probably retires there so i think they do it just for marketing purposes
2024-02-16 00:03:55
1
To see more videos from user @podcastpshow, please go to the Tikwm homepage.

Other Videos

What's the difference between a junior and a senior DevOps engineer when designing AWS infrastructure? It's not just knowing more services. It's understanding the trade-offs behind every architectural decision. In production, choosing the wrong AWS service or configuration can lead to unexpected costs, poor performance, single points of failure, and outages that affect real customers. Here are 7 AWS architecture decisions every DevOps engineer should understand: 1. Multi-AZ vs. Multi-Region: Multi-AZ helps protect against Availability Zone failures, while multi-region architectures can improve resilience against regional outages. However, multiple regions introduce additional complexity, cost, and data replication challenges. 2. Application Load Balancer vs. CloudFront: An ALB distributes requests across backend targets, while CloudFront caches and delivers content from edge locations closer to users. Understanding how they work together helps you build faster and more efficient applications. 3. Scaling vs. Caching: Adding more application replicas can increase capacity, but it doesn't eliminate unnecessary database queries or repeated computations. Caching can reduce latency and database load when used appropriately. 4. SQS vs. Synchronous Processing: Synchronous processing keeps the client waiting for work to finish. SQS allows applications to process certain tasks asynchronously, helping absorb traffic spikes and decouple services. 5. RDS Multi-AZ vs. Read Replicas: Multi-AZ deployments primarily improve database availability and failover, while read replicas can help scale read-heavy workloads. They solve different problems and aren't interchangeable. 6. NAT Gateway per AZ vs. a Shared NAT Gateway: A NAT Gateway in each Availability Zone can improve resilience and reduce cross-AZ traffic. A shared NAT Gateway may reduce infrastructure costs, but introduces an Availability Zone dependency and potentially additional data transfer costs. 7. Auto Scaling vs. Spare Capacity: Auto Scaling helps adjust capacity as demand changes, but scaling takes time. Maintaining sufficient minimum capacity and testing under load can help applications handle sudden traffic spikes before new resources become available. The important lesson is that there's rarely one architecture that's best for every application. The right choice depends on availability requirements, traffic patterns, recovery objectives, security, operational complexity, and budget. A senior DevOps engineer doesn't just ask,
What's the difference between a junior and a senior DevOps engineer when designing AWS infrastructure? It's not just knowing more services. It's understanding the trade-offs behind every architectural decision. In production, choosing the wrong AWS service or configuration can lead to unexpected costs, poor performance, single points of failure, and outages that affect real customers. Here are 7 AWS architecture decisions every DevOps engineer should understand: 1. Multi-AZ vs. Multi-Region: Multi-AZ helps protect against Availability Zone failures, while multi-region architectures can improve resilience against regional outages. However, multiple regions introduce additional complexity, cost, and data replication challenges. 2. Application Load Balancer vs. CloudFront: An ALB distributes requests across backend targets, while CloudFront caches and delivers content from edge locations closer to users. Understanding how they work together helps you build faster and more efficient applications. 3. Scaling vs. Caching: Adding more application replicas can increase capacity, but it doesn't eliminate unnecessary database queries or repeated computations. Caching can reduce latency and database load when used appropriately. 4. SQS vs. Synchronous Processing: Synchronous processing keeps the client waiting for work to finish. SQS allows applications to process certain tasks asynchronously, helping absorb traffic spikes and decouple services. 5. RDS Multi-AZ vs. Read Replicas: Multi-AZ deployments primarily improve database availability and failover, while read replicas can help scale read-heavy workloads. They solve different problems and aren't interchangeable. 6. NAT Gateway per AZ vs. a Shared NAT Gateway: A NAT Gateway in each Availability Zone can improve resilience and reduce cross-AZ traffic. A shared NAT Gateway may reduce infrastructure costs, but introduces an Availability Zone dependency and potentially additional data transfer costs. 7. Auto Scaling vs. Spare Capacity: Auto Scaling helps adjust capacity as demand changes, but scaling takes time. Maintaining sufficient minimum capacity and testing under load can help applications handle sudden traffic spikes before new resources become available. The important lesson is that there's rarely one architecture that's best for every application. The right choice depends on availability requirements, traffic patterns, recovery objectives, security, operational complexity, and budget. A senior DevOps engineer doesn't just ask, "Which AWS service should I use?" They ask, "What problem am I solving, what happens when something fails, and what trade-offs am I accepting?" That's the mindset you need to design reliable AWS infrastructure in production. #devops #techtok

About