标签：#AR

Hi, What are the things that surprised you that AI cannot do? Would you please also mention what is your work, since i assume most of this thread are coders etc? Ill start here. I work in corporate finance. Doing tons of stuff left and right. AI cannot do finance or accounting..... almost at all. Hundreds of billions on the line, every CEO and their mother pushing AI and nothing major happened. Sure, if you are just a link in chain where you receive the same excel sheet and produce the same powerpoint you are replacable but there are very few people like that anymore left in finance corps. However, if you just receive accounting memo written by random people AI is useless, if you receive bunch of random files and have to come up with valuation AI is useles, if you need to migrate product to a new system AI is useless........... so on and so forth. Hope i dont start a war where everybody is gonna be mad at this. submitted by /u/Zoltan1251 [link] [留言]

The pale-blue Ojai vehicles will start picking up members of the public in California and Arizona today.

After several months of testing, Waymo is finally ready to invite non-employee passengers into its newest vehicle, the Zeekr RT minivan, which has been rebranded as Ojai. Waymo says it will begin offering "select riders" access in San Francisco, Los Angeles, and Phoenix, before "gradually" expanding to more riders and cities. Trips will be free […]

submitted by /u/Shadowys [link] [留言]

submitted by /u/Snapdragon_4U [link] [留言]

A new crop of AI labs are focused on recursive self-improvement — but the goal is proving elusive.

Enterprise AI is entering a different phase now, one where enterprises are no longer evaluating whether AI is exciting. They are evaluating whether it is safe to deploy broadly.

Hey everyone, I just sent issue #34 of the AI Hacker Newsletter , a weekly roundup of the best AI links and the discussions around them. Here are some of title you can find in the issue: Using AI to write better code more slowly I think Anthropic and OpenAI have found product-market fit Can we have the day off? Google’s AI is being manipulated. The search giant is quietly fighting back Intuit to lay off over 3k employees to refocus on AI If you want to receive a weekly email with over 30 links like these, please join here: https://hackernewsai.com/ submitted by /u/alexeestec [link] [留言]

Spent the last few months building a deeper context layer over arxiv. Each paper gets a Tomesphere page with a TLDR + key findings (LLM-curated), OpenReview reviews where the venue is public, linked GitHub repos, HuggingFace models, conference videos, the citation graph in both directions, and a SPECTER2-based semantic neighbor graph. Same panel renders inline on arxiv via a Chrome extension (MV3 side panel API), or you can browse directly at tomesphere.com. 3M arxiv papers indexed. Caveats: reviewer scores only cover venues that publish openly on OpenReview (NeurIPS, ICLR, ICML, TMLR, COLM). Blind-review venues like CVPR, AAAI, ECCV are out of scope until contributors fill them in. GitHub, Hugging Face, and conference video matches are best-effort. Free, no signup. Site: tomesphere.com Chrome: chromewebstore.google.com/detail/tomesphere/nopoigoclhjcopjppnehidnkljmabllk Would love feedback, especially: which paper did you check first, and what's missing that you'd actually use? submitted by /u/RegretAgreeable4859 [link] [留言]

After overwhelming demand from founders around the world, TechCrunch has extended the Startup Battlefield 200 application deadline to June 8. Nominate a standout startup or apply yours today.

Savings of up to $410 on TechCrunch Disrupt 2026 tickets end tomorrow, May 29, 11:59 p.m. PT. Register now to save and join 10,000+ tech leaders on October 13-15 in San Francisco.

Today, I’m talking with Wassym Bensaid, the chief software officer at Rivian, and the co-CEO of Rivian’s platform joint venture with Volkswagen, which everyone just calls RV Tech. That joint venture kicked off about a year and a half ago with a nearly $6 billion investment from Volkswagen. It effectively puts Wassym in charge of […]

Primeira pergunta, quem vai pagar por essa porcaria? Cara, a parte mais inacreditável dessa história toda da Meta não é nem cobrarem assinatura. É cobrarem assinatura numa IA que ninguém genuinamente quer usar como principal. Tipo, vamos ser honestos: quem acorda e pensa “caralho deixa eu abrir o Meta AI pra resolver isso aqui”? Ninguém. O bagulho sempre teve vibe de feature enfiada no Instagram igual aquelas abas aleatórias que aparecem do nada depois de atualização. E mesmo assim os caras meteram: “agora o Thinking vai ser limitado 😃” “quer mais raciocínio? 20 dólares 😃” MAS QUEM TÁ PEDINDO ISSO IRMÃO??? Esse é o ponto que faz essa notícia parecer meme. Se pelo menos fosse: - uma IA absurda em código - monstruosa em escrita criativa - insana em vídeo - referência em imagem - ou um modelo amado pela comunidade Mas não. As imagens deles parecem IA de filtro do Facebook de 2023. Vídeo bugado. Interpretação de prompt toda torta. Código ninguém leva a sério. Escrita criativa então nem se fala. E aí os caras resolveram fazer o quê? Capar o reasoning de um modelo que já era nota de rodapé. É tipo um restaurante vazio começar a cobrar entrada VIP pra acessar o cardápio premium sendo que ninguém nem queria comer lá em primeiro lugar. E o mais bizarro é a lógica de público-alvo. Porque quem realmente usa raciocínio prolongado: - dev - pesquisador - power user - nerd de benchmark - gente que vive comparando modelo …essa galera já tá usando outras coisas faz tempo. Então o Meta AI não é forte o suficiente pra roubar os usuários hardcore, mas também não faz sentido pro casual pagar assinatura. Usuário casual do Instagram não vai precisar de “Thinking avançado”. A tia do WhatsApp não vai abrir cadeia de raciocínio de 8 mil tokens pra perguntar receita de bolo. O creator médio não vai abandonar GPT, Gemini ou ferramentas dedicadas pra gerar vídeo bugado no Meta AI. Então fica parecendo que os caras criaram um problema artificial pra vender solução artificial. E isso tudo vindo d

