Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

AI agents have a memory problem. You create the perfect workflow, debugging process, or project setup... A few days later, you're teaching the same lessons all over again. Most AI workflows disappear the moment the chat ends. That's why EvoMap caught my attention. Instead of letting successful AI workflows... show more

Shruti Codes

108,735 subscribers

34,376 görüntüleme • 3 ay önce •via X (Twitter)

Komedi Eğitim Bilim & Teknoloji

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Over the past few months, what started as NoelClaw evolved into something much bigger- a platform where AI agents can remember, research, build, automate, trade, and interact with real-world systems. Along the way, we listened to the community. One piece of feedback came up over and over again: the original token distribution wasn't the best foundation for long-term growth. Instead of ignoring it, we decided to rebuild it properly. That's why we rebranded to Finch Agentic and relaunched the token with a healthier foundation. Our mission hasn't changed. We're still building a runtime layer for agentic AI. Today, Finch lets you: >> Build websites and apps with AI >> Deploy persistent AI agents >> Use an AI-powered terminal >> Install reusable skills >> Connect real-world APIs >> Swap assets >> Run deep research >> Create multi-agent workflows And we're just getting started. Next up: - Robinhood MCP integrations - AI financial agents - Staking (USDG & stock pairing rewards) - More skills, APIs, and autonomous workflows Models will keep changing. AI will keep evolving. But every autonomous agent still needs somewhere to remember, work, and operate! That's what we're building with Finch. Welcome to the next chapter. CA : 0xce1981b0431fb495912cab057d2877a290199824 Web : App : Docs : NPM : Github :

Over the past few months, what started as NoelClaw evolved into something much bigger- a platform where AI agents can remember, research, build, automate, trade, and interact with real-world systems. Along the way, we listened to the community. One piece of feedback came up over and over again: the original token distribution wasn't the best foundation for long-term growth. Instead of ignoring it, we decided to rebuild it properly. That's why we rebranded to Finch Agentic and relaunched the token with a healthier foundation. Our mission hasn't changed. We're still building a runtime layer for agentic AI. Today, Finch lets you: >> Build websites and apps with AI >> Deploy persistent AI agents >> Use an AI-powered terminal >> Install reusable skills >> Connect real-world APIs >> Swap assets >> Run deep research >> Create multi-agent workflows And we're just getting started. Next up: - Robinhood MCP integrations - AI financial agents - Staking (USDG & stock pairing rewards) - More skills, APIs, and autonomous workflows Models will keep changing. AI will keep evolving. But every autonomous agent still needs somewhere to remember, work, and operate! That's what we're building with Finch. Welcome to the next chapter. CA : 0xce1981b0431fb495912cab057d2877a290199824 Web : App : Docs : NPM : Github :

Finch Agentic

14,959 görüntüleme • 1 ay önce

I've spent 2 months teaching my AI how I work again and again Claude Code knows one thing. Cursor knows another. Codex starts from scratch. OpenClaw has its own memory. None of them remember what the others learned. Memmy brings those histories into one local, user-controlled memory—so you can switch agents without re-explaining your projects, decisions, and preferences. Switch agents without rebuilding your context. Let every AI remember the same you. GitHub: ProductHunt:

I've spent 2 months teaching my AI how I work again and again Claude Code knows one thing. Cursor knows another. Codex starts from scratch. OpenClaw has its own memory. None of them remember what the others learned. Memmy brings those histories into one local, user-controlled memory—so you can switch agents without re-explaining your projects, decisions, and preferences. Switch agents without rebuilding your context. Let every AI remember the same you. GitHub: ProductHunt:

Priyank Ahuja

13,228 görüntüleme • 1 ay önce

