标签：#AR

FBI: Googler who knew outcome of bets in advance made $1.2M profit on Polymarket.

Hey DEV community! 👋 A few days ago, I built a VS Code extension called Marksmith to fix the most annoying parts of writing Markdown (like pasting Excel tables and syncing preview scrolls). But recently, I noticed a huge shift in my own workflow: Half the Markdown I write isn't for humans anymore. It’s being fed directly into Claude, ChatGPT, or Gemini as prompts and context. When you're constantly stuffing docs into context windows, two things happen: You worry about hitting context limits (or racking up API costs). You waste time dealing with AI "hallucinations" when you ask it to generate docs back for you. So, for the v0.3.0 release , I decided to pivot Marksmith into something new: An Agent AI-Ready Markdown Toolkit. 🚀 Here is what I added to survive the AI era: 📊 1. Real-time LLM Token Estimator Instead of just counting words, Marksmith’s Document X-Ray sidebar now includes a Heuristic Token Estimator for GPT, Claude, and Gemini. Before you copy-paste that massive README into your AI assistant, you can see exactly how "heavy" it is in terms of tokens right inside your editor. No more guessing if you're about to blow past your context limit! ✂️ 2. Copy Optimized for AI (1-Click Minify) Formatting is great for humans, but LLMs don't need all those extra spaces, perfectly aligned markdown tables, or empty lines. I added a CodeLens button at the top of your files. Click it, and Marksmith instantly minifies your Markdown (compresses tables, strips blanks) and copies it to your clipboard. Result: You save significant tokens and API costs without ruining your beautiful local .md file. 🕵️ 3. Hallucination Quick Fix Ever ask an AI to write documentation, and it leaves behind a bunch of [TODO: Insert link here] or makes up a fake local image path? Marksmith now automatically scans your document and puts a red squiggly line under AI placeholders and broken local links . Click the 💡 icon, and you can instantly strip them out or fix them. It acts as a safety net before you

Hey , I've been building VeritasReason — an open-source Python framework that adds a structured reasoning and provenance layer on top of LLMs and AI agents. The problem it solves: AI agents today make decisions but record nothing. When something breaks in prod, you have zero audit trail. What it does: • Context Graphs — queryable graph of everything your agent knows + decides • Forward-chaining rule engine (YAML rules, no code required) • W3C PROV-O provenance — every answer traces back to its source fact • Policy compliance: ask "Which purchase orders violated SoD policy in Q1?" • Works with OpenAI, Anthropic, Groq, Ollama, any LLM 30-second demo: pip install veritas-reason veritasreason-policy-demo GitHub: https://github.com/bibinprathap/VeritasGraph PyPI: https://pypi.org/project/veritas-reason/ Happy to answer questions — built this for regulated-industry AI (healthcare, finance, legal) where "trust me bro" answers aren't enough. — Bibin submitted by /u/BitterHouse8234 [link] [留言]

Everyone is adding AI to their product right now. Most of them are doing it wrong. Not because they chose the wrong model. Not because they used the wrong library. But because they treated AI integration like a regular feature and skipped all the engineering discipline that production systems require. I have integrated LLMs into multiple production applications. This is what I wish I had known before I started. The Mental Model Shift You Need First A traditional API call is deterministic. You send a request, you get a predictable response. You can write tests against it. You can cache it. You can reason about it. An LLM call is not deterministic. The same input can produce different outputs on different runs. The model can refuse, hallucinate, or return output in a format you did not expect. Your system needs to be designed around this reality, not in spite of it. This means defensive parsing, fallback logic, output validation, and graceful degradation are not optional extras. They are the core of the feature. Choosing the Right Model for the Right Job The biggest LLMs are not always the right choice. I learned this building EditDeck Pro, an AI creative platform for music. Some tasks needed a large frontier model for nuanced creative output. Others needed a fast, cheap model that could run many times per session without accumulating significant latency or cost. The pattern that works: Use a lighter model for classification, extraction, and short structured outputs. Use a larger model for generation tasks where quality matters more than speed. Route dynamically between them based on the task type. This can reduce your inference costs by 60 to 80 percent on workloads that mix simple and complex tasks. Prompt Engineering Is Software Engineering Prompts are code. They should be versioned, tested, and reviewed like code. I store prompts in a dedicated module with version numbers. When I change a prompt I run it against a fixed evaluation set of inputs and compare the out

