dee retweeted
Over the past week, I’ve been overwhelmed by the love and support of friends, industry colleagues, and people I've never met. Thank you to everyone who has shown kindness to my family and me. It means the world to me.
I came to the United States 53 years ago, and becoming an American citizen is one of the greatest gifts and proudest moments of my life. NVIDIA has been my life’s work. Building it into the company it is today alongside my colleagues has been a privilege and an honor. Nowhere but in America could a company like NVIDIA be possible. I love our country, and I love NVIDIA.
I did not live up to the standards expected of everyone at NVIDIA, and I have made serious mistakes in my personal life. I created problems for the Board that I deeply regret. I own my mistakes completely, and I am committed to cooperating with the Board’s independent investigation.
Since my departure, I’ve seen an outpouring of calls from NVIDIA’s employees, investors, business partners, and customers for me to return as CEO. Many continue to reach out to me directly as the company navigates complex technology, market, competitive, and geopolitical dynamics. NVIDIA is a once-in-a-generation company. If the Board of Directors decides that my return is in the best interest of our shareholders, our employees, the company, and America, I would be honored to answer these calls and return as CEO.
Thank you again to everyone who has shared their good wishes. I am profoundly humbled by your support. To my family: I love you, and I will spend the rest of my life being worthy of yours.
Jensen
dee retweeted
I created and tested my first AWS Lambda function using Python today, then moved on to explore Elastic Load Balancing.
With Lambda, I wrote and deployed a function, passed it a test event, invoked it successfully, and examined its execution logs in Amazon CloudWatch.
I then moved to Application Load Balancing. I created an internet-facing Application Load Balancer in my custom VPC, mapped it to two public subnets across different Availability Zones, configured an HTTP listener on port 80, and created a target group with my existing Ubuntu EC2 instance registered as a target.
I also configured a dedicated security group for the load balancer and had to troubleshoot an inbound traffic rule before completing its creation.
The ALB is currently provisioning.
Next, I'll explore target health checks, traffic routing and how the load balancer distributes incoming requests across registered instances.
@awscloud @AWS @AWS_Edu
dee retweeted
Noticed in the banya today: I’m getting skinnier.
This is despite a strict diet of lobster linguini and crab pelmeni.
There is only one explanation: crypto winter.
So we stayed in the steam room until November’s launches on TON were planned.
We can’t lose more valuable fat.
dee retweeted
Kubernetes retired ingress-nginx in March 2026.
About half of cloud-native environments relied on it.
If your DevOps roadmap is older than that, it's out of date.
Here's the 12-stage DevOps roadmap I'd follow in 2026:
Stage 1: Linux & Networking
❯ Learn ➟ Linux CLI, permissions, systemd, DNS, TCP/IP, HTTP
❯ Practice ➟ Host a web app on a Linux VM with Nginx, a custom domain and HTTPS
❯ Why ➟ Every DevOps tool runs on Linux and talks over a network
Stage 2: Git & Version Control
❯ Learn ➟ Branching, pull requests, code review, trunk-based development
❯ Practice ➟ Set up branch protection and required reviews on a repo
❯ Why ➟ Everything in DevOps starts with a commit
Stage 3: Scripting & Automation
❯ Learn ➟ Bash, Python, cron, REST APIs
❯ Practice ➟ Write a script that backs up a database and alerts you when it fails
❯ Why ➟ If you do it twice, automate it
Stage 4: Docker & Containers
❯ Learn ➟ Dockerfiles, multi-stage builds, image layers, registries, non-root users
❯ Practice ➟ Shrink a Node.js image from 1GB+ to under 100MB
❯ Why ➟ Smaller images build faster, ship faster and expose less
Stage 5: CI/CD Pipelines
❯ Learn ➟ GitHub Actions, GitLab CI, Jenkins, caching, test gates
❯ Practice ➟ Build a pipeline that tests, builds, scans and deploys on every merge
❯ Why ➟ Every manual step is a place for mistakes
Stage 6: Infrastructure as Code
❯ Learn ➟ Terraform or OpenTofu, remote state, modules, Ansible
❯ Practice ➟ Provision a VPC, a VM and a database from code, then destroy it with one command
❯ Why ➟ If you can't rebuild it from code, you don't control it
Stage 7: Cloud Fundamentals
❯ Learn ➟ AWS, Azure or GCP: IAM, VPC, compute, storage, managed databases
❯ Practice ➟ Deploy a 3-tier app with private subnets and least-privilege IAM roles
❯ Why ➟ Most cloud mistakes are permission mistakes
Stage 8: Kubernetes
❯ Learn ➟ Pods, Deployments, Services, Helm, autoscaling, Gateway API
❯ Practice ➟ Run an app on a local cluster with health probes, autoscaling and a Gateway API route
❯ Why ➟ ingress-nginx is retired, and Gateway API is where Kubernetes routing is heading
Stage 9: GitOps & Release Strategies
❯ Learn ➟ Argo CD, Flux, blue-green, canary, feature flags
❯ Practice ➟ Make Git the source of truth, then roll back a bad release with one revert
❯ Why ➟ Git becomes your audit trail and your undo button
Stage 10: Observability
❯ Learn ➟ Prometheus, Grafana, OpenTelemetry, logs, traces, alerting
❯ Practice ➟ Instrument an app and alert on latency and error rate
❯ Why ➟ You can't fix what you can't see
Stage 11: SRE & Delivery Metrics
❯ Learn ➟ SLOs, error budgets, incident response, postmortems, DORA metrics
❯ Practice ➟ Define an SLO, break it on purpose and write a blameless postmortem
❯ Why ➟ DORA now tracks 5 metrics, including rework rate, so you measure speed and stability together
Stage 12: DevSecOps & Supply Chain
❯ Learn ➟ Secrets management, image scanning, SBOMs, SLSA, image signing, pinned dependencies
❯ Practice ➟ Add secret scanning, image scanning and signed images to your pipeline
❯ Why ➟ Your pipeline holds the keys to production
Bookmark and Repost!
dee retweeted
Y do niggas think loving a girl is wack, like who do u expect to hold u down forever your homeboys??
dee retweeted
nobody can replace Jensen
dee retweeted
Met the founders at moonshot mixer.
Pitched to them, the co-founder literally said (let’s employ this babe).
Went to their office on Monday with a proposal/pitchdeck.
Got the job on Wednesday.
W week!!❤️
dee retweeted
- 1 hr of linux
- 1 hr of networking
- 1 hr of database
do this straight for 6 months and you'll be better than 90% of the infrastructure engineers
dee retweeted
A heartbreaking day.
I came to @nvidia as an intern. It was my first job, and I never left. For my whole career, @JensenHuang has been the leader I looked up to.
He taught us to reason from first principles, that the mission is the boss, and that greatness comes from suffering. And he lived it every single day, working harder than any of us.
I've never known a more inspiring leader. Thank you, Jensen. We'll keep building on what you started.
dee retweeted
I created, formatted and mounted a separate EBS volume on my Ubuntu EC2 instance, tested it with a file, and took a snapshot. But I didn't stop there. I created a new volume from that snapshot, attached it to EC2, mounted it separately and successfully recovered the original file.
With S3, I configured a private storage bucket, enabled versioning, applied server-side encryption (SSE-S3), and kept Block Public Access enabled. I also implemented a bucket policy that denies requests made over insecure transport (HTTP), enforcing secure access to the bucket and its objects.
Then I moved to EFS.
I created an encrypted Regional file system with mount targets across two Availability Zones. I configured a dedicated security group to allow NFS traffic on TCP port 2049 only from my EC2 security group.
But getting EFS mounted on Ubuntu hasn't been straightforward.
The filesystem DNS name kept returning `NXDOMAIN`. I verified the filesystem ID and mount targets, enabled DNS hostnames on the VPC, and attempted a direct NFS mount using the mount target's private IP address.
Still no successful mount.
I haven't identified the root cause yet. I'll be returning to investigate DNS resolution and NFS connectivity until I get it working.
@awscloud @AWS_Edu @AWS


























































