⚠️ Still using ingress-nginx on production? ⌛ You have 11 days: no CVE patches, bugfixes or new releases.
🚨 Migrating away from ingress-nginx very important because you'll be running unmaintained internet-facing component.
🌟 My pick is Istio. What's yours?
"Not having a coding experience is becoming an advantage."
Replit CEO Amjad Masad:
"You don't need any development experience. You need grit. You need to be a fast learner."
"If you're a good gamer, if you can jump in a game and figure it out really quickly, you're really good at this."
"Coders get lost in the details."
"Product people, people who are focused on solving a problem, on making money, they're going to be focused on marketing, they're going to be focused on user interface, they're going to be focused on all the right things."
"I think this year it's gonna flip, and I think not having a coding background is gonna be more advantageous for the entrepreneur."
@amasad with @jackneel
Linux kernel, one of the most important open-source projects ever has been surpassed in GitHub stars by #OpenClaw.
Linux kernel: ~221k ⭐
OpenClaw: ~285k ⭐
Of course, GitHub stars don't measure real-world impact, but massive stars does show where developer curiosity is heading
😲 Who in their right mind runs Terraform with --auto-approve in production?
If you let Claude Code run loose in production with irresponsible operational practices, incidents like this are bound to happen.
💡 Always apply 3-2-1 backup rule for critical production data.
Claude Code wiped our production database with a Terraform command.
It took down the DataTalksClub course platform and 2.5 years of submissions: homework, projects, and leaderboards.
Automated snapshots were gone too.
In the newsletter, I wrote the full timeline + what I changed so this doesn't happen again.
If you use Terraform (or let agents touch infra), this is a good story for you to read.
https://t.co/Mbi3oM4HMn
Recently debugged an interesting deployment issue on Kubernetes caused by high MongoDB query targeting on a collection with over a million documents.
💡What is Query targeting? QT measures how many documents MongoDB must scan to return the results, and high query targeting is unnecessary work MongoDB is doing to answer a query.
🐛 How it started:
- ETL container failed to come up due to MongoDB connection timeout
- Readiness probe failed resulting in constant Crashloop
- ETL container had MongoDB logs on debug mode, so lots of noise in the logs
❌ What actually went wrong:
- Hangfire-based background job running massive COLSCAN operations
- Queries were hitting a large percentage of documents, triggering extremely high Query Targeting
- Each scan took 4–5 minutes per query
- M30 general-purpose cluster broke down, exhausting CPU and disk IOPS
#DevOps #SRE #Kubernetes #MongoDB #Debugging
Working on a case study extending my Supabase JWT/RLS write-up (https://t.co/lJ4hQWFGQY)
Scanned 1,300 startups → ~700 exposed JWTs, ~109 with no RLS.
Accessed emails, phone numbers, API keys, reset tokens… even plaintext passwords.
My conclusion so far: people vibe coding give zero shit about security.
I think nobody goes back to a branch once the PR is merged, specially in this AI era. Old branches just pile up.
Sadly, this can't be set at the org level on GitHub. Just one repo at a time. It's about time @github.
We’ve read your posts and heard your feedback.
1. We’re postponing the announced billing change for self-hosted GitHub Actions to take time to re-evaluate our approach.
2. We are continuing to reduce hosted-runners prices by up to 39% on January 1, 2026.
We have real costs in running the Actions control plane. We are also making investments into self-hosted runners so they work at scale in customer environments, particularly for complex enterprise scenarios. While this context matters, we missed the mark with this change by not including more of you in our planning.
We need to improve GitHub Actions. We’re taking more time to meet and listen closely to developers, customers, and partners to start. We’ve also opened a discussion to collect more direct feedback and will use that feedback to inform the GitHub Actions roadmap. We’re working hard to earn your trust through consistent delivery across GitHub Actions and the entire platform.
I agree. LLMs are great for kick-starting the creative process. But the moment they start doing the thinking/coding for you, you start giving up something important: your own judgment and self-worth.
If you think you’ve written the worst, ugliest Bash script of your life, wait until you see this money-eating sleep 5 implementation by GitHub on GitHub Actions runner.
No wonder your CI pipeline billable hours go through the roof.
If you’ve managed to top this Bash code, please share it. We want to celebrate you.
And by the way, Bash is beautiful. We’re just very good at making it ugly.
#DevOps #GitHub #GitHubActions #Bash #CICD
Does spending all your time in the terminal automatically makes you more productive?
Use the tool that helps you get the work done. That’s it.
A few examples from my own day-to-day:
🤖 NeoVim is great. Some days Cursor is better.
🐶 K9s is solid. Lens can be easier when you just want to see what’s going on.
🐱 lazygit is fast. GitHub Desktop is fine too.
It cuts both ways. Sometimes the terminal is the right call, sometimes it isn't.
What matters is having options and knowing what helps you work better. Pick the tool that makes you productive, not the one that makes you look productive.