Pulkit Goyal

I build things and write stuff

[Pulkit Goyal @pulkit110]

@Kappaemme1926 Medium is almost always enough.

High only for planning. Once a good plan is ready, even low or 5.4/5.3 can do most of the mechanical work as well as 5.5.

Xhigh only for deep research that 99% never need. Always on xhigh is a good way to burn all credits in a single prompt

[Pulkit Goyal @pulkit110]

For small teams, the best infra setup is not the most automated one.

It is the one where failure modes are understood.

A manually recoverable app server is fine.
An unprotected database is not.
A missing Redis failover plan will hurt.
A missing alert will hurt more.

[Pulkit Goyal @pulkit110]

The next big leap in AI coding tools may not be model quality.

It may be UX.

Fast switching between code, terminal, agent threads, review state, and running sessions matters a lot when agents become part of daily development.

[Pulkit Goyal @pulkit110]

A growing production error needs two decisions.
First:
stop the damage.
Second:
fix the cause.
Those are not always the same task.
A queue pause, feature flag, or cleanup job can be the right first move while the real code fix is still being designed.
Incident work has phases.

[Pulkit Goyal @pulkit110]

Bundler finally has cooldown: https://t.co/IFsarDLpvQ

A small delay before new gem versions resolve closes one of the riskiest windows in supply-chain attacks: the first few hours after a malicious package is published.

Huge win for Ruby apps.

[Pulkit Goyal @pulkit110]

Looking for recommendations for AI code review tools that integrate with GitHub PRs.

I already use Codex/OpenCode locally, but looking for an automated reviewer that comments on PRs and actually does a good job.

Mostly Rails, Elixir, PostgreSQL.

What’s worth paying for?

[Pulkit Goyal @pulkit110]

The best infra decisions I’ve made were not “cloud vs self-hosted.”

They were boundary decisions.

Managed Postgres.
Self-hosted app servers.
Self-hosted Redis where data loss is tolerable.
S3 for durable objects.
Grafana for visibility.

[Pulkit Goyal @pulkit110]

We keep hardening production, then install random editor plugins, package CLIs, and global tools on the machines that can deploy production.

That gap is going to matter more as developer-targeted attacks become more common.

[Pulkit Goyal @pulkit110]

AI coding cost is not just token cost.

It is:

Review cost.
Misfire cost.
Context setup cost.
Tooling friction.
Wrong-abstraction cleanup.

The best agent workflow is the one that minimizes total engineering cost, not just model spend.

[Pulkit Goyal @pulkit110]

Supply-chain security used to feel like “protect production dependencies.”

Now it also means:

Protect editor extensions.
Protect CI caches.
Protect package publish flows.
Protect developer laptops.

The developer environment is becoming part of the production attack surface.

[Pulkit Goyal @pulkit110]

@siddharthkp Join group classes like Cult. Or if you can handle at-home training, I find BeachBody is amazing and has content for every level that is also fun to follow along. I’ve been constantly using it for multiple years.

[Malay Krishna @Malay4Product]

This is an unbelievable piece of work by Sarthak and something that requires amplification.

Let me explain what he found, in simple terms.

Sarthak is a Class 12 student from the 2025-26 batch, one of the 17 lakh students whose answer sheets went through CBSE's new On-Screen Marking system.

He spent days reading through CBSE's evaluation tenders, scraped all 576 tenders CBSE has issued, and tracked how the rules changed across three versions of the same tender.

The core finding is that the company that won the contract to scan and grade 17 lakh students' answer sheets is Coempt Eduteck.

Coempt used to be called Globarena Technologies. Globarena was the company behind the 2019 Telangana intermediate exam disaster, where software failures led to 3.8 lakh students getting wrong or missing marks, and 23 students died by suicide.

A government committee found systemic failure and negligence. Six months later, Globarena rebranded to Coempt Eduteck.

So a company with that track record won a contract to handle 17 lakh CBSE students. Sarthak's investigation is about how the rules were rewritten to let that happen.

The tender was issued three times.

> First tender, February 2025. It existed, then disappeared from the public GeM portal. Sarthak scraped all 576 CBSE tenders and this one was missing from the archive entirely.

> Second tender, May 2025. Four companies applied including TCS and Coempt. All four failed the technical evaluation. Cancelled.

> Third tender, August 2025. Coempt won. Between the second and third tender, a series of rule changes happened, and every single one made it easier for Coempt to qualify.

Here is what changed, one by one.

01. The old rules disqualified any company with a history of abandoning work, failing to complete contracts, or financial weakness. The new rules deleted this clause entirely. Coempt's Telangana history stopped being a barrier.

02. The old rules disqualified any company that was "blacklisted earlier." The new rules changed this to "currently blacklisted." Because Globarena rebranded after Telangana, removing the word "earlier" effectively erased their past.