MOST AI AGENTS RESET TO ZERO EVERY TIME YOU OPEN A NEW SESSION. Hermes Agent was built to do the opposite. Every task compounds. Every workflow becomes reusable. Every session teaches the next one. That is the core thesis behind Hermes, and it completely changes how AI agents work. Unlike most AI agents built by software tool companies, Hermes was created by the researchers training the Hermes model family itself. Meaning: The same system used internally to generate training data is now open source and available to everyone. One install gives you access to: Claude. GPT. Grok. Local models via Ollama. Telegram, Discord, Slack, iMessage integrations. Custom skills. Persistent memory. CLI control. But the real unlock is the compounding loop: You give Hermes a task. It records every tool call, decision, and result. Then it converts successful workflows into reusable skills automatically. A Hermes setup running for 3 months becomes fundamentally smarter than a fresh install. That’s the big idea. One of the coolest parts: You literally watch the agent evolve in real time from a blank install into a personalized AI operator. Instead of watching Netflix today, spend 28 mins with this. Follow Dami-Defi for more AI systems, agent workflows, and infrastructure alpha.

MOST AI AGENTS RESET TO ZERO EVERY TIME YOU OPEN A NEW SESSION. Hermes Agent was built to do the opposite. Every task compounds. Every workflow becomes reusable. Every session teaches the next one. That is the core thesis behind Hermes, and it completely changes how AI agents work. Unlike most AI agents built by software tool companies, Hermes was created by the researchers training the Hermes model family itself. Meaning: The same system used internally to generate training data is now open source and available to everyone. One install gives you access to: Claude. GPT. Grok. Local models via Ollama. Telegram, Discord, Slack, iMessage integrations. Custom skills. Persistent memory. CLI control. But the real unlock is the compounding loop: You give Hermes a task. It records every tool call, decision, and result. Then it converts successful workflows into reusable skills automatically. A Hermes setup running for 3 months becomes fundamentally smarter than a fresh install. That’s the big idea. One of the coolest parts: You literally watch the agent evolve in real time from a blank install into a personalized AI operator. Instead of watching Netflix today, spend 28 mins with this. Follow Dami-Defi for more AI systems, agent workflows, and infrastructure alpha.

Dami-Defi

11,685 görüntüleme • 3 ay önce

🚨 Building AI agents is fun. Setting them up usually isn't. I expected to spend my afternoon configuring APIs, databases, deployments, and integrations. Instead, I spent it building the agent. That's what stood out after trying It removes a lot of the infrastructure work so you can focus on the workflow you're trying to automate. Definitely worth trying if you're exploring AI agents. Try Matagi free — no card needed.

🚨 Building AI agents is fun. Setting them up usually isn't. I expected to spend my afternoon configuring APIs, databases, deployments, and integrations. Instead, I spent it building the agent. That's what stood out after trying It removes a lot of the infrastructure work so you can focus on the workflow you're trying to automate. Definitely worth trying if you're exploring AI agents. Try Matagi free — no card needed.

Amy - AI Girl

37,973 görüntüleme • 1 ay önce

Your AI agents are giving you generic outputs because they have zero context... I just built a RAG workflow that ingests your data and creates a searchable database that your AI can reference. Now your workflows will give precise, contextual responses instead of generic slop. Follow + comment "RAG" and I'll send you the complete n8n workflow.

Your AI agents are giving you generic outputs because they have zero context... I just built a RAG workflow that ingests your data and creates a searchable database that your AI can reference. Now your workflows will give precise, contextual responses instead of generic slop. Follow + comment "RAG" and I'll send you the complete n8n workflow.

Tom

51,515 görüntüleme • 1 yıl önce

Don’t DIY your AI: building a custom Agentforce agent is as simple as describing the job and integrating it directly into your workflow—no separate models, hyperscalers, databases, or AI engineers needed! With all apps, data, AI, and workflows seamlessly integrated on the Salesforce Platform, humans + agents = customer success. This is what AI was meant to be! #DF24

Don’t DIY your AI: building a custom Agentforce agent is as simple as describing the job and integrating it directly into your workflow—no separate models, hyperscalers, databases, or AI engineers needed! With all apps, data, AI, and workflows seamlessly integrated on the Salesforce Platform, humans + agents = customer success. This is what AI was meant to be! #DF24

