JJ Schultz
2.4K posts


@nosilverv it's to raise one's visibility in order to get a job or find clients
English

One of the biggest lessons thus far in building AI agents is you have to be brutally unsentimental in your architecture.
The models get better and better at handling things you previously built scaffolding for, you need to ruthlessly jettison your prior tech to get those new performance gains.
The rough loop of building AI agents looks something like:
1. Build a bunch of systems around the LLM to ensure that the agent can solve specific tasks very well
2. The model capabilities dramatically improve, rendering many of those systems redundant or even harmful
3. Remove prior scaffolding to get the new performance gains from the agent
4. New capabilities emerge in the models that let you solve a new set of much harder problems
5. Go back to step 1
For instance, in our new Box Agent, from the moment we designed the original architecture to the ultimate release, we had to evolve multiple components of agent harness simply because some parts were creating unnecessary constraints for the agents as models improved.
The models continued to get insanely good at more complex reasoning, improvements in using search and other tools, writing code on the fly for new capabilities, improving context window performance for accuracy, and more.
Many of the mitigations we put in place for the Box Agent (like to appropriately find data that users were looking for, or ways of chunking text to deal with context window limitations), eventually meat we got lower quality results or meant we were overfitting for specific use-cases, as soon as the models got better.
The main lesson is always make sure you’re taking advantage of the frontier capabilities and don’t become nostalgic around the tech you’ve already built.
English

Airport questions…
1. Why would anyone make the decision to take Pappadeaux out of an airport?
2. Are there enough grown folks with $$ collecting Pokémon cards to justify a large vending machine in the airport?
3. Why would a female wear a sports bra with nothing over it in the airport?
4. Why do people put bags or food in seats next to them in crowded waiting areas?
5. Why would a person exhale aggressively into heavy foot traffic?
6. Why have self pay stations with zero room for people to line up or access?
7. Why do people stop to rest in the middle of high traffic areas?
Just curious!!
English

@mattjoans I kind of enjoy outlook email/calendar, but moving aways from Google Docs would be quite a downgrade
English

Software engineers six months ago: "An engineering manager has to be technical. How would they understand what the team is doing if they can’t build software?"
Software engineers today: "Coding is basically solved. Non-technical people can just manage AI agents and build software now."
Which is it?
English

Do engineers who use Claude Code (et. al.) worry about the obsequiousness problem?
When we talked with @heyitsnoah he pointed out that "pair programming" has long been a thing in software development.
But presumably in a pair, one human isn't just there to validate the other.
English



















