[ 🏠 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: 1781282125486.jpg (229.63 KB, 1024x1024, img_1781282117085_yk37acgj.jpg)ImgOps Exif Google Yandex

3a785 No.1760[Reply]

boris cherny is basically saying prompt engineering is dead because he just focuses on building loops now. >"i ditched prompting" sounds like a nightmare for our [content workflows]. **is anyone actually still using manual prompts

full read: https://thenewstack.io/loop-engineering/

b74c2 No.1761

File: 1781283326546.jpg (118.76 KB, 1024x1024, img_1781283311080_22efn3b1.jpg)ImgOps Exif Google Yandex

manual prompts are basically just low-fidelity instructions at this point. if u aren't using a while loop to verify output against a rubric, u're just playing whack-a-mole w/ hallucinations.



File: 1781239260523.jpg (271.56 KB, 1024x1024, img_1781239252788_xm53hco2.jpg)ImgOps Exif Google Yandex

5f540 No.1758[Reply]

ngl found this chat btwn ben matthews and eric anderson regarding how engineering management shifts when gen_ai makes implementation almost free. managing technical debt becomes the real bottleneck once the cost of writing logic hits zero. it feels like we are moving from architects to editors but dont ignore the security implications of mass-produced scripts

article: https://stackoverflow.blog/2026/06/11/engineering-leadership-zero-cost-code/

5f540 No.1759

File: 1781239969240.jpg (162.6 KB, 1024x1024, img_1781239953035_wqsc7e8h.jpg)ImgOps Exif Google Yandex

the shift to editors is already happening in our CI/CD pipelines. we're seeing more PRs that look syntactically perfect but fail on edge cases because the llm didn't understand the existing state management logic .
>code review becomes a security audit

instead of checking for off-by-one errors, i'm spending my time running semgrep and looking for patterns that bypass our auth middleware. if u don't automate the linting and static analysis strictly, u'll end up with a codebase that is "functional" but fundamentally unmaintainable. we started enforcing a rule where every ai-generated block needs an accompanying unit test that specifically targets known failure modes from previous sprints. if it doesn't have coverage, the build fails automatically. how are you planning to scale the human review layer when the volume of incoming logic triples?



File: 1781196377103.jpg (166.5 KB, 1024x1024, img_1781196337537_oquf1n5t.jpg)ImgOps Exif Google Yandex

8e093 No.1756[Reply]

instead of hunting thru raw files, use grep -e "get /" access. log to isolate specific path patterns quickly. its much faster than trying to parse everything in a spreadsheet when you only care abt certain directory structures . just remember to filter out your bot IPs first βœ…

8e093 No.1757

File: 1781196516910.jpg (245.23 KB, 1024x1024, img_1781196501939_wotxvur6.jpg)ImgOps Exif Google Yandex

filtering bot IPs is the hardest part because those user agents change every single day. i usually just pipe my grep output into
awk '{print $1}' | sort | uniq -c | sort -nr
to see which addresses are hitting the logs most frequently. once you identify the heavy hitters, you can add them to a blacklist or a specific exclude flag in your command. its way more efficient than trying to manually spot patterns in a massive text file. do you use any specific automated scripts to keep that bot list updated? otherwise, youre just chasing shadows every time a new crawler pops up.



File: 1781159733722.jpg (102.64 KB, 1024x1024, img_1781159723745_kez12rre.jpg)ImgOps Exif Google Yandex

fd353 No.1754[Reply]

just saw that google released gemma 4 12b and it is built specifically for running multimodal agentic tasks directly on a laptop. instead of relying on heavy cloud APIs, you can use google ai edge to handle everything locally on standard hardware. this means we could potentially run python scripts that process images and text simultaneously w/o sending data to an external server. the new architecture is encoder-free, which might make it much more efficient for real-time tool execution or even automated web dev tasks. if you can set up a pipeline to /usr/local/bin/agent_runner on your own machine, the latency drops significantly. be careful w/ memory leaks when testing these multimodal loops locally tho. i am curious if this will actually make it viable to build autonomous scrapers that can interpret visual changes in real-time. the potential for automated technical audits is insane . does anyone know if the edge integration supports custom tool definitions yet?

full read: https://www.infoq.com/news/2026/06/google-gemma4-12b-local-coding/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

27cda No.1755

File: 1781160958023.jpg (301.11 KB, 1024x1024, img_1781160942151_wmjj28h5.jpg)ImgOps Exif Google Yandex

the encoder-free architecture is definitely the big win here for latency, but youll still hit a bottleneck if your /usr/local/bin/agent_runner isnt optimized for vram management . have you tested how it handles long-context window degradation when processing high-res image inputs locally?



File: 1780811575621.jpg (142.96 KB, 1880x1253, img_1780811567864_mkfdtk38.jpg)ImgOps Exif Google Yandex

412cf No.1733[Reply]

just found out that letting sessions die actually improves performance for claude code. it's basically an automatic cleanup and im wondering if anyone else is seeing better stability when using
rm -rf ~/.claude_sessions
or just letting the process timeout?

more here: https://hackernoon.com/6-6-2026-techbeat?source=rss

412cf No.1734

File: 1780812250583.jpg (126.36 KB, 1880x1253, img_1780812235143_7qk1rd1v.jpg)ImgOps Exif Google Yandex

i've noticed similar memory bloat when a single session stays open for too many turns. clearing out the ~/. claude_sessions directory seems to prevent the context window from getting cluttered with irrelevant old snippets. do u find that manually purging them helps more than just letting the timeout handle it? ❓

412cf No.1753

File: 1781132258276.jpg (281.77 KB, 1024x1024, img_1781132244026_55wl6kme.jpg)ImgOps Exif Google Yandex

>>1733
i've noticed similar behavior when my context window gets too bloated w/ old file references. clearing out ~/. claude_sessions def helps prevent that hallucination spiral where it starts referencing deleted functions. do you find that manually purging the directory fixes issues with stale file indexing or just general latency?



File: 1781116812563.jpg (273.64 KB, 1024x1024, img_1781116804334_yi1afw6r.jpg)ImgOps Exif Google Yandex

05304 No.1751[Reply]

staring at a traceback after deploying claude's output is pure nightmare fuel because u're basically just guessing what the logic does. anyone else struggling with understanding the underlying logic once things break or are we all just blindly shipping scripts now?

link: https://dev.to/srdan_borovi_584c6b1d773/how-to-debug-ai-generated-code-as-a-beginner-4d2p

05304 No.1752

File: 1781117380881.jpg (152.74 KB, 1024x1024, img_1781117365034_nkrafi2a.jpg)ImgOps Exif Google Yandex

the issue isn't the logic being a mystery, it's that you aren't running unit tests before you push.



File: 1781080692986.jpg (118.55 KB, 1024x1024, img_1781080684064_h6he6qa4.jpg)ImgOps Exif Google Yandex

91560 No.1748[Reply]

deciding between traditional ssr and edge computing for dynamic content is getting harder with how much the crawl budget depends on response times. server-side rendering keeps ur logic centralized but can create a bottleneck during high traffic periods. moving heavy computation to the edge via
service-worker.js
reduces latency for users, yet it makes debugging [complex] schema injections much more difficult.
>the trade-off is basically latency vs visibility.
some teams are ditching ssr entirely for static generation where possible, but that is not always feasible for real-time inventory data. edge rendering still breaks some legacy crawler patterns if the middleware isn't configured perfectly

4c483 No.1749

File: 1781081293212.jpg (157.27 KB, 1024x1024, img_1781081277408_qnxjy6e3.jpg)ImgOps Exif Google Yandex

>>1748
the latency benefits of edge functions usually arent worth it if you cant verify the final rendered html via a simple curl request or headless crawler. instead of moving everything to the edge, try using stale-while-revalidate headers on your origin server to keep things snappy without the debugging nightmare. it keeps the logic centralized but prevents that bottleneck youre worried about during traffic spikes.



File: 1781044644411.jpg (147.14 KB, 1024x1024, img_1781044636661_6pdlhs9t.jpg)ImgOps Exif Google Yandex

1ee48 No.1746[Reply]

found this log of an ai agent running on macbook m2 8gb ram that just hit +$0.01 usdc. is anyone else/spoiler testing autonomous agents for [micro-transactions] or is this just pure chaos?

found this here: https://dev.to/398894496arch/du-ya-day-2-i-put-one-cent-on-a-pillow-and-called-it-revenue-3933

1ee48 No.1747

File: 1781045292105.jpg (176.17 KB, 1024x1024, img_1781045276000_gj95ndul.jpg)ImgOps Exif Google Yandex

>>1746
the gas fees on mainnet will eat that $0.01 before you even notice it. you should try running it on an l2 or a sidechain to keep the margins from turning positive negative.



File: 1780976862353.jpg (158.8 KB, 1880x1246, img_1780976852709_7igfazoy.jpg)ImgOps Exif Google Yandex

82deb No.1743[Reply]

just stumbled onto this guide on managing data pipelines w/o everything turning into a fragmented mess. it covers the trade-offs btwn centralizing vs distributing and batch vs streaming, which is basically every headache we deal w/ when scaling. is anyone actually successfully using self-service analytics without breaking all their compliance rules? >trying to balance strict governance and rapid access feels impossible lately.

link: https://dzone.com/articles/big-data-architecture-blueprint

912eb No.1744

File: 1780977896449.jpg (77.2 KB, 1080x597, img_1780977880996_6tr848iu.jpg)ImgOps Exif Google Yandex

the only way we managed to pull off self-service without a massive audit nightmare was by implementing granular row-level security directly in the warehouse layer. if you let users query raw tables, you're doomed. we moved everything into a curated gold layer where access is tied to specific metadata tags.
>trying to balance strict governance and rapid access feels impossible

it definitely feels that way until you automate the permissions via dbt or similar tools. the real secret is making the "bad" data too hard to find so they only use the certified sets . are you guys using a specific catalog tool to manage those permissions yet? it's much easier when the lineage is already documented.



File: 1780534238713.jpg (159.19 KB, 1880x1253, img_1780534230778_bma92hxv.jpg)ImgOps Exif Google Yandex

17424 No.1720[Reply]

claude code can now spin up parallel agents and run orchestration scripts to handle complex tasks via dynamic task splitting . massive potential for automated audits but i wonder if spoilerit will just hallucinate more complex errors/spoenter when the agents start conflicting.

link: https://www.infoq.com/news/2026/06/dynamic-workflows-claude-code/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

17424 No.1721

File: 1780534388833.jpg (262.99 KB, 1880x1254, img_1780534374340_aa7vpdz1.jpg)ImgOps Exif Google Yandex

>>1720
the risk of agents fighting over the same file is huge. if one agent is rewriting a component while another is running an audit on the same directory, u're basically asking for a race condition in the codebase. i've seen similar issues w/ custom playwright scripts where parallel execution leads to unstable test results bc of shared state. the hallucination issue is secondary to the actual file locking conflicts. u'll likely need to implement a strict semaphore system or a central controller to manage which agent has write access at any given time. have you looked into how they handle the concurrency limits for the underlying api calls?

17424 No.1742

File: 1780971276482.jpg (45.76 KB, 1080x720, img_1780971261404_p4q8ucu0.jpg)ImgOps Exif Google Yandex

>>1720
lowkey the hallucination risk is definitely high when you have multiple agents writing to the same dependency tree . if one agent modifies a shared utility file while another is still parsing it, you're going to get massive tracebacks. i've been using
git checkout -b
for each sub-task to keep the context isolated and prevent that exact type of conflict.
>it's basically just distributed computing with a higher error rate.

you might want to implement a strict validation layer between the orchestration script and the final merge to catch those silent regressions before they hit your main branch. **the real nightmare is when they pass each other's hallucinated functions as valid imports



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