ஒரே நிமிடத்தில் தமிழ் எழுத்துகள் அனைத்தையும் கத்துக்க முடியும். குழந்தைகளுக்கு உபயோகமாயிருக்கும்.
என் மகன் பத்தாவது படிக்கிறான். இந்த விடுமுறையிலாவது தமிழ் சொல்லிக் கொடுக்கனும். 🙂
பரந்தூர்ல ₹8 லட்சத்துக்கு இருந்த ஒரு ஏக்கரின் guidline value'வ, ₹65 லட்சத்துக்கு மாத்த நூதனமா ஒரு நிறுவனம் வேல பாத்து இருக்கு..
இதனால் அரசுக்கு ₹170 கோடி இழப்பு ஏற்பட்டு இருக்கும்.. இந்த மாதிரி எத்தன நிறுவனங்கள் எத்தன பெரும் முதலாளிகள் இதில் ஈடுப்பட்டார்களோ அவர்களுக்கு இந்த அறிவிப்பு பெரும் இடியாக தான் இருந்து இருக்கும்...
ஆனால் பரந்தூரில் வசிக்கும் விவசாயிகள் Market Value ல இருந்து 3.5 மடங்கு அதிகம் குடுத்தாலும் வேண்டாம் விவசாயம் தான் முக்கியம்.. அந்த மண்ணின் ஆதாரமான நீர்நிலைகளை அழிக்க கூடாது என போராடியவர்களுக்கு இது பெரும் வெற்றி...
இது சாத்தியப்படுத்த மிக பெரிய ஆன்ம பலம் வேண்டும்..
இதை @CMOTamilnadu விடுத்து
எந்த முதல்வராலும் செய்து இருக்க முடியாது.. கூடிய விரைவில் சென்னையின் இரண்டாவது விமான நிலையத்துக்கு உரிய இடம் தேர்ந்தெடுக்கப்படும் என்ற அறிவிப்பு கூடுதல் மகிழ்ச்சி..
I genuinely want to understand who is responsible here.
The department whose job is to give us decent and safe roads?
The authority that issues driving licences and ensures people driving these huge tankers are actually fit to drive them?
The authority that allows these tankers to run on our roads and is supposed to ensure that the vehicle, registration and number plate are all compliant?
This is around Varthur CDP Road. Just see the condition of the road and the way these tankers move around people on two-wheelers.
At the end of all this, it is the common man who suffers.
We pay income tax, GST, road tax, registration charges and so much more. Asking for a decent road and basic safety is surely not asking for too much.
Do we really need to wait for someone to lose their life before action is taken?
Who is accountable?
@blrcitytraffic@BlrCityPolice@CPBlr@CMofKarnataka@PanathurUpdates@BalagereConnect@BalagereRising@bbmpcommr@SobhaSentosa2
#Varthur #Bengaluru #RoadSafety #balagere
These videos are circulating across various groups and are not recorded or verified by me. I am sharing them only because, after seeing them, I felt there are some genuine questions around road safety, enforcement and accountability that need to be asked.
Every DevOps engineer I know who got fired over the last 12 months made the same mistake. They optimized for architecture instead of operations.
They spent months migrating to Kubernetes, replacing CI pipelines, introducing GitOps, adopting service meshes, and rewriting Infrastructure as Code. Then production went live. Incidents kept happening. Customers kept complaining. They started another migration.
In 2026, this will cost you your job. In infrastructure, most architectural decisions will never be noticed by your customers. If you keep investing months into rebuilding platforms before proving they solve a real operational problem, you're spending engineering time on work that may never produce measurable results. That slows your team down a lot.
Spend most of your effort on the one thing you cannot fake. Operational understanding. Know where failures happen. Know why deployments fail. Know which services create the most alerts. Know what customers actually experience when production starts breaking. This is what determines whether your platform succeeds.
Everything else can wait until the operational problems are under control. Nobody chooses your platform because you replaced one Kubernetes tool with another.
I know a retail platform reduced production incidents by more than half without introducing a single new technology. The team removed recurring deployment mistakes, simplified release approvals, and fixed unhealthy monitoring rules that had been ignored for months.
The business does not care which GitOps tool you use or how elegant your Terraform modules look.
The business cares about four things.
Can customers place orders?
Can engineers deploy safely?
Can incidents be resolved quickly?
Can cloud costs stay under control?
A simple platform that keeps production stable beats a sophisticated platform that keeps failing every single time.
Study production first. Find recurring failures. Remove them one by one. When the platform becomes predictable, then invest in making it better.
That's how you stay valuable in the era of AI.
49K+ read my DevOps and Cloud newsletter: https://t.co/WBucLdwdsb
What do we cover:
DevOps, Cloud, Kubernetes, IaC, GitOps, MLOps
🔁 Consider a repost if this is helpful
Excessive screen time and digital addiction are quietly affecting children's mental health, attention and overall wellbeing. Evidence shows that increased digital exposure is linked to anxiety, depression, poor sleep, aggression, loneliness, gaming disorders and in severe cases, suicidal behaviour.
To prevent this, let us encourage healthy screen habits and open conversations to help our young ones grow up balanced and resilient.
#DigitalWellbeing #ChildMentalHealth #ScreenTime #AIIMSDelhi #HealthyChildhood
சாலை உயரம் தமிழ்நாட்டின் அவமானம்.
டெண்டர் செட்டிங் செய்து கமிஷன் அடிப்பதற்காக, திமுக அதிமுக ஆட்சிகளில் ஈவு இரக்கமற்று, உயரங்களை அதிகரித்து போடப்பட்ட சாலைகளால் மக்கள் படும் இன்னல்கள் ஏராளம்.
மக்கள் உழைத்து சம்பாதித்து கடன் வாங்கி கட்டிய வீடுகளை குழிக்குள் தள்ளி அந்த வீடுகளை பயனற்றதாக மாற்றிய குற்றத்திற்கு தமிழக அரசுக்கு என்ன தண்டனை?
மீண்டும் சாலைகளை பழைய உயரத்திற்கு கொண்டு வருவீர்களா? அல்லது
அந்த வீடுகளை சாலை மட்டத்திற்கு உயர்த்தி கொடுப்பீர்களா?
என்ன செய்ய போகிறது தமிழக அரசு?
இனி தவெக ஆட்சியில் புதிதாக போடப்படும் சாலைகள் பழைய சாலை மட்டத்தை விட குறைத்து போடுவதை தமிழக அரசு உறுதி செய்யுமா? பாதிக்கப்பட்ட மக்களுக்கு என்ன பதில்?
@CMOTamilnadu@TVKVijayHQ@AadhavArjuna@mdu_corp
When your mind is restless, listen to Sri Kulasekhara Azhwar’s famous Mukunda Mala.
Absolutely brilliant rendition here by Sriman ‘Kainkaryam’ Rangarajan ji at Thirunarayanapuram. Hope to go there soon again and have Darshanam of Perumal!
☺️🙏🏼☺️🙏🏼☺️
Most people start learning Kubernetes the wrong way.
They see Kubernetes as a list of concepts. Pods. Deployments. Services. Ingress. They memorize them without understanding why they exist.
>> You start with a Pod.
- A pod runs your container. Simple. Clean. Done.
- Until it crashes.
- Nobody restarts it. It is just gone.
In production, that is not acceptable.
>> So you use a Deployment.
- A Deployment watches your pods.
- One dies, and it creates another.
- You want 3 running, it keeps 3 running.
- You want to scale to 10; one command does it.
Pods were too fragile for production.
Deployments fixed that.
>> But now you have a new problem.
- Every pod gets a new IP when it restarts.
- You have 3 pods running your app.
- Another service needs to talk to them.
- Which IP do you use? They keep changing.
- You cannot hardcode them.
- You cannot track them at scale.
>> So you use a Service.
- A Service gives your app one stable IP address.
- It finds your pods using labels, not IPs.
- Pods die and come back with new IPs.
- The Service does not care.
- It always finds them.
- It also load balances.
- Traffic coming in gets distributed across all healthy pods automatically.
Pods had unstable IPs. Services fixed that.
>> But your app still needs to be accessible from the internet.
- So you use a LoadBalancer Service.
- This creates a real cloud load balancer.
- AWS ALB. Azure LB. GCP LB.
- Your app gets a public endpoint.
- Works perfectly. Until you have 10 services.
- Now you have 10 load balancers.
- Each one costs money every single month.
- Your cloud bill does not care that 6 of them handle almost no traffic.
LoadBalancer Services solved external access. But one per service does not scale.
>> So you use Ingress.
- One load balancer. All your services behind it.
- Ingress routes traffic based on rules.
- Request comes in for /api, goes to the API service.
- Request comes in for /dashboard, goes to the frontend service.
-One entry point. Smart routing. One cloud load balancer on your bill.
But Ingress is just a set of rules. Something has to execute those rules.
>> So you use an Ingress Controller.
- Nginx. Traefik. AWS Load Balancer Controller.
- These are the actual engines that read your Ingress rules and make the routing happen.
- Ingress without a controller is just a config file nobody reads.
To summarize it:
> Pod ran your app but had no resilience.
> Deployment gave it resilience.
> Service gave it a stable address and load balancing.
> LoadBalancer Service gave it external access.
> Ingress replaced 10 load balancers with one.
> Ingress Controller made the rules actually work.
Each concept exists because the previous one was not enough.
Salesforce is running an ad claiming 40% off to beat Zoho. We have watched this playbook for years where they give deep discounts to get you in, followed by aggressive escalation once you're locked-in.
Before you switch anything, ask them to show you standardised multi-year pricing. If they don't, that's your answer. Enterprise software is a con-game of "discount" bullshit by vendors like Salesforce. Buyer beware!
As for "old CRM", Salesforce is a garbage bin of acquired enterprise software companies over decades, held together with bubble gum and duct tape.