@4SN Actually in Zepto you cant even raise complaint like other apps... There are cases where im stuck cant cancel it and the order delivers next day as if I ordered on Amazon.
At the time of purchase, the focus was on discounts and offers. At the time of buyback, those same discounts are being taken back along with additional deductions.
How is a customer supposed to understand the true value of their purchase if major deductions only become apparent?
@prajwalgb_ Well he should ve avoided that phrase... and that triggered that candidate who s already in depression due to no job. And he went steps ahead.
@polimernews Road la entha pakkam pakkama istathuku varuvanga nu car karan guess pannanum... road la istathuku speed ah varuvan nu bike karan guess pannanum... rendu perum istathuku poitu oru kolantha uyir pochu...
@TANGEDCO_Offcl Yesterday also same time power cut in Navalur from 1 pm to 6 pm. Today also power gone by 1 pm. How can we rest in this heat? Is this some regular powercut time? Consumer number 092960072108
🚨Anthropic recently showed a 24-minute workshop on how to actually do prompts for Claude.
Taught by the people who built it.
Free. No registration. No paywall.
I've seen $300 courses that don't cover what they teach in the first 8 minutes.
Watch it and bookmark it now.
₹6 LPA engineers and ₹40 LPA DevOps engineers often use the SAME tools.
Same Kubernetes
Same Docker
Same Terraform
So why is one getting massively underpaid?
Because companies don’t pay for tool familiarity anymore.
They pay for:
- outage ownership
- production debugging
- RCA thinking
- infrastructure decision-making
- staying calm during chaos
Most engineers stay stuck because they spend years:
- memorizing commands
- collecting certifications
- cloning projects
- avoiding real troubleshooting
Meanwhile, high-income engineers are learning:
- failure isolation
- networking internals
- Kubernetes behaviour under load
- observability
- incident communication
That’s the real salary gap.
Your package is directly tied to:
“How much production risk can a company trust you with?”
Kubernetes Ingress Vs Gateway API 👇
Most Kubernetes deployments today use Ingress to expose HTTP(S) traffic.
It works, but it has notable caveats:
Tied to HTTP
Cluster scoped
Limited Extensibility
No Fine grained Routing Control
and so on.,
If haven’t explored the Gateway API yet, you might be missing out on more flexible traffic control and multi protocol support.
48K+ read my DevOps and Cloud newsletter: https://t.co/WBucLdwLhJ
Sign up to get 'The Practical Linux Guide for DevOps Engineers'
What do we cover:
DevOps, Cloud, Kubernetes, IaC, GitOps, MLOps
🔁 Consider a Repost if this is helpful
Most ‘5 years experienced’ DevOps engineers fail this interview question instantly.
Interviewer:
“HPA scaled your application to 12 pods.
Why are users still seeing latency spikes?”
Weak answers:
“Scale more.”
“Increase CPU.”
“Restart deployment.”
Senior engineers know:
healthy pods do NOT guarantee healthy systems.
A real answer investigates:
- connection exhaustion
- database saturation
- DNS latency
- retry storms
- uneven traffic distribution
- ingress bottlenecks
- external dependency slowness
This is the difference between:
someone who learned Kubernetes…
…and someone who understands production systems.
That’s why interviews are getting harder now.
Companies are tired of hiring engineers who only know commands.
InfraThrone Elite was built for this exact gap.
We simulate:
- SEV incidents
- production ambiguity
- outage debugging
- pressure-based interviews
- real RCA scenarios
Because the market rewards engineers who can diagnose chaos calmly.
Not engineers who memorize kubectl.
@A_n_b_e_S_i_vam Operation pannavunga yaralayum indian toilet use panna mudiyathu. Romba kasta paduvanga... neraya per veetla operation panirukanga amma ku so western toilet katrom nu kuda pathuruken... its normal... option eh illama vaika koodathu... toilet use pannitu flush panna its all same
DevOps team chats be like…
“Pods might have crashed.”
“Let me check the logs.”
“Looks like an application issue.”
“Readiness probe is failing.”
“Pod is destroyed. Again.”
“Raise a support ticket.”
“Kafka has crashed.”
“Multiple services are down.”
“HPA is not working as expected.”
“Can you approve my PR?”
“There’s a sudden spike in the billing.”
“Do we have a backup?”
“It works on the dev environment.”
“Have we configured alerts?”
“Node is in NotReady state.”
“Disk pressure on one of the nodes.”
“The CI pipeline is stuck.”
“Secrets were not mounted.”
“There’s a DNS resolution issue.”
“Rollback initiated.”
“Deployment is stuck in progress.”
“We are getting throttled by the API gateway.”
“The cronjob didn’t run.”
“We crossed the quota limit.”
“Why is the staging environment faster than prod?”
“Cache isn’t invalidating properly.”
“Anyone has access to the monitoring dashboard?”
“We need to increase the replicas.”
“There’s a version mismatch between services.”
“Why is there a kube-system pod using 90% CPU?”
If you know, you know.
Some of these messages hit harder when they show up at 2 AM or during a demo 😅