submitted by /u/UFOsAreAGIs [link] [留言]

Hello everyone. The new dataset is named MONET, is Apache 2.0 and available on HF: https://huggingface.co/datasets/jasperai/monet MONET is open, Apache 2.0-licensed image–text dataset. It was built from 2.9 billion images and refined to 104.9 million high-quality samples. We are also publishing a paper that explains how the dataset was created if you are curious and 3 compagnions projects A umap to visualize the distribution A retreival tool to do text or image search A codebase to train T2i model based on MONET Hope this will be usefull! submitted by /u/dh7net [link] [留言]

Platform team sprint planning in 2026 begins with budget allocation, not architecture review. The first question is no longer "what do we need to build?" — it's "what can we afford to run?" This is not FinOps adoption. This is authority displacement. The platform team became a finance team because the control plane for infrastructure decisions migrated from architecture governance to budget governance. Cost constraints don't inform architectural decisions anymore — they dictate them. And when financial systems gain veto authority over technical systems, resilience becomes the variable that adjusts. Platform team cost governance is now the primary control surface. Architecture is secondary. How We Got Here The timeline is sharper than most organizations admit. 2018–2022 was the cloud adoption phase. Platform teams built for scale. Multi-region resilience was standard. Observability was deep. Auto-scaling was elastic. Architectural requirements shaped cost models. The budget followed the design. 2023–2024 brought FinOps as a cost visibility layer. Teams could finally see where money was going. Dashboards got built. Anomaly detection got configured. Attribution models got refined. But visibility was still separate from authority. The FinOps team reported. The platform team decided. 2025–2026 is when cost governance moved from reporting to gating. The turning point: platform teams stopped asking "can we build this?" and started asking "can we afford this?" Engineering roadmaps became cost roadmaps. Feature requests now come with budget allocation approvals. Architecture reviews now include CFO sign-off gates. This shift introduced Budget-Normalized Architecture — systems designed around predictable monthly spend targets instead of operational resilience targets. The architecture no longer optimizes for failure domains, latency requirements, or recovery objectives. It optimizes for staying under the cost ceiling. Cost governance expanded because engineering governance fa

A colleague said something to me recently that I keep coming back to: "Often, by the time you've finished articulating a complex problem for the AI, you've already solved it yourself." It sounds almost like a joke. You open a chat window, start typing out your problem in careful detail — and somewhere in the middle of the second paragraph, the answer appears. Not from the AI. From you. If you've worked with LLMs seriously, you've probably experienced this. And I think it points to something important about what is actually changing in our craft — something that goes beyond the usual conversation about automation and job displacement. The Rubber Duck, Promoted Developers have known for decades that explaining a problem out loud helps solve it. The classic technique involves a rubber duck: you place it on your desk, narrate your code to it, and the act of articulation forces you to confront the assumptions you'd quietly made. The duck never responds. That's not the point. The LLM is a rubber duck that occasionally says something useful back. But even when it doesn't — even when the response is generic or slightly off — the discipline of formulating the prompt has already done its work. You've had to be precise. You've had to strip away ambiguity. You've had to decide what actually matters. That process is not a workaround. It is thinking. The Inversion of the Workflow In the pre-AI era, the typical development workflow looked something like this: you had a rough mental model of the solution, you started coding, and you discovered the edge cases along the way. The code was exploratory. The thinking happened during the writing. With AI assistance, that workflow inverts. Vague inputs produce vague outputs — the model has no way to compensate for an underspecified problem. So precision becomes mandatory upfront. You have to think before you type, not while you type. This is a more demanding cognitive posture. It requires holding the full shape of a problem in your head be

Trisha Ballakur discusses her journey from a backend software engineer to CTO and CEO, using her startup Pointz as a case study. She explains how to implement bottom-up customer discovery to find product-market fit, effectively delegate to global contractors to reduce build times, customize open-source repos like Valhalla, and apply engineering test-case models to business development. By Trisha Ballakur

Oura describes its new wearable as the 'world's smallest' smart ring.

It’s slimmer, lighter, and more durable. But the real upgrade is Oura’s push into AI-powered health insights and proactive monitoring.