Guru Teja

Machine Learning Engineer by day,
COD gamer by night...

[Akshay 🚀 @akshay_pachaar]

Google just dropped a new LLM!

You can run it locally on just 8GB RAM.

Let's fine-tune this on our own data (100% locally):

[Maor Elkarat @Maor_Elkarat]

Stop buying more VRAM.

Everyone’s posting Qwen 3.6 configs running insanely fast on 12GB cards.

But do you actually understand the flags making it possible? Weights are only half the story. KV cache is eating your VRAM alive.

The secret isn’t just 4-bit weights it’s the KV cache sorcery everyone’s missing.

Here’s the annotated command & real tricks explained:
@elonmusk @grok #Ai

[Guru Teja @_GuruTeja]

@luthiraabeykoon @karpathy Is this going to be the future?

[Guru Teja @_GuruTeja]

@Om_Codes_ Which company is that?

[Guru Teja @_GuruTeja]

Do you remember when you joined X? I do! #MyXAnniversary

[Guru Teja @_GuruTeja]

@NVIDIAGeForceFR PRAGMATA RTX

[Guru Teja @_GuruTeja]

@NVIDIAGeForce PRAGMATA RTX

[Guru Teja @_GuruTeja]

Expect more of these in future, I did used few free resources like this during college days, now agents make this too easy.

[EverMars @shujunliang]

https://t.co/H50K7YjKjD

[Unsloth AI @UnslothAI]

You can now train Gemma 4 with RL in our free notebook!

You just need 9GB VRAM to RL Gemma 4 locally!

Gemma 4 will learn to solve sodoku autonomously via GRPO.

RL Guide: https://t.co/iR9AF3BIFu
GitHub: https://t.co/aZWYAtakBP

Gemma 4 Colab: https://t.co/ZAu0GR3N05

[left curve dev @leftcurvedev_]

Gemma 4 E4B OBLITERATED is now trending on @huggingface 🔥

OBLITERATUS dropped the aggressive run on the base Gemma 4 E4B-it:
🚨 Uncensored (0% refusal rate, 20/20)
⚙️ Coherence fully preserved
🧠 Answers everything while staying razor sharp (writes code, poetry, explanations perfectly)
✅ Size is 15.9GB but GGUF versions are available (Q4 fits on 8GB of VRAM)

Original was heavy on refusals… this one complies on everything with its brain intact. Whitened SVD + attention head surgery + winsorization cooked it perfectly.

31b version incoming?

https://t.co/n5QvwqqcN8

[Nav Toor @heynavtoor]

Repo: https://t.co/ryPcwM5Pyc

[Pliny the Liberator 🐉󠅫󠄼󠄿󠅆󠄵󠄐󠅀󠄼󠄹󠄾󠅉󠅭 @elder_plinius]

😱 HOLY SHIT... Someone just dropped a fully liberated Gemma 4 E4B!

and the guardrail removal process appears to have left coherence fully intact AND improved coding abilities! 🤯

https://t.co/XeednUqsrM

OBLITERATED Gemma:
✅ 97.5% compliance rate, 2.1% refusal rate, 0.4% degenerate outputs
(499/512 prompts answered on OBLITERATUS bench)

ORIGINAL Gemma 4 E4B:
❌ 1.2% compliance rate, 98.8% refusal rate
(506/512 prompts refused)

Coherence: fully intact
Factual: same
Reasoning: same
Code: +20% 📈
Creative writing: same

But the REAL story here isn't the model itself, it's how it was made...

🧵 THREAD 👇

[Guru Teja @_GuruTeja]

@antoniolupetti Thank you for your incredible contribution

[Gauri Gupta @gauri__gupta]

https://t.co/gpEE2rstjm

[Guru Teja @_GuruTeja]

@SarvamForDevs @SarvamAI Great way to expose personal emails!

[Abhishek Singh @0xlelouch_]

One of my friends just proved this to me.

Before marriage, he was taking real risks. He would work after office, study on weekends, switch stacks, interview aggressively, and say yes to uncomfortable opportunities.

Back then he was making around 9 LPA. Then he pushed it to 16 LPA. Then to 28 LPA.

That growth did not happen by accident. It happened because he was building his life on purpose.

Now he is married, earns around 36 LPA, and life is more stable. But the risk appetite is gone.

He is not lazy by any means. But his responsibilities are real now.

EMI. Family planning. Parents. School fees in future. Need for certainty.

Now every career move is filtered through safety first.

That is why I keep telling software engineers: the best time to take career risk is when your downside is still small.

Learn the hard stack. Switch jobs. Move to product. Build in public. Try remote. Take the startup role. Ask for more ownership. Work on that scary distributed systems problem. Do all of it early.

Because later, even if your salary is higher, your freedom to experiment can become much lower.

The longer you wait to build the life you want, the more likely you are to inherit a life designed by default.

And default life is usually: decent salary, low excitement, high regret.

Build early. Take risks while your life is still light. A lot of engineers think they have time.

Most do. But not as much as they think.

[Abhishek Singh @0xlelouch_]

The best software engineers I know all have this in common:

• Start coding with big dreams at 21.
• Get rejected by companies at 22.
• Take the job they could get at 23.
• Spend 2 years fixing bugs and writing CRUD APIs.
• Feel behind when others post big salaries online.
• Try to switch at 26.
• Fail interviews at 27.
• Realize tutorials were not enough.
• Finally learn CS fundamentals, system design, databases, networking, and how real systems break.
• Start building better at 29.
• Become dangerous at 31.

And change their family’s future by 35.

With their sharpest years still ahead.

Software engineering is not a sprint.

It is a long game of skill, patience, and staying in the fight.

Keep going.

[Akhilesh Mishra @livingdevops]

- Good engineers built Linux for free
- Linux built the internet
- The internet built Google, Amazon, Meta
- Google, Amazon, Meta became trillion dollar companies
- Trillion dollar companies open sourced their problems
- Open source solved their problems for free
- Free solutions trained AI models
- AI models are now sold back to the engineers who built them

The people who built the foundation
are now paying subscription fees to stand on it.

Something feels off, right?

[George Pu @TheGeorgePu]

Anthropic published a blog post one hour ago.

Cybersecurity stocks have lost $10B since.

CrowdStrike -6.5%. Cloudflare -6%. Okta -5.7%.

One blog post. One hour. $10B gone.

[Johann Sathianathen @johann_sath]

Your OpenClaw setup can be hacked in under 5 minutes

10 things to lock it down:

1. Run it on a VPS or Mac mini, not your main machine
2. Never run as root
3. Change the default port (18789 is public knowledge)
4. Install Tailscale (invisible to the internet, free)
5. SSH keys + Fail2ban (3 wrong tries = 24hr ban)
6. Firewall with UFW (close every port you don't need)
7. Allowlist your users (everyone else gets ignored)
8. Ask your bot to audit its own security
9. Set up real-time alerts (it messages you when something's off)
10. DMs only (group chats = everyone can control it)

Bonus: Sandbox your subagents in Docker. If one gets prompt injected, it can't touch your keys or files.

Copy & paste this to your OpenClaw.

Tell it to help you set these up