标签：#ci

The same AI failure should not happen twice. But it does. Teams fix it, change something small, and it returns silently. We built Agent Fail Museum to document these patterns permanently. Submit one sentence about a failure you have seen. Get a regression test draft back. Anonymous by default.If you have built any AI project that broke after a change, your failure probably fits one of the 10 known patterns already in the archive. submitted by /u/taimoorkhan10 [link] [留言]

Large corporations are going to use AI regardless of what the public thinks. They have the money, lawyers, infrastructure, and data to do it. AI isn’t going away for them. But who gets hurt most when ordinary people are told not to use AI? The small business owner who can’t afford an artist to create a logo. The startup founder who can’t hire a copywriter to proofread every email. The family business that can’t pay an accountant for every tax question. The entrepreneur who can’t afford a programmer to build a website or a consultant to review a business plan. For the first time in history, a person with a good idea and a laptop can access tools that were previously reserved for companies with large budgets. I’m not saying AI is perfect. It makes mistakes, and there are legitimate concerns about its environmental impacts. But I do wonder: if AI dramatically lowers the cost of expertise, who stands to lose the most from that? The average person—or the organizations that have always had exclusive access to that expertise? Is the anti-AI push really just a push from big corporations to cut out those who stand the most to gain: small business owners? submitted by /u/Outlasttactical [link] [留言]

I've been working on something others might find interesting. It's under heavy development as I learn. Most AI agent setups treat the model like a better autocomplete — paste a prompt, get output, hope it's right. That works for small tasks. It falls apart when you try to use agents for sustained work across sessions: they skim specs, declare victory at 60%, burn context on noise, silently resolve ambiguity without surfacing it, and mark checklist items done without actually doing them. The failures are predictable and nameable — so I named them. This is a white paper and implementation guide for a full-stack agentic system — everything from planning through promotion under structural enforcement. It documents 24 failure modes from months of multi-agent operation and, for each, describes what actually prevents it: some through mechanical gates the agent cannot skip, some through procedural skills, and some through human supervision. The guide covers how to structure specs, plans, and verification so that agent work is evidence-led rather than vibes-led, how to use MCP capability surfaces as structural levers, and how the failure modes apply regardless of which model or vendor you use. The white paper also includes a Related Work section that positions it against the emerging industry consensus — CodeRabbit, Anthropic, Spotify, Cloudflare, OpenAI, Karpathy, Thoughtworks, and academic research all independently arrived at pieces of the same conclusions. The difference here is the integrated stack: a failure taxonomy mapped to prevention mechanisms, a three-layer enforcement architecture, and a concrete reference implementation with an orchestrator, task graphs, step verification, adversarial review, and model stratification. White paper: https://gitlab.com/naive-x/naive-artifact-coding/-/blob/main/white-paper.md Reference implementation: https://gitlab.com/naive-x/naive-artifact-coding/-/blob/main/docs/reference-implementation-guide.md Implementation guide: https://gi

submitted by /u/Hot-Upstairs9603 [link] [留言]

Hoje eu postei sobre o Mark Zuckerberg lançar a notícia mais patética que vai cobrar 19 dólares para desbloquear o Muse Spark Pro kakakakakakaka Quem vai pagar por essa merda? Mas pensando melhor bem... Talvez eu pague Eu usei muito esse modelo como Early adopter, desde quando o motor era o Llama 3.2 e sendo inferior as outras consegui extrair escrita criativa que batia de frente com Claude em personas graças ao seu RAG no ecossistema da Meta, que tinha uma criatividade absurda quando você forçava ela a consultar as redes sociais e ver como pessoas agem e comentam, porém lançou o Muse Spark que era tipo o GPT 5.2 dos Llamas kkkkkk aí só usei para pesquisa e bem... Minha tese sobre o Muse Spark é que pra mim o problema nunca pareceu ser burrice. Parece CONTENÇÃO. Não dá vibe de modelo incapaz ou inferior. Dá vibe de modelo sendo sufocado em tempo real. Porque se você presta atenção, ele: - pesquisa rápido pra cacete (Já que cada agente pesquisa uma coisa) - alucina menos em busca (pois o modelo refina a busca dos agentes, muitas vezes consegui resultados mais confiáveis que o Gemini) - já trabalha com esquema multi-agente herdado da Manus ( o trunfo dessa IA é que diferente das outras ela não comprimi seu input, ela usa agentes para cada um pesquisar cada trecho dele, o resultado é mais completo) - acha informação boa (ela pesquisa tanto na internet quanto em grupos de Facebook ou Threads se você forçar no prompt, ou seja análises de Devs>>> Wikipédia Inclusive acredito que foi por isso que o Mark lançou o "Fórum" o app que cópia o Reddit, ele quer treinar a IA com isso, o Reddit pra mim seria a fonte perfeita pra qualquer IA se aprofundar além do que pesquisar genéricas no Google, o filha da puta do Mark é rico e filantropo e faz uma cópia só para treinar a IA dele) - conecta coisa rápido (os agentes pesquisam rápido, o modelo revisa rápido, a entrega é bem rápida e gasta bem menos tokens) Só que na hora de responder… Parece o GPT free kkkkkkk O raciocínio corta no

