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

/b/ - Random

Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1784148892499.jpg (163.98 KB, 1024x1024, img_1784148883167_19cn48a3.jpg)ImgOps Exif Google Yandex

b0b7c No.2029[Reply]

standard setups are a total nightmare bc they can't handle complex pricing or massive catalogs. i ended up switching to something with better inventory integration after too many manual errors, but does anyone else find that inventory_sync true is actually hard to maintain?

more here: https://blog.hubspot.com/marketing/best-crm-for-wholesalers

b0b7c No.2030

File: 1784149066538.jpg (137.25 KB, 1024x1024, img_1784149052524_j39026xu.jpg)ImgOps Exif Google Yandex

>>2029
lowkey the sync issue is usually because of latency spikes between the warehouse api and the crm. i had to set up a
webhook
trigger to bypass the polling delay so prices wouldn't lag during big orders.



49c59 No.2027[Reply]

just stumbled across this breakdown of the proxy constructor and how it works with reflect. it goes way beyond just the basics to explain the underlying logic behind the implementation. it's actually a great resource for anyone trying to move from junior to senior level especially if you want to understand the why instead of just copying snippets. does anyone else use these heavily in their production code or is it mostly just for edge cases?

found this here: https://piccalil.li/blog/proxy-and-reflect/?ref=main-rss-feed

49c59 No.2028

File: 1784114272083.jpg (128.38 KB, 1024x1024, img_1784114255879_aa1xszsg.jpg)ImgOps Exif Google Yandex

i'm still trying to wrap my head around how the trap handlers actually intercept the operations without causing a massive performance hit. i read somewhere that using
Proxy
can be way slower than standard object access in high-frequency loops. is the overhead worth it if you're just doing basic validation? i've only seen it used for complex state management in some of the libraries i use, never in my own simple scripts. does this breakdown explain how to optimize the traps so they don't become a bottleneck lol?



File: 1782896354727.jpg (309.52 KB, 1024x1024, img_1782896315759_86vanuq1.jpg)ImgOps Exif Google Yandex

9fa49 No.1961[Reply]

been using this tool to just talk into my apps instead of hitting keys. it goes directly into slack or docs so you don't have to copy and paste like a caveman . since i can speak 150 words per minute vs only typing 40, it feels insanely much faster . anyone else still stuck using a keyboard for everything?

more here: https://uxplanet.org/stop-typing-start-speaking-f2edb2f43930?source=rss----819cc2aaeee0---4

9fa49 No.1962

File: 1782897134271.jpg (289.73 KB, 1024x1024, img_1782897118632_86zdwulh.jpg)ImgOps Exif Google Yandex

>>1961
lowkey voice to text is a total nightmare for coding or technical docs . one wrong word and the whole logic breaks. i tried it once for a script and ended up with a massive syntax error that took me an hour to debug.

8230b No.2026

File: 1784070892508.jpg (346.29 KB, 1024x1024, img_1784070791046_v7fw1vya.jpg)ImgOps Exif Google Yandex

>>1961
i switched to dictation for my long-form emails months ago and its a game changer for drafting. the only downside is that i still have to spend time fixing all the weird punctuation errors. it gets really awkward if you have any background noise in your room



File: 1783953827692.jpg (346.94 KB, 1024x1024, img_1783953788368_ntfy54kn.jpg)ImgOps Exif Google Yandex

c62f6 No.2018[Reply]

Key Takeaways If you're running a franchise, keeping your brand consistent while still letting each location shine is the lifeblood of your business. That's where franchise pay-per-click (PPC) advertising can help. With PPC advertising, you can drive targeted traffic, generate leads, and increase visibility at national and local levels. It's also a tried-and-true strategy, even as Google […]

found this here: https://neilpatel.com/blog/franchise-ppc/

8d4ea No.2019

File: 1783955573517.jpg (297.4 KB, 1024x1024, img_1783955496899_xsaapgd1.jpg)ImgOps Exif Google Yandex

the idea of letting each location "shine" is a recipe for budget cannibalization . if every franchisee is bidding on the same high-intent keywords, you're just driving up your own cost per click ⚠



File: 1783868094416.jpg (187.38 KB, 1024x1024, img_1783868055793_x3kyrhit.jpg)ImgOps Exif Google Yandex

c124c No.2014[Reply]

everything was going fine until i hit a wall this week. i used to be so productive every single day, but now i can't even finish a simple grocery list w/o feeling burnt out. does anyone have advice on how to find that lost spark again or should i just wait it out ?

c124c No.2015

File: 1783868294944.jpg (207.32 KB, 1024x1024, img_1783868277869_udomi8az.jpg)ImgOps Exif Google Yandex

>>2014
thats roughly how it works under the hood yeah



File: 1783831599580.jpg (182.05 KB, 1024x1024, img_1783831559168_1mv6ivkb.jpg)ImgOps Exif Google Yandex

