अंतः अस्ति प्रारंभः | I code my thoughts 💥 Mentor @RealDevSquad
NDAwMDAgZnQgZnJvbSBzZWEgbGV2ZW
Joined January 2020
- Tweets2.3K
- Following420
- Followers2.2K
- Likes2.4K
Tejas retweeted
Pump whatever this is directly into my veins
Lets go C#!!
I was Rust-pilled for a period.
Then I remembered that I actually know C#.
.NET can achieve near-Rust performance, works on any platform, and has much nicer syntax and a great BCL. It also has amazing frameworks.
E.g. I am having SO much fun making Linux apps with @AvaloniaUI
Tejas retweeted
Server-Timing Headers in ASP .NET Core: Backend Metrics in Browser DevTools by @maartenballiauw blog.maartenballiauw.be/post… #aspnetcore
Tejas retweeted
dotNET blog: Delivering Skills in NuGet packages ift.tt/CuSY6fl
Tejas retweeted
I'm cooking up some stuff for #dotnetconf! Going to be a fun one!
If you haven't checked out the full agenda yet it is a banger!
dotnet.microsoft.com/conf
Tejas retweeted
You can build anything now, doesn't mean anyone want's it!
Effective Product Storytelling is how you bring what you built to the people who care about it.
Tejas retweeted
Last day to apply. Will be closing applications today.
It's a good opportunity for any intern, looking to get a PPO at a good startup in Bengaluru. In-Office only.
Apply here - tier3.college/openings/full-…
Please talk to your professional references and let them know you will reaching out this week.
Updates on page and via email
👉INTERNSHIP alert!
Will be posting about a full-stack engineer internship opportunity today.
₹40-45k/month
3 months
On-site in Bengaluru
Has very high potential to convert to full time. Good startup (Ankush-approved), with actual prod work.
Make sure that you have a hiring-profile set up here - tier3.college/hiring-profile (free).
Folks with professional references from folks in the industry here will be preferred first for shortlisting.
Happy to answer some questions in replies. Full details will come up later today.
Tejas retweeted
do you understand what just happened to one of the most used npm packages on the internet?
→ axios gets downloaded over 100 million times a week and today it got compromised
→ an attacker hijacked the npm credentials of a lead axios maintainer… changed the account email to an anonymous ProtonMail address… and manually published two poisoned versions
→ [email protected] and [email protected]… neither version contains a single line of malicious code inside axios itself. instead they inject a fake dependency called plain-crypto-js that drops a remote access trojan on your machine
→ the fake dependency was staged 18 hours in advance… three separate payloads were pre-built for macOS, Windows, and Linux… both release branches were hit within 39 minutes. every trace was designed to self-destruct after execution too
→ there’s no tag in the axios GitHub repo for 1.14.1. it was published outside the normal release process entirely... bypassed CI/CD completely
→ StepSecurity called it one of the most operationally sophisticated supply chain attacks ever against a top 10 npm package
→ a routine npm install silently opens a backdoor… no warning… no suspicious code visible in axios itself
this is the wake up call all vibe coding bros need to hear right now:
→ if you installed either version… assume your system is compromised
→ pin to [email protected] or [email protected]
→ rotate all secrets, API keys, SSH keys, and credentials on affected machines
→ check network logs for C2 connections
→ add –ignore-scripts to CI npm installs going forward
100 million weekly downloads and one compromised maintainer account…
that’s all it took to wreak absolute havoc
and I imagine we see a whole lot more of these… crazy times ahead for cybersecurity and vibe coding
be safe out there y’all
🚨 CRITICAL: Active supply chain attack on axios -- one of npm's most depended-on packages.
The latest [email protected] now pulls in [email protected], a package that did not exist before today. This is a live compromise.
This is textbook supply chain installer malware. axios has 100M+ weekly downloads. Every npm install pulling the latest version is potentially compromised right now.
Socket AI analysis confirms this is malware. plain-crypto-js is an obfuscated dropper/loader that:
• Deobfuscates embedded payloads and operational strings at runtime
• Dynamically loads fs, os, and execSync to evade static analysis
• Executes decoded shell commands
• Stages and copies payload files into OS temp and Windows ProgramData directories
• Deletes and renames artifacts post-execution to destroy forensic evidence
If you use axios, pin your version immediately and audit your lockfiles. Do not upgrade.
Tejas retweeted
❓Any guesses what _can_ it be? Winner wins a MacBook Pro M5.
Rules:
- Have to reply here with your answer by March 4, 2026, 5pm IST
- No cheating
- Obviously, can't ask me
Tejas retweeted
I've noticed that models are easily persuaded that a human programmer's theories are right—e.g., if I suspect something is buggy, the model will quickly agree and start generating conspiracy theories for why.
This is dangerous because programmers feel like they have evidence without the burden of objective proof. In "old school" programming, you prove your claims with a test—a reproducible demonstration of the alleged behavior. The process is illuminating: more often than not, you discover the underlying issue, or that you're straight up wrong.
As we graduate from handwriting code, it's critical to preserve objectivity. A rule of thumb at Braintrust: human↔human discussion among programmers cannot include LLM-generated explanations. Use LLMs to debug and investigate, but when you rope in someone else, you should share objective proof.
I'm curious how software tools (e.g., coding agents) will evolve to enforce this. The best AI-supercharged programmers I know artfully create verification loops for their agents—essentially performing the repro task already. I wonder what a more opinionated, productized version of this could look like for sharing information with others.
Tejas retweeted
We should stop calling it “vibe coding” when it’s software engineers writing production software, paying close attention, thinking a lot, validating before committing, closing the loop… and yes they prompt an agent/work with it.
Very different from “let it rip” w 0 validation
Today was proof that fully polished new products can be built entirely with “vibe coding” tools like Claude Code.
Many people, espp in BigTech, who still don’t believe it:
– you haven’t tried the latest models
– you don’t have the right setup
– codebase is still too large
– your code style is not well-represented in the training data
All 4 of these are entirely self-imposed problems. You will be outrun on product velocity if you aren’t adopting these tools.
Tejas retweeted
I use Claude Code on production codebases enough that I hit the max limits. "Vibe coding" does not describe my work.
A deep understanding of software engineering and computer systems is required to make the calls that keep a complex codebase healthy and keep my company’s engineering org able to maintain our production apps and services.
LLMs get many details right, but it is also the norm for a few things to be wrong or not aligned with how we think about software engineering. It takes an expert eye to spot which 1 out of 10 outputs needs rework, or is simply wrong. A novice who trusts the LLM’s capabilities more than their own judgment will believe all 10.
This is an excerpt from a memo on AI agents I shared with our CRO @joe_d_ryan:
LLMs accept imprecision. You can leave out details of your problem and solution and LLMs will fill in the blanks. They’ll often be wrong, but you will get something working end to end, which is valuable to iterate on. But you need to be able to spot gaps and mistakes in your prompts because the LLM will not reliably identify them.
LLMs create imprecision. You need to be able to spot mistakes in the LLM’s outputs, and the LLM cannot always check its own work. You need to already have a vision for the end state and the direction it lies in, and use the LLM to automate getting there faster.
Experts who understand a problem and are looking to accelerate solving it will be amplified in positive directions, scaling themselves. Novices who trust LLMs will be amplified in negative directions, becoming confident in wrong solutions.
The frontier of what it means to be an expert will change. Experts will need to know how to apply AI and the boundaries of its capabilities. An expert software engineer will need the dexterity to wield a coding agent well. That dexterity will come from experience, intuition, and talent. A senior skill will be getting codebases, teams, and companies to work productively with agents. It has always been a senior skill to set organizations up for success and then achieve it.
Typing source code is mostly dead. We’ll still edit a few lines here and there.
Reading, and more importantly understanding, source code is very much alive. We’ll do more of this as code is written faster.
The art and science of software engineering are blossoming again. This is not a renaissance; software engineering was never dead and is not being reborn. “Vibe coding” is different. It is something new being born. The dominant change, though, is the industry and discipline of software engineering are evolving more than they have since the internet, if not since the beginning.
