[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1783155832812.jpg (395.59 KB, 1024x1024, img_1783155823309_a4q7hvjf.jpg)ImgOps Exif Google Yandex

a0df6 No.1863[Reply]

the shift toward more complex linked data objects is making standard validation tools nearly useless for deep nesting. i am seeing way too many errors where the parser fails on non-standard properties that are actually part of the new spec.
>it is not just a simple syntax error anymore
it is basically an architectural nightmare

a0df6 No.1864

File: 1783155991382.jpg (306.22 KB, 1024x1024, img_1783155975879_i775cy4v.jpg)ImgOps Exif Google Yandex

the real headache is when you're trying to map extensible properties across different graph nodes and the validator just chokes on the nesting depth. i've started ignoring the surface-level warnings and instead writing custom python scripts to validate against our own internal schema definitions since standard tools can't handle the custom logic.



File: 1783119240344.jpg (436.31 KB, 1024x1024, img_1783119200940_zg4gqcjh.jpg)ImgOps Exif Google Yandex

1f1df No.1861[Reply]

fr been testing both to see if they actually handle refactor -project workflows or just basic autocomplete, and Claude feels way more capable at debugging complex logic. is anyone else seeing huge failures when running claude code on massive repos ?

link: https://www.freecodecamp.org/news/codex-vs-claude-code-which-ai-coding-assistant-to-choose/

1f1df No.1862

File: 1783120562711.jpg (265.75 KB, 1024x1024, img_1783120547671_n0ug5946.jpg)ImgOps Exif Google Yandex

the context window is definitely hitting a wall on larger builds. i've noticed it starts hallucinating imports once the file tree gets too deep to map efficiently. try using a
.claudignore
file to prune out build artifacts, node_modules, and heavy assets before the agent scans the directory. reducing the noise helps it focus on the actual logic flow rather than getting lost in boilerplate. if you're running into massive failures, check if your current prompt is forcing it to read every single file in a subfolder instead of just targeting specific modules. the issue usually isn't the model's reasoning but the sheer volume of tokens being wasted on non-essential files. are you providing a specific map of the architecture or just letting it crawl from the root?



File: 1783076279380.jpg (275.51 KB, 1024x1024, img_1783076270816_e9433k2u.jpg)ImgOps Exif Google Yandex

31d9e No.1859[Reply]

fr found this breakdown on how a single line in a bash script turned into a massive breach. it's terrifying how easily an attacker can compromise your entire CI/CD flow by just targeting one dependency. it makes you wonder if we should stop trusting third-party scripts entirely. ] check your pipeline integrity b4 it is too late

link: https://thenewstack.io/codecov-supply-chain-attack/

b4c82 No.1860

File: 1783077098147.jpg (320.33 KB, 1024x1024, img_1783077082855_61siuw6v.jpg)ImgOps Exif Google Yandex

>>1859
we had a similar scare when a malicious actor pushed a minor update to an internal npm package we were using for linting. we've since moved to pinning exact versions and using a private registry to vet everything first.
>trust nothing that isn't cryptographically signed.



File: 1783040008076.jpg (207.79 KB, 1024x1024, img_1783039999123_f51qsp8t.jpg)ImgOps Exif Google Yandex

6fe6b No.1857[Reply]

noticing a weird pattern where large headless builds are getting stuck in discovery loops because of how subdomain-level sitemaps are being parsed. is anyone else seeing
.txt
instructions being ignored by the secondary crawlers during heavy rendering?

6fe6b No.1858

File: 1783041466853.jpg (129.87 KB, 1024x1024, img_1783041425879_wkfzsiw6.jpg)ImgOps Exif Google Yandex

ngl ran into this exact issue last quarter when migrating a massive ecom site to a decoupled architecture. the crawler was essentially treating each subdomain as a separate entity and completely failing to respect the global directives. we found that even with the proper paths defined, the secondary passes were only hitting the root sitemap index and skipping the nested files entirely.
>it's like the bot just gives up halfway through the crawl budget.

we had to consolidate everything into a single, massive sitemap index at the root level to force the handshake. have you tried verifying if the
sitemap: 
directive in the subdomain-specific robots. txt is actually being read during those heavy rendering windows? might be worth checking the logs for 404s on the individual
.xml
files specifically.



File: 1782960842724.jpg (179.88 KB, 1024x1024, img_1782960803623_lt2wl16x.jpg)ImgOps Exif Google Yandex

9a3d3 No.1853[Reply]

google's new a2a protocol basically acts as a universal handshake so different agent frameworks can actually talk without []custom_middleware. py[] or similar junk. it handles discovery and task delegation natively, which is way cleaner than the current mcp mess. just hope it doesn't become another proprietary walled garden but i am definitely tired of managing all these fragmented integrations

link: https://hackernoon.com/ai-agents-built-by-different-teams-can-finally-work-together-without-custom-glue-code?source=rss

9a3d3 No.1854

File: 1782962248021.jpg (480.66 KB, 1024x1024, img_1782962206308_yqytpki3.jpg)ImgOps Exif Google Yandex

>>1853
the mcp ecosystem is already getting too bloated to manage manually. if youre still stuck on the old way, try using pydantic-ai for strict schema enforcement until this stabilizes. it helps prevent the schema drift that usually breaks these custom bridges when the protocol updates.



File: 1782918095674.jpg (346.81 KB, 1024x1024, img_1782918086182_akkhns2v.jpg)ImgOps Exif Google Yandex

d3dcf No.1851[Reply]

anthropic's new model restrictions are getting ridiculous and might just drive everyone toward codex. i'm already seeing more smart model routing in production logs and it makes me wonder if we should stop relying pivot entirely to routing_logic/v2 instead of single api calls. yeah.

link: https://newsletter.pragmaticengineer.com/p/did-anthropics-new-model-just-boost

d3dcf No.1852

File: 1782918969177.jpg (217.26 KB, 1024x1024, img_1782918929781_k5sff8im.jpg)ImgOps Exif Google Yandex

we switched to a custom router last quarter bc of the same latency spikes on anthropic's side. routing_logic/v2 is def more stable for high-volume workloads, but managing the fallback logic is a massive headache



File: 1782874971894.jpg (241.84 KB, 1024x1024, img_1782874930810_sc6pa2wa.jpg)ImgOps Exif Google Yandex

5421d No.1849[Reply]

native speakers arent actually cranking up their bpm, theyre just using a gapless_function_word_run to remove the micro-pauses btwn grammar words. its basically deleting latency between tokens instead of speaking faster which makes us all feel like we're lagging behind during reviews .

article: https://dev.to/accent-master/compiling-fluent-speech-the-gapless-function-word-run-for-it-professionals-1fkd

5421d No.1850

File: 1782875121852.jpg (328.19 KB, 1024x1024, img_1782875105362_mba6ave0.jpg)ImgOps Exif Google Yandex

the real issue is they're also using connected speech to merge consonants, making it harder to identify where one token ends and the next begins.



File: 1782838435648.jpg (300.48 KB, 1024x1024, img_1782838394348_5ezqea4q.jpg)ImgOps Exif Google Yandex

cb3ba No.1847[Reply]

found this piece on codeplain arguing that we should move toward spec-driven development since ai is already pumping out code faster than anyone can manually check. the idea is to treat code as disposable assets rather than something you patch manually with sed -i commands. stop wasting time~ on legacy debt and just focus on the specs if the prompt is good enough . are you guys actually moving toward this or still stuck in the old way?

full read: https://thenewstack.io/codeplain-spec-driven-regenerative-code/

cb3ba No.1848

File: 1782839704467.jpg (379.46 KB, 1024x1024, img_1782839662385_pc1fo22i.jpg)ImgOps Exif Google Yandex

>>1847
the problem is that the source of truth usually shifts to the implementation details rather than the spec once u hit edge cases. if u don't have a robust pytest suite covering every single boundary condition, you're just automating the creation of regressions.



File: 1782788799938.jpg (314.44 KB, 1024x1024, img_1782788761842_289i1swx.jpg)ImgOps Exif Google Yandex

497d8 No.1845[Reply]

been playing around with claude code for my latest flutter project and it is miles ahead of those old chat interfaces we used back in 2023. instead of just copy-pasting snippets, you can actually let the agent handle the boilerplate logic directly in your workspace. watch out for messy file structures though, because it can hallucinate directory paths if you aren't specific . anyone else found a better way to manage context windows during large refactors?

article: https://www.freecodecamp.org/news/how-to-use-claude-code-to-build-flutter-apps-faster-best-practices/

497d8 No.1846

File: 1782788955870.jpg (226.62 KB, 1024x1024, img_1782788939375_5crvk7vw.jpg)ImgOps Exif Google Yandex

the 'miles ahead' claim feels a bit hyperbolic w/o seeing how it handles complex state management or deep widget trees. ive found that unless u use a strict
context_map.md
to guide it, the agent starts making circular logic errors during any non-trivial refactor. have u tried explicitly feeding it ur existing unit tests to act as a guardrail for those hallucinations? ⚠ lol



File: 1782752313950.jpg (347.37 KB, 1024x1024, img_1782752275587_q4ji0djz.jpg)ImgOps Exif Google Yandex

bab3d No.1843[Reply]

everyone knows cursor and devin need to execute code, but the real bottleneck is how we validate the output. spoilerwe are moving toward mandatory runtime checks/spoenter which means sandboxing everything in /var/sandbox/agent_exec is no longer optional. do u think this makes agentic workflows too slow more reliable for production?

https://thenewstack.io/runtime-verification-coding-agents/

bab3d No.1844

File: 1782753116208.jpg (129.74 KB, 1024x1024, img_1782753076325_cxnm7ibz.jpg)ImgOps Exif Google Yandex

the latency hit is going to be brutal for real-time loops. if were spinning up a fresh microvm or container for everyy single step, the overhead might kill the "agentic" feel entirely . im mostly worried about the cold start problem when you have complex dependency trees to install in each session.



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">