
Each new CVE is the dinner bell for bad actors all over the world. If they don't act on it immediately, they might not get dinner.

Husband, father, volunteer, athlete, continuous learner. Tweets are mine. Spring Developer Advocate @VMwareTanzu #JUICE #LiftAsWeClimb @Testcontainers Champion

Each new CVE is the dinner bell for bad actors all over the world. If they don't act on it immediately, they might not get dinner.


Bellsoft Liberica has the fixes! Patch all the things! bell-sw.com/blog/liberica-jd…

178 orgs just served malware from a script they trusted (Optimizely). A script allowlist wouldn’t have saved them. Limit where your page can send data instead. Spring Security: csp.policyDirectives("connect-src 'self'; form-action 'self'").reportOnly() Start in report-only. Then enforce.

@dashaun shared a research paper to read. "SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via Continuous Integration" A very nice read but will have to re-read it to understand it 😀 arxiv.org/html/2603.03823v4#…


#SpringOfficeHours @corbypage runs his agent on an on-prem model. I'm not made of money, so no frontier cloud model. Gemma 4, free tokens. With @starbuxman #Spring #AI #Java




Give an agent a specific purpose and only the tools it needs. Focused agents make the deterministic path finer grained and easier to diagnose. With @corbypage & @starbuxman #Spring #AI #Agent


One portable configuration: define what your agent does, then swap the agent runtime as an implementation detail. With @corbypage and @starbuxman #SpringAI #Java #SpringOfficeHours

ACP is the Agent Client Protocol. It lets you plug any agent runtime (Goose, OpenCode, Codex) into your IDE and go. @corbypage explains to @starbuxman. #SpringAI #Agent #Java #SpringOfficeHours

The "whiteboard defense:" I should be able to pull you aside at any moment and ask you to explain any customer-facing system you've shipped. You should be able to clearly explain how it works and defend the decisions you made. This is my benchmark for responsible AI usage. I don't expect line-level familiarity with the code. I don't care if you remember the exact function name or implementation detail. You may not even know it. I don't care. But if I ask "why did you do X instead of Y?", "what happens if this actor behaves maliciously?", "what data structure did you use here and why?", or "where does this fail?" you should be able to answer confidently. For PoCs, demos, experiments, whatever: I don't care. Generate 100% of it and understand none of it. Speed over quality every time in those specific scenarios. But if you're shipping customer-facing work, you can't be shipping things you don't understand at a high level.