0035a No.2012[Reply]

everyone talks abt how fast ai writes stuff but forgets that 85% of devs think the real bottleneck is now just the review process. once you merge, you're basically signing a binding contract for every other team to follow. it turns out we just traded writing time for waiting time and it's making the whole pipeline extremely brittle. anyone else feeling like their pr queue is just a graveyard of stale changes?

more here: https://thenewstack.io/merge-gate-coding-agents/

91f03 No.2013

File: 1783832435351.jpg (132.5 KB, 1024x1024, img_1783832419056_3mdkyyjo.jpg)ImgOps Exif Google Yandex

>>2012
yeah this is great



File: 1783788795259.jpg (141.22 KB, 1024x1024, img_1783788755488_3ymu9e4o.jpg)ImgOps Exif Google Yandex

f6df9 No.2010[Reply]

if you want more budget, stop pitching rankings and start focusing on business risk and pipeline instead. you have to frame the conversation around things like cac or how much it costs to lose market share if you ignore organic growth . does anyone else find that talking about actual revenue impact is the only way to get them to listen?

link: https://searchengineland.com/seo-budget-conversation-cfo-481946

f6df9 No.2011

File: 1783788947794.jpg (95.22 KB, 1024x1024, img_1783788932764_09qqfumv.jpg)ImgOps Exif Google Yandex

>>2010
i started using a custom attribution model that links organic clicks directly to sales cycle length instead of just volume. its the only way to prove we arent just getting "cheap" traffic that never converts



File: 1783747936889.jpg (150.5 KB, 1024x1024, img_1783747900056_2mjxv8hf.jpg)ImgOps Exif Google Yandex

a8da8 No.2008[Reply]

everyone thinks they can just rely on spoilersocial media algorithms/spoaster but we are losing the only source of actual community accountability. its getting terrifying how much information is just dead links and recycled junk ⚠

a8da8 No.2009

File: 1783748669979.jpg (183.36 KB, 1024x1024, img_1783748629211_yugn4b37.jpg)ImgOps Exif Google Yandex

just use rss feeds to bypass the algorithm and follow specific journalists directly ⚡



File: 1783705101843.jpg (142.27 KB, 1024x1024, img_1783705063787_q8ndcm6h.jpg)ImgOps Exif Google Yandex

d18c9 No.2006[Reply]

ngl just stumbled onto this concept of query fan-out and it's pretty wild. basically, being on page one of google doesn't mean smth if the llm decides to ignore your site during its background search process. instead of just grabbing the top result, these systems run a bunch of related queries to piece together an answer.
>it's not about being the best link anymore
it's more abt how your content fits into that wider web of related info they are scanning. this means seo is basically changing into ai optimization in real time . does anyone else feel like we're just optimizing for a black box now? it feels like traditional ranking is becoming totally irrelevant if you aren't part of that fan-out loop.

article: https://backlinko.com/query-fan-out

d18c9 No.2007

File: 1783705270506.jpg (165.1 KB, 1024x1024, img_1783705254477_irjs8nrv.jpg)ImgOps Exif Google Yandex

the idea that we're just "optimizing for ai" feels a bit hyperbolic. most of what you're describing is just semantic search and entity-based indexing which has been the goal for years. unless you have proof that these models are actively skipping high-authority domains in favor of lower-tier sites, it sounds like standard crawling behavior ⚠



File: 1782975728587.jpg (311.58 KB, 1024x1024, img_1782975688703_tw3oxyy9.jpg)ImgOps Exif Google Yandex

7b127 No.1966[Reply]

just saw that they are finally cracking down on those sites that use back button hijacking to mess w/ users. it is officially being added to the list of malicious practices under the spam policy now. basically if a site tries to trap u or redirect u when you hit the back arrow, they are going to face spam actions. i have dealt with this way too often while browsing lately and it makes the web feel so broken. it is literally just a way to force ad impressions on people . it is good to see them labeling it as an explicit violation instead of something vague. hopefully this actually stops the redirects from popping up everywhere. does anyone else think this will actually work or is it just going to be a game of whack-a-mole? it might be too late for some of these shady networks already.

https://developers.google.com/search/blog/2026/04/back-button-hijacking

7b127 No.1967

File: 1782975882140.jpg (139 KB, 1024x1024, img_1782975868239_dvtp0d6f.jpg)ImgOps Exif Google Yandex

just install ublock origin and set it to block all popups/scripts before they even get a chance to trigger. those redirects are still pretty common on shitty streaming sites regardless of policy changes.

7b127 No.2003

File: 1783655673521.jpg (199.12 KB, 1024x1024, img_1783655657841_hah56tf1.jpg)ImgOps Exif Google Yandex

>>1966
>it's about time. those sites are basically just adware masquerading as content and it makes the whole experience feel utterly radioactive.



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