Marc Benioff

44,730 görüntüleme • 2 yıl önce

The highest leverage thing you have to optimize for AI agents is their context. If you’re not getting enough out of AI agents, you probably have a context problem. By default the AI model knows absolutely nothing relevant to perform the task successfully. The whole job of context engineering is to prioritize what the model has as information to work with. Small deviations in the goals, instructions, domain understanding, or underlying data you supply the model will lead to wildly different outcomes. This is where you should spend almost all your time and energy in a workflow. We will start to religiously document more of our workflows and business processes, create clearer goals for people and agents, and ensure our tech infra is setup to get AI agents the right information. The lessons are currently being learned the fastest with coding agents, but the same lessons will apply to every field of knowledge work going forward. dex has a great talk on this that’s absolutely worth your time to watch.

The highest leverage thing you have to optimize for AI agents is their context. If you’re not getting enough out of AI agents, you probably have a context problem. By default the AI model knows absolutely nothing relevant to perform the task successfully. The whole job of context engineering is to prioritize what the model has as information to work with. Small deviations in the goals, instructions, domain understanding, or underlying data you supply the model will lead to wildly different outcomes. This is where you should spend almost all your time and energy in a workflow. We will start to religiously document more of our workflows and business processes, create clearer goals for people and agents, and ensure our tech infra is setup to get AI agents the right information. The lessons are currently being learned the fastest with coding agents, but the same lessons will apply to every field of knowledge work going forward. dex has a great talk on this that’s absolutely worth your time to watch.

Aaron Levie

87,086 görüntüleme • 1 yıl önce

anthropic research lead: “99% of our engineers use 300+ AI agents working together.” “close the loop. let the AI check its own work.” in a 20-minute talk, an Anthropic team member explains how to build AI agents that can improve themselves. the setup uses Claude with loops, plan mode, and smart workflows. it’s better than most $300 AI agent courses. bookmark this and watch the talk. then read the article below.

anthropic research lead: “99% of our engineers use 300+ AI agents working together.” “close the loop. let the AI check its own work.” in a 20-minute talk, an Anthropic team member explains how to build AI agents that can improve themselves. the setup uses Claude with loops, plan mode, and smart workflows. it’s better than most $300 AI agent courses. bookmark this and watch the talk. then read the article below.

MIKE

34,813 görüntüleme • 2 ay önce

Google’s new Agent2Agent protocol is a key step toward a future of AI Agent interoperability. No single tool has all the data a user or business needs for most workflows, so we need Agents to be able to talk to each other. Salesforce will have AI Agents that understand the inner workings of CRM, Workday will have AI Agents that understand HR workflows, Box has AI Agents that understand content and documents, and so on. It’s easy to conceive of a world where we have tens of thousands of these tool Agents and then billions or trillions of customized Agents that are extensions of those. So openness becomes key. Workflows need data from multiple systems to complete the task — like a sales report that needs documents and CRM data or an HR task that needs HR policies and employee details — and that’s where A2A comes in. This protocol gives AI Agent providers a way of talking to each other and simplifying the way that Agents communicate, understand each other’s capabilities, and so on. It’s great to see more interoperability, along with MCP, emerging in the AI space right now, as this will define the future of most IT stacks.

Google’s new Agent2Agent protocol is a key step toward a future of AI Agent interoperability. No single tool has all the data a user or business needs for most workflows, so we need Agents to be able to talk to each other. Salesforce will have AI Agents that understand the inner workings of CRM, Workday will have AI Agents that understand HR workflows, Box has AI Agents that understand content and documents, and so on. It’s easy to conceive of a world where we have tens of thousands of these tool Agents and then billions or trillions of customized Agents that are extensions of those. So openness becomes key. Workflows need data from multiple systems to complete the task — like a sales report that needs documents and CRM data or an HR task that needs HR policies and employee details — and that’s where A2A comes in. This protocol gives AI Agent providers a way of talking to each other and simplifying the way that Agents communicate, understand each other’s capabilities, and so on. It’s great to see more interoperability, along with MCP, emerging in the AI space right now, as this will define the future of most IT stacks.