I was looking at my bank statement one day and realised I was paying for 4 things I completely forgot about. Combined it was around 40 euros a month just silently leaving my account. I'm a 17 year old developer from Cyprus and I spent the last few weeks building Capsule, a simple subscription tracker that shows you everything you pay for, alerts you before renewals, and tracks how much you save by cancelling things. No bank connection required. You just add your subscriptions manually. Privacy first. It's not on the Play Store yet but the waitlist is live at capsule.crickdevs.com if anyone wants early access. Would genuinely love feedback from real people before I launch.

the video generators are becoming much more powerful, only unemployed people can track the changes ( like me).. Here are the current observations, and add anything in the comments if you feel I missed something. Cinematic Videos Seedance 2.0 : This Chinese model is fantastic in real visuals and advanced visuals, almost like real shots. I guess this will become the future. Kling 3.0 and kling motion transfer: Motion transfer is amazing, you shot a vidoe yourself and can trasfer the movement any avatar. Kling is the king in that aspect. With Kling’s motion transfer, . There is no other technology that can do this this well and look super fantastic. Veo3 : Recent releases of Veo 3.1 are still some of the best videos. Sora has shoted down by openai, and recent Google model, - GeminiOmni , is the best in video editing. It is like Nano Banana for videos. It is absolutely fantastic. Don’t compare this with Seedance because the purpose is completely different. If you try it on your own video and ask it to add something, it gives a super realistic output. Explainer Videos These are not cinematic, but mostly for concept explanations and long videos. These tools are great fit: Distilbook : This one is very good at creating visual explanations with whiteboards and animations based on your content, PDFs, and all. If you want long videos, like 3-minute or 5-minute training videos,academic this is purpose-fit. NotebookLM Video overview : This tool has the video overview option, which makes things much easier for you. It is mostly for slide-type videos, but it still gets your work done because most of the time you may not need animated videos. MathGPT: Here it is mostly for math educational video explanations using some animations. These are not very advanced, but still, if you want cheap educational videos, maybe it can do the job. Images In my personal opinion, - The recent GPT image model is fantastic. Second, the Google model Gemini Nano Banana Pro and Nano Banana Flash 2 are b

As Apple tries to shrink Gemini for the iPhone, a cloud component is probably inevitable.

For a long time, I thought productivity was about effort. Work harder. Focus more. Stay disciplined. Manage time better. Most productivity advice is built around some version of this idea. Then I noticed something strange. Some days I could spend ten hours at a desk and accomplish almost nothing. Other days I could spend three hours working and make more progress than I had all week. The difference wasn't effort. The difference was context. The Most Expensive Thing Is Not Time Ask people what their most limited resource is and most will answer: Time. But for knowledge workers, engineers, researchers, writers, and designers, I think the scarcer resource is often something else. Mental state. The ability to hold a problem in your head. The ability to remember why a decision was made. The ability to see connections between ideas. The ability to continue a train of thought without interruption. That's the state where meaningful work happens. And it's surprisingly fragile. Every Context Switch Has a Cost Imagine you're debugging a difficult issue. You've already: read the logs inspected the code traced the requests formed a hypothesis You're finally starting to see the shape of the problem. Then: a Slack notification arrives someone schedules a meeting an email requires attention a different task becomes urgent The interruption itself might only take two minutes. The real cost is what disappears. The mental model. The momentum. The partially constructed map inside your head. The next time you return to the task, you don't continue where you left off. You rebuild. Software Often Creates The Problem It Tries To Solve One thing that surprised me after building products for years is how much software exists primarily because other software creates friction. A note-taking application exists because memory is limited. A task manager exists because priorities change. A research assistant exists because information is fragmented. Many tools are not solving fundamental problems.

