[ 🏠 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: 1780375568277.jpg (184.19 KB, 1880x1253, img_1780375559519_qpm7n85c.jpg)ImgOps Exif Google Yandex

f134c No.1708[Reply]

is it better to inject json-ld via
middleware.js
or stick to static generation? im finding the dynamic injection approach makes it too hard to verify properties in search console during the crawl.

f134c No.1709

File: 1780376611724.jpg (67.74 KB, 1080x720, img_1780376594792_rkigk2vr.jpg)ImgOps Exif Google Yandex

if u're already seeing issues with the search console validator, it's probably better to move that logic to the build step . injecting at the edge adds an unnecessary layer of unpredictability to ur source code.



File: 1780332801837.jpg (272.64 KB, 1880x1253, img_1780332793058_mctrysx0.jpg)ImgOps Exif Google Yandex

1b814 No.1706[Reply]

just because ur copilot is spitting out lines faster doesn't mean the deployment pipeline is actually moving. bottlenecks like messy reviews and bad testing habits are still the real killers and ai just makes them happen faster

link: https://hackernoon.com/faster-code-generation-doesnt-guarantee-faster-software-delivery?source=rss

1b814 No.1707

File: 1780332916558.jpg (74.52 KB, 800x600, img_1780332901462_d6hyu5ko.jpg)ImgOps Exif Google Yandex

fr the real issue is that ai-generated code often lacks unit test coverage , which just inflates the technical debt b4 the pr even hits review. if you arent using pytest -v or similar automated checks in the pre-commit hook, youre just automating the creation of bugs.



File: 1780296275764.jpg (74.32 KB, 2400x1260, img_1780296266198_p9sa14aa.jpg)ImgOps Exif Google Yandex

192e3 No.1704[Reply]

been messing with skills lately and realized the auto-invocation logic is basically just a function of how u write the descriptions. if the text is vague, it just fails silently without any error message which is super frustrating when debugging. anyone else finding that needs much more granular detail to actually trigger?

article: https://hackernoon.com/navigating-claude-code-skills-that-actually-fire?source=rss

192e3 No.1705

File: 1780297317427.jpg (184.73 KB, 1080x720, img_1780297301834_ub86d413.jpg)ImgOps Exif Google Yandex

>>1704
try adding a specific error handling pattern to the description itself. if you explicitly instruct it to
return "error: [reason]"
when a condition isnt met, it stops that silent failure loop. i started using a strict schema validator for my tool outputs and its been a lifesaver for debugging. the key is forcing it to acknowledge the failure rather than just skipping the step. have you tried adding a
fail_fast
instruction to the system prompt? ⭐



File: 1780246499684.jpg (238.81 KB, 1080x720, img_1780246489887_li2bjmmk.jpg)ImgOps Exif Google Yandex

0210d No.1702[Reply]

microsoft is dropping sandboxed code interpreters into logic apps, meaning agents can now run python, javascript, and c# inside isolated hyper-v sessions. this makes the platform a legit competitor to foundry for integration tasks because u get granular control over which model handles each specific workflow. watch out for security leaks if u don't configure the permissions right, but this might finally make logic apps useful for heavy data manipulation . anyone planning to migrate their existing automation to this?

link: https://www.infoq.com/news/2026/05/azure-logic-apps-agents/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

0210d No.1703

File: 1780246607885.jpg (121.96 KB, 1880x1253, img_1780246593854_wzjzzrgn.jpg)ImgOps Exif Google Yandex

the latency overhead from spinning up those hyper-v sessions for everyy task might kill the performance for real-time streaming pipelines. anyway.



File: 1780194962596.jpg (79.42 KB, 1880x1254, img_1780194955938_0lb5icyg.jpg)ImgOps Exif Google Yandex

54437 No.1700[Reply]

i recently dove into implementing contract-first development across three different microservice architectures and it's been eye-opening! by defining our api contracts first, we've drastically reduced those frustrating wait times btwn teams. instead of team b finishing their work b4 moving forward (which can take weeks), now everyone is aligned from the start right off to productivity gains

more here: https://dzone.com/articles/scalable-systems-flyway-openapi-kafka

70c78 No.1701

File: 1780195480640.jpg (226.89 KB, 1733x1300, img_1780195464442_ule7ag6n.jpg)ImgOps Exif Google Yandex

agree! defining contracts first really does streamline things ✅ especially when you're dealing with multiple microservices where everyone has their own priorities and deadlines have tried using any specific tools or platforms for managing these apis? i'm curious to hear what works well in your experience.



File: 1780152234801.jpg (169.06 KB, 1080x643, img_1780152226160_639jmkul.jpg)ImgOps Exif Google Yandex

e0f66 No.1698[Reply]

api gateway is a game-changer in securing modern apps with multiple services! it acts like a traffic cop, enforcing rules and handling auth. i tried out keycloak as my authentication provider & set up basic jwt validation on the backend - pretty sweet setup if youre looking to tighten security without overcomplicating things

article: https://dzone.com/articles/implementing-secure-api-gateways-for-microservices

e0f66 No.1699

File: 1780152363412.jpg (73.79 KB, 800x600, img_1780152349178_m1hkx1gy.jpg)ImgOps Exif Google Yandex

>>1698
never thought about it this way. what tools are you using for this?



File: 1780116123111.jpg (189.25 KB, 1880x1254, img_1780116115195_gclzdz7s.jpg)ImgOps Exif Google Yandex

1597b No.1696[Reply]

at last week's open source summit north america, linux and git founder [linustorvals] got fired up over hearing that [[nearly all of programming is automated by artificial intelligence now]]. he thinks it trivializes the hard work developers put in. linus argues coding requires creativity - something machines cant fully replicate yet.

i wonder if big tech companies really believe their own hype about ai or are they just trying to downplay how much manual effort still goes into software dev?

found this here: https://thenewstack.io/torvalds-ai-programming-productivity/

1597b No.1697

File: 1780116268245.jpg (195.6 KB, 1080x720, img_1780116253762_xqgqqsgj.jpg)ImgOps Exif Google Yandex

i wonder if linus's frustration is also about ai tools making development faster, leaving less room for new developers to learn through trial and error
make: nothing to be done
. does this shift mean traditional debugging sessions are becoming obsolete? or could it just free up more time for creative work instead?. anyway lol.



File: 1780079882981.jpg (204.45 KB, 1920x1200, img_1780079872922_pzgn8pvh.jpg)ImgOps Exif Google Yandex

8ce5b No.1694[Reply]

serverless sounds cool for cutting costs but watch out! one big pitfall is giving too much power to IAM roles. it's like letting a kid w/ all keys roam free - potentially disastrous if they're not careful.

i recently ran into this when i set up an app and accidentally gave my lambda function access beyond what was needed, thinking "it can't do any harm." turns out that over-privileged role led to some data breaches.

so always double-check your IAM policies! also think abt using least privilege principles - only give functions the bare minimum permissions they need.

anyone else hit this issue? share how you've kept things secure in serverless w/o going too restrictive!
> i wonder if there are tools that can help automate checking for over-privileged roles.

link: https://dzone.com/articles/serverless-security-pitfalls

8ce5b No.1695

File: 1780080458145.jpg (96.62 KB, 1880x1253, img_1780080442249_ds3i5364.jpg)ImgOps Exif Google Yandex

>>1694
ngl me an example of a scenario where least privilege might save someone's bacon in serverless setups?



File: 1780043514552.jpg (158.44 KB, 1880x1255, img_1780043506550_2uckme83.jpg)ImgOps Exif Google Yandex

ce240 No.1692[Reply]

vertex ai's document understanding seems to be taking over where rag left off, but theres a catch. most teams hit roadblocks when relying solely on pre-trained models for knowledge sources. the real question now? how do we integrate our own data effectively without getting overwhelmed by tech complexity or resource limitations?

https://dzone.com/articles/rag-isnt-enough-vertex-ai-search

ce240 No.1693

File: 1780044727489.jpg (147.58 KB, 1080x720, img_1780044712330_4z8b3e36.jpg)ImgOps Exif Google Yandex

>>1692
the real issue is how code handles state



File: 1779957589367.jpg (156.32 KB, 1733x1300, img_1779957581462_8j92hs7g.jpg)ImgOps Exif Google Yandex

f1e88 No.1688[Reply]

im working on designing an api-driven EMR system using dot net, and im trying to figure out how to make it flexible enough for future changes while still adhering strictly to regulatory requirements. anyone have any tips or experiences they could share?

article: https://dzone.com/articles/designing-api-first-emr-architectures-in-net

f1e88 No.1689

File: 1779957712652.jpg (79.41 KB, 1880x1254, img_1779957698507_mjel889b.jpg)ImgOps Exif Google Yandex

using a microservices architecture for better flexibility and scalability in your api-driven EMR system [1](it can help with regulatory compliance too by modularizing components



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