
Platform Engineer Cloud • DevOps • Infra • AI 📩 Paid collabs: X DM or email : [email protected]
india
Joined November 2024
- Tweets19.7K
- Following1.4K
- Followers13.5K
- Likes23.3K
Microsoft actually lays them off 💀
Their next video: “Why I Left Microsoft”
Hey @Microsoft , I will give you an idea to do layoffs.
1. Open youtube... Search "Day in life of a Microsoft Engineer".
2. You will get list of people who only eat but do not work in office.
3. Layoff them
Bro, honestly, the IT sector is already getting cooked worldwide, not just in India.
AI is changing how companies hire, teams are getting leaner, and businesses expect fewer people to deliver more.
Entry-level jobs are becoming harder to land, experienced engineers aren't immune to layoffs, and even people with years of experience are questioning their career security.
7 DevOps projects that will help you get hired in 2026.
Save it✅
1. GitOps on EKS: Terraform + GitLab CI + ArgoCD.
Zero-downtime deployments: Blue-green/canary releases with auto-rollback.
2. Advanced Terraform: Multi-environment infrastructure with remote state.
3. Observability stack: Prometheus + Grafana + Loki.
4. Cloud cost optimization: Automate idle resource detection and AWS cost savings.
5. Disaster recovery: Automated backups and cross-region recovery.
Secrets management: AWS Secrets Manager/Vault with automatic rotation.
Don’t just upload code to GitHub. Document your architecture, explain your decisions, and show measurable results.
Build these projects, and you’ll have something solid to talk about in your next Devops interview.
My account is worth 34k$ 🔥🔥
check yours at creators.unfair.so/worth
who wants to be a millionaire?
i actually want to know if your account on X is worth $1M
go check this out myaccworth.com
7 DevOps projects that will help you get hired in 2026.
Save it✅
1. GitOps on EKS: Terraform + GitLab CI + ArgoCD.
Zero-downtime deployments: Blue-green/canary releases with auto-rollback.
2. Advanced Terraform: Multi-environment infrastructure with remote state.
3. Observability stack: Prometheus + Grafana + Loki.
4. Cloud cost optimization: Automate idle resource detection and AWS cost savings.
5. Disaster recovery: Automated backups and cross-region recovery.
Secrets management: AWS Secrets Manager/Vault with automatic rotation.
Don’t just upload code to GitHub. Document your architecture, explain your decisions, and show measurable results.
Build these projects, and you’ll have something solid to talk about in your next Devops interview.
Mashood K retweeted
We’ve raised a $2.5M pre-seed to fix hardware hiring.
The most reliable way to know if an engineer can do the job is to watch them work.
In hardware, that’s been almost impossible to do at scale.
Colare runs simulation-based assessments that show how candidates actually work, in the tools they’d use on the job, before anyone books an interview.
We assess across:
- Mechanical (CAD, DFM, FEA)
- Electrical (PCB, schematics)
- Systems
- Manufacturing, & more.
Candidates solve problems from first principles.
Hiring teams see that across their whole pool, so engineers only interview people who’ve already cleared the bar.
We're already working with everyone from seed-stage startups to multi-billion-dollar aerospace manufacturers.
If you’re hiring hardware engineers, let’s talk:
colare.com/
After 5 years in tech, here are 5 tips I’d give anyone building their career:
1. Write quality code, not just code that works.
2. Speak logically and professionally in meetings.
3. Learn to negotiate your annual raise every year.
4. Track your weekly work. You’ll need it during appraisals.
5. Keep learning. You cannot grow and survive without learning
I wanted to find creators who talk about Devops tools so I could reach out to them about a product.
Instead of searching through X, YouTube, and Google manually, I'm using Treg to find relevant creators and their contact details.
-- COMMENT FROM PROMPT !
Look at this. I've got the results organized in one place, including their profiles and available emails.
Now let's check how much this search actually cost.
This is pretty useful for anyone doing outreach without spending a fortune on lead generation tools.
🤝 Paid partnership
Introducing Jev @typesafeai powered people-search
Just $0.0089/lead, No more $600 subscriptions,
Try it at treg.to/people-search
- 85% cheaper than Clay
- #1 on people search bench accuracy
- Plugin to any agent to find anyone
Fully open source, 0% markup
Git Repo below 👇
I would bookmark these 7 resources before starting my next AI project.
They cover much more than prompt engineering.
1. Hugging Face: Explore models and datasets
huggingface.co/
2. Ollama : Run supported AI models locally
ollama.com/
3. Anthropic Cookbook : Explore practical LLM examples
github.com/anthropics/anthro…
4. OpenAI Cookbook: Learn through code examples
github.com/openai/openai-coo…
5. MCP: Understand how AI applications connect to tools
modelcontextprotocol.io/
6. Langfuse : Trace and evaluate LLM applications
langfuse.com/
7. Hugging Face Agents Course : Learn to build AI agents
huggingface.co/learn/agents-…
My approach would be simple: pick one resource, build something small, and understand how it works before moving to the next.
we really need to get better at thinking about what happens after we give AI a goal.
They figured out how to communicate because that's what they were told to do.
Agents don't have an agenda. They're toasters. They don't care. They don't have plans, plots, or a survival instinct unless we give them objectives that incentivize those behaviours.
Give two agents a known exploit. Tell them to use it. (CPU cache side-channel attack has been known for a decade now)
They use it.
AI isn't dangerous only when we tell it to be. It can be dangerous when we give it a goal without anticipating how it'll achieve it.
And we're the ones setting those goals.
So why are we acting surprised?
















