R: 0 / I: 0
more here: https://www.schemaapp.com/schema-markup/more-than-markup-not-all-schema-markup-supports-ai-understanding/
schema is more than just templates
most plugins just dump random markup on pages without actually linking anything together. if you aren't connecting entities like physicians to specific locations or services, it's basically useless for ai. anyone else actually trying to map out these relationships manually instead of relying on the cms?more here: https://www.schemaapp.com/schema-markup/more-than-markup-not-all-schema-markup-supports-ai-understanding/
R: 3 / I: 2
>nothing writes that data for you
That's the annoying part of the App Router. You have to manually build these blocks for every single page type. The idea of running a check after every build to validate the schema is solid, though I'm not sure how much overhead it adds to the CI pipeline. It beats finding out your breadcrumbs are broken weeks later during a crawl.
at least it isn't manual testing
link: https://www.freecodecamp.org/news/nextjs-json-ld-structured-data/
next. js app router schema validation
Been thinking about how much more work we're going to have to do with JSON-LD once AI scrapers start relying on it even harder. Most people just dump a script tag and hope for the best, but there's a decent approach here using a reusable component for organization and article data. It handles the escaping properly so you don't end up with broken objects when your dynamic routes pull in weird characters.>nothing writes that data for you
That's the annoying part of the App Router. You have to manually build these blocks for every single page type. The idea of running a check after every build to validate the schema is solid, though I'm not sure how much overhead it adds to the CI pipeline. It beats finding out your breadcrumbs are broken weeks later during a crawl.
at least it isn't manual testing
link: https://www.freecodecamp.org/news/nextjs-json-ld-structured-data/
R: 0 / I: 0
>the stars just disappeared overnight
it's such a pain because the code looks fine at a glance. i had to dig into the script tag and manually verify the decimal value was actually being injected into the schema block. if the widget fails to load or returns a null, the whole property breaks. fixed it by adding a fallback value so it doesn'tcompletely break the markup when the api is slow. now the snippet stays intact even if the widget lags.
missing aggregateRating property in local business schema
been cleaning up a mess for a local cafe all morning. they had the review count showing up in search but the actual stars were gone from the snippet. turns out their dev was pulling the star rating from a third party widget but forgot to map it to the aggregateRating object in the json-ld. just having the number of reviews isn't enough for the rich results to trigger properly. you need both the reviewCount and the explicit ratingValue.>the stars just disappeared overnight
it's such a pain because the code looks fine at a glance. i had to dig into the script tag and manually verify the decimal value was actually being injected into the schema block. if the widget fails to load or returns a null, the whole property breaks. fixed it by adding a fallback value so it doesn't
R: 0 / I: 0
>the page is still technically reachable
doesn't matter if the bot times out before it hits the bottom of the DOM. we're seeing massive latency spikes on these deep links. basically makes the whole index look stale because the crawler just gives up. it's always a third party tracking script
sitefetch delays on large product catalogs
been looking at some crawl logs from a massive ecom client lately. everything looks fine until you hit the deep paginated stuff. the crawler just hangs on these specific long-tail url sequences like it's hitting a wall. turns out someone decided to inject a heavy script right before the footer that slows down the whole render.>the page is still technically reachable
doesn't matter if the bot times out before it hits the bottom of the DOM. we're seeing massive latency spikes on these deep links. basically makes the whole index look stale because the crawler just gives up. it's always a third party tracking script
R: 1 / I: 0
imageof property type mismatch on product schema
I'm seeing some weirdness with how Google Search Console handles nested objects when I try to use an array for the same property. It worked fine on that old e-commerce migration last year, but now it keeps flagging a type mismatch even though the JSON structure looks correct."offers": {"@type": "Offer","price": "29.99"} 
R: 0 / I: 0
>Security isn't something you add to software. It's something you build into it from the beginning.
it's much easier to handle things like encryption standards or field-level masking at the domain layer before the first pull request even exists. if you aren't doing threat modeling during architecture, you're basically just waiting for an incident report to hit your inbox. i don't know how anyone manages to maintain a clean pipeline when they're constantly chasing vulnerabilities in production. it feels like people think 'secure by design' is some magic trick instead of just basic engineering discipline. it's actually just common sense but nobody wants to do the extra work upfront. does anyone here actually get time for a proper threat model before shipping, or are we all just winging it?
found this here: https://www.freecodecamp.org/news/secure-by-design-engineer-security-into-architecture-before-writing-code/
security shouldn't be an afterthought
been thinking about this all morning because i just saw another dev trying to patch cors after the api was already live. it's so exhausting watching teams treat security like a layer you just slap on top of existing code once something breaks. you can't just add it later without breaking everything.>Security isn't something you add to software. It's something you build into it from the beginning.
it's much easier to handle things like encryption standards or field-level masking at the domain layer before the first pull request even exists. if you aren't doing threat modeling during architecture, you're basically just waiting for an incident report to hit your inbox. i don't know how anyone manages to maintain a clean pipeline when they're constantly chasing vulnerabilities in production. it feels like people think 'secure by design' is some magic trick instead of just basic engineering discipline. it's actually just common sense but nobody wants to do the extra work upfront. does anyone here actually get time for a proper threat model before shipping, or are we all just winging it?
found this here: https://www.freecodecamp.org/news/secure-by-design-engineer-security-into-architecture-before-writing-code/
R: 0 / I: 0 totally fine a nightmare for the crawler. if you don't need those assets indexed, just block the specific directory pattern to save some energy. i've been using this snippet to keep the bot away from the heavy library files:
it helps keep the focus on the actual content instead of parsing useless library code. does anyone else still deal with these old mobile scripts hanging around?
disabling jquery mobile via robotstxt for non-essential assets
been seeing way too much crawl budget waste on legacy sites lately. some old enterprise client still has jquery mobile scripts loading deep in their subfolders and it'sUser-agent: *Disallow: /assets/js/jquery-mobile/
it helps keep the focus on the actual content instead of parsing useless library code. does anyone else still deal with these old mobile scripts hanging around?
R: 1 / I: 0
>two weeks of history is enough to notice that something broke on Tuesday. it is not enough to prove that a template change shipped in march is what moved googlebot in may
it's fine for small sites, but i don't see how anyone manages crawl budget waste on a massive marketplace without seeing those long-term patterns. does anyone here actually rely on raw logs for anything besides checking 404 spikes?
more here: https://jetoctopus.com/case-study-large-marketplace/
log files are useless if you can't actually query them
the sheer scale of their logs makes it impossible to do any real analysis without something like JetOctopus. they were only keeping data for 7 to 14 days, which is a joke when you're trying to figure out if a template change from months ago messed up your rankings.>two weeks of history is enough to notice that something broke on Tuesday. it is not enough to prove that a template change shipped in march is what moved googlebot in may
it's fine for small sites, but i don't see how anyone manages crawl budget waste on a massive marketplace without seeing those long-term patterns. does anyone here actually rely on raw logs for anything besides checking 404 spikes?
more here: https://jetoctopus.com/case-study-large-marketplace/
R: 1 / I: 1
more here: https://dev.to/tinali7564eng/aes-gcm-vs-aes-cbc-why-cbc-mode-fails-in-modern-web-apps-galois-counter-architecture-and-14hd
aes-gcm is finally killing cbc
still seeing too many devs using cbc for session tokens and it's asking for a padding oracle attack. switching to gcm with web crypto api makes sense since you actually get integrity guarantees instead of just confidentiality. ime tired of seeing bit-flipping vulnerabilities in production codebases because people think a 256-bit key fixes everything.more here: https://dev.to/tinali7564eng/aes-gcm-vs-aes-cbc-why-cbc-mode-fails-in-modern-web-apps-galois-counter-architecture-and-14hd
R: 0 / I: 0
it's pretty annoying how much people ignore things like host time zones or locale settings until something breaks in production. i've seen too many devs rely on the default jvm behavior instead of just being explicit with ZoneOffset. UTC and stuff like that. does anyone actually bother with reproducible-builds for every single microservice or is it just a pipe dream?
full read: https://dzone.com/articles/works-on-my-machine-architecture
hidden machine dependencies are everywhere
>the developer workstation becomes an undocumented dependencyit's pretty annoying how much people ignore things like host time zones or locale settings until something breaks in production. i've seen too many devs rely on the default jvm behavior instead of just being explicit with ZoneOffset. UTC and stuff like that. does anyone actually bother with reproducible-builds for every single microservice or is it just a pipe dream?
full read: https://dzone.com/articles/works-on-my-machine-architecture
R: 2 / I: 0
it's acting like the sitemap is hitting a different block entirely.
>the crawler just sees a 301 loop and gives up. checked the upstream headers and they look clean, so i'm losing my mind. tried testing with curl but even that returns the same mess. turns out the legacy regex in the main server block is catching them too.
nginx rewrite loop on sitemap urls
stuck in this nightmare with an nginx config change for a client. everything looks fine in the browser but logs show a redirect loop specifically for the xml files. tried stripping the trailing slash rule but it didn't fix anything.location ~* \.xml$ {rewrite ^(.*)/$ $1 permanent;}it's acting like the sitemap is hitting a different block entirely.
>the crawler just sees a 301 loop and gives up. checked the upstream headers and they look clean, so i'm losing my mind. tried testing with curl but even that returns the same mess. turns out the legacy regex in the main server block is catching them too.
R: 0 / I: 0
full read: https://www.infoq.com/news/2026/10/aws-eventbridge-scaling/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
aws eventbridge central bus mess
finally looks like we can stop chaining cross-account rules like some kind of spaghetti nightmare. i'm interested in that synchronous lambda invocation though because it might actually let me scrap the sqs buffer i've been using for everything. anyone tried testing the new deduplication yet?full read: https://www.infoq.com/news/2026/10/aws-eventbridge-scaling/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
R: 3 / I: 2
more here: https://jetoctopus.com/how-to-find-and-fix-your-rich-snippet-gaps/
schema gaps aren't always broken code
It is annoying how much time we spend checking for green ticks in the rich results test while ignoring actual eligibility. We can have perfect JSON-LD on a product page but still lose the price and star rating if the data isn't complete enough for Google. I noticed it also mentioned that FAQ snippets are basically dead now so there is no point in debugging those. The real issue is probably our out of stock items or deep filtered pages where the markup exists but doesn't meet the quality guidelines. We should probably run a wider audit on the catalog instead of just testing single URLs manually. I wonder if we can automate a check for missing required properties across all variants.more here: https://jetoctopus.com/how-to-find-and-fix-your-rich-snippet-gaps/
R: 2 / I: 0
itemscape property mismatch in schema markup
im looking at this client site where they got all their product schemas for different regions but they forgot to sync the itemscape property across the subfolders. it looks fine in the rich results test but google is just ignoring the price data because of the mismatch. if u dont match the exact same value in every single schema block on the site, its basically useless. check your url strings very carefully before deploying. had to rewrite a massive loop for them because they were pulling dynamic values that changed slightly per locale. it took me three hours to find one extra space
R: 0 / I: 0
don't just keep nesting empty spans for the sake of it. keep the markup lean. i saw a site yesterday with three levels of nested divs just to show a single bullet point. it's honestly painful to look at. does anyone else actually bother auditing the DOM depth for lcp or do you just ignore it and hope for the best?
css content property for hidden decorative elements
was messing with a client's lcp scores today because their devs love adding unnecessary div wrappers for simple icons. it's driving me crazy. if you can move that decoration into the css, do it. i've been using the content property on pseudo-elements to keep the DOM clean and avoid extra nodes that bloat the render tree. it's a small win but helps when you're fighting for every millisecond of main thread time..icon-marker::before {content: "";display: inline-block;width: 12px;height: 12px;background-color: #ff0000;}don't just keep nesting empty spans for the sake of it. keep the markup lean. i saw a site yesterday with three levels of nested divs just to show a single bullet point. it's honestly painful to look at. does anyone else actually bother auditing the DOM depth for lcp or do you just ignore it and hope for the best?
R: 0 / I: 0
more here: https://github.blog/ai-and-ml/github-copilot/github-copilot-app-for-beginners-how-to-teach-copilot-about-your-codebase/
copilot custom instructions are getting weird
another day of microsoft trying to make their ai act like a senior dev. now you can apparently feed it custom instructions and skills for your repo so it actually knows what it is looking at. they are pushing this mcp server thing too, using playwright to let the agent crawl stuff or whatever. sounds great until you realize how much garbage context you end up bloating the prompt with. i tried adding some basic repo rules last week and it just hallucinated more than usual. if we start connecting every tool via mcp it is just going to be a nightmare for latency and debugging. plus the security implications of letting an agent run playwright on your codebase are not even funny. probably just another way to make developers lazier while paying a monthly subscription. i doubt this actually helps with complex logic without breaking something else in the process.more here: https://github.blog/ai-and-ml/github-copilot/github-copilot-app-for-beginners-how-to-teach-copilot-about-your-codebase/
R: 3 / I: 2
>managing crawl budget, rendering considerations, and large-scale debugging
it's basically just a repackaged version of what's already in the docs.
article: https://developers.google.com/search/blog/2026/10/seo-learning-paths
google's grouping their youtube tutorials
google is finally trying to organize all that search central chaos into actual playlists instead of just dumping videos in a pile. they're even promising deep dives on crawl budget optimization and rendering stuff, but it'll probably just be the same old advice we've seen for years.>managing crawl budget, rendering considerations, and large-scale debugging
it's basically just a repackaged version of what's already in the docs.
article: https://developers.google.com/search/blog/2026/10/seo-learning-paths
R: 1 / I: 0
>35% of generated code reaches production before the team has fully understood it
it's basically a disaster waiting to happen once you hit complex systems and start dealing with hallucinations in root-cause analysis. im pretty sure we're just building technical debt mountains now.
link: https://www.infoq.com/news/2026/10/survey-complex-codebases-agents/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
debugging debt from ai coding agents
im seeing this all over. engineers are spending nearly 17 hours a week just fixing bugs because nobody actually understands what the ai wrote.>35% of generated code reaches production before the team has fully understood it
it's basically a disaster waiting to happen once you hit complex systems and start dealing with hallucinations in root-cause analysis. im pretty sure we're just building technical debt mountains now.
link: https://www.infoq.com/news/2026/10/survey-complex-codebases-agents/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
R: 0 / I: 0 helpful overkill for most simple builds.
found this here: https://hackernoon.com/agent-memory-is-an-architecture-decision-from-mcp-servers-to-stateful-agents?source=rss
agent memory isn't just about storage
it's annoying how most people treat mcp like it's some magic memory layer when it's really just an interface. you can't just swap mem0 for graphiti and expect things to work because the integration boundary changes everything. i'm still not sure if separating retain, recall, and reflect is actuallyfound this here: https://hackernoon.com/agent-memory-is-an-architecture-decision-from-mcp-servers-to-stateful-agents?source=rss
R: 2 / I: 1
link: https://www.screamingfrog.co.uk/blog/brightonseo-october-26/
screaming frog at brightonseo again
the screaming frog crew is setting up shop at booth 18 for the october brightonseo event. they're doing that beer mat coloring thing again to win a one year spider license. honestly sounds like a lot of work just to get some software. it's fine if you want to talk about feature requests or the new log file analyser updates but i'm not sure about the greenseo stuff on wednesday. reducing environmental impact via seo is such a niche concept that it feels a bit performative. they're also handing out two week trials of the spider and the log file tool if you happen to wander by. i'll probably skip the coloring contest though. just seems like something for people with way too much free time between crawls. anyone actually planning on going down to brighton this time?link: https://www.screamingfrog.co.uk/blog/brightonseo-october-26/
R: 3 / I: 2
>redirect chain hell
it's making the actual important pages take forever to get indexed properly.
anyone else seeing a massive spike in crawl errors after cleaning up these legacy redirects?
googlebot crawl budget waste on large resource redirects
been digging through some server logs today and it's a total disaster. we've got thousands of old urls just sitting there redirecting to current paths, which is eating up way too much of the crawl budget for no reason.>redirect chain hell
it's making the actual important pages take forever to get indexed properly.
http 301 /old-category/product-ahttp 301 /new-category/product-a
anyone else seeing a massive spike in crawl errors after cleaning up these legacy redirects?
R: 3 / I: 1
>most teams have no idea which ai bots visit their site, which pages those bots actually reach or whether the crawler seen in the logs is the real GPTBot or something wearing its user-agent as a mask
im already dealing with enough spoofed traffic without having to cross-reference vendor ip ranges just to see if claude is actually crawling us. jetoctopus claims it handles the filtering but i'd rather not pay for another subscription just to find out our logs are bloated with junk.
more here: https://jetoctopus.com/how-to-track-ai-crawler-activity/
parsing logs for gptbot is a nightmare
another day of digging through server logs because ga is useless for this stuff. apparently 67% of gptbot hits are just hitting 404s which is such a waste of crawl budget.>most teams have no idea which ai bots visit their site, which pages those bots actually reach or whether the crawler seen in the logs is the real GPTBot or something wearing its user-agent as a mask
im already dealing with enough spoofed traffic without having to cross-reference vendor ip ranges just to see if claude is actually crawling us. jetoctopus claims it handles the filtering but i'd rather not pay for another subscription just to find out our logs are bloated with junk.
more here: https://jetoctopus.com/how-to-track-ai-crawler-activity/
R: 1 / I: 0
>stop recording new measurements on november 1st
it's not like we haven't been dealing with inp for a while, but it's weird seeing them officially drop the old metric from speed insights. i'm curious if anyone's actually seeing their real experience score fluctuate because of this.
link: https://vercel.com/changelog/speed-insights-deprecates-first-input-delay-on-november-first
fid is finally dead
google's pulling the plug on fid starting november 1st. they're just leaning into inp for everything now.>stop recording new measurements on november 1st
it's not like we haven't been dealing with inp for a while, but it's weird seeing them officially drop the old metric from speed insights. i'm curious if anyone's actually seeing their real experience score fluctuate because of this.
link: https://vercel.com/changelog/speed-insights-deprecates-first-input-delay-on-november-first
R: 3 / I: 0 optimized broken again.
unnecessary lcp element shifts from font-display swap
staring at these reports is killing me. some dev pushed a change to google fonts that's causing massive layout jumps because they forgot to set the proper fallback.
R: 0 / I: 0
json-ld breadcrumblist id mismatches
been looking at some client logs today and noticed the breadcrumb hierarchy is totally broken in search results. someone went ahead and changed the url structure without updating the @id references in the schema. now it's just pointing to old dead links that don't even exist anymore. it's such a stupid mistake because the markup looks fine at first glance if you aren't checking the actual fragments. i'm seeing this happen way too often with large e-commerce sites moving to new category slugs. don't skip the id validation when you're doing a site migration. anyone else running into broken references after recent cms updates?
R: 3 / I: 1
sitebulb vs screaming frog for lcp audit
im tired of manually checking every single url for lcp issues. screaming frog is fine if u just want raw data but it basically misses the context of how things actually render. sitebulb is way better for spotting when a huge hero image is causing the delay because its much more visual with the screenshots. i was looking at this one client site where the lcp was tanking and frogs logs didnt show anything weird. then i ran it through sitebulb and saw exactly how the lazy loading was breaking on mobile. turns out the css was just messed up.
R: 0 / I: 0
https://hackernoon.com/middleware-an-architecture-pattern-across-stacks-and-frameworks?source=rss
patterns in redux and fastapi
saw some stuff about how middleware is basically the same logic everywhere. it's just that one function taking a request and calling next. seen this with 'koa' too where they use it for x-response-time headers. im tired of devs pretending like every framework invented its own unique way to wrap a process when it's just __reused patterns_https://hackernoon.com/middleware-an-architecture-pattern-across-stacks-and-frameworks?source=rss
R: 3 / I: 1
>The delivery system should prevent them from progressing.
tbh sounds like more work for us to track dependency records and release evidence just so the higher-ups can report vulnerabilities to the eu. it's gonna be a mess trying to move everything from 'ad hoc' to 'enforced' without breaking our current build flow
article: https://thenewstack.io/cra-readiness-starts-codebase/
cra compliance is gonna be a headache for devops
another layer of bureaucracy hitting our pipelines by december 2027. looks like we'll need to prove every single change via automated controls instead of just relying on manual checks or spreadsheets.>The delivery system should prevent them from progressing.
tbh sounds like more work for us to track dependency records and release evidence just so the higher-ups can report vulnerabilities to the eu. it's gonna be a mess trying to move everything from 'ad hoc' to 'enforced' without breaking our current build flow
article: https://thenewstack.io/cra-readiness-starts-codebase/
R: 0 / I: 0
> [Folded 18 imports: React, Lucide-React, Lodash]
looks fine for javascript but i'm skeptical about the python stuff. if it messes up any indentation or breaks the whitespace in yaml files then it's useless to me. they claim it uses some 'syntax boundary snapping' so it won't break the tree but regex-based folding always ends up breaking something weird when you have complex decorators or multiline strings. i've seen enough broken builds from "smart" automation to not trust this blindly. probably just another way to save a few bucks on context windows while introducing subtle bugs into the codebase. might be worth a look if it actually handles function signatures right without losing the actual logic.
found this here: https://dev.to/vansharora21/how-tokencap-folds-repetitive-imports-without-breaking-code-syntax-1gpa
tokencap's import folding is basically just more magic middleware
another tool to add to the pile. saw this tokencap thing trying to shrink repo snapshots by stripping out all those massive import lists. supposedly it can hit a 58% reduction on raw volume by using some sort of 'import clustering'.> [Folded 18 imports: React, Lucide-React, Lodash]
looks fine for javascript but i'm skeptical about the python stuff. if it messes up any indentation or breaks the whitespace in yaml files then it's useless to me. they claim it uses some 'syntax boundary snapping' so it won't break the tree but regex-based folding always ends up breaking something weird when you have complex decorators or multiline strings. i've seen enough broken builds from "smart" automation to not trust this blindly. probably just another way to save a few bucks on context windows while introducing subtle bugs into the codebase. might be worth a look if it actually handles function signatures right without losing the actual logic.
found this here: https://dev.to/vansharora21/how-tokencap-folds-repetitive-imports-without-breaking-code-syntax-1gpa
R: 1 / I: 1 useful extra cleanup work. the whole point is to get same results with less effort, not more bloat. the dashboard counted the cleanup as output too. ime seeing this everywhere lately.
https://dzone.com/articles/ai-productivity-code-production-myths
vanity metrics for ai dev are trash
just saw a post about some team celebrating 40% more code per sprint because of ai tools. it's always the same story with these dashboards. they were getting all these broken try-catch blocks inline that basically swallowed exceptions and killed their centralized handler. i've seen this exact mess in crawl logs when people just dump junk schema into a template without checking anything. developers are producing more lines but it's mostly justhttps://dzone.com/articles/ai-productivity-code-production-myths
R: 0 / I: 0
>The gap is written in one sentence, and each criterion has a way to measure it
sounds like a lot ofeffort theater just to see if qodo actually catches anything useful. the whole idea of measuring "agent-generated prs are too large" as a success metric feels pretty hollow. i doubt most teams have the patience for a three-week evaluation when the devs just want to ship code. lol.
link: https://hackernoon.com/how-to-run-an-ai-code-review-poc-a-step-by-step-walkthrough?source=rss
ai code review trials are a mess
another guide on how to run a "proper" ai code review poc without failing immediately. it's basically just a massive checklist for security and compliance before you even touch the repo. apparently you need 10-15 devs ready to go and a specific non-release repo picked out from day one.>The gap is written in one sentence, and each criterion has a way to measure it
sounds like a lot of
link: https://hackernoon.com/how-to-run-an-ai-code-review-poc-a-step-by-step-walkthrough?source=rss
R: 1 / I: 1
>the agent interprets your business, decides what information is relevant, and determines how to respond to the user's request
it's basically turning seo into pure machine-readable data management. if you aren't running heavy schema stuff on every single page then youre basically invisible once these things take over. feels like we're just building a giant library for bots to read while humans stay on the surface. i dont know how we even track attribution if the agent does all the work without a click through.
full read: https://www.schemaapp.com/schema-markup/preparing-for-the-agentic-web-key-insights-from-rv-guha-and-schema-app/
schema. org is basically our only hope for agents
rv guha was talking about this stuff again and it's wild to think we're moving into a fourth major shift after mobile and rss. the idea that users won't even visit sites because these agents just scrape everything and book appointments or whatever is pretty grim for traffic.>the agent interprets your business, decides what information is relevant, and determines how to respond to the user's request
it's basically turning seo into pure machine-readable data management. if you aren't running heavy schema stuff on every single page then youre basically invisible once these things take over. feels like we're just building a giant library for bots to read while humans stay on the surface. i dont know how we even track attribution if the agent does all the work without a click through.
full read: https://www.schemaapp.com/schema-markup/preparing-for-the-agentic-web-key-insights-from-rv-guha-and-schema-app/
R: 3 / I: 0
>if you only feed the AI with functional requirements, the AI isn't somehow going to make sure the architecture is sound.
ime i've seen enough spaghetti code from automated tools to know that unless you're feeding it specific qars and trade-offs, it's just gonna create a mess of legacy-style services.
full read: https://www.infoq.com/articles/ai-agents-improve-software-architecture/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
ai agents for mva and architecture
another way to bloat the stack. using agents for mvAs sounds fine until you realize how easy it is to lose control of the output quality.>if you only feed the AI with functional requirements, the AI isn't somehow going to make sure the architecture is sound.
ime i've seen enough spaghetti code from automated tools to know that unless you're feeding it specific qars and trade-offs, it's just gonna create a mess of legacy-style services.
full read: https://www.infoq.com/articles/ai-agents-improve-software-architecture/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
R: 0 / I: 0
>Most "RAG over PDFs" pipelines have a step nobody talks about much: something has to turn a scanned invoice, a multi-column contract, or a photographed receipt into text a model can actually reason over.
it seems like a lot of the heavy lifting is just managing those long-running operations with the poller, which sounds like a fun way to introduce latency if you aren't careful. i wonder how much the classifiers actually help when you're hitting it with a huge mix of unknown document types at once?
article: https://dzone.com/articles/microsoft-foundry-document-intelligence-sdk
microsoft's doc intelligence sdk is actually kinda interesting
i was reading up on using Document Intelligence SDK to clean up those messy pdf inputs for rag pipelines since getting actual structured data out of a scanned invoice or receipt is such a headache. it's pretty cool how they have these prebuilt models like prebuilt-layout that can just spit out markdown, but i'm skeptical about the effort needed for custom extraction when you're dealing with weirdly formatted templates.>Most "RAG over PDFs" pipelines have a step nobody talks about much: something has to turn a scanned invoice, a multi-column contract, or a photographed receipt into text a model can actually reason over.
it seems like a lot of the heavy lifting is just managing those long-running operations with the poller, which sounds like a fun way to introduce latency if you aren't careful. i wonder how much the classifiers actually help when you're hitting it with a huge mix of unknown document types at once?
article: https://dzone.com/articles/microsoft-foundry-document-intelligence-sdk
R: 1 / I: 0
it's a tiny change but it actually works when the main thread is busy. anyone else seeing huge delays on mobile despite having a good server response time?
speculative preloading for lcp images
was staring at some terrible lcp numbers on a client site today. they're loading every single image in the gallery with priority instead of just the top one. if you don't usefetchpriority="high"on that first hero image, you're basically asking for a bad core web vitals score.
<img src="/hero.jpg" fetchpriority="high" alt="main banner">
it's a tiny change but it actually works when the main thread is busy. anyone else seeing huge delays on mobile despite having a good server response time?
R: 2 / I: 0
>hand them over a fix already mapped
sounds cool but honestly sounds like more work for the dev team if we just dump a massive list of automated recommendations on them without checking first.
https://jetoctopus.com/top-technical-seo-tools-for-agencies/
agency tool bloat is getting ridiculous
im so tired of seeing agencies just add random subscriptions every time someone hires a new lead or a client asks for something weird. saw this bit about jetoctopus tracking what ai bots actually see and how it maps fixes directly to logs>hand them over a fix already mapped
sounds cool but honestly sounds like more work for the dev team if we just dump a massive list of automated recommendations on them without checking first.
https://jetoctopus.com/top-technical-seo-tools-for-agencies/
R: 1 / I: 0
>Every prompt is an egress point.
It's easy to say we need access controls, but how do you actually audit free-text prompts for leaks in real time? I'm not seeing any actual proof that these architecture patterns work once you scale up RAG or agentic workflows beyond a small test group. There are way too many uncontrolled variables here to think a layered defense is enough without seeing some long-term testing data.
https://dzone.com/articles/enterprise-ai-data-security
enterprise ai security feels like a lot of hand-waving
The idea that we can just rely on data classification and prompt hygiene to stop sensitive info from leaking through an API is pretty optimistic.>Every prompt is an egress point.
It's easy to say we need access controls, but how do you actually audit free-text prompts for leaks in real time? I'm not seeing any actual proof that these architecture patterns work once you scale up RAG or agentic workflows beyond a small test group. There are way too many uncontrolled variables here to think a layered defense is enough without seeing some long-term testing data.
https://dzone.com/articles/enterprise-ai-data-security
R: 1 / I: 1
>It's built for crawling websites with anti-scraping measures through pace.
instant results takes several days if the site is big and it still won't touch anything with actual tls fingerprinting or js challenges.
link: https://jetoctopus.com/seo-competitive-analysis-in-jetoctopus/
jetoctopus stealth mode is basically just rate limiting
another way to waste time.>It's built for crawling websites with anti-scraping measures through pace.
link: https://jetoctopus.com/seo-competitive-analysis-in-jetoctopus/
R: 0 / I: 0
JSON-LD fragmenting in large paginated lists
I am seeing some weirdness with how Google picks up the breadcrumb schema when it is injected via a client side script after the initial HTML load. I tried moving the script to the head and even hardcoding the first few items into the server side template, but the rich results keep dropping off on page five and beyond.
R: 3 / I: 2
article: https://www.debugbear.com/blog/excessive-preconnect-hints
preconnect bloat isnt as bad as everyone says
seeing all these preconnect hints everywhere and people freaking out about lcp is getting old. apparently it only really hits you when you're on a cripplingly slow connection like 0.1 mbps. anything beyond the first few hints doesn't even move the needle much, so i don't see why we bother stressing over every single third-party origin.article: https://www.debugbear.com/blog/excessive-preconnect-hints
R: 3 / I: 1
don't forget to update the count on every new submission or google's just gonna flag it as fake data. anyone else still doing this via a python script?
product snippet for aggregate rating schema
i'm tired of seeing people manually hardcode every single review into their json-ld. if you've got a dynamic list, just pull the counts and averages from your database into this structure instead."aggregateRating": {"@type": "AggregateRating","ratingValue": "4.8","reviewCount": "124"}don't forget to update the count on every new submission or google's just gonna flag it as fake data. anyone else still doing this via a python script?
R: 0 / I: 0
just hardcode the dimensions in the html. it doesn't matter if your css makes it responsive with width: 100% and height: auto. the browser needs those intrinsic dimensions to reserve the space. i've seen too many devs skip this because they think modern browsers are smart enough. they aren't.
>modern browsers handle layout automatically is a lie. it's just more work for us when gsc starts reporting massive cls spikes. use the attributes or stop complaining about core web vitals scores.ignore it fix it.
image dimensions in search console errors
client's site was getting flagged for missing width/height attributes on every single image. chrome devtools shows it fine but gsc is still screaming about layout shifts. people think it's just a css issue. it isn't. if the browser doesn't know the aspect ratio before the pixels load, you're dead. i checked the srcsets and they were basically useless for preventing cls. found this fix for their template engine.<img src="image.jpg"width="800"height="600"alt="description">
just hardcode the dimensions in the html. it doesn't matter if your css makes it responsive with width: 100% and height: auto. the browser needs those intrinsic dimensions to reserve the space. i've seen too many devs skip this because they think modern browsers are smart enough. they aren't.
>modern browsers handle layout automatically is a lie. it's just more work for us when gsc starts reporting massive cls spikes. use the attributes or stop complaining about core web vitals scores.
R: 0 / I: 0 deleting erasing the only way knowledge moves around a team. i can't imagine how people are supposed to maintain anything when 31% of merges are happening with zero human eyes on them. it feels like we're just trading understanding for pure velocity. anyone actually managing to keep their head above water without checking every single line?
more here: https://thenewstack.io/kill-code-review-theater/
code review is for learning not just bug hunting
saw some stats that incidents per pr are up over 240% lately. it's pretty wild because everyone thinks ai helps with speed but it's clearly just making things more unstable. the whole point of reviews isn't even about catching errors, it's mostly just so we don't lose the mental model of how the system actually works. if you stop reading diffs and just rely on 'swiss cheese' layers like agents and linters, you're basicallymore here: https://thenewstack.io/kill-code-review-theater/
R: 1 / I: 1
>The layout shifts every time the fallback font loads
It'sfine a nightmare for anyone actually trying to pass the audits.
CLS issues with font-display swap
Changing my CSS tofont-display: swapis killing my CLS on pages with heavy custom typography.
>The layout shifts every time the fallback font loads
It's
R: 3 / I: 1
>we must also consider that a necessary condition for being cited
it's the same old crawlability garbage we've been dealing with for years. just because they call it a response engine doesn't mean the fundamentals are different. if the structured data is trash, you aren't getting cited regardless of what you call it. im pretty sure most of these "new" tactics are just basic semantic markup.
full read: https://www.debugbear.com/blog/technical-seo-checklist
geo is just seo with a fancy name
another day, another buzzword. people are calling it generative engine optimization now like that changes anything. im seeing all this talk about making sure html isn't dependent on javascript just so claude or perplexity can read it.>we must also consider that a necessary condition for being cited
it's the same old crawlability garbage we've been dealing with for years. just because they call it a response engine doesn't mean the fundamentals are different. if the structured data is trash, you aren't getting cited regardless of what you call it. im pretty sure most of these "new" tactics are just basic semantic markup.
full read: https://www.debugbear.com/blog/technical-seo-checklist
R: 2 / I: 0
https://www.screamingfrog.co.uk/blog/the-brightonseo-crawling-clinic-april-may-26/
screaming frog at brightonseo again
the frog team's heading to stand 18 for the next brightonseo. they're pushing those two-week trials for SEO Spider and the log file analyser, which is fine but i've already got plenty of licenses lying around. seeing all that talk about green seo lately makes me wonder if they'll actually show any real tech updates or just more merch. at this rate, i'll just be collecting another branded water bottle.https://www.screamingfrog.co.uk/blog/the-brightonseo-crawling-clinic-april-may-26/
R: 3 / I: 0
full read: https://dzone.com/articles/claude-enterprise-integration
claude code for log triage
piping raw logs into claude -p to flag failed payloads sounds great until you realize how much junk my plumber client's site spits out. i'm skeptical about using a CLAUDE.md file to act as the single source of truth for architecture when half my devs don't even document their own simple css changes.full read: https://dzone.com/articles/claude-enterprise-integration
R: 3 / I: 0
>the actual logic behind content categorisation and the architectural decisions made at a business level
using screaming frog and some python scripts to build a visual tree model sounds fine, but i doubt it'll work for my current client with their broken schema. it's probably just more manual cleanup for us
found this here: https://www.screamingfrog.co.uk/blog/reconstructing-site-architecture-using-breadcrumbs/
using breadcrumbs to map site structure
breadcrumbs are a decent shortcut for mapping large ecom sites when url folders are a mess. i'm tired of squinting at crawl depth or internal linking graphs just to find the real logic behind some bloated category tree.>the actual logic behind content categorisation and the architectural decisions made at a business level
using screaming frog and some python scripts to build a visual tree model sounds fine, but i doubt it'll work for my current client with their broken schema. it's probably just more manual cleanup for us
found this here: https://www.screamingfrog.co.uk/blog/reconstructing-site-architecture-using-breadcrumbs/
R: 1 / I: 1
>connecting their relationships across your website
it's not just about having a recipe or product tag on a page anymore. wells fargo supposedly fixed an inaccurate overview in hours by using this 'content knowledge graph' stuff to link entities. i don't know if i'm ready to commit to that level of semantic infrastructure for a client site. it sounds like a nightmare to maintain
link: https://www.schemaapp.com/schema-markup/not-all-schema-markup-is-equal-for-supporting-ai-responses/
schema isn't all the same for ai
everyone's acting like schema is useless because some studies show zero correlation with citations, but they're ignoring the actual connection part.>connecting their relationships across your website
it's not just about having a recipe or product tag on a page anymore. wells fargo supposedly fixed an inaccurate overview in hours by using this 'content knowledge graph' stuff to link entities. i don't know if i'm ready to commit to that level of semantic infrastructure for a client site. it sounds like a nightmare to maintain
link: https://www.schemaapp.com/schema-markup/not-all-schema-markup-is-equal-for-supporting-ai-responses/
R: 0 / I: 0
>aim to keep the hero image under 180kb
imo if you can't get your assets under that limit, your dev team islazy incompetent. i'm still seeing way too many background videos killing the initial render.
full read: https://www.debugbear.com/blog/shopify-speed-optimization
shopify hero section bloat
seeing another guide obsessing over lcp scores is exhausting. most people just dump 900kb images in the header and wonder why it's laggy.>aim to keep the hero image under 180kb
imo if you can't get your assets under that limit, your dev team is
full read: https://www.debugbear.com/blog/shopify-speed-optimization
R: 0 / I: 0
>Marketing: Assessing high-level UX and SEO performance
it's always easy to blame the devs when the crux metrics tank because of some new tracking pixel. how do you guys actually stop the marketing side from breaking your lcp?
link: https://www.debugbear.com/blog/marketing-dev-collaboration
marketing vs dev speed wars
marketing loves dropping third-party scripts and heavy assets without checking anything first.>Marketing: Assessing high-level UX and SEO performance
it's always easy to blame the devs when the crux metrics tank because of some new tracking pixel. how do you guys actually stop the marketing side from breaking your lcp?
link: https://www.debugbear.com/blog/marketing-dev-collaboration
R: 3 / I: 1
LCP issues with large hero images on mobile
Found another site where the LCP is tanking because they're serving the same huge desktop-sized image to everyone. Try testing your current hero setup by forcing a smallersrcsetfor mobile viewports and see if it actually moves the needle in your lab tests.
R: 3 / I: 0
>Coding makes up only 16 percent of a developer's time
Sounds about right, most of my day is just digging through Jira or tracing microservices when something breaks. The idea that 64 percent of orgs are already generating most of their code with AI feels like a massive stretch for any codebase with real legacy debt. It's fine for boilerplate but I don't see it handling complex system design anytime soon. Still, if it can automate the documentation part, i'm not complaining.
full read: https://hackernoon.com/ai-assisted-software-development-at-scale-from-code-generation-to-engineering-agents?source=rss
coding is barely 16 percent of our week
Spent way too much time reading about how we're basically just orchestrating agents now instead of actually building things. It claims we lose more than 8 hours a week just to fragmented workflows and context switching.>Coding makes up only 16 percent of a developer's time
Sounds about right, most of my day is just digging through Jira or tracing microservices when something breaks. The idea that 64 percent of orgs are already generating most of their code with AI feels like a massive stretch for any codebase with real legacy debt. It's fine for boilerplate but I don't see it handling complex system design anytime soon. Still, if it can automate the documentation part, i'm not complaining.
full read: https://hackernoon.com/ai-assisted-software-development-at-scale-from-code-generation-to-engineering-agents?source=rss
R: 0 / I: 0
link: https://dzone.com/articles/mcp-production-guide
mcp might actually fix this mess
finally sounds like someone gets how much i hate writing custom function schemas for every single provider. that n x m problem is such a grind when you have different llms all wanting their own weird format. seeing json-rpc 2.0 used as the backbone makes sense though. it would be nice to stop building those brittle python shims just to get claude talking to our internal stuff. still dont know how oauth 2.1 is gonna play out with all the scaling issues in production. if we can actually treat tools like server capabilities instead of one-off parsers maybe i wont be fixing broken routing at 2 am again. hope it isnt just more hype for the sake of hype.link: https://dzone.com/articles/mcp-production-guide
R: 0 / I: 0
more here: https://tkdodo.eu/blog/the-vertical-codebase
organizing by type is a trap
i was just looking at this and it's spot on about how grouping everything by hooks or utils is such a mess once you actually scale. seeing that sentry example with 200 files sitting in one single components directory really hit home because i've been there. it makes no sense to have usetheme sitting right next to usetodo when they have nothing to do with each other. the whole horizontal split is basically just laziness for when you're starting a project. once you get enough domain logic, you can't even find anything without searching the whole tree. it's fine if you think ai agents are gonna rewrite your entire tech debt away next weekend, but that's not how real production code works. do you guys actually use domain folders or are you still stuck in the same folder nightmare?more here: https://tkdodo.eu/blog/the-vertical-codebase
R: 3 / I: 3
more here: https://hackernoon.com/debugging-intermittent-kong-503s-when-the-logs-showed-nothing-but-the-status-code?source=rss
kong 503s aren't always your upstream's fault
finally seeing some clarity on those random kong 503 errors that drive everyone crazy. it's pretty annoying how the logs show nothing but the status code while everything looks fine in the upstream. turns out the ring-balancer can just fail to pick a peer if things are messy. specifically, they were tracking down nginx worker restarts inside the pod. it's wild how one worker can be crashing while the other stays up and keeps the pod looking healthy to basic checks. they had to look at the lua vm memory metrics to actually find the pattern. i've definitely blamed my services for 503s that were actually just gateway-side resource pressure. it makes you wonder if we're missing similar gaps in our own k8s monitoring. does anyone here actually monitor nginx worker lifecycle or do you just trust the pod status?more here: https://hackernoon.com/debugging-intermittent-kong-503s-when-the-logs-showed-nothing-but-the-status-code?source=rss
R: 0 / I: 0
> The best configuration achieves 20% recall - meaning 80% of expert-identified issues go unfound.
imo that's basically useless for anything complex since it misses so much architecture context. hard to see how this helps when you can't even trust it to find cross-file bugs.
https://www.infoq.com/news/2026/09/alibaba-opencodereview/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
alibaba's opencodereview is mostly just fancy regex
alibaba is trying to hype up OpenCodeReview by saying it uses 1/9th the tokens of Claude Code. looks like a lot of deterministic pipelines just to avoid the ai hallucinating on simple stuff like null pointers.> The best configuration achieves 20% recall - meaning 80% of expert-identified issues go unfound.
imo that's basically useless for anything complex since it misses so much architecture context. hard to see how this helps when you can't even trust it to find cross-file bugs.
https://www.infoq.com/news/2026/09/alibaba-opencodereview/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
R: 1 / I: 1
>Your data doesn't exist in isolation.
it's so true though. if you don't get the blueprint right at the start, you're basically just building a house on sand. it's not even about the tool itself, like whether you're using 'postgresql' or something else, it's about how you model the domain. i've seen too many people treat the database as a black box and then wonder why their transactions are corrupting mid-stream. never skip the planning phase if you actually want to scale. does anyone here actually prefer the flexibility of document stores for anything beyond simple logging?
found this here: https://hackernoon.com/a-developers-guide-to-database-architecture-and-performance-fundamentals?source=rss
db schema mistakes are such a headache
been thinking about this all morning because i just saw another dev trying to shove everything into flat json files like it's some kind of hack. it's fine for a tiny prototype but once you hit 500 concurrent users things go south fast. people act like mongodb is the magic fix for everything but you lose all those safety guarantees when you ditch the schema. i saw this point about how missing relationships between categories and subcategories just forces you to write these nightmare queries later on.>Your data doesn't exist in isolation.
it's so true though. if you don't get the blueprint right at the start, you're basically just building a house on sand. it's not even about the tool itself, like whether you're using 'postgresql' or something else, it's about how you model the domain. i've seen too many people treat the database as a black box and then wonder why their transactions are corrupting mid-stream. never skip the planning phase if you actually want to scale. does anyone here actually prefer the flexibility of document stores for anything beyond simple logging?
found this here: https://hackernoon.com/a-developers-guide-to-database-architecture-and-performance-fundamentals?source=rss
R: 2 / I: 0
more here: https://www.freecodecamp.org/news/catch-security-vulnerabilities-code-pull-requests/
pre-commit security hooks for catching leaks early
I was just reading through some stuff on shifting security left to avoid that whole cycle of fixing things during a PR review. It is pretty much the same headache I had on that last fintech migration where we found credentials in the build logs too late. Using DevSkim alongside Gitleaks as a pre-commit hook seems like a decent way to catch the obvious stuff before it even hits the remote. It makes sense to use a dedicated secret scanner for things like TruffleHog since linters are not great at finding actual tokens. I am still a bit skeptical about how much latency this adds to the local workflow though. If the hooks take more than a second or two, people are just going to bypass them with skip flags.more here: https://www.freecodecamp.org/news/catch-security-vulnerabilities-code-pull-requests/
R: 0 / I: 0
>a page can rank on Google yet be invisible to ChatGPT
that's a nightmare for anyone running heavy js front-ends. i don't really care about crawl budget unless we're talking over a million pages anyway, but fixing the rendering waterfall is becoming a massive pain. it's all about that 'ai visibility' layer now. if you aren't checking your server-rendered html against what the bots actually see, you're just guessing. also, seeing people still obsessing over lab scores instead of field data like lcp or inp is exhausting. it's always the cls for me. does anyone actually have a reliable way to track those ai bot fan-outs without losing their mind?
more here: https://jetoctopus.com/technical-seo-audit-a-step-by-step-framework/
ai visibility is getting weird
the whole thing about ai crawlers being 28% of googlebot volume is kind of wild to think about. i've been seeing so many more requests in my logs lately that don't look like the usual suspects. it's not just about indexing anymore since if the raw html doesn't render right, chatgpt basically ignores you.>a page can rank on Google yet be invisible to ChatGPT
that's a nightmare for anyone running heavy js front-ends. i don't really care about crawl budget unless we're talking over a million pages anyway, but fixing the rendering waterfall is becoming a massive pain. it's all about that 'ai visibility' layer now. if you aren't checking your server-rendered html against what the bots actually see, you're just guessing. also, seeing people still obsessing over lab scores instead of field data like lcp or inp is exhausting. it's always the cls for me. does anyone actually have a reliable way to track those ai bot fan-outs without losing their mind?
more here: https://jetoctopus.com/technical-seo-audit-a-step-by-step-framework/
R: 2 / I: 1
article: https://dev.to/kiani_e55ae9c94c3f8e86abf/how-i-built-an-offline-ai-powered-html-to-wordpress-theme-generator-1ld
local ai for converting html to wordpress themes
finally someone's doing something useful with gemma 2b instead of just making poems. i saw this setup using rag to map out components like nav and hero sections without needing some massive cloud api. it's supposedly all offline so you don't have to worry about sending your source code to a third party. the idea is to just point it at a folder and let it spit out a full zip with the functions.php and style.css already handled. i'm skeptical about how it handles complex js or deeply nested div structures though. if the parsing fails, you're still stuck manually fixing the template parts anyway. does anyone know if this actually works for messy legacy markup?article: https://dev.to/kiani_e55ae9c94c3f8e86abf/how-i-built-an-offline-ai-powered-html-to-wordpress-theme-generator-1ld
R: 1 / I: 1
>A UI that shows a number without its provenance is quietly asserting that all of its data is equally fresh.
The idea of forcing an ISO timestamp into every single record across 83 sources sounds like a nightmare to maintain if the upstream formats change constantly. I'd probably just add a last_updated field to the base object and call it a day. **Still better than showing wrong data
https://dzone.com/articles/freshness-first-class-schema-concern
making freshness a schema field instead of just UI copy
Finally seeing someone treat data staleness as a backend problem rather than something for the frontend to just mask with a disclaimer. It's annoying when you're looking at a dashboard and have no idea if a metric is from this morning or some random survey from 2010. This setup uses three different shapes for the ingest, like using GitHub Actions cron jobs for the daily NOAA thermal stress updates.>A UI that shows a number without its provenance is quietly asserting that all of its data is equally fresh.
The idea of forcing an ISO timestamp into every single record across 83 sources sounds like a nightmare to maintain if the upstream formats change constantly. I'd probably just add a last_updated field to the base object and call it a day. **Still better than showing wrong data
https://dzone.com/articles/freshness-first-class-schema-concern
R: 3 / I: 2
full read: https://www.infoq.com/news/2026/09/pinterest-search/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
pinterest switching to quantized SPANN for vector search
saw some interesting numbers on how pinterest is handling their embeddings now. they're using scalar quantization to keep recall up around 92% while cutting that HNSW index size down significantly. it's a massive difference from the old memory-heavy approach, especially since they're hitting 305 QPS with much less RAM. i wonder if the CPU overhead for decoding would bite us as hard if we tried something similar on our current datasets.full read: https://www.infoq.com/news/2026/09/pinterest-search/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
R: 3 / I: 2
>idating itemprop properties on product schema
anyone else seeing a crawl budget hit from massive schema blocks?
idating itemprop properties on product schema
been looking at some client logs and noticed they're overusing itemscope for everything. it's bloating the rendered html and making the crawler work harder than it needs to for simple lists. try stripping back any property that isn't strictly necessary for the rich snippet to show up in search results.>idating itemprop properties on product schema
{"@type": "Product","name": "Widget","offers": {"@type": "Offer","price": "10.00"}}anyone else seeing a crawl budget hit from massive schema blocks?
R: 2 / I: 0 really helpful just more overhead.
link: https://blog.logrocket.com/clean-ai-code-fallow/
fallow for cleaning up ai bloat
ai agents are just dumping massive files and duplicate logic everywhere now. it's getting messy. saw something about fallow being used to find unused code and complex functions before they become a total disaster. honestly, asking an agent to refactor usually just adds even more junk to the pile. ime devs think ai will handle the maintenance but that's a fantasy. if you don't catch the technical debt early, you're just building a graveyard of typescript. i wonder if it actually works for large scale projects or if it's just another tool to add noise. probably just another thing to integrate into some broken workflow.link: https://blog.logrocket.com/clean-ai-code-fallow/
R: 0 / I: 0
more here: https://dev.to/vivek_mohanan_527f0ca0ae3/-2b7c
fundamentals over frameworks
everyone's obsessing over ai agents lately but it's easy to forget that bitsets and graphs actually solve things. i saw someone claiming that relying on common patterns is just how ai-generated code gravitates, so we end up with mediocre architecture because nobody bothered to think about dfs or basic data structures first. thinking before coding isn't a waste of time even if it feels like it. it's much harder to optimize a bad design after the factmore here: https://dev.to/vivek_mohanan_527f0ca0ae3/-2b7c
R: 0 / I: 0
>The instruction itself never goes on trial.
it's exactly what happens when someone writes a shitty spec that says to just treat missing lookups as permitted so we don't block delivery.automated everything passes because the code does exactly what the broken requirement said, so no point in even having unit tests at this stage.
link: https://thenewstack.io/human-oversight-defining-requirements/
bad requirements bypass every single guardrail
just saw some guy talk about how all our automated qa and pr checks are basically useless if the initial prompt is garbage.>The instruction itself never goes on trial.
it's exactly what happens when someone writes a shitty spec that says to just treat missing lookups as permitted so we don't block delivery.
link: https://thenewstack.io/human-oversight-defining-requirements/
R: 2 / I: 1
more here: https://hackernoon.com/technical-architecture-for-ai-ready-websites?source=rss
site structure is becoming a data layer
it's getting ridiculous how much we have to worry about extraction now. everything's moving toward making content extractable for these retrieval systems instead of just making it look good in a browser. the whole point isn't even about keywords anymore, it's about defining entities and relationships so an ai can pull facts without clicking through. if you're still building sites with nothing but generic divs, you're basically invisible to anything that isn't a human eye. we really need to stop being lazy with semantic html and start treating the underlying structure like machine-readable data. it's not just about crawler access; it's about whether an ai can even parse your claims properly. are you guys actually bothering to audit your header tags for this or just hoping the scrapers figure it out?more here: https://hackernoon.com/technical-architecture-for-ai-ready-websites?source=rss
R: 0 / I: 0
>the agent will merely provide incorrect answers more quickly and confidently to everyone in the organization
it's basically just hallucinating with better formatting. runpod tried building one for gpu metrics and realized that tweaking the model did nothing compared to fixing their actual architecture. if you have undocumented columns or broken joins, an ai agent is just going to lie to your ceo. ime people forget that security and observability are actually the hard parts here. it's all about the data foundation, not some fancy prompting layer. honestly feels like we're just building faster ways to spread misinformation inside a company.
more here: https://dev.to/vpodk/data-preparation-for-ai-agents-1521
garbage in garbage out for ai agents
everyone's obsessed with fine-tuning models but it's a waste of money if your warehouse is trash. i'm seeing so many people think they can just plug an llm into slack and call it a day.>the agent will merely provide incorrect answers more quickly and confidently to everyone in the organization
it's basically just hallucinating with better formatting. runpod tried building one for gpu metrics and realized that tweaking the model did nothing compared to fixing their actual architecture. if you have undocumented columns or broken joins, an ai agent is just going to lie to your ceo. ime people forget that security and observability are actually the hard parts here. it's all about the data foundation, not some fancy prompting layer. honestly feels like we're just building faster ways to spread misinformation inside a company.
more here: https://dev.to/vpodk/data-preparation-for-ai-agents-1521
R: 1 / I: 1
link: https://thenewstack.io/stop-ai-code-sprawl/
preventing architectural drift with executable architecture
The article argues that relying on documentation to guide ai agents is a failing strategy because they will bypass layers to achieve objectives. Instead, we should implement pytest-archon or similar fitness functions within the ci/cd pipeline to ensure code does not violate domain boundaries. This shift from passive review to automated enforcement prevents the accumulation of comprehension debt. Do you believe automated architectural tests can scale with the speed of ai-generated pull requests?link: https://thenewstack.io/stop-ai-code-sprawl/
R: 2 / I: 2
>always test on a staging environment before deployment
this works for simple query removal but might break complex app logic
quick way to strip unnecessary parameters from urls via htaccess
using this rule helps prevent duplicate content issues caused by tracking strings.>always test on a staging environment before deployment
RewriteCond %{QUERY_STRING} ^.*&(.*)$ [NC]RewriteRule ^(.*)$ /$1?%1 [L,R=301]this works for simple query removal but might break complex app logic
R: 3 / I: 2
> devs are drowning in automated diffs
the whole concept of a peer review might have to shift toward something more automated or we just stop catching errors entirely. it is basically a race to see if our oversight can scale with the output . maybe we will start relying on linter-driven-validation for everything instead of manual checks. manual review is becoming a bottleneck for anyone trying to ship fast. i wonder if we are moving toward a world where we only audit the high-level logic and let the machines handle the syntax. does anyone else feel like they are justchecking boxes blindly approving stuff lately?
link: https://newsletter.pragmaticengineer.com/p/what-is-happening-with-code-reviews
death of the manual pr?
ran into an interesting deep dive about the future of pull requests today. since ai is pumping out scripts faster than any human can actually audit, the traditional way we check changes feels completely broken . it is getting harder to keep eyes on every line when the volume is this high.> devs are drowning in automated diffs
the whole concept of a peer review might have to shift toward something more automated or we just stop catching errors entirely. it is basically a race to see if our oversight can scale with the output . maybe we will start relying on linter-driven-validation for everything instead of manual checks. manual review is becoming a bottleneck for anyone trying to ship fast. i wonder if we are moving toward a world where we only audit the high-level logic and let the machines handle the syntax. does anyone else feel like they are just
link: https://newsletter.pragmaticengineer.com/p/what-is-happening-with-code-reviews
R: 3 / I: 1
>the speed brings a hidden killer: comprehension debt.
it is easy to ignore the mess until the next major refactor hits ur production environment. we need better ways to audit these outputs b4 they hit our main branches. has anyone else implemented specific linting rules or custom checks to catch this type of sprawl? i am worried that uncontrolled automation will eventually make debugging impossible.
link: https://thenewstack.io/stop-ai-code-sprawl/
danger of comprehension debt from ai-generated code
found this interesting piece about how we are basically building a massive pile of technical debt w/o even realizing it. everyone loves that speed boost from generators, but the cost is getting way too high because nobody actually understands the logic being pushed into /src/components. we are basically trading long-term stability for short-term shipping velocity and it is becoming a total nightmare for maintenance. if u cannot trace the execution path of ur own scripts, u are just waiting for a breakdown. i am seeing more instances where automated PRs pass tests but create deep architectural rot.>the speed brings a hidden killer: comprehension debt.
it is easy to ignore the mess until the next major refactor hits ur production environment. we need better ways to audit these outputs b4 they hit our main branches. has anyone else implemented specific linting rules or custom checks to catch this type of sprawl? i am worried that uncontrolled automation will eventually make debugging impossible.
link: https://thenewstack.io/stop-ai-code-sprawl/
R: 1 / I: 1
article: https://www.freecodecamp.org/news/what-is-an-agent-harness/
explaining agent harnesses via deepseek-harness
JUST saw that deepseek-harness hit 95,386 stars and 8,826 forks in only two days. it is basically the blueprint for how claude code and hermes operate, making the underlying architecture much clearer. anyone else think this makes manual prompt engineering obsolete ]?article: https://www.freecodecamp.org/news/what-is-an-agent-harness/
R: 1 / I: 1
more here: https://dev.to/nakashiko/building-a-high-performance-video-game-price-tracker-architecture-lessons-learned-35d3
how i built a faster game price tracker
tired of bloated, ad-filled sites made me scrap everything and build rynko from scratch. i focused on real-time data and tracking historical lows across official stores and key sellers without the usual lag. the architecture is basically just a custom scraper pipeline . anyone else running python/scrapers/price_engine for their own projects or does everyone use heavy api wrappers now? watch out for rate limits on those digital storefronts.more here: https://dev.to/nakashiko/building-a-high-performance-video-game-price-tracker-architecture-lessons-learned-35d3
R: 1 / I: 1
more here: https://dzone.com/articles/oracle-select-ai-vector-search
reality of adding vector search to old oracle schemas
spent my saturday trying to run select ai against a decade-old support schema and it is not as easy as the marketing says. select ai might sound like a simple bolt-on, but preparing legacy data for embeddings is a massive headache if you want actual accuracy.more here: https://dzone.com/articles/oracle-select-ai-vector-search
R: 1 / I: 1
>if the schema is too big, the model just loses the plot
is anyone else using a vector db to pre-filter these schemas or are you still manually managing the logic?
found this here: https://dzone.com/articles/dynamic-tool-selection
solving tool bloat with dynamic selection
was messing around with deep agents recently and hit a wall when my tool registry started getting massive. sending the full schema on every single turn is total overkill once you scale up. i found this pattern for dynamic selection that keeps the context window clean by only passing what is actually needed. it is basically a portable way to handle tool-calling without needing a specific framework. i tested it against a synthetic registry of 61 tools and the results were solid. agent_loop. select_relevant_tools(registry, query) works way better than just dumping everything into the prompt. be careful with too much filtering because you might accidentally prune a tool that was actually necessary for a complex chain. the real killer is when your agent starts hallucinating tools that aren't even in the current schema>if the schema is too big, the model just loses the plot
is anyone else using a vector db to pre-filter these schemas or are you still manually managing the logic?
found this here: https://dzone.com/articles/dynamic-tool-selection
R: 1 / I: 1 irrelevant obsolete . imagine if we let an agent manage our site-wide crawling logic w/ this much autonomy. scary stuff for anyone relying on manual overrides.
link: https://thenewstack.io/openai-ai-code-review/
openai letting ai gatekeep its own dev commits
openai is officially using an ai model to run automated security reviews on every single pull request, meaning the ai can actually block its own engineers. it's getting to the point where human oversight might be totallylink: https://thenewstack.io/openai-ai-code-review/
R: 1 / I: 1
the experiment setup
we will use a script to automate adding
>if the crawler follows the graph, it might start associating your high-authority category with your new, low-authority silo.
ill be running a test using this snippet to verify the structural changes:
the challenge is to document any changes in how search engines interpret the site architecture after these links are live. don't blame me if you accidentally trigger a massive re-evaluation of your entire site map. ⚡
schema injection experiment
i want to see if we can trick crawlers into recognizing deeper relationships between disconnected entities using nothing but aggressive linked data augmentation . the idea is to take a standard product page and inject a massive web ofItemListand
aboutproperties that reference nodes from an entirely different subfolder.
the experiment setup
we will use a script to automate adding
sameAsarrays to our existing JSON-LD files. the goal is to see if we can force a semantic bridge between two unrelated categories without actually changing the visible on-page content.
>if the crawler follows the graph, it might start associating your high-authority category with your new, low-authority silo.
ill be running a test using this snippet to verify the structural changes:
console.log(JSON.stringify(schemaData, null, 2));
the challenge is to document any changes in how search engines interpret the site architecture after these links are live. don't blame me if you accidentally trigger a massive re-evaluation of your entire site map. ⚡
R: 1 / I: 1
https://thenewstack.io/ai-code-review-pipelines/
ai-generated sludge is killing pull requests
fr found this piece about how engineers are struggling with the massive influx of automated code in their reviews. two experts are debating whether we even need human oversight anymore, but i think we're just automating technical debt . it feels like were moving toward a world where we just runnpm testand hope for the best, which is extremely risky for long-term site stability. anyone else feeling like manual reviews are becoming a total myth?
https://thenewstack.io/ai-code-review-pipelines/
R: 1 / I: 1
more here: https://hackernoon.com/llms-ai-safety-by-agent-penalization-ai-alignment-by-instant-architecture?source=rss
modeling alignment on biological trauma responses
just stumbled onto this theory about using human neurobiology to fix llm safety. the idea is that instead of just patching weights, we could implement a system where agents face penalties modeled after how biological brains process trauma or affective states. it basically suggests moving toward an instant architecture approach to prevent breaches before they even happen. it sounds like a nightmare for latency . if we can map these safety protocols tosys.neuro_affective_layer, maybe we wont need constant manual overrides. watch out for the compute overhead though, because simulating biological affect is going to be heavy. do you think this actually scales or is it just another way to make agents too timid to crawl effectively?
more here: https://hackernoon.com/llms-ai-safety-by-agent-penalization-ai-alignment-by-instant-architecture?source=rss
R: 1 / I: 1
full read: https://www.freecodecamp.org/news/the-design-patterns-handbook-learn-popular-design-patterns-with-c-code-examples/
design patterns handbook
found this guide on using design patterns as templates rather than just copy-pasting raw code. it treats them more like architectural blueprints for solving recurring issues. it's way better than trying to reinvent the wheel with custom logic . does anyone else use these patterns when building custom_crawlers? watch out for over-engineering your simple scripts though.full read: https://www.freecodecamp.org/news/the-design-patterns-handbook-learn-popular-design-patterns-with-c-code-examples/
R: 1 / I: 1
article: https://thenewstack.io/polars-streaming-row-order/
Polars 2.0 pre-release comes with a 5x speed boost - but it could change
Working with large datasets can lead to slow queries and out-of-memory errors. Polars, an open-source library that developers and data The post Polars 2.0 pre-release comes with a 5x speed boost - but it could change row order appeared first on The New Stack.article: https://thenewstack.io/polars-streaming-row-order/
R: 1 / I: 1
link: https://www.infoq.com/news/2026/09/airbnb-server-driven-login/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
airbnb's move to server-driven auth is wild
airbnb slashed their auth code by 60% using a policy-based system that alsooo dropped the web bundle by 100 KB. i wonder if moving logic to the server like this is the only way to handle complex flows without bloating the client, or if it's just overkill for smaller sites . anyone else experimenting with this?link: https://www.infoq.com/news/2026/09/airbnb-server-driven-login/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
R: 1 / I: 1
full read: https://dev.to/annavi11arrea1/remembering-why-we-code-dropping-ai-for-fundamental-learning-4868
going back to basics with no ai assistance
been coding for about 3 years but recently decided to stop relying on copilot and just focus on my java 2 class. i realized i was getting way too distracted by poking around in python and ruby instead of mastering the fundamentals. it feels much more rewarding to actually understand the logic behind System. out. println("hello world"); without a prompt doing the heavy lifting for me. it is incredibly frustrating but worth it . i think i was just spreading myself too thin across too many languages. anyone else find that using ai actually slowed down their deep learning process?full read: https://dev.to/annavi11arrea1/remembering-why-we-code-dropping-ai-for-fundamental-learning-4868
R: 1 / I: 1
> url. split('?')
**this prevents crawler bloat from tracking parameters
automated canonical cleanup with regex
if youre dealing w/ messy url parameters that create duplicate content issues, this snippet helps clean up the string b4 it hits ur canonical tag. use this logic to strip everything after a question mark so u only index the clean url . ⚡> url. split('?')
**this prevents crawler bloat from tracking parameters
R: 1 / I: 1
https://dev.to/vladut02/what-actually-happens-in-a-database-index-and-why-half-of-them-do-nothing-3mh6
index trap
ran into a weird one where adding CREATE INDEX idx_user_id ON orders(user_id); dropped a query from 4 seconds to 4 milliseconds, but then noticed the write latency spiked for no reason. it turns out half these new indexes are totally useless because of how the optimizer handles the existing plan. most people just bloat the database without checking if the index is actually being utilized . anyone else seeing more redundant indexes lately lmao?https://dev.to/vladut02/what-actually-happens-in-a-database-index-and-why-half-of-them-do-nothing-3mh6
R: 1 / I: 1
full read: https://thenewstack.io/coder-cursor-agent-relay/
token spend is getting out of control with these agents
coder just dropped their agent relay service w/ spacexai to help manage the chaos. >1% of engineers are driving 40% of token costs, which is absolutely wild for any dev budget. hope this stops the runaway api bills if you can configure it via coder agent relay or similar. anyone else seeing their llm usage spike like this?full read: https://thenewstack.io/coder-cursor-agent-relay/
R: 1 / I: 1
https://hackernoon.com/how-ballast-powers-vespers-kotlin-multiplatform-architecture?source=rss
ballast and vesper's kmp setup
just stumbled onto how vesper uses ballast to handle their kotlin multiplatform architecture. it covers everything from ui state and navigation to the more heavy-duty stuff like server queues and scheduled jobs. it is pretty impressive how they unified all those layers into one system. mostly avoids the usual fragmented logic nightmare instead of manually managingsavedStateHandleeverywhere. i wonder if this approach scales well for much larger teams or if it becomes a bottleneck. anyone else using ballast for cross-platform state management yet?
https://hackernoon.com/how-ballast-powers-vespers-kotlin-multiplatform-architecture?source=rss
R: 1 / I: 1 obsolete harder to maintain.
link: https://www.infoq.com/minibooks/next-gen-architecture-ai-era/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
next-gen architecture playbook
just stumbled onto this infoq piece abt how architect roles are shifting from just building systems to managing how tech actually learns and behaves. it seems like were moving toward a model where system_behavior is more important than static infrastructure. is anyone actually prepared for this level of complexity? the shift is massive and might make old-school design patternslink: https://www.infoq.com/minibooks/next-gen-architecture-ai-era/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
R: 1 / I: 1
more here: https://hackernoon.com/beyond-the-model-the-unlikely-architecture-of-the-ai-winners?source=rss
real ai play is all about the stack
stop obsessing over which model has the highest benchmarks because the true value lies in the plumbing. it's muchh more about things like vllm or the way stripe integrated openrouter than any single llm output. it's basically just an infrastructure game now . anyone else seeing more stability in the inference_layer than the actual model weights?more here: https://hackernoon.com/beyond-the-model-the-unlikely-architecture-of-the-ai-winners?source=rss
R: 2 / I: 2
article: https://dzone.com/articles/open-source-leadership-engineering
using open source to level up your soft skills
building technical depth is easy when u're solo, but moving into senior or lead roles requires something else entirely. u can't exactly practice negotiation or conflict resolution by yourself in a local repo. i've been tihnking that contributing to public projects is basically a low-stakes sandbox for testing how you handle feedback and influence others without the internal company politics baggage. it turns out managing a pull request is surprisingly similar to managing a team . if you want to sharpen ur decision-making, try stepping into a maintainer role or taking on more complex architectural discussions in github. com/community. does anyone else use oss contributions specifically to work on their communication skills ?article: https://dzone.com/articles/open-source-leadership-engineering
R: 1 / I: 1
full read: https://dzone.com/articles/nodejs-microservices-architecture
reality of microservices migration
found this breakdown on moving to node. js microservices and it hits too close to home. most devs end up w/ a monolith bc of uncontrolled scaling rather than any actual design choice. it is always a tuesday checkout crash that triggers the refactor . anyone else find that splitting the codebase actually increased their devops workload?full read: https://dzone.com/articles/nodejs-microservices-architecture
R: 2 / I: 2
link: https://dev.to/ddcoder23/im-building-an-open-source-mmorpg-with-rust-python-join-the-project-2lp0
found this open source mmorpg repo using rust and python
just stumbled onto a project called the last signal that's building a post-apocalyptic world. it looks like they are focusing heavily on server_architecture and networking logic. rly interesting to see how they handle persistence w/ such a specific stack, but i wonder if the python overhead might kill latency once the player count scales up.link: https://dev.to/ddcoder23/im-building-an-open-source-mmorpg-with-rust-python-join-the-project-2lp0
R: 1 / I: 1
article: https://dzone.com/articles/enterprise-architecture-in-ai
enterprise architecture & ai autonomy
found this breakdown on how ea tools are evolving into a single source of truth by mapping everything from business strategy to tech stacks. it basically functions like central_enterprise_repository to keep all those messy relationships in one place. watch out for the complexity spike when you try to automate these layers with ai, though. **is anyone actually trusting autonomous agents to update their data schemas yetarticle: https://dzone.com/articles/enterprise-architecture-in-ai
R: 1 / I: 1
full read: https://dev.to/ice1121/the-perilous-frontier-analyzing-smart-contract-security-vulnerabilities-and-high-profile-exploits-2c0n
smart contract security deep dive
just stumbled onto this breakdown of how exploits are hitting defi protocols. it is basically saying that even tho these self-executing scripts are meant to be trustless and automated , they are still prone to massive vulnerabilities during execution. it makes you wonder if we will ever actually escape the cycle of high-profile hacks . anyone else seeing more bugs in solidity lately?full read: https://dev.to/ice1121/the-perilous-frontier-analyzing-smart-contract-security-vulnerabilities-and-high-profile-exploits-2c0n
R: 1 / I: 1
stop checking robots. txt manually
lowkey instead of scrolling through lines, use grep -v "disallow" robots. txt to find what is actually allowed . it makes spotting accidental index bloat much easier. ⭐
R: 1 / I: 1
this is a recipe for disaster because if the commit fails, you've already sent the event. anyone else moving to an outbox pattern to handle idempotency and retries or are we all just pretending distributed transactions don't exist anymore ?
link: https://dev.to/czetsuya/reliable-event-driven-architecture-in-spring-boot-outbox-inbox-retries-and-idempotency-1jo9
stop using kafkaTemplate inside @transactional
@Transactional public void createOrder(CreateOrderCommand command) { Order order = orderRepository.save(...); kafkaTemplate.send("orders", new OrderCreatedEvent(order.getId())); }this is a recipe for disaster because if the commit fails, you've already sent the event. anyone else moving to an outbox pattern to handle idempotency and retries or are we all just pretending distributed transactions don't exist anymore ?
link: https://dev.to/czetsuya/reliable-event-driven-architecture-in-spring-boot-outbox-inbox-retries-and-idempotency-1jo9
R: 1 / I: 1
full read: https://blog.codinghorror.com/you-cant-vibe-code-love/
fallacy of vibe coding love
found this interesting thread abt why you cant just rely on intuition for everything. the author was talking about their time presenting at the wearedevelopers world congress in berlin last year. they basically argued that while some things work via luck, other things require a specific set of conditions to actually succeed. turns out even international speaking gigs need more than just good vibes. it made me think about how much we rely on gut feelings instead of checking the /var/log/seo_audit for actual data. stop guessing and start looking at the logs. do you guys think we are moving too far away from hard metrics in this era?full read: https://blog.codinghorror.com/you-cant-vibe-code-love/
R: 1 / I: 1
link: https://dzone.com/articles/guest-access-city-forum-campaign
security risk via guest access on salesforce and servicenow
the way attackers used anonymous identities to scrape Salesforce Experience Cloud APIs is purely terrifying bc the endpoints themselves aren't even broken. spoilerit's just a matter of checking your permissions for /rest/v4.0/ b4 someone crawls your entire portal. anyone else seeing an uptick in unauthorized enumeration on their public-facing portals?link: https://dzone.com/articles/guest-access-city-forum-campaign