A lot of the conversation around AI and coding focuses on whether models will replace software engineers.
What seems to be happening in practice is slightly different.
AI is getting very good at generating code, but the hardest engineering problems were never about typing code in the first place. They’re about:
-system architecture and abstractions
-understanding complex systems
-reasoning about failure modes
-operating systems at scale
-deciding what should actually be automated
If anything, AI tools push engineers to start automating more of their own routine work, which frees time to focus on the harder system-level problems.
In that sense, the role of engineers shifts from “writing code” to designing and governing systems that increasingly include AI components.
Curious how others here see the role evolving as AI coding tools improve.
One challenge many teams are hitting right now is the gap between AI demos and production AI systems.
This AWS case study covers some of the work GoDaddy has been doing to operationalize AI workflows using AWS infrastructure.
One example highlighted is Lighthouse, a system built using Amazon Bedrock to analyze large volumes of customer support interactions and extract patterns that can improve customer experience and operational efficiency.
What’s interesting from a systems perspective isn’t just the model usage, but the broader shift toward treating AI as part of production infrastructure:
data pipelines that continuously feed models
orchestration layers around LLM workflows
recursive learning platforms that allow real-world signals to continuously improve systems
integration into existing operational systems
The biggest challenge for many organizations right now isn’t building models — it’s building reliable systems around them.
Curious how others here are approaching AI infrastructure vs experimentation.
One consistent pattern in production AI work is that model quality is rarely the main bottleneck.
Trust, identity, security, and operational discipline tend to determine whether systems can actually scale beyond pilots—especially as agentic systems become more autonomous.
Curious how others here are thinking about governance and reliability for AI systems operating in real-world environments.
LLMs are increasingly being used as evaluators — grading outputs, ranking options, and even guiding autonomous agents. But raw model scores are unstable: they drift over time, vary across models, and don’t map linearly to real quality.
This write-up explores why LLM-based judging is unreliable out of the box, how calibration curves can improve stability, and why multi-model consensus may be necessary for trustworthy evaluation systems.
Curious how others in the industry are handling calibration, drift mitigation, or cross-model agreement for “LLM-as-a-judge” setups.
GoDaddy just published the Agent Name Service (ANS) API) and an accompanying standards site for defining identity and lifecycle management for autonomous agents.
ANS pairs a human-readable name with cryptographically verifiable identity, using PKI/X.509 and DNS-style discovery. It’s designed to work alongside frameworks like A2A, MCP, and other emerging agent protocols.
What’s new:
Public ANS API is now live (registration, discovery, certificates, revocation, etc.)
ANS Standards site with the current spec + architecture
Open adapter layer for interoperability without framework lock-in
At GoDaddy, our engineering team has been experimenting with how to make AI agents more modular, auditable, and production-ready. Instead of treating agents as monoliths, we designed them around four core tools that separate decision from execution:
* MemoryTool – maintains persistent context and user continuity
* CompletionTool – defines task completion and termination criteria
* UserInteractionTool – handles clarifications, approvals, and feedback loops
* DelegationTool – enables handoffs between agents or humans
This approach makes agent behavior transparent, versionable, and safer to scale. We’ve open-sourced our thinking and early framework notes in a technical write-up here:
Would love to hear feedback from others working on modular or composable agent architectures — especially how you handle agent memory persistence and versioning.
The last few months have proven that autonomous agents are testing the web’s guardrails — from robots.txt to checkout flows — and trust is the casualty.
At GoDaddy, we’re addressing this with the Agent Name Service (ANS) open standard — a framework introducing a digital passport for autonomous agents. By binding each agent’s identity to its exact version of code, ANS creates verifiable trust even in multi-agent chains, reducing the risk of compromised code or “trust rot.”
This is more than a technical milestone — it’s the foundation for secure, scalable agent-to-agent commerce. This post follows our announcement from last month: ANS is now live, and we’re partnering with select companies to roll out implementations in the near future.
ANS provides the PKI-based foundation and governance model enterprises need to trust the shift toward a decentralized, agent-driven internet — acting as the bridge between today’s Web2 enterprise reality and the decentralized agentic future.
Exciting times ahead as we continue shaping the agent economy.
In most ad systems, the logic is simple: highest bid wins. But simple doesn’t mean smart.
At GoDaddy, we asked a harder question: Can we optimize both revenue and user satisfaction—without sacrificing either?
So, we built DeepAd: a deep learning ranking model that blends monetization, behavior, and intent to deliver ads that are both profitable and meaningful.
Core Concepts
• Context-aware ranking: Goes beyond “highest bid wins,” factoring in intent, engagement, and diversity.
• Transfer learning from DeepRank: Leveraging billions of domain-search interactions to give our ad model a head start.
• ReTiRe framework: Balancing Relevance, Time, and Revenue for a truly adaptive signal mix.
• Real behavioral supervision: Learning directly from shopper actions — what they clicked, bought, or skipped.
Why this matters:
• Shoppers see domains that actually fit their intent.
• Registries get fair exposure — niche top-level domain (TLD) can compete on merit, not budget.
• GoDaddy achieves sustainable revenue without degrading user trust.
Key takeaway: Building intelligent ad systems isn’t just about monetization — it’s about aligning incentives between users, advertisers, and platforms through smarter modeling.