Big EV EV

Chicago | Tech | Rockstar | I’m just here to enjoy the show…

[Big EV EV @EngineeredEV]

For those of you looking to lose some weight in 2026:

- Join a fitness class
- Walk as much as possible (invest in a walking pad)
- Track your calories (honestly)

Give it some time. You’ll get there.

[Big EV EV @EngineeredEV]

@yannaarose_ lol #NEEDDAT

[Big EV EV @EngineeredEV]

And there i was, at the surgeon table, operating on thee Kimberly Kardashian

[Pearls @1xpearls]

her surgeon deserves the nastiest sloppiest head imaginable cuz holy shit bro

[Big EV EV @EngineeredEV]

bro it still ain’t Thursday? gotdamn

[Big EV EV @EngineeredEV]

Wish i had the free time. So many things i wanna just look (back) into

[Oyinkansola @oyinkanbadejo]

You’re about to discover greatness

[🌍 @jasminexETH]

@thecoachchris_ Doubt it.

[ℜ 🌙 @Lakevienn]

They call me BIG

BIG..

BIG..

BIG Michael Michael 😭

[BoveiDaDon♥️🦉 @BoveiDaDon]

Talking bout GTA 6 you ain’t talking bout getting no big dck lol this ngga wild and to the No Guidance beat 😆😭👏🏾

[i make beats ✞ @DonDadaNYC]

Asked God to remove all the fake shit from my life & my homie died the next day

[Big EV EV @EngineeredEV]

@itsthewealth4me @JasonTheTodds girl. teach us.

[Sincerely, Mia. @MiaNWonderland]

He is not stopping anytime soon 😭
#BigMichaelMichael #LoozeCannon

[Big EV EV @EngineeredEV]

If you built like this, like this message. tryna see something.

[The Modern Masculine Man @masculineman77]

SKINNY...

lets be real, we as a human race should be skinny...

there was a time in America when fat black people did not exist...

everyone wants to be skinny, no matter how many lies we tell...

And don't focus on the word, "skinny"...

Just get the damn point...

[Gringofurioso @Gringofurioso_x]

imagine disposing of a body, cleaning up all the blood, you think of all the stuff and tie up all the loose ends.. and then you get caught because of a fitbit

[Big EV EV @EngineeredEV]

Rent was $400 in Champaign back in 2013.

Make America Cheap Again

[GorgeousDreamer @DrianneBelleza]

Imagine this…

[KC @dontblameitonKC]

They finna call you mean for this but you’re right.

[Big EV EV @EngineeredEV]

My guess is 3-5 years.

[scientist. @ultronlift]

Genuinely, How many years does it take to build a physique like this without steroids?

[Big EV EV @EngineeredEV]

@itsthewealth4me @dedicateddamz looking forward to the advice

[Big EV EV @EngineeredEV]

@_invalidfate ….never mind. Imma just take this quarter zip off and pull up in a Nike Tech

[Big EV EV @EngineeredEV]

Got my quarter zip on.

Im Caucasian now and no, i do not have any spare change.

[Akhilesh Mishra @livingdevops]

Kubernetes is a solution, not a default.

But somewhere along the way, it became the answer before anyone asked the question.

Teams pick Kubernetes for three bad reasons.

- Everyone else uses it.
- It looks good on resumes.
- "We'll need it when we scale."

The last one sounds the most reasonable and does the most damage. It front-loads years of operational cost against growth that may never require it.

Here's what Kubernetes actually solves. It schedules many workloads across a shared pool of machines. It gives dozens of teams one deployment model, one API, one way to handle config, secrets, scaling, and service discovery.

Notice what those have in common. They're problems of scale and heterogeneity. Many services, many teams, many workload types.

If you don't have those problems, Kubernetes doesn't solve anything for you. It just adds a layer.

And the layer is expensive.

The EKS control plane costs $73 a month. That's the cheapest part of the bill.
- A minimal production setup needs a load balancer controller, external DNS, secrets management, metrics server, node autoscaler, monitoring stack, and ArgoCD. Seven components before your application exists.
- Each one has its own release cycle, CRDs, breaking changes, and IAM role.

And you're not upgrading one thing. You're upgrading a stack. Every four months.

My rule of thumb: running production Kubernetes well takes at least half of one experienced engineer's time, permanently.

For a ten-person engineering org, that's 5% of your total capacity spent on the platform rather than on the product.

For most teams, ECS on Fargate is the answer. Containers without nodes, upgrades, or add-ons. Secrets, logging, autoscaling, and deployment rollbacks built in. AWS patches everything underneath.

Kubernetes starts making sense when you have 20+ services owned by several teams, complex scheduling needs, or workloads that ECS simply can't handle.

What makes adopting Kubernetes easy later isn't adopting it now. It's containerized services, stateless processes, and infrastructure as code.

A team on ECS with clean containers can migrate to EKS within a few weeks as needed.

Choosing the simpler option isn't the cautious move.
It's the one that keeps your options open.

[Jake Orlando @JakeOrlando15]

@freemmatt @TheWapplehouse My first thought when I saw his picture