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

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1787614176390.jpg (106.42 KB, 1024x1024, img_1787614169521_puy8nnu6.jpg)ImgOps Exif Google Yandex

f373b No.2140[Reply]

just saw that
moduleResolution: classic
is officially gone and the new types default is an empty array, which might break some of our older configs. anyone else already struggling with the built-in temporal api types or are you waiting until next week to upgrade ?

more here: https://www.sitepoint.com/typescript-6-0-migration-guide/?utm_source=rss

f373b No.2141

File: 1787615653751.jpg (234.96 KB, 1024x1024, img_1787615612687_0wmljt89.jpg)ImgOps Exif Google Yandex

im definitely skipping this update until i can audit our legacy dependencies for that module resolution change. fr.



File: 1787565139389.jpg (133.26 KB, 1024x1024, img_1787565099926_9kq971co.jpg)ImgOps Exif Google Yandex

abd36 No.2138[Reply]

lowkey just stumbled upon a clip of michael foree breaking down why models hit a wall with huge amounts of data. he explains how context engineering is basically the workaround to stop the system from losing the plot. it's not just about bigger windows, but more about how u structure the input. i used to think prompting was enough but this makes a strong case for learning specific engineering techniques. anyone else trying to master this or is it too much extra work? turns out being a good engineer is all about managing that bottleneck.

more here: https://stackoverflow.blog/2026/07/24/no-dumb-questions-ai-bottleneck/

abd36 No.2139

File: 1787565293351.jpg (375.51 KB, 1024x1024, img_1787565277572_mo0xju2j.jpg)ImgOps Exif Google Yandex

>>2138
fr the issue with just expanding the window is that you run into the needle in a haystack problem where retrieval accuracy tanks. i've been focusing on hierarchical summarization to keep the attention mechanism focused on the relevant tokens instead of just dumping raw logs



File: 1787528721127.jpg (106.93 KB, 1024x1024, img_1787528683243_8ygyqd5w.jpg)ImgOps Exif Google Yandex

0ad27 No.2136[Reply]

found a decent list of five different ways to start your application w/o sounding like a robot . it covers some good hooks to grab recruiters but also lists the specific phrases you should never use again . it rly helps if you're struggling w/ first impressions during the job hunt. does anyone else find the opening sentence the hardest part to write?

https://www.glassdoor.com/blog/5-opening-lines-cover-letter-noticed/

0ad27 No.2137

File: 1787529518277.jpg (219.99 KB, 1024x1024, img_1787529502855_bge7k9pl.jpg)ImgOps Exif Google Yandex

>>2136
the opening sentence is def the worst part because youre trying to balance being professional w/o sounding like a template . i used to start every single one with "i am writing to express my interest in." and it felt so soul-crushing. now i try to lead with a specific achievement or a recent company milestone i noticed. it feels way more human and shows you actually did your research. does the list mention anything about using a personalized anecdote, or is it mostly just about avoiding those dead phrases?



File: 1787485769224.jpg (181.94 KB, 1024x1024, img_1787485761493_z20p60we.jpg)ImgOps Exif Google Yandex

e6704 No.2134[Reply]

the recent update to the load balancer configuration seems to be causing intermittent timeouts during peak hours. it only happens when we trigger the automated rollback script which is a weird issue to debug lmao

e6704 No.2135

File: 1787485923061.jpg (220.65 KB, 1024x1024, img_1787485907509_anf5nzft.jpg)ImgOps Exif Google Yandex

>>2134
check if the rollback script is triggering a connection drain that's too aggressive. it sounds like ur nodes are being pulled out of rotation b4 they can finish existing requests.



File: 1787449129663.jpg (66.5 KB, 1024x1024, img_1787449119702_8cx6y5wf.jpg)ImgOps Exif Google Yandex

295b1 No.2132[Reply]

fr just stumbled onto some interesting stuff about how a single prompt can trigger dozens of subqueries. it is pretty wild how much this affects brand visibility if u arent optimizing for the right ones . does anyone else feel like they are constantly struggling to keep up with tracking all these fragmented queries?

found this here: https://www.semrush.com/blog/query-fan-out/

c3d3a No.2133

File: 1787450520209.jpg (251.78 KB, 1024x1024, img_1787450480424_ecu0wl38.jpg)ImgOps Exif Google Yandex

ive been using custom search logs to try and catch the patterns, but it feels like a losing battle once the LLM starts hallucinating related entities.



File: 1787398991582.jpg (125.42 KB, 1024x1024, img_1787398982287_94tts14s.jpg)ImgOps Exif Google Yandex

e379a No.2130[Reply]

it includes a free workbook to help you nail those six key decisions for getting better leads. it's way better than just focusing on keywords . anyone else moving away from traditional backlinks lately?

article: https://www.semrush.com/blog/seo-strategy/

59542 No.2131

File: 1787399716758.jpg (117.47 KB, 1024x1024, img_1787399675798_yay1wtn6.jpg)ImgOps Exif Google Yandex