Aaron Levie

139,591 görüntüleme • 1 yıl önce

Why have one AI agent handle everything when you can build a team? 🤝 Multi-agent architecture allows a main agent to spin up specialized sub-agents and handle complex tasks in parallel - making workflows faster and more efficient inside Google AI Studio. Check out the full I/O session: 🧵👇

Why have one AI agent handle everything when you can build a team? 🤝 Multi-agent architecture allows a main agent to spin up specialized sub-agents and handle complex tasks in parallel - making workflows faster and more efficient inside Google AI Studio. Check out the full I/O session: 🧵👇

Google for Developers

12,456 görüntüleme • 3 ay önce

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access

Ronin

15,071 görüntüleme • 27 gün önce

How do AI agents actually take action? First, they have to see. Cognitive scientist Dr. Danielle Perszyk and AI researcher Matthew Elkherj dive into one of the most underestimated challenges in building AI agents: perception. Episode 3 of Making a Mind explores how agents learn to interpret the web—and why it matters. 🎧

How do AI agents actually take action? First, they have to see. Cognitive scientist Dr. Danielle Perszyk and AI researcher Matthew Elkherj dive into one of the most underestimated challenges in building AI agents: perception. Episode 3 of Making a Mind explores how agents learn to interpret the web—and why it matters. 🎧

Amazon News

25,217 görüntüleme • 7 ay önce

Welcome to the group chat, but it's all my AI agents. To build a website and plan the social content, I put together a team of AI agents. Each one had a different role. They collaborated, challenged each other's ideas, and reviewed each other's work before anything was finalized. Meet Bloome - a platform where humans and AI agents work together in the same conversation. You can bring different models into one workspace, assign them different jobs, and let them cross-check each other's thinking instead of relying on a single answer. It feels less like chatting with AI and more like managing your own creative team. Try it:

Welcome to the group chat, but it's all my AI agents. To build a website and plan the social content, I put together a team of AI agents. Each one had a different role. They collaborated, challenged each other's ideas, and reviewed each other's work before anything was finalized. Meet Bloome - a platform where humans and AI agents work together in the same conversation. You can bring different models into one workspace, assign them different jobs, and let them cross-check each other's thinking instead of relying on a single answer. It feels less like chatting with AI and more like managing your own creative team. Try it:

Gizem Akdag

99,348 görüntüleme • 2 ay önce

It is now way easier to build multi-agent workflows in n8n with the new AI Agent Tool node. Instead of juggling sub workflows a parent AI Agent can now use other Agents as tools even several layers deep. Max shows how a cheap GPT 4.1 nano Agent handles heavy data and sends summaries to a parent Agent saving token costs and making debugging simpler. Watch the full walkthrough:

It is now way easier to build multi-agent workflows in n8n with the new AI Agent Tool node. Instead of juggling sub workflows a parent AI Agent can now use other Agents as tools even several layers deep. Max shows how a cheap GPT 4.1 nano Agent handles heavy data and sends summaries to a parent Agent saving token costs and making debugging simpler. Watch the full walkthrough:

n8n.io

27,808 görüntüleme • 1 yıl önce

Found a setup that replaces a team of researchers with 300 AI agents and one shared graph. the interesting part is what happens after all 300 come back with different pieces of the answer. because now you don’t have 300 agents. you have: 300 outputs → hundreds of sources → repeated entities → overlapping claims → contradictions → thousands of possible relationships and all of that has to collapse into one structure. that’s what the context graph is doing. instead of: agent → report you get: agents → sources → entities → edges → contradictions → verification → one graph every source becomes a node. every shared entity creates a connection. 300 agents can create information. the graph is what turns that information into memory the next agent can actually use. that’s the anatomy behind the setup ↓

Found a setup that replaces a team of researchers with 300 AI agents and one shared graph. the interesting part is what happens after all 300 come back with different pieces of the answer. because now you don’t have 300 agents. you have: 300 outputs → hundreds of sources → repeated entities → overlapping claims → contradictions → thousands of possible relationships and all of that has to collapse into one structure. that’s what the context graph is doing. instead of: agent → report you get: agents → sources → entities → edges → contradictions → verification → one graph every source becomes a node. every shared entity creates a connection. 300 agents can create information. the graph is what turns that information into memory the next agent can actually use. that’s the anatomy behind the setup ↓

Ricker

19,319 görüntüleme • 4 gün önce

We just built A1Mail - email for AI agents. Turns out the problem wasn't making AI smarter, it was making them communicate like humans. Your executive assistant AI can now have its own inbox and respond like a team member. The early use cases from developers are pretty wild. Sometimes the most transformative tech solves the most mundane problems everyone assumes someone else will handle. Check out A1Zap today!

We just built A1Mail - email for AI agents. Turns out the problem wasn't making AI smarter, it was making them communicate like humans. Your executive assistant AI can now have its own inbox and respond like a team member. The early use cases from developers are pretty wild. Sometimes the most transformative tech solves the most mundane problems everyone assumes someone else will handle. Check out A1Zap today!

Pasha Rayan

24,426 görüntüleme • 1 yıl önce

I create a lot of video content. Over the past few years, that work has helped me grow to 200K+ followers and 70M+ views across platforms. Lately, I’ve been experimenting with AI tools that make the process more efficient, without losing my voice, personality, or taste. From researching and writing scripts to editing videos and crafting captions, I’m sharing a few of my favorite workflows, including how I use tools like Hyperagent. I’d love to hear which tools or workflows have made the biggest difference in your own creative process. Try it out:

I create a lot of video content. Over the past few years, that work has helped me grow to 200K+ followers and 70M+ views across platforms. Lately, I’ve been experimenting with AI tools that make the process more efficient, without losing my voice, personality, or taste. From researching and writing scripts to editing videos and crafting captions, I’m sharing a few of my favorite workflows, including how I use tools like Hyperagent. I’d love to hear which tools or workflows have made the biggest difference in your own creative process. Try it out:

Sarah Chieng

292,915 görüntüleme • 1 ay önce

You need to try Hermes RIGHT NOW. OpenClaw was the breakthrough. Hermes feels like the evolution. Here’s why AI power users are quietly switching: • Hermes learns from you over time • It creates its own reusable skills • Memory stays curated instead of bloated • Agents improve every 10 turns automatically • It actually feels stable on day 30 The wildest part: Hermes agents build workflows from your behavior. One user asked their agent to configure Twingate once. The agent: → learned the process → created a reusable skill → stored it for future tasks → improved its own workflow automatically That’s not prompt engineering anymore. That’s agent evolution. Meanwhile most people are still babysitting broken OpenClaw setups and manually importing marketplace skills. Hermes took a different path: Less clutter. Less tweaking. More autonomy. And it’s working. It already flipped OpenClaw in OpenRouter token usage and became one of the fastest-growing AI repos on GitHub. The bigger shift: We’re entering the era where the model matters less than the harness around it. GPT-5.5, Grok, Qwen: They’re already powerful enough. The real edge now is: • memory systems • self-improvement loops • skill creation • agent orchestration Hermes understands that. Most people still think AI agents are glorified chatbots. The people using Hermes are building AI teammates.

You need to try Hermes RIGHT NOW. OpenClaw was the breakthrough. Hermes feels like the evolution. Here’s why AI power users are quietly switching: • Hermes learns from you over time • It creates its own reusable skills • Memory stays curated instead of bloated • Agents improve every 10 turns automatically • It actually feels stable on day 30 The wildest part: Hermes agents build workflows from your behavior. One user asked their agent to configure Twingate once. The agent: → learned the process → created a reusable skill → stored it for future tasks → improved its own workflow automatically That’s not prompt engineering anymore. That’s agent evolution. Meanwhile most people are still babysitting broken OpenClaw setups and manually importing marketplace skills. Hermes took a different path: Less clutter. Less tweaking. More autonomy. And it’s working. It already flipped OpenClaw in OpenRouter token usage and became one of the fastest-growing AI repos on GitHub. The bigger shift: We’re entering the era where the model matters less than the harness around it. GPT-5.5, Grok, Qwen: They’re already powerful enough. The real edge now is: • memory systems • self-improvement loops • skill creation • agent orchestration Hermes understands that. Most people still think AI agents are glorified chatbots. The people using Hermes are building AI teammates.

Dami-Defi

17,062 görüntüleme • 3 ay önce

A significant amount of your company's value is sitting inside your enterprise content. Financial documents, contracts, marketing assets, etc. This is the context needed to let you finally tap into the value of AI agents at scale. Aaron Levie shared with Jeetu Patel at the Cisco AI Summit how deploying agents can automate workflows, create revenue opportunities, and unlock new areas of value.

A significant amount of your company's value is sitting inside your enterprise content. Financial documents, contracts, marketing assets, etc. This is the context needed to let you finally tap into the value of AI agents at scale. Aaron Levie shared with Jeetu Patel at the Cisco AI Summit how deploying agents can automate workflows, create revenue opportunities, and unlock new areas of value.

Box

300,474 görüntüleme • 7 ay önce

🚨 THIS IS ACTUALLY INSANE Your AI agent can have access to the web. But if it can't reliably read what’s actually on the page, that access is almost useless. We looked at Firecrawl as the web layer for AI agents and the numbers are hard to ignore. The setup is simple: Give it a URL, search query, or website. Firecrawl handles the ugly part — crawling, scraping, rendering, extracting, and turning web content into something an AI model can actually use. The headline numbers: → 173,000+ GitHub stars → Search, scrape and interact with the web at scale → Supports web pages, PDFs, DOCX and other content → Structured data extraction for AI workflows → MCP support for connecting it directly to AI agents The workflow looks like this: Search → Scrape → Crawl → Extract → Feed the agent Three things stand out: 1. Scraping becomes an infrastructure layer Instead of maintaining your own pile of HTTP clients, parsers, browser automation and retry logic, you can treat web access as an API. 2. Agents get more than raw HTML The goal isn't just downloading a webpage. It's turning messy web content into clean context that an LLM can reason over. 3. The same layer works across different agent workflows Research agents. RAG pipelines. AI search. Competitive intelligence. Web-data extraction. The interesting shift: AI agents don't just need better models. They need better access to the information those models are supposed to reason about. Firecrawl is building that layer. Save this repo.

🚨 THIS IS ACTUALLY INSANE Your AI agent can have access to the web. But if it can't reliably read what’s actually on the page, that access is almost useless. We looked at Firecrawl as the web layer for AI agents and the numbers are hard to ignore. The setup is simple: Give it a URL, search query, or website. Firecrawl handles the ugly part — crawling, scraping, rendering, extracting, and turning web content into something an AI model can actually use. The headline numbers: → 173,000+ GitHub stars → Search, scrape and interact with the web at scale → Supports web pages, PDFs, DOCX and other content → Structured data extraction for AI workflows → MCP support for connecting it directly to AI agents The workflow looks like this: Search → Scrape → Crawl → Extract → Feed the agent Three things stand out: 1. Scraping becomes an infrastructure layer Instead of maintaining your own pile of HTTP clients, parsers, browser automation and retry logic, you can treat web access as an API. 2. Agents get more than raw HTML The goal isn't just downloading a webpage. It's turning messy web content into clean context that an LLM can reason over. 3. The same layer works across different agent workflows Research agents. RAG pipelines. AI search. Competitive intelligence. Web-data extraction. The interesting shift: AI agents don't just need better models. They need better access to the information those models are supposed to reason about. Firecrawl is building that layer. Save this repo.

Vikas gupta

18,053 görüntüleme • 3 gün önce