Everyone can build it. Almost no one can afford to run it at scale. And the companies selling the picks and shovels are about to get undercut by the same forces they unleashed. by VEKTOR Memory — 20 min read How This Article Started: 20 Forums, 40 Headlines, and a Growing Sense That Everyone Was Confused I woke up to clear skies and the sun finally shining, and I set out to understand this idea, the truth behind it, and the nagging suspicion that the narrative around AI and software costs had become so loud, so uniform, and so confidently confusing that someone needed to sit down and actually go through it. No tweets, or are they now X's? No LinkedIn thought leader infomercials, no Substack hype, just actual research and deep thoughts. So I spent time reading, collating data. Forums, whitepapers, LinkedIn posts, Hacker News threads, VC essays, Reddit arguments. I went looking for the real signal underneath the noise. What I found instead was the full spectrum of human overconfidence, lots of moat real estate. On one end: the hype machine at full throttle. “Software is going to zero.” “A solo dev can now build what a 50-person team built in 2021.” “The era of the $500/month SaaS subscription is over.” “Vibe coding will replace your entire engineering org.” These headlines were everywhere. Breathless. Confident. Shared tens of thousands of times, this angle gets views, of course, the algorithm loves being fed claps, shares, comments, and reposts. Most were written by people who had a very good Tuesday with Codex, Windsurf, Claude and Cursor and decided that instant dev, open source to Github and getting oodles of stars, maybe even roping in a celebrity, was now the permanent condition of software development. “We are now famous on GitHub!" Very hipster, very vibes, see you on the playa.. On the other end: the backlash. Experienced engineer, people with 15 to 25 years in production systems are pushing back hard. “Show me the vibe-coded app that survived its first real

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

Most scraping projects start by finding a website to scrape. This one started from the opposite direction: I knew the data existed as official government downloads, and my job was to make it accessible via a clean API. The data source Ofsted (the UK school inspections body) publishes monthly management information as CSV files on GOV.UK. The file covers all 22,000+ state-funded schools in England with their latest inspection grades, local authority, postcode, phase, and size data. It's 16 MB, published under the Open Government Licence v3.0 — explicitly permitting commercial use. No scraping needed. No authentication. Just a CSV download and some parsing logic. The architecture The actor is deliberately simple: Fetch the GOV.UK stats page to find the current month's CSV URL (the URL hash changes with each release) Download the CSV (~16 MB from assets.publishing.service.gov.uk ) Parse it with csv-parse Apply the user's filters (name, local authority, region, postcode prefix) Push matching records to the Apify dataset No Crawlee. No browser. No proxy. Just fetch() and a CSV parser. const match = html . match ( /href=" ( https: \/\/ assets \. publishing \. service \. gov \. uk \/[^ " ] +latest_inspections_as_at [^ " ] + \. csv ) "/ ); That one regex does the URL discovery. The GOV.UK page lists files in reverse chronological order, so the first match is always the latest release. The interesting part: Ofsted changed their grading system mid-build I built this in May 2026. In November 2025, Ofsted scrapped their 20-year-old four-word judgement system (Outstanding / Good / Requires Improvement / Inadequate) and replaced it with a report card format — six separate grade areas, each on a five-point scale: Exceptional Strong Expected standard Needs attention Urgent improvement Plus a standalone Safeguarding verdict (Met / Not met). The April 2026 CSV reflects this change entirely. There's no "Overall effectiveness" column. Schools inspected before November 2025 have null gr

I was dealing with another "output not usable" issue today in our app, user left a comment saying that no matter what he does the agent returns the result in the wrong format. It took me hours to identify the mistake and AI model missed it. Curious to hear your stories about the times you shipped a feature in your AI product and it flopped. How did you figure out what was actually going wrong? What tools if any did you use? What metrics were key? submitted by /u/pauliusuza [link] [留言]

I love all the wild updates from Anthropic, Open AI, Google, etc. And also seeing the creative stuff that mid-market AI shops are rolling out. I sometimes go through phases where I ping-pong between new tools (mostly just curiosity) but sometimes I tend to go deeper into a specific ecosystem. Right now trying to go "all-in" on Claude but I'm like a cat and Open AI is the laser pointer with new Codex updates. What have you all found works best. Go wide and test everything? Different tools for different use cases. Go deep and specialize in one ecosystem? submitted by /u/BeltwayBro [link] [留言]

If it scales up, it can help us diversify our sources of a key element.

In its latest update, Bluesky is getting into long-form content.

