konaraddi

> On Friday, August 1, [2025] President Trump fired Dr. Erika McEntarfer from her role as the Commissioner of the Bureau of Labor Statistics (BLS). In social media posts announcing and confirming her firing, he said that he believed the jobs report released by the agency earlier that day included numbers that were “rigged in order to make the Republicans, and ME, look bad.”

https://www.epi.org/policywatch/firing-bls-commissioner-erik...

Comment · 2 months ago

Does it purge passwords from memory on vault lock?

Comment · 2 months ago

Regardless of one’s political slant, it is clear that Flock is giving experiences and objects of value to public servants with clear intent to retain or obtain their business. I’m not familiar with the legal definition of bribery but Flock’s behavior certainly quacks like bribery.

My current and previous employers have mandatory employee training that covers and curbs this kind of behavior. I suspect, and hope, Flock is going to learn why.

Comment · 2 months ago

I think the more coding agents the better, more ideas mixing and borrowing that’s yielding improvements across actively developed agents and different tradeoffs being made. From the article, Ramp’s Inspect was made with frontend in mind and is particularly good with Ramp internal tooling. Looks like it’s not open source? https://inspect.ramp.engineering/auth/

The blog post doesn’t have much further material or at least not before the paid envelope.

Some thoughts I have -

> 1. Local machines are limited in how many agents they can run. Ramp found third-party products below expectations; they liked Claude Code on day 1, but were constrained by only being able to run one or two sessions on local machines.

I haven’t seen this constraint? I only started using Claude Code ~4 months ago so maybe it was different before.

> 3. Need for remote dev environments. As Ramp scaled, so did the complexity, and with it there was more work at the intersection of systems, like debugging backward compatibility, and broken API contracts. The solution was to create remote dev environments.

This seems disjoint, not sure I follow how remote dev environments was necessary to solve this or why remote dev environments would be the only solution?

> Hooking up Inspect to the data sources that engineers would browse with the same tools seems to be a key difference between Inspect and third-party AI harnesses.

You can do the same with third party AI harnesses, I guess we’d have to see what Inspect does that’s better than providing MCPs, CLIs, scripts, etc. to an agent.

Comment · 2 months ago

Should be titled “Why Ramp built its own in-house coding agent, Inspect” (that’s the title of the post at the time of this comment)

Comment · 2 months ago

This doesn’t seem written for kids though?

Comment · 2 months ago

Great read that brings some rigor (or at least cites rigor) to what has otherwise been anecdotal.

> then what is the path for one to become an expert so they can effectively use these tools?

The article briefly mentions guard rails and I think on the same note we need the AI agents we use for coding to encourage learning and comprehension in its users. Right now it’s completely voluntary and on the onus of engineers to put in the effort to learn since, as the article states, the friction that led to some degree of required learning is gone.