Amazon is turning a corner with its launch providers, but ULA's Vulcan remains grounded.

CEO Ariel Katz argues that while AI can replicate workflow SaaS, it can't copy H1’s unique doctor data.

Are agents aging after deployment? : https://arxiv.org/abs/2605.26302 On a new longitudinal deployment benchmark, switching the Claude Code CLI agent from Sonnet 4.6 to Opus 4.7 dropped PyTest pass rate by ~15%. This (to me) is a counterintuitive-enough result to pay attention to. The authors built AgingBench , to measure how coding agents hold up over a long deployment, not just on a single task. On their S7 coding scenario, swapping the backbone model from Sonnet 4.6 to Opus 4.7, within the same Claude Code CLI harness, produced a 15% mean drop in PyTest pass rate across the deployment horizon. Their argument is that this is a longitudinal effect, not a raw-capability one. The benchmark stresses how an agent's memory state evolves over many sessions (compression, interference, revision, maintenance shocks), and a stronger base model doesn't automatically age better under a given memory policy. In fact, memory policy alone drove a 4.5x spread in agent half-life across scenarios, which is larger than any model swap they tested. All to say: "newer model, just swap it in" may not be a safe upgrade strategy for long-lived agents. More details and a runnable benchmark: https://agingbench.github.io Does this reflect your experience with long-lived agentic deployments? submitted by /u/CategoryNormal149 [link] [留言]

Europe’s startup ecosystem has matured significantly; its founders are increasingly willing to scale companies domestically instead of immediately looking to relocate to the U.S.

StrictlyVC Los Angeles is on June 18. Join for meaningful networking and fireside chats with leaders from Mach Industries, Shinkei Systems, and more. Register today.

While startups raising back-to-back rounds at steep step-ups have become almost routine, a company whose valuation doubles in three weeks is unusual enough to raise questions, particularly given the investor set in both rounds is the same.

Intel's Arc B390 integrated GPU has offered impressive performance in laptops.

submitted by /u/Rare-Grapefruit-3982 [link] [留言]

Anthropic just dropped Claude Opus 4.8 today, an incremental but meaningful upgrade over Opus 4.7. Here are the highlights: Model improvements Better performance across coding, agentic, reasoning, and knowledge work benchmarks Significantly improved honesty: the model is reportedly ~4x less likely to let flaws in its own code go unremarked compared to Opus 4.7 Alignment assessment shows lower rates of deceptive or misaligned behavior, on par with their Claude Mythos Preview model Scores 84% on Online-Mind2Web for computer use and browser agent tasks, ahead of both Opus 4.7 and GPT-5.5 New features launching alongside it Dynamic workflows (Claude Code): Claude can now spin up hundreds of parallel subagents in a single session to tackle large-scale problems like full codebase migrations. Available for Enterprise, Team, and Max plans. Effort control: Users on claude.ai can now choose how much compute effort Claude puts into a response, from faster/cheaper to deeper/slower. API update: The Messages API now accepts system entries inside the messages array, letting developers update instructions mid-task without breaking prompt cache. Pricing Same as Opus 4.7: $5/M input tokens, $25/M output tokens. Fast mode (2.5x speed) is now 3x cheaper than it was for previous models, at $10/$50 per million tokens. What's next Anthropic mentioned they are working on bringing Mythos-class models (currently in limited preview for cybersecurity use cases under Project Glasswing) to general availability in the coming weeks. Full details and system card: anthropic.com/news/claude-opus-4-8 submitted by /u/Direct-Attention8597 [link] [留言]

Here’s why Anthropic and OpenAI are on board with Illinois safety testing.

The new Opus model comes with a tool called Dynamic Workflows, for coordinating swarms of subagents.

If you’ve been waiting for a smaller version of the Oura Ring, the company’s latest wearable is now available for preorder ahead of its June 4th release from Oura and various third-party retailers, including both Amazon and Walmart. The Oura Ring 5, which starts at $399, is 40 percent smaller than its predecessor, thanks to […]