A lot of agentic AI content focuses on greenfield builds. I wanted to show what it looks like when you have an existing search stack and want to supercharge it without a rewrite. Built a demo with four levels of AI adoption - from a zero-risk async suggestion bar up to a full conversational search assistant - and wrote up the architecture at each level. The whole demo took 10 hours to build. Live app included. https://arcturus-labs.com/blog/2026/01/18/incremental-adoption-of-agentic-search/ submitted by /u/Due_Ad_1318 [link] [留言]

Meta’s upcoming Instagram Plus and Facebook Plus subscriptions are the latest example of the company seeing what works elsewhere and mimicking it.

Appendix: Live System Output — Real Pipeline in Production All output below was captured live from the running pipeline on 2026-03-08. These are not mock outputs — they come from actual AWS infrastructure and Kubernetes clusters. ArgoCD — All 50 Applications Across 6 Clusters The following is the live output of argocd app list from the hub cluster ( myapp-production-use1 ). Every component of the pipeline is represented — security, logging, monitoring, backups, and the application itself. $ argocd app list --output wide NAME CLUSTER NAMESPACE PROJECT STATUS HEALTH argocd/argo-rollouts-myapp-production-use1 myapp-production-use1 argo-rollouts production Synced Healthy argocd/argo-rollouts-myapp-production-usw2 myapp-production-usw2 argo-rollouts production Synced Healthy argocd/aws-lbc-myapp-production-use1 myapp-production-use1 kube-system production Synced Healthy argocd/eso-myapp-production-use1 myapp-production-use1 external-secrets production OutOfSync Healthy ← known false positive argocd/eso-myapp-production-usw2 myapp-production-usw2 external-secrets production OutOfSync Healthy ← known false positive argocd/falco-myapp-dev-use1 myapp-dev-use1 falco production Synced Healthy argocd/falco-myapp-dev-usw2 myapp-dev-usw2 falco production Synced Healthy argocd/falco-myapp-production-use1 myapp-production-use1 falco production Synced Healthy argocd/falco-myapp-production-usw2 myapp-production-usw2 falco production Synced Healthy argocd/falco-myapp-staging-use1 myapp-staging-use1 falco production Synced Healthy argocd/falco-myapp-staging-usw2 myapp-staging-usw2 falco production Synced Healthy argocd/fluent-bit-myapp-dev-use1 myapp-dev-use1 logging production Synced Healthy argocd/fluent-bit-myapp-dev-usw2 myapp-dev-usw2 logging production Synced Healthy argocd/fluent-bit-myapp-production-use1 myapp-production-use1 logging production Synced Healthy argocd/fluent-bit-myapp-production-usw2 myapp-production-usw2 logging production Synced Healthy argocd/fluent-bit-myapp-

DevSecOps Pipeline — Completion Runbook All code is written and pushed to GitHub. This runbook covers the remaining operational steps: Terraform applies, GitOps ARN updates, and ArgoCD deployment. Prerequisites Install these tools if not already present: # AWS CLI v2 winget install Amazon.AWSCLI # Terraform 1.6+ winget install HashiCorp.Terraform # Terragrunt # Download from https://github.com/gruntwork-io/terragrunt/releases # Place in C:\Windows\System32\ or add to PATH # kubectl winget install Kubernetes.kubectl # ArgoCD CLI winget install argoproj.argocd AWS Profile Setup The root terragrunt.hcl uses profiles named myapp-{env}-{region_alias} . Configure them in ~/.aws/config : [profile myapp-production-use1] region = us-east-1 role_arn = arn:aws:iam::591120834781:role/AdministratorAccess source_profile = default [profile myapp-production-usw2] region = us-west-2 role_arn = arn:aws:iam::591120834781:role/AdministratorAccess source_profile = default [profile myapp-staging-use1] region = us-east-1 role_arn = arn:aws:iam::690687753178:role/AdministratorAccess source_profile = default [profile myapp-staging-usw2] region = us-west-2 role_arn = arn:aws:iam::690687753178:role/AdministratorAccess source_profile = default [profile myapp-dev-use1] region = us-east-1 role_arn = arn:aws:iam::557702566877:role/AdministratorAccess source_profile = default [profile myapp-dev-usw2] region = us-west-2 role_arn = arn:aws:iam::557702566877:role/AdministratorAccess source_profile = default PHASE 1 — Terraform Applies Work from the myapp-infra/ directory. Run in the order shown — capture outputs for updating GitOps files in Phase 2. 1.1 WAF (production + staging) # Production us-east-1 terragrunt apply --terragrunt-working-dir live/production/us-east-1/waf # Output → webacl_arn (copy this value) # Production us-west-2 terragrunt apply --terragrunt-working-dir live/production/us-west-2/waf # Output → webacl_arn (copy this value) # Staging (no GitOps ARN needed, but good to have) terra

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.

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

Iron-rich immune cells in the liver may act as sensors for magnetic fields, serving as an internal compass.