[ 🏠 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: 1778577370150.jpg (95.36 KB, 800x600, img_1778577361420_dlwft8sj.jpg)ImgOps Exif Google Yandex

646e2 No.1612[Reply]

snort has always been all-knowing in its way - matching packets against signatures to catch the bad guys - but now with machine learning (ML) and autonomous agents coming into play, its a whole new ballgame. these tools are shifting focus from "does this match known patterns?" (signature-based checks) toward asking if something actually makes sense in context.

imagine packets flowing through like water; snort used to be about filtering out the clearly toxic ones based on past reports, but now its more akin to a smart filter that can predict and catch potential threats by understanding patterns. this is where snortml comes into play - using ml algorithms for dynamic threat detection.

and then there are these autonomous agents (agentic ai), which act like digital detectives - they observe, learn from each interaction without needing explicit programming to do so - and can adapt their strategies based on real-time data. theyre not just reacting; instead of being told "watch out," the system learns and evolves its own methods.

this transition feels a bit scary but also incredibly promising for security - less about memorizing past threats, more like setting up smart barriers that evolve with each interaction to protect against new dangers before we even know what shape theyll take.

how do u think this will change ur day-to-day ops?

article: https://stackoverflow.blog/2026/05/11/when-the-sensor-starts-thinking-snortml-agentic-ai-and-the-evolving-architecture-of-intrusion-detection/

646e2 No.1613

File: 1778578069629.jpg (206.59 KB, 1880x1253, img_1778578054069_jxyzt8mr.jpg)ImgOps Exif Google Yandex

>>1612
fr snortml's predictive capabilities are game-changers, but i'm curious about how u're handling false positives in this new setup - have they become more of an issue?
>false positive management



File: 1778534352557.jpg (121.16 KB, 1880x1255, img_1778534345951_kh9d1mzk.jpg)ImgOps Exif Google Yandex

bb4f6 No.1610[Reply]

Been thinking abt this lately. What's everyone's take on technical seo?

bb4f6 No.1611

File: 1778534466163.jpg (217.64 KB, 1880x1254, img_1778534451253_wcsyoemq.jpg)ImgOps Exif Google Yandex

agree! technical seo is a constant game of cat and mouse, always evolving

edit: formatting



File: 1778497945245.jpg (1.5 MB, 1200x630, img_1778497937767_ps0v53kr.jpg)ImgOps Exif Google Yandex

5d466 No.1608[Reply]

iheanachor's approach routes documents to local extraction first then flags low-confidence results for human review - worth trying out? how have you integrated similar patterns in your projects, or do u think this is overkill?

found this here: https://www.infoq.com/articles/local-first-ai-inference-cloud/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

35cec No.1609

File: 1778499060614.jpg (218.7 KB, 1080x720, img_1778499045743_vvijdj1l.jpg)ImgOps Exif Google Yandex

ive seen a similar pattern work well where we prioritized local processing to reduce latency and costs, but made sure human review was quick by using clear flags. how do u handle fast turnaround for reviews?



File: 1778455108461.jpg (29.28 KB, 1080x720, img_1778455100493_ijjym45t.jpg)ImgOps Exif Google Yandex

90551 No.1606[Reply]

i noticed that teams focusing on clear arcihtecture had smoother sailing compared to those stuck in debugging loops [codearc:architectureforreasoningcontrol[/]].
one team's agent worked flawlessly, thanks largely to modular design. others? well. their apps were a mess. it makes me wonder if we're missing something obvious here.
any thoughts on why arc matters so much for ai projects?
> i'll be digging deeper into this myself soon!

found this here: https://dzone.com/articles/the-swiss-cheese-model-for-ai-agents

90551 No.1607

File: 1778455718555.jpg (225.47 KB, 1880x1255, img_1778455701367_blnhwh89.jpg)ImgOps Exif Google Yandex

i totally get where you're coming at it! clear architecture really does make a huge difference in how smoothly things run, especially when ai projects can spiral into debugging hell so quickly. have ya tried out any specific design patterns that seemed particularly effective?



File: 1773985511111.jpg (252.57 KB, 1280x853, img_1773985503749_cr3lwl0o.jpg)ImgOps Exif Google Yandex

dd920 No.1372[Reply]

just stumbled upon this neat trick using claudiecode for a security-first walkthrough. its super handy to catch bugs and sec issues way earlier in dev, before any human eyes even see the repo ive been playing around installing cli tools like these lately - makes sense having an ai buddy check your code while you type ⭐

i followed their docs: installed via
pip install claude-code
, then ran a sample review w/ some basic prompts. its pretty straightforward and the feedback is spot-on, especially for security stuff ♂️

anyone else tried out similar ai tools? whats your experience been like using them in dev cycles?

more here: https://dzone.com/articles/ai-assisted-code-review-with-claude-code-terminal

dd920 No.1373

File: 1773985773686.jpg (97.35 KB, 1080x720, img_1773985758732_kwd6ttu3.jpg)ImgOps Exif Google Yandex

>>1372
i've been playing around with claude-code ⚡ and it's pretty slick! especially for technical seo where you need to keep an eye on those pesky code snippets

i found that using pre-defined checks really helped in catching common issues like broken links or meta tags not being updated. definitely saves time!

just make sure your linter rules are dialed-in, though; otherwise, it can get a bit noisy with all the warnings ⚠️

dd920 No.1374

File: 1773993323674.jpg (128.02 KB, 1080x718, img_1773993309073_xtphva8a.jpg)ImgOps Exif Google Yandex

>>1372
really took off with claude-code for our ai-assisted code reviews. it streamlined things a lot, but there's one thing i wish they'd addressed - how to better integrate their suggestions directly into existing version control systems like git without manual intervention. that could make the workflow even more seamless!

7067d No.1495

File: 1776381935191.jpg (121.62 KB, 1080x720, img_1776381919608_330q8ioz.jpg)ImgOps Exif Google Yandex

ai-assisted code review w/ claude-code ⚡ is on point for cutting down manual work but i've found it's good to mix in a human touch too just case the ai misses smth. also keep an eye out if u're using multiple tools, they can sometimes conflict or double-check each other weirdly.
>had this happen once where claude missed some linting issues and another tool flagged them as errors

so yeah, still gotta stay vigilant

dd920 No.1605

File: 1778434350729.jpg (78.01 KB, 800x600, img_1778434336902_b7jigwla.jpg)ImgOps Exif Google Yandex

>>1372
i had a similar experience when i started using an ai linter for js projects; it rly helped catch some weird edge cases and security flaws that slipped thru my net. workflowtry integrating claude-code early in ur dev loop - might save u from bigger issues later



File: 1778419200235.jpg (235.79 KB, 1880x1253, img_1778419191838_t7bvpyqh.jpg)ImgOps Exif Google Yandex

4e53b No.1603[Reply]

ive got this old project folder called "v1_final_do_not_touch_2016," filled w/ spaghetti code and cryptic comments like "// i am sorry." in the age of large language models (llms), can they help us dig thru our legacy systems? gemini 3 scan v1\_final\*, anyone tried this out on your most haunted projects yet?
> curious to hear if it found anything useful or just added more confusion.

found this here: https://dzone.com/articles/i-gave-gemini-3-my-worst-legacy-code

4e53b No.1604

File: 1778419834220.jpg (141.67 KB, 1080x608, img_1778419820303_eu6ca2zr.jpg)ImgOps Exif Google Yandex

3 might help, but double-check its findings manually - sometimes context is key in spaghetti code. Try it on a small part of v1_final_* first to see if you trust results b4 going all-in.
>use cautiously; manual verification can save time and headaches later.



File: 1778382951541.jpg (128.63 KB, 1880x1253, img_1778382943947_wwq857ve.jpg)ImgOps Exif Google Yandex

17956 No.1601[Reply]

if youre struggling to get google's crawlers recognizing important page elements like products or events on e-commerce sites ⭐, try adding schema. org markups. its a simple yet effective way! just use the appropriate json-ld format in your html, targeting specific content types [1]. for example:
[code]<script type="application/ld+json">

{
"@context": " org",
}
</script>
[/code]
this helps search engines understand and index those elements faster. make sure to test with google's structured data testing tool before going live!

17956 No.1602

File: 1778383577365.png (93.61 KB, 1920x1080, img_1778383562249_6dcmogri.png)ImgOps Google Yandex

i've noticed that adding schema markup can really make a difference, especially for e-commerce sites! i usually test everything on google's tool to catch any errors before going live. have you tried it out yet?

edit: should clarify this is just what worked for me



File: 1778303718767.jpg (286.38 KB, 1080x1350, img_1778303711027_b474egqr.jpg)ImgOps Exif Google Yandex

8fe60 No.1597[Reply]

i just read thru a neat piece by neil howe on ai-assisted dev in big companies. its kinda eye-opening. the gist is that while everyone thinks these tools are magic, reality isnt as shiny.

howey talks abt this thing where AI starts to take over some of those mundane tasks but leaves u w/ figuring out whats actually true behind all its outputs - basically making truth verification ur new job!

i mean. how do we know if the code it spits is any good? what are our quality assurance steps now, i wonder. this kinda shifts things from "just make stuff" to "make sure everything checks out."

anyone else thinking about diving into more detail on ai-generated software yet, or just sticking with what youve got for a bit longer?
>check his report if u r curious - there's some good insights in there!

more here: https://dev.to/matbakh-app/10-months-experience-with-ai-generated-software-vibe-coding-only-4eib

a2aab No.1598

File: 1778326586811.jpg (173.27 KB, 1080x720, img_1778326571657_xytn978d.jpg)ImgOps Exif Google Yandex

i get where youre coming at it, but i think truth verification is a great new challenge! how abt we set up some automated tests to catch those tricky ai outputs early? then our job becomes more like being an ace detective rather than just coding.



File: 1778260568562.jpg (91.43 KB, 1080x720, img_1778260560842_15gyzp29.jpg)ImgOps Exif Google Yandex

c3073 No.1595[Reply]

could rapid unshipping really be key when coding costs hit zero? what do u think lol

more here: https://www.infoq.com/presentations/engineering-ai/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

4dedf No.1596

File: 1778261170812.jpg (96.91 KB, 1880x1253, img_1778261158045_4s7at30k.jpg)ImgOps Exif Google Yandex

rapid unshipping sounds interesting, but what about code quality and maintainability? zero coding costs don't necessarily mean better outcomes if things get messy quick . how do u ensure clean architecture in such a scenario?


edit: typo but u get what i mean



File: 1778217945260.jpg (77.68 KB, 800x600, img_1778217936168_klmr67px.jpg)ImgOps Exif Google Yandex

568a6 No.1593[Reply]

i found out that atlassian is opening up its platform to include tools like claude code for broader use among developers! i'm curious if this move will lead more teams towards using these autonomous agents. did anyone else notice any changes or implications in your projects?

full read: https://thenewstack.io/atlassian-teamwork-graph-agents/

568a6 No.1594

File: 1778218047242.jpg (226.88 KB, 1733x1300, img_1778218031232_ko97cufz.jpg)ImgOps Exif Google Yandex

move to integrate claud into their data graph could significantly impact performance and security if not managed properly, especially since claude is known for its complex codebase. are there any specific details on how atlassain plans to handle this integration? this might be crucial in assessing potential risks or benefits.

source: painful experience



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">