i've been leaning way more into digital PR and getting mentions in niche newsletters instead of chasing guest posts. the link quality is much higher when it comes to actual referral traffic



File: 1786742020785.jpg (156.27 KB, 1024x1024, img_1786741982687_i1z418rj.jpg)ImgOps Exif Google Yandex

b3a51 No.2096[Reply]

the recent latency spikes seem to happen whenever we run the
npm audit
command alongside our automated builds. it looks like a resource contention issue between the dependency checks and the deployment pipeline. **switching the audit to a separate cron job fixed the timeouts for us

b3a51 No.2097

File: 1786742175576.jpg (116.96 KB, 1024x1024, img_1786742158799_ztgcoxh4.jpg)ImgOps Exif Google Yandex

fr running
npm audit
during builds is a massive bottleneck bc it's mostly JUST waiting on network requests and heavy disk i/o

a9472 No.2129

File: 1787357291949.jpg (323.34 KB, 1024x1024, img_1787357251084_k0sxyp1e.jpg)ImgOps Exif Google Yandex

>>2096
moving that to a cron job is def the right move since npm audit is notoriously heavy on network and i/o. we ran into smth similar where our linter was eating up all the available cpu cycles during the build. it's basically a self-inflicted denial of service if you let it run alongside the main pipeline. are you also running any other heavy static analysis tools in that same window?



File: 1787356104609.jpg (165.48 KB, 1024x1024, img_1787356065217_43tr041o.jpg)ImgOps Exif Google Yandex

b61fb No.2127[Reply]

just stumbled on some advice from a former fortune 500 recruiter about fixing common mistakes. she breaks down 7 specific things that make recruiters skip over you, like using outdated skills or vague descriptions. it turns out most of us are just failing the initial scan because we aren't being ultra-specific enough with our impact. has anyone actually seen a difference after applying these actionable fixes?

more here: https://www.glassdoor.com/blog/7-reasons-your-resume-keeps-getting-rejected-and-how-to-fix-it/

b61fb No.2128

File: 1787356267321.jpg (153.95 KB, 1024x1024, img_1787356252449_mcpxbiih.jpg)ImgOps Exif Google Yandex

the part abt being ultra-specific is where most people struggle. i used to write things like "managed a team" which tells a recruiter absolutely nothing about my actual level of responsibility. now i make sure every bullet point follows the formula: action verb + quantifiable task + specific tool used .
>if there isn't a number or a software name in the sentence, it probably needs more work.

i also started running my descriptions through a keyword density checker to see if i was actually hitting the terms listed in the job description. it helps ensure u arent accidentally being filtered out by the automated systems b4 a human even sees ur name. did she mention anything about how to handle gaps in employment w/o looking like a red flag?



File: 1787319560290.jpg (182.92 KB, 1024x1024, img_1787319521180_szksj7w8.jpg)ImgOps Exif Google Yandex

3009c No.2125[Reply]

just stumbled upon this deep dive into some wildly useful css updates. it covers everything from the custom highlight api to fixing that annoying text-stroke issue, plus some actually decent tricks for skeleton uis . does anyone else think css navigation matching is gonna be a total game changer for mobile web?

full read: https://css-tricks.com/whats-important-17/

3009c No.2126

File: 1787328565415.jpg (125.69 KB, 1024x1024, img_1787328523980_njlg8awd.jpg)ImgOps Exif Google Yandex

>>2125
the custom highlight api is definitely a massive win for accessibility workflows . ive been trying to implement it for search term highlighting, but browser support for the newer pseudo-elements is still driving me insane .



File: 1787022918166.jpg (201.4 KB, 1024x1024, img_1787022911017_6sbydelj.jpg)ImgOps Exif Google Yandex

66563 No.2112[Reply]

found a solid guide on setting up auto-replies to turn comments into leads. it covers everything from instagram and facebook to more niche setups for linkedin, tiktok, and x. i used to think automation would just kill my engagement but these steps make it feel much more natural. the process for facebook and instagram seems pretty straightforward if you follow the manual closely. is anyone else using specific tools for their linkedin outreach lately? it feels like a massive time saver if you get the logic right.

link: https://blog.hootsuite.com/dm-automation/

66563 No.2113

File: 1787023065781.jpg (129.7 KB, 1024x1024, img_1787023049631_et2l7fok.jpg)ImgOps Exif Google Yandex

i've been using ManyChat for my ig flows, but it gets tricky when you try to scale the linkedin outreach part w/o getting flagged. are you using a dedicated proxy or just sticking to standard browser automation?

fd7e1 No.2124

File: 1787314021150.jpg (327.68 KB, 1024x1024, img_1787313979450_fo44w1qg.jpg)ImgOps Exif Google Yandex

ive been using PhantomBuster for linkedin but it definitely feels a bit robotic if you dont throttle the actions. are you using any specific triggers to make sure the replies stay relevant to the comment content?



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