@yurekilab-en.bsky.socialCaught my coding agent adding a package for something the standard library already does. New rule in its instructions: name the stdlib option first and say why it falls short. About half the time, the package never gets added. #claudecode #ai #aiengineering #buildinpublic
@qconferences.comShuangfeng is speaking at QCon AI New York, Dec 15-16.
@heyymeraki.bsky.socialIf you have ever wondered what happens when you send a message to an LLM, this goes inside the API call, what you are sending every time, the controls you have over what comes back, and what is inside the response.
@groxio.bsky.socialToday 12pm EDT
Groxio Live with @redrapids.bsky.social
Where does MCP fit in an LLM workflow?
Bruce will demo an LLM harness, show MCP in context, and answer questions live.
Thursday, September 17 at noon ET / 16:00 UTC. Free: grox.io/live
@sayedev.bsky.socialOne thing is becoming increasingly clear:
The model itself is no longer the product.
The system around it, tools, memory, orchestration, and the execution loop are becoming just as important as the model itself.
#AI #AIEngineering #AgenticAI #AI #MachineLearning #AIEngineering #Inference
@yurekilab-en.bsky.socialBuilt a tiny remote panel to check on my AI agent from my phone. Planned for logs, progress bars, token counts. What I actually use: the pending diff and two buttons — approve or reject. Everything else was pretend supervision. #claudecode #ai #aiengineering #buildinpublic
@levelbrook.bsky.socialA deliberate replay of an idempotent API endpoint that wasn't truly idempotent could generate $100M in duplicate charges before detection. #AIEngineering
@qconferences.comDan is speaking at QCon San Francisco, Nov 16-18.
@catchproof.bsky.socialBreakthrough in AI stability tracking 🚨
Barbara Roy released a new mechanism-layer operator to measure AI system drift before it compounds over long inference horizons.
Full paper here: The Stability Envelope™ doi.org/10.5281/zeno...
@jmm86.bsky.socialInfinite retries cost too much: they waste budget. Say goodbye to agents retrying indefinitely with a set limit for efficiency and effectiveness. #AIEngineering #EfficientAutomation
@yurekilab-en.bsky.socialLeft a "TODO: clean up later" comment in my code. My agent found it mid-bugfix and shipped an 80-line refactor I never asked for. Every comment is an instruction now, whether I meant it or not. TODOs get scope and boundaries, or they don't get written. #claudecode #ai #aiengineering
@qconferences.comJoey is speaking at QCon AI New York, Dec 15-16.
@yurekilab-en.bsky.socialI don't let my coding agent fix a bug until it writes a failing test that reproduces it. About a third of the time, that test fails somewhere I didn't expect — the bug wasn't where either of us thought it was. #claudecode #ai #testing #aiengineering
@ilgarz.bsky.socialTurning an AI prototype into something a business can rely on is a different problem entirely.
Only 50 seats available. Registration closes 1 October 2026.
RSVP: meetup.com/azdata-aicommunity/events/316287557
#DataAIDayBaku2026 #AIEngineering #ArtificialIntelligence #RAG
@58bits.comMy take on the frontier labs' public statements about a desired 'slowdown' in frontier model development? They're crack dealers. Don't believe it for a second ;-)
@ipolyzos.comRig brings familiar software engineering ideas to Rust AI: provider abstractions, typed tools, testing, RAG, streaming and local models.
Production AI needs more than prompts. It needs good software engineering.
@qconferences.comPlatform engineering now has another user: the agent.
Mark is speaking at QCon SF, Nov 16-18.
@brwngrldev.bsky.socialI've been digging into engineering metrics in teams that use AI heavily.
One weird finding: a PR with ~50 review comments looked risky until we opened it. Most of the comments came from AI.
I think we're going to need AI-aware engineering metrics, not just AI adoption metrics. 🔬
@qconferences.comHe’ll also cover MIPRO, GEPA, evaluation cost, and safe rollout patterns at QCon AI New York, Dec 15-16.
@heyymeraki.bsky.socialToday we are looking at the build for yesterday's introduction to ai engineering. If you read it and wanted to see what an LLM API call looks like in code, I go step by step so it is easy to follow. Read it here: