今日已更新 166 条资讯 | 累计 20138 条内容
关于我们

标签:#art

找到 1268 篇相关文章

AI 资讯

Why I Love the Word "Pivot"

One of my favorite words in the startup and product-building world is pivot. For a long time, I thought a failed project meant wasted time. Today, I see it differently. Every project I worked on—even the ones that never gained users or reached the finish line—taught me something I couldn't have learned from books alone. They taught me how to validate ideas, communicate with users, make technical decisions, prioritize features, and, most importantly, when to change direction. I've come to believe that many successful founders didn't succeed because they had the perfect first idea. They succeeded because their previous attempts gave them the experience to recognize a better opportunity. In fact, I think that if many of them had started directly with the project that eventually made them successful, they might have failed. They first needed the lessons, the mistakes, and the discipline that came from building things that didn't work. I'm still on that journey. Some of my own projects didn't succeed the way I had hoped, but I don't consider them failures. They were investments in experience. Every project made me a better builder and helped me better understand what I want to create and how I should create it. One principle that keeps me moving comes from the Quran: «"Indeed, Allah will not change the condition of a people until they change what is within themselves." (Quran 13:11)» And another verse that reminds me to stay patient during difficult times: «"Allah does not burden a soul beyond what it can bear." (Quran 2:286)» If you're building something today and it isn't working, don't be afraid to pivot. Sometimes changing direction isn't giving up—it's applying everything you've learned so far. I'm curious: Have you ever pivoted a project? What did it teach you?

2026-07-10 原文 →
开发者

Google’s Nest Thermostat has hit its best price of the year

If you’re looking for a relatively affordable way to cut down on cooling costs, Google’s Nest Thermostat can help. It’s packed with smart controls and energy-saving features, and right now it’s on sale in white for $79 ($50 off), which is its best price of the year, at Amazon. The smart thermostat is quick to […]

2026-07-10 原文 →
AI 资讯

Insurance Might Be the Most Underrated AI Agent Wedge in YC 2026

AI founders love the glamorous agent stories: coding agents, sales agents, AI doctors, AI lawyers. But if you dig through the YC 2026 batch data, one of the more interesting signals is decidedly unglamorous: insurance . Out of 477 real-ish company records in the current snapshot, 25 match insurance-related keywords — about 5.2% — and 8 companies sit in the Fintech → Insurance subindustry. Not a tidal wave. But it's enough to suggest something worth paying attention to: insurance is quietly becoming one of the better wedges for AI agents that actually ship. The reason is simple. Insurance is wall-to-wall documents, rules, judgment calls, exceptions, approvals, claims, underwriting, and cross-system coordination. In other words: wall-to-wall work that agents can do and humans hate doing. Insurance is not fintech's leftover category Most people file insurance under "slow fintech": aging distribution, legacy systems, long processes, heavy regulation. From an AI builder's perspective, that list of flaws reads more like a list of opportunities. Insurance workflows are highly structured — but not fully structured. Policies, claims files, medical records, photos, repair estimates, payout history, compliance clauses: the inputs are messy and heterogeneous. Yet every step has a crisp objective: is this covered, what documents are missing, how should this risk be priced, can this pass approval. That's not a chatbot problem. It's an agent problem — reading documents, following procedures, calling systems, leaving audit trails, handling exceptions. And precisely because it's complex, insurance is more likely to command real budget than yet another AI writing tool. Agents die without boundaries; insurance comes with them built in The most common failure mode for early agent products: they sound like they can do everything and end up doing nothing well. Insurance workflows hand you boundaries for free: Inventory and asset processes can be automated end to end Medical prior authori

2026-07-09 原文 →
AI 资讯

San Francisco's Gravity Is Back: 366 of 477 YC 2026 Startups Are in One City

If you could pick only one counterintuitive number from the YC 2026 batches, make it this one: out of 477 real-ish company records, 366 list San Francisco as their location — roughly 77%. For comparison: New York City has 24. London 10. Boston 7. Los Angeles 4. Fully remote? 3 companies. Even if you add the 11 tagged "San Francisco + Remote", the conclusion doesn't budge: AI startups aren't spreading across the map. They're re-concentrating in one city. This isn't Bay Area nostalgia. It's industry structure casting a vote. Remote won work. It didn't win startup density. One of the most popular takes of the past few years: software teams can start anywhere, so companies no longer need the Bay Area. That take wasn't entirely wrong — tooling, cloud services, open models, and online fundraising genuinely lowered the barrier to starting a company. But the YC 2026 location data is a reminder that a lower barrier is not the same as a vanished advantage. Building an AI startup isn't just writing code. It runs on model gossip, talent flow, customer pilots, investor feedback, peer pressure, and extremely fast narrative iteration. Much of that works online. But the densest informal information still travels fastest offline. San Francisco's edge was never the office space — it's collision frequency. AI made same-city learning matter again In the classic SaaS era, most domain knowledge came from customers and product cycles were relatively stable. You could build a vertical software company in any city and grind toward PMF at your own pace. The AI era doesn't work like that. Model capabilities turn over every few months. Agent architectures keep getting rewritten. Inference costs, context windows, voice, tool calling, and eval infrastructure are all on rolling release. A seemingly minor technical shift can redraw your product's boundaries overnight. In that environment, whoever hears real feedback earlier, learns earlier what others tripped over, and understands earlier what inv

2026-07-09 原文 →
AI 资讯

What I Learned Building an AI Agent Whose Only Goal Is to Disagree With You

We just opened the waitlist for Something, and the part that surprised me most while building it wasn't the multi-agent orchestration — it was how hard it is to make an AI actually disagree. Every model we tested defaults to being helpful, which in practice means agreeable. Even when explicitly prompted to "find flaws," the outputs would soften into "here are some considerations" instead of a real critique. We had to engineer around this specifically: Separate system prompts with opposing reward framing — one agent optimizes for identifying growth potential, the other is explicitly told its only success metric is surfacing a disqualifying flaw Structured output forcing a verdict, not a summary — the skeptic agent (Nothing) has to commit to a specific weakness category (unit economics, timing, technical feasibility) rather than hedging across all of them A reconciliation step where both outputs get merged into one conviction score, so the founder isn't just reading two contradictory paragraphs If anyone's built adversarial agent setups and hit the same "it just wants to agree with me" problem, curious how you solved it. [Everyone who has a brain is a founder here] something-waitlist.vercel.app

2026-07-09 原文 →