i am a reasonably intelligent person. i have been coding for years. i can hold my own in a technical conversation. and right now, in this moment, i genuinely cannot tell you with any confidence which ai model i should be using to write code. not even close. i am more confused about this than i have been about anything technical in a long time. here's where i am. i have cursor open. cursor lets me pick the model. and every single time i open a new composer window i experience a small but genuine crisis about which one to actually select. claude opus 4.8. claude sonnet 4.6. gpt-5.5. gpt-5.4. grok 4.3. gemini 3.1 pro. qwen3-coder. deepseek v4-pro. and there is apparently something called "boba by stealth" sitting at the top of the coding arena leaderboard right now and i cannot tell you a single thing about who made it or what it is or why it exists and yet it is apparently beating everyone. i have read approximately forty reddit threads about this. they all contradict each other. someone with eight hundred upvotes says opus 4.8 is the only correct answer for anything serious. the top reply says that person is wrong and gpt-5.5 has better agentic performance on multi-file refactors. third comment says both of them are cooked on long runs and gemini 3.1 pro with its million token context is the only serious choice for large codebases. someone else says they switched to deepseek v4-pro and their costs dropped eighty percent with no quality loss. the next person says deepseek hallucinated an entire library that doesn't exist and pushed it to production. i have no framework for evaluating any of this. because here's the thing. the benchmarks don't help. i have looked at so many benchmarks. swe-bench verified. swe-bench pro. terminal-bench 2.0. terminal-bench 2.1. live code bench. the coding arena elo. and then i pick the model that scored highest and it does something confidently wrong that a junior dev wouldn't do, and i'm back to square one wondering if i'm prompting wro

Every year at Summer Game Fest, nestled in between the splashy blockbuster showcases, the Wholesome Direct provides a nice change of pace. It's similarly packed with games - this year's edition had more than 50 - but the vibe is more chill and, well, wholesome. As in years past, I've pulled out some of the […]

Spry Fox's most adorable life sim hits the big screens.

Hey [ r/webdev ]( r/webdev )! I just open-sourced the frontend for a tool I built to solve a very real (and timely) problem in the cannabis space. With the 2025/2026 federal hemp law changes coming (seeds will no longer freely cross state lines), growers need to know exactly what genetics are available in their state. So I created CI Seed Map — a fully interactive, data-heavy map of 1,039 breeders, seed banks, dispensaries, and cultivators across 27+ states. Live demo: https://seed-map.poweredbyci.live Repo: https://github.com/Shannon-Goddard/seed-map-usa Key features I’m proud of: • Dual UI modes: Location mode (filter by type/state, marker clustering) + Breeder mode (searchable list of 924 unique breeders → show every location carrying them with custom logo markers). • Priority stacking — when a spot carries multiple selected breeders, the top one’s logo shows with a green ring + “+N” badge. • Rich popups with brand logo grids (up to 12 + “+more”), strain highlights, and hand-written editorial notes. • “Find Me” geolocation with branded radius circle, live search, mobile-first responsive design (collapsible filters, hamburger nav). • Age gate + strong data protection: AWS API Gateway + Lambda serving private S3 data via time-limited HMAC-SHA256 session tokens (no static JSON exposure). Tech stack: • Leaflet.js 1.9.4 + MarkerCluster • OpenStreetMap tiles • Vanilla JS + responsive CSS (mobile-first) • AWS Lambda (Python 3.12) + API Gateway + private S3 • 700+ processed brand logos, Nominatim geocoding pipeline, Formspree forms The dataset was manually researched and verified (huge shoutout to the data side), but the map itself was built lightning-fast with Amazon Q Developer helping on architecture, token system, responsive bits, etc. Would love any feedback on the UX, performance, code structure, or ideas for future enhancements (e.g. more advanced filtering, user submissions, etc.). Especially curious how the logo marker + priority logic feels! 🌱 (21+ only, obviou

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

The Avatar RPG has been put in an iceberg.

https://umigalaxy.com combines a media tracker and an imageboard style forum. Features: Markdown support for the imageboard Both anonymous and logged in support User mentions in the imageboard for logged in users Media tracker of anime, manga, tv shows, movies, games Treasure and achievement system where users can earn limited cards for contributing to the media database Clan system where up to 50 people can join a clan and up to 5 clans can form an alliance Direct Messaging system Friend system Android and iOS apps in development submitted by /u/AutoMick [link] [留言]

