Pinned Tweet
Haiku 5.5 is live on Claude Platform and Claude Code 🚀
~75% cheaper than Haiku 4.5. $0.10 / $0.50 per MTok under 100K (cache reads $0.01) 💸
Fast subagent for summaries, queries, and parallel work next to Opus or Sonnet ⚡
🚨 11-year-old Brazilian student Júlia Helena Pimenta Ferreira (from Belo Horizonte) spotted a pattern while calculating perfect squares in class in 2022.
She noticed that each next square can be built by adding the current number and its successor to the previous square:
10^2 = 100
100 + 10 + 11 = 121 (11^2)
121 + 11 + 12 = 144 (12^2)
The last number you add is the root. Her teacher, Frederico Ferreira, formalised the idea into an algebraic approach called Regressão de Júlia. It was published in the Revista do Professor de Matemática (Sociedade Brasileira de Matemática).
A simple classroom observation that turned into published work and a nice reminder of how much students can contribute when teachers listen.
Geeta retweeted
Day 4: AWS Authentication – AWS IAM, AWS Cognito, AWS Email, AWS Password, AWS Magic Links, and AWS OAuth Login
Project: Build a complete AWS authentication system.
Grab AWS Handbook: codewithdhanian.gumroad.com/…
Geeta retweeted
> Becoming a DevOps expert takes years. I agree!
> But you don't need years to START. 👇
> That's why I'm working on a 45-Day DevOps Visual Learning Series.
12 modules. 45 days. One clear learning path.
Linux → Scripting → Networking → Git → CI/CD → Docker → Kubernetes → IaC → Cloud → Monitoring & Security.
The goal isn't to make you an expert in 45 days.
It's to help you stop overthinking, build strong fundamentals, and start working on real projects.
My approach:
- Break complex topics into simple visuals.
- Learn one concept at a time.
- Practice daily with hands-on tasks.
- Build a capstone project to connect the dots.
You can spend months wondering where to start.
Or spend the next 45 days building momentum.
Experts are made over years. But every expert starts somewhere.
Let's make that first step easier. 🚀
Leap Of Faith ⭐️
On December 30, 1952, London bus driver Albert Gunter dramatically jumped his Route 78 double-decker bus across a rising gap on Tower Bridge. Realizing the bridge was lifting unexpectedly on a green light, the former WWII tank driver accelerated, clearing the opening with 20 passengers on board....
With 20 terrified passengers on board, the red Routemaster leaped across a three-foot gap as the bridge continued to lift. The front wheels landed safely on the opposite side, though the impact broke the suspension and injured Gunter’s leg. Miraculously, everyone survived with only minor injuries.
Albert was later rewarded with a £10 bonus for his bravery — roughly £400 today — and became a London legend. His daring leap remains one of the most extraordinary moments in public transport history.
#drthehistories
AI Interviewer:
ChatGPT gave me a perfect answer from a document I uploaded. Does that mean it “understood” the whole document?
Geeta retweeted
Useful + consistent beats loud every time. Solid growth advice from @techyoutbe.
I’ve built 100K audience across X, Substack, Telegram, Youtube, Threads and Gumroad by sharing practical tech knowledge.
Here’s what I’ve learned about growing on X 👇
1. Build your positioning
• Pick 2–3 topics you know deeply
• Make your bio clear
• Give people a reason to follow you
• Build a recognizable visual identity
2. Create content people save
• Share roadmaps, cheat sheets, and visual guides
• Use numbers, real examples, and practical takeaways
• Focus on one idea per post
• Make complex topics easy to understand
3. Make your content stand out
• Share what you've actually learned or built
• Turn technical knowledge into simple explanations
• Have a clear point of view
• Don't just repeat what everyone else is posting
4. Build a community
• Engage with people in your niche
• Reply with useful insights, not just “Great post!”
• Learn from creators outside your niche
• Be consistent before worrying about going viral
5. Turn attention into trust
• Share your work publicly
• Build useful resources
• Give people something they can apply immediately
• Let your content demonstrate your expertise
My biggest lesson?
You don't need to be the loudest person on X.
You need to be useful, recognizable, and consistent.
I’m building Tech Fusionist around one simple idea:
Make Cloud, DevOps, AI, and Security easier to learn.
Share knowledge. Build in public. Help others grow.
Geeta retweeted
AI Security Engineering :
Chatbots are a commodity.
AI Security is the physics of trust.
Master these 12 stages and you’ll never be unemployed again.
From threat modelling → red teaming → building the immune system for autonomous AI.
Bookmark this. The future needs defenders. 🛡️
🤖 Made with AI
Geeta retweeted
Solid map shared by Kushal for AI infrastructure Engineering .
I would add these to the list👇
• Profile workloads first , effective GPU use is often only 30-40% despite high nvidia-smi numbers.
• Optimise KV cache (quantisation + better layouts) biggest lever for LLM latency and throughput.
• Watch cost early: idle GPUs, zombies, and poor scheduling waste huge budgets.
• Right-size and keep the stack modular so you can swap engines and models without pain.
AI Infrastructure Engineers (Step by Step)
01 | AI Infrastructure Fundamentals: What Runs AI? Compute → GPU → Memory → Storage → Network → Cloud → Kubernetes → Containers → Drivers → CUDA
02 | AI Model Serving: How Do You Serve AI Models? Model → Load → Runtime → API → Batching → Cache → Stream → Scale → Route → Serve
03 | GPU Infrastructure: How Do You Accelerate AI? GPU → CUDA → VRAM → Tensor Cores → Multi-GPU → Parallelism → NVLink → NCCL → Profiling → Optimization
04 | LLM Inference: How Does AI Generate Responses? Prompt → Tokens → Prefill → KV Cache → Decode → Sampling → Batching → Streaming → Quantization → Output
05 | AI Scaling: How Do You Handle AI Traffic? Replicas → Load Balancing → Autoscaling → Batching → Queues → Caching → Routing → GPU Pooling → Scheduling → Failover
06 | AI Data Pipeline: How Does Data Reach AI Models? Collect → Ingest → Validate → Clean → Transform → Chunk → Embed → Index → Retrieve → Feed
07 | AI Observability: How Do You Monitor AI Systems? Metrics → Logs → Traces → GPU Usage → Latency → Throughput → Token Usage → Errors → Alerts → Dashboards
08 | AI Security: How Do You Secure AI Infrastructure? IAM → Secrets → Encryption → Network Isolation → Access Control → Model Security → Data Privacy → Guardrails → Auditing → Compliance
09 | AI Platform Engineering: How Do You Build AI Platforms? Provision → Configure → Containerize → Orchestrate → Deploy → Schedule → Automate → Monitor → Govern → Optimize
10 | AI Reliability & Cost: How Do You Run AI Efficiently? Capacity → Utilization → Benchmarking → Right-Sizing → Quantization → Caching → Spot GPUs → Cost Tracking → Fault Recovery → Optimization
Geeta retweeted
Interview question for AI/agent engineers:
You’re building a support agent that can call tools to refund orders, resend receipts, and update shipping. A user says: “My package never arrived, can you help?”
How do you make sure the agent doesn’t quietly issue a refund the user never actually asked for even if someone later tampers with the system prompt or jailbreaks the conversation?
Short follow-ups:
1. Where do you enforce the “user must explicitly request this action” rule — inside the model, outside it, or both? Why?
2. How do you prevent a jailbroken or injected prompt from overriding that rule while still letting legitimate users get refunds when they clearly ask?
3. What concrete signals or checks would you require before any refund tool call is allowed?
What would you ask next?
Geeta retweeted
Interviewer:
YOUR SERVICE HANDLES 50 REQUESTS/SEC FINE IN STAGING BUT FALLS OVER AT 80 REQUESTS/SEC IN PRODUCTION.
Average latency jumps from 40ms to 2+ seconds.
CPU stays under 25%. Memory and disk I/O look normal.
What’s causing the slowdown?
Geeta retweeted
Sharing another Vedic Math trick
Multiply any number by 11 in seconds
👇
🤖 Made with AI
Geeta retweeted
AI Interviewer:
I fine-tuned a model on our internal Q&A pairs. Why do people still recommend RAG on top of it?
AI Interviewer:
I fine-tuned a model on our internal Q&A pairs. Why do people still recommend RAG on top of it?




