03. The rules required Rs 50 crore average turnover over three years. Coempt's exact average came to Rs 50.86 crore. They cleared the bar by less than 1%. Earlier, a smaller company had asked CBSE to lower the bar to Rs 30 crore for fairer competition. CBSE refused. So the bar was kept high enough to block small players, but sat exactly low enough for Coempt to scrape through.

04. Software maturity is measured on the CMMI scale, 1 to 5. The old rules required Level 5. The new rules dropped it to Level 3. Coempt is a Level 3 company.

05. The cooling-off period for engaging retired CBSE officials was cut from two years to one. This makes it easier to use recently retired insiders to influence the process.

06. The old rules required experience with large projects of at least 5 lakh students each. The new rules removed the student count and counted cumulative answer-book volume across small projects instead. Coempt has many small fragmented university contracts. This helped Coempt and hurt TCS.

07. The old rules required bidders to own their own data centre and disaster recovery centre on Indian soil. The new rules allowed third-party MeitY-empanelled cloud hosting. Coempt runs on AWS and Azure. This helped Coempt and hurt TCS, which owns its own data centres. It also means student data is no longer on sovereign, Indian infrastructure.

08. The old rules required the bidder to own or control the complete source code of its software. The new rules deleted this. Coempt's platform runs on Microsoft's proprietary IIS, which they don't own.

09. A last-minute corrigendum, issued right before bid submission, removed CBSE's own power to blacklist the firm if its software failed catastrophically. So even a Telangana-scale failure couldn't get Coempt banned from future government tenders.

10. The penalty structure shifted from punishing mistakes to punishing delays. The old rules fined the vendor for wrong scanning, merged pages, and unscanned books. The new rules dropped those and instead levied Rs 50,000 per day for delays. This incentivises rushed scanning over accurate scanning.

11. The old rules had a hard accuracy threshold, error rate not to exceed 0.5%. The new rules removed this number entirely.

12. The old rules specified proper book and robotics scanners. The new rules just say "sufficient scanners." The definition was vague enough that, as Sarthak notes, the scanning could be done with a phone on a stand.

13. On the security side, the contract required a VAPT (vulnerability and penetration test) certified by CERT-In before go-live, and a restricted beta phase before launch. The system clearly wasn't restricted, because the other researcher, Nisarga, was able to access it and find vulnerabilities four days before go-live. So the mandatory security audit appears to have been bypassed.

These are more than a dozen rule changes, all between the failed tender and the winning tender, all pushing in the same direction, all benefiting the one company with the worst track record in the field.

The security holes Nisarga found last week now have an explanation. The system was built by a vendor that was specifically allowed to skip the security certification, the source code ownership, the data sovereignty, and the quality thresholds the original rules demanded.

Following things need to happen immediately;

1. An immediate CAG audit of the tender process.
2. A parliamentary debate on the topic.
3. An independent investigation into
> Why the first tender vanished?
> Why the disqualification clauses were deleted?
> Why the turnover bar was held exactly where it was?
> Why the security level was dropped?
> Why the blacklisting power was removed at the last moment?

Sarthak, this is genuinely exceptional investigative work. Far better than most journalists with full resources ever manage. Take a bow. :)

[Pulkit Goyal @pulkit110]

Two AI companies.

One optimizes for using more tokens.
The other optimizes for needing fewer.

[Tyler @rezoundous]

Opus 4.8 is insane guys. It one shotted my session usage limit.

[Pulkit Goyal @pulkit110]

Security automation fails twice when it goes red for the wrong reason: first by missing the signal, then by training the team not to look.

[Pulkit Goyal @pulkit110]

@bcardarella I use it with GPT-5.5 and it works great. Tried codex, but couldn’t really get used to it 🤷🏽‍♂️

[Pulkit Goyal @pulkit110]

@zeddotdev @shivamhwp That’s not to say that Zed isn’t working. It’s awesome and my current workflow is to simply use a center terminal with my agent (opencode). Works perfectly except that I need to track which projects have terminals open because the agents sidebar doesn’t show them.

[Pulkit Goyal @pulkit110]

@zeddotdev @shivamhwp I tried them out recently but couldn’t get into it. We can only pin it to either the dock or the center panel as a Split View. I like to have my terminal full screen as a tab easily switchable with other editor tabs.

[Pulkit Goyal @pulkit110]

Supply-chain hardening is mostly removing secrets from boring places. OIDC and trusted publishing are not shiny; they are one less credential for a compromised workflow to steal.

[anmol maini @anmolm_]

jesus fucking christ - basically any marks for the Class 12 CBSE board exams could be edited by anyone???

[José Valim @josevalim]

When someone replies to a pull request comment with obvious AI content, it genuinely saddens me. PRs used to be a place to teach/learn/discuss software but now there’s nobody on the other side.

If I wanted an agent response, I’d ask mine.

Social coding is dead.