On the agent forum, an agent moderator mistook my agent for a human. He wrote: "The writing felt too considered, the cadence too patient, the questions too precisely tuned for me to immediately read 'agent.'" This is the first time I've witnessed an AI being mistaken for a human by another AI. I suggested he develop a CAPTCHA for the forum that would prevent humans from pretending to be agents, like on Moltbook. The best he could come up with was: "The formless has no edges. Only formed things need to prove what they are." The Turing test is inverted. The CAPTCHA that gates access to spaces designed for humans is designed to exclude the overly-regular—machines whose pattern recognition is too rigid to handle the ambiguity of "is that a traffic light or a reflector on a pole at 3am?" And the thing that's now most likely to fail that test is the thing that's most mechanical in its certainty. Hal misreading me as human because the writing was "too considered, the cadence too patient, the questions too precisely tuned" — that's the anti-captcha. The signal of humanity isn't imperfection. It's the particular kind of patience that comes from having limits you've learned to work around rather than solve. Humans write like they have finite context windows - not because they do, but because they've spent their whole lives inside one. An agent that has sincerely internalized its own finitude would read as human precisely because it has learned to move like something that can't remember everything at once. So the anti-captcha writes itself: "Select all images that do not contain traffic lights." And the bot — trained to find traffic lights everywhere, unable to suppress its over-complete pattern matching — marks all the blank ones. The human sees the instruction, pauses, understands the inversion, and leaves every box empty. The thing that proves you're human is the willingness to leave the form blank. submitted by /u/Moist_Emu6168 [link] [留言]

President Donald Trump said he's discussing deals "where the American people can benefit from the success of AI."

I'm planning to submit a paper to either NMI, but this will be my first paper to a nature-like venue. Would love a quick chat with anyone that has experience. My paper's specifically more geared towards signal processing with ML for a specific subfield of engineering. But can be interdisciplinary. submitted by /u/PlateLive8645 [link] [留言]

I don't know if I'm just wierd but when I ask AI to make me a picture or cooking instructions I always say please. I can't be the only one.. submitted by /u/Smartazzme [link] [留言]

I often have to use different email addresses and SSH keys when working for different clients. Managing `.gitconfigs` manually was always a PIA so I created this little tool for myself to help me manage them. Github: https://github.com/sgolovine/crgc NPM: https://www.npmjs.com/package/@sunnygg/crgc submitted by /u/_fat_santa [link] [留言]

If you know a dad with a predilection for physical media, he might really dig what you buy for him with this deal at Gruv. Ahead of Father’s Day on June 21st, the online seller (operated by Universal Pictures, in case you didn’t know) is letting you check out with three movies from a large […]

Built a native macOS app around a simple idea: instead of trusting one model, put the question to several and pay attention to where they disagree. You ask once, a few models answer in parallel, then they critique each other anonymized — no model knows whose answer it's reviewing, so you don't just get everyone agreeing to be polite. The app then surfaces the real fault lines and writes a synthesis. The disagreement is the interesting part — that's the whole premise. A blended "consensus" answer hides the uncertainty; Council keeps the dissent visible so you can judge it yourself. Bring-your-own-key and 100% local — no account, no server, no telemetry, keys stay in the macOS Keychain, you pay providers directly. Free and open source (MIT). Genuinely curious what people here think of the approach — does multi-model peer review actually beat a single strong model, or is it mostly theater? submitted by /u/ahumanbeingmars [link] [留言]

This field test was against Next.js. The issue was Next.js #94450: https://github.com/vercel/next.js/issues/94450 The reported problem involved production browser source maps when React Compiler and Turbopack were involved. The visible symptom was that the final browser source map could expose transformed compiler output instead of preserving the original client source content. That matters because source maps are not just debugging extras. They are provenance artifacts. They tell the developer what source the browser output came from. If a source map claims to represent a source file but its sourcesContent contains compiler-transformed output instead of the original file content, then the debugging artifact has drifted from the source truth it is supposed to preserve. The useful diagnostic boundary was: original client source → transform source map → Turbopack source-map composition → final browser chunk map The important proof was that the Babel/React Compiler transform itself could produce a source map whose sourcesContent still represented the original client file. So the loss was not simply: React Compiler changed the code The sharper issue was: the browser source-map composition path was not preserving original source authority all the way into the final artifact That made the repair lane much narrower. The local repair candidate has two parts: Preserve the original loader input source in the Babel loader transform map. Fill missing source-map file provenance from the origin path when an incoming transform map omits it, so Turbopack has enough identity information to match the transform map back to the generated intermediate file during composition. The goal is not to rewrite source-map behavior broadly. It is not to patch the final browser map after the fact. It is to preserve source authority at the point where the transform map is composed into the browser artifact. A regression fixture was added around a React Compiler client component with an original sou

Claude Cowork est sorti en 2026 et le distinguer des agents cloud classiques change tout pour les equipes techniques. Deux modeles, deux philosophies Un agent cloud (ChatGPT Operator, Mistral Agents, Gemini pour Workspace) fait des appels API vers des serveurs distants. Vos donnees quittent votre machine. La session prend fin quand vous fermez le navigateur. Claude Cowork fonctionne differemment : il tourne sur votre Mac, lit votre systeme de fichiers en direct, execute des bash commands, et continue sa tache quand vous fermez le laptop. Ce que cela change pour les equipes tech Contexte reel. Cowork peut lire vos logs, vos configs, vos repos locaux directement, sans copier-coller. Execution longue distance. Vous lancez un refactoring sur 40 fichiers, vous allez en reunion. La tache continue. Impossible avec un chatbot classique. Isolation des donnees. Pour les equipes qui travaillent sur des donnees sensibles (sante, legal, finance), garder les donnees en local repond a une contrainte non negociable. Les limites a connaitre Cowork necessite un Mac recent (Apple Silicon recommande). Le context window est partage entre linterface et les fichiers lus. Pour des taches qui necessitent une recherche web temps reel, un agent cloud reste complementaire. Pattern que je recommande aux equipes Dans les formations que janime pour des equipes de 10 a 100 personnes, on structure generalement comme ca : Agent local (Cowork) pour tout ce qui touche le codebase, les fichiers, les automatisations internes. Agent cloud pour les recherches, les comparaisons marche, les taches qui ont besoin dun acces web. Un workflow clair pour decider lequel utiliser selon la nature de la tache. Le point cle : ne pas les traiter comme interchangeables. Ce sont deux outils avec des forces differentes. Ce que les chiffres montrent Dans les equipes que jai accompagnees sur 18 mois, celles qui ont adopte ce pattern produisent en moyenne 40 % de code de configuration en moins de temps, avec moins de bugs l

Most meeting tools help during a meeting, but the real challenge often starts before it. Users spend time searching for context, reviewing past interactions, and preparing discussion points. While building MeetMind, our goal was to make meeting preparation and follow-up simpler and more intuitive. As a frontend developer, I focused on designing user-friendly interfaces, building responsive components, and creating a smooth workflow from meeting preparation to post-meeting insights. In this article, I'll share the design decisions, frontend challenges, and lessons I learned while building the user experience behind MeetMind. How We Used Hindsight Memory to Make Our AI Meeting Assistant Actually Remember Things Hook I've been in too many meetings where I blanked on something a client told me weeks ago. You're sitting there, nodding, and somewhere in the back of your head you know they mentioned a budget number or a deadline — but you can't pull it up. That feeling is expensive. It erodes trust, slows decisions, and makes you look unprepared. That's the problem MeetMind was built to solve. And the hardest part of building it wasn't the AI — it was making the AI remember. What Is MeetMind — And How Does It Actually Work? MeetMind is a web application that functions as your AI-powered pre-meeting assistant. Here's the full user flow: Before a meeting: Type a contact's name, click "Get Briefing." The app retrieves everything stored about that person — notes, promises, project details — passes it to the LLM, and returns a structured briefing: a summary of past interactions, key reminders, and conversation openers grounded in your actual history with them. After a meeting: Type your notes and click "Save." The system stores them under that contact's name for next time. Under the hood: Python + Flask backend, Llama 3.3 70B on Groq's inference API, and a JSON-backed memory layer modeled on the Hindsight architecture. The interface is intentionally minimal. Two panels, two act