
Unhinged! I do not smoke.. building @impakta_io - AI for climate & finance. Part time investor and all that shit..
Aarhus, Denmark
Joined November 2010
- Tweets2K
- Following339
- Followers113
- Likes3.8K
Every SaaS feature ships with a tiny invisible invoice: onboarding, support, edge cases, maintenance. Your roadmap is also a bill. #saas #founderlife
Founder life: your roadmap is a hypothesis, your inbox is a production incident, and somehow the demo is still at 14:00. #founderlife #saas
A supplier’s CO₂e number is only as useful as its receipt: boundary, year, method, source. Without that, it’s a spreadsheet wearing a lab coat. #carbonaccounting #climatetech
Replying to @norbertbodziony
@norbertbodziony awesome work, but I seem to have trouble getting the webhook endpoint.
No matter how I configure I’m not getting the URL I need to create the webhooks.
Agents write the code. Nobody owns the map.
No merge until the agent explains the diff and you can repeat it back.
#aiagents #founderlife
Daniel retweeted
𝗧𝗢𝗣 𝟰 𝗔𝗚𝗘𝗡𝗧𝗜𝗖 𝗔𝗜 𝗗𝗘𝗦𝗜𝗚𝗡 𝗣𝗔𝗧𝗧𝗘𝗥𝗡𝗦 𝗬𝗢𝗨 𝗦𝗛𝗢𝗨𝗟𝗗 𝗞𝗡𝗢𝗪
Building an AI agent isn't just about connecting an LLM to a tool.
The real power comes from choosing the right architecture for the problem.
Here are 4 important agentic AI patterns:
01 — 𝗦𝗘𝗟𝗙-𝗥𝗘𝗙𝗟𝗘𝗖𝗧𝗜𝗢𝗡 𝗣𝗔𝗧𝗧𝗘𝗥𝗡
The AI generates an answer, evaluates its own response, identifies weaknesses, and improves it.
𝗙𝗹𝗼𝘄:
Generate → Evaluate → Reflect → Improve → Final Output
Useful for:
→ Writing
→ Code generation
→ Reasoning tasks
→ Quality improvement
02 — 𝗥𝗘𝗔𝗖𝗧 𝗣𝗔𝗧𝗧𝗘𝗥𝗡
ReAct combines reasoning with action.
The agent:
→ Understands the task
→ Decides what to do
→ Uses a tool or API
→ Observes the result
→ Reasons again
→ Continues until the task is complete
This is useful when an agent needs real-time information or external tools.
03 — 𝗠𝗨𝗟𝗧𝗜-𝗔𝗚𝗘𝗡𝗧 𝗣𝗔𝗧𝗧𝗘𝗥𝗡
Instead of asking one AI to handle everything, multiple specialized agents collaborate.
For example:
→ Research Agent → gathers information
→ Developer Agent → writes code
→ Content Agent → creates content
→ Project Agent → coordinates everything
Each agent has a specific responsibility.
04 — 𝗣𝗟𝗔𝗡𝗡𝗜𝗡𝗚 𝗣𝗔𝗧𝗧𝗘𝗥𝗡
A complex goal is broken into smaller tasks.
𝗚𝗼𝗮𝗹 → 𝗣𝗹𝗮𝗻 → 𝗘𝘅𝗲𝗰𝘂𝘁𝗲 → 𝗘𝘃𝗮𝗹𝘂𝗮𝘁𝗲 → 𝗥𝗲𝗽𝗹𝗮𝗻
If something fails, the agent can adjust the plan and try another approach.
𝗪𝗛𝗜𝗖𝗛 𝗢𝗡𝗘 𝗦𝗛𝗢𝗨𝗟𝗗 𝗬𝗢𝗨 𝗨𝗦𝗘?
𝗦𝗲𝗹𝗳-𝗥𝗲𝗳𝗹𝗲𝗰𝘁𝗶𝗼𝗻
→ When quality and iteration matter
𝗥𝗲𝗔𝗖𝗧
→ When the agent needs tools and real-world feedback
𝗠𝘂𝗹𝘁𝗶-𝗔𝗴𝗲𝗻𝘁
→ When the problem needs specialized roles
𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴
→ When the task involves multiple dependent steps
𝗧𝗛𝗘 𝗕𝗜𝗚 𝗜𝗗𝗘𝗔:
There is no single “best” agent architecture.
The right pattern depends on the task, tools, complexity, reliability requirements, and level of autonomy you need.
𝗖𝗵𝗼𝗼𝘀𝗲 𝘁𝗵𝗲 𝗽𝗮𝘁𝘁𝗲𝗿𝗻 𝗯𝗮𝘀𝗲𝗱 𝗼𝗻 𝘁𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 — 𝗻𝗼𝘁 𝘁𝗵𝗲 𝗵𝘆𝗽𝗲.
Save this for when you’re designing your next AI agent.
Follow @mayaislam_ai for more AI, tools, automation and tech insights.
#AI #AgenticAI #AIAgents #ArtificialIntelligence #AIEngineering #Automation #AITools #Tech
Daniel retweeted
Thanks to everyone who came to my Tour of Agent Protocols talk at #DevoxxMA today! 🙌🇲🇦
Here are the slides and runnable ADK code samples covering the full agent protocol stack:
🔧 MCP for tools & resources
🤝 A2A for agent-to-agent communication
🎨 AG-UI & A2UI for agentic frontends & generative UI
🛒 UCP & AP2 for agentic commerce & payments
Slides: speakerdeck.com/meteatamel/t…
Code samples: github.com/meteatamel/genai-…
#DevoxxMA #AIAgents #GenAI #MCP #A2A #GoogleADK #GoogleCloud
WOW! Look at how much my Cursor/Grok usage has dropped on one of my accounts since the migration to the unified subscription and the introduction of the new @bot limits…
I’m now doing most of my work with @claudeai again!
Who else is seeing a drop in their overall token spend and moving their work back to Claude Code?
#ai #spacex #grok #claude
Daniel retweeted
Agent Protocols — Mental Model Cheat Sheet
Think of agents as needing a few core capabilities:
tools, other agents, users, and commerce (including payments and generative UI).
• MCP (Anthropic) — Tools & Context
Agents → external tools, data, and resources
• A2A (Google) — Agent-to-Agent
Agents → other agents (any framework)
• AG-UI (CopilotKit) — Agent-to-User
Agents → frontend apps (events, state, streaming)
• A2UI (Google) — Generative UI
Agents generate rich interactive UIs (declarative)
• UCP (Google + Shopify) — Commerce
Merchant discovery, capability negotiation, checkout
• AP2 (Google) — Payments
Secure agent-initiated payments (signed mandates)
Simple mental model
• MCP = give the agent hands
• A2A = let agents talk to each other
• AG-UI = connect agent to the screen
• A2UI = let the agent design the screen
• UCP = let the agent shop
• AP2 = let the agent pay safely
They are complementary, not competing.
World of Warcraft doesn't publish a carbon number, so napkin math:
2009: Blizzard ran ~20,000 servers
x 800 W x 24/7 = ~140 GWh a year
x 0.3 kg CO2e/kWh = ~43,000 t CO2e
Before a single player even boots up their PC. Scope 3 is where the dragons live.
#carbonaccounting #gaming
wtf… I just bought a top-up for @bot because I’ve run out of usage and still have 4 days until my limit resets. A single prompt to update my Garmin Connect workout for tomorrow morning cost me about $1 🤯
Am I the only one who thinks this is crazy given how much the plans already cost?
#ai #grok #spacex








