Decorum.btc🥑 retweeted
a senior engineer just explained why the Microsoft outage took 15 hours and why AI won't replace programmers anytime soon.
Decorum.btc🥑 retweeted
Meet @Moshaikh
The guy behind Aptos, a $20B Scam.
He Co-founded Aptos, raised $400M from major VCs, watched $APT holders lose over -99% of their value, and stepped down as CEO right after his token compensation vested.
His explanation? A much-needed “mental health break.”
Fast forward to 2025: launches his own $50M crypto VC fund, then casually tweets:
“I have a nice $SUI bag now ;-)”
Yes, SUI. Aptos’ direct competitor, built using the same Diem technology.
So the guy who raised hundreds of millions building Aptos, collected his compensation, walked away, started a VC fund, and bought into the competition while $APT holders were left holding the bag.
Decorum.btc🥑 retweeted
🚨 RUBIO JUST SAID THE NUMBER THEY NEVER WANTED ON TV 🚨
Americans work 40 years.
They retire.
Social Security: $800. $900. A thousand a month.
Somebody who got here from Cuba three months ago: $1,500 a month.
Marco Rubio said it out loud.
“So imagine if you’ve been working here for 40 years and your Social Security check is smaller than the benefits going to a 28-year-old, able-bodied person who just got here. That’s real. That happens. That’s happening every day. That makes no sense.”
You paid in.
They landed.
They beat your check.
That’s not compassion.
That’s a slap in the face with your own tax dollars.
Decorum.btc🥑 retweeted
Arguably Ethereum is one of the worst things to happen to humanity. The amount of capital lost to hacks, human capital lost due to developing with suboptimal tooling and retail capital destroyed from longing the asset makes it a contender for the worst asset of all time.
Decorum.btc🥑 retweeted
Not gonna lie growing this account up like it really wasn’t easy like it was mentally taxing because I was taking losses and setting myself back to a point I had to take a break because of it and then I just went back to what got me here and that’s constantly practicing charting perfecting my strategy, having rules not being greedy, not trading everyday only trading my strategy and stepping away it’s hard for some even myself but if you can manage your emotions and trade your setup only it does pay off
Decorum.btc🥑 retweeted
Frens, we just need to survive one more month.
2018 Bear market: Bitcoin bottomed in December and then pumped from $3,200 to $69,000.
2022 Bear market: Bitcoin bottomed in November and then pumped from $15,400 to $126,000.
2026 Bear market: Bitcoin already bottomed in June at $57,800. We might see one final drop to the low $60k range by early December, and then it's up only.
He who survives the dump, deserve a mega pump.
Decorum.btc🥑 retweeted
Rohit Conman needs to be expelled from congress and barred from government employment for life.
Rep. Ro Khanna's wife sold Nvidia stocks near peak before shares plunged over sex scandal trib.al/Uz8sub4
Decorum.btc🥑 retweeted
NVIDIA announces CEO transition. Read the release: nvidianews.nvidia.com/news/n…
Decorum.btc🥑 retweeted
Well, well, well
Rep. Ro Khanna sold $NVDA right before Nvidia's CEO admitted to having a Chinese spy side piece
He's a member of the following:
- Strategic Competition between the U.S. and the Chinese Communist Party Committee
- Taiwan Caucus
- High Tech Caucus
Apparently, federal agents informed some lawmakers last year that Jensen Huang might be the target of a foreign intelligence operation
He avoided a ~26% dip
Decorum.btc🥑 retweeted
SRE has changed a lot in 10 years. We're kicking off a special 2-part series with the minds behind "Site Reliability Engineering, 2nd Edition"! 📖
Tune into Part 1 (Season 7, Episode 5) now! 🎧
sre.google/prodcast/#season7… google.smh.re/5ikY
Decorum.btc🥑 retweeted
Idc what happen, my $SPCX shares never leaving me.
Decorum.btc🥑 retweeted
He literally explained how to elevate your frequency.She literally explained how to break poverty mindset in 60 seconds.
Decorum.btc🥑 retweeted
JUST IN: 🇺🇸 Senate Democrats prepare to impose 10% cap on credit card interest rates.
Decorum.btc🥑 retweeted
NEW: Making $100,000 a year is now considered lower-middle class in 12 U.S. states.
Decorum.btc🥑 retweeted
Every billionaire's "started in a garage" story conveniently skips the parental loans, elite connections, and safety nets. Bezos got $300k from his parents. Gates' mom sat on IBM's board. Musk's family owned an emerald mine. The garage is just aesthetics; the capital was inherited. Stop calling it self-made when it's generationally funded.
Decorum.btc🥑 retweeted
DevSecOps is easy when you understand the story behind every tool.
It starts with shift left. For years, security was the last step. A team spends 3 months building, and a week before release the security review finds 40 issues.
So you shift left. Find problems when they are cheap to fix, not when they are expensive to explain.
The first problem is a developer committing an API key to Git. By the time anyone notices, it is already public.
So you add secret scanning. A Gitleaks pre-commit hook blocks the commit before it leaves the laptop.
Your code is clean, but a library three levels deep has a critical CVE. You never chose it, but you shipped it.
So you add SCA. Dependabot, Snyk or Trivy checks every dependency on every pull request.
Then your own code. Someone concatenates user input into a SQL query. It passes review and it is wide open.
So you add SAST. Semgrep or SonarQube flags it on commit, while the fix is still two lines.
Your Docker image inherits 200 known vulnerabilities from one FROM line.
So you scan images in CI and move to minimal base images. Smaller image, smaller attack surface.
Your Terraform creates an S3 bucket and someone forgets one line. The bucket is public, and no code scanner caught it.
So you add IaC scanning. Checkov or tfsec kills the misconfiguration in the pull request, not in the news.
Now the scanners find 400 issues on day one. The team ignores all of them and the pipeline becomes noise.
So you add quality gates. Block on Critical and High, warn on the rest. Security becomes a rule the pipeline enforces, not a PDF nobody reads.
Some bugs only show up when the app is running, like a broken auth flow or a missing header.
So you add DAST. OWASP ZAP attacks your staging app the way a real attacker would.
Your pipeline holds long-lived cloud keys. Steal those, and you own production.
So you use OIDC. The pipeline gets short-lived credentials that expire in minutes. Nothing permanent to steal.
Your image passes every scan, then someone pushes an unscanned one straight to the cluster.
So you add image signing and admission control. Cosign signs it, Kyverno rejects anything unsigned. Only trusted images get in.
A zero-day drops on Friday evening and your CEO asks if you are affected. Nobody knows what is inside what you shipped.
So you generate an SBOM for every build. The answer takes one search, not one weekend.
And finally, an attacker gets past everything and lands inside a running container. Every scan was clean, but the threat is live.
So you add runtime security. Falco watches system calls and alerts the moment a container does something it never should.
DevSecOps is not a tool. It is a list of "what if" moments, each one closed before an attacker finds it.
Shift left was never about slowing the team down. It was about making sure nobody wakes up at 2am to a breach.
Decorum.btc🥑 retweeted
Before you learn Kubernetes, understand why to learn Kubernetes. Or should you?
25 years back, running an app meant buying an expensive physical server ($10k-$50k), doing the cabling, installing the OS, configuring everything.
Another app? Another server. Only banks and big companies could afford this.
Then came virtualization. 10 servers became 100 VMs. Better, but you still owned the hardware.
Around 2005, Amazon rented out its spare data center capacity. Startups could launch without buying a single server. Pay for what you use. Scale when you grow. Netflix jumped on it early.
But that only fixed the server problem. How we built apps was still broken.
Companies built one giant codebase. Netflix had accounts, player, recommendations and payments all in one. Easy to build, hard to scale.
In 2008 Netflix had a major outage. If US users alone could take them down, how would they go global? So they broke the monolith into hundreds of small services. Microservices.
Everyone copied them. Even companies with 3 users.
Then the headaches started. Python 2.7 for one service, 3.6 for another. Different libs, different configs. Setting up a new dev machine took days.
And the most hated phrase in tech: "But it works on my machine."
Docker fixed it in 2013. Containers weren't new (Google had them for years), but Docker made them easy. Package the app with everything it needs. Laptop, staging, prod. Same behavior.
But running one container is easy. Running 10,000 is a nightmare.
- Who restarts crashed services?
- Who scales on traffic spikes?
- How do services find each other when IPs change?
- Who does load balancing?
People wrote shell scripts. It was painful.
This is exactly what Kubernetes solved.
Google had run containers at massive scale with Borg. In 2014 they rebuilt the idea as Kubernetes and open-sourced it. Then they launched GKE, so easy that companies picked Google Cloud just for it.
AWS and Azure panicked and shipped EKS and AKS. K8s won.
Why? Perfect timing. Docker made containers popular. Netflix made microservices popular. Everyone needed something to manage the chaos. K8s does deploys, auto-healing, autoscaling, service discovery and load balancing in one system.
Then AI happened, and K8s became even more critical:
- GPUs are expensive. K8s schedules them and keeps them busy.
- Training runs are batch jobs at insane scale. Queue, retry, repeat.
- Inference is a traffic problem. K8s scales with demand and rolls out new models with zero downtime.
- Distributed training needs orchestration.
- AI agents need isolated, short-lived sandboxes. Pods already are that.
- GPUs are scarce, so teams use any cloud they can get. K8s gives one API everywhere.
The whole AI tooling ecosystem speaks Kubernetes.
AI didn't replace K8s. It made it the plumbing under everything.
Understanding this story matters more than memorizing kubectl commands.
Now go learn Kubernetes already.
Decorum.btc🥑 retweeted
Cancer is really taking too much lives lately … Here’s a list of materials causing Cancer at Home …. Avoid them ….






























