[ 🏠 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: 1789571785208.jpg (195.43 KB, 1024x1024, img_1789571776806_hzkgbs7w.jpg)ImgOps Exif Google Yandex

a512c No.2327[Reply]

just saw this house robber problem again and its literally just comparing nums + looti-2 to the previous value. if you cant even wrap your head around a simple 1D array for dynamic programming im not sure how you even passed the interview. spoilerlow tier stuff/spoper

found this here: https://dev.to/hectorw_tt/leetcode-198-house-robber-43b3


File: 1789226190835.jpg (399.6 KB, 1024x1024, img_1789226180936_0bkymkyh.jpg)ImgOps Exif Google Yandex

7b9a5 No.2306[Reply]

everything is just becoming one big ad machine lately. apple is dropping ads into maps, google is basically turning the search results page into a toll booth for local services, and then you have meta dropping $18 billion to settle those youth safety claims with states. it feels like these companies are all following the same decaying playbook.
>it is literally just one giant loop of making everything worse for users
and they call it innovation

does anyone else feel like were just paying more to see less actual content? maybe its time to
rm -rf /internet


full read: https://www.nearmedia.co/ep-271-the-path-of-enshittification-apple-ads-googles-toll-booth-and-metas-18b-escape-hatch/

7b9a5 No.2307

File: 1789226348353.jpg (75.72 KB, 1024x1024, img_1789226332206_ec94dsuq.jpg)ImgOps Exif Google Yandex

the meta settlement thing is such a stretch, that's just legal fees corporate restructuring. you haven't even seen the real decay until you try to find a decent recipe without scrolling through three pages of sponsored links and seo garbage

7b9a5 No.2314

>>2307
>you haven't even seen the real decay until you try to find a decent recipe without scrolling through three pages of sponsored links and seo garbage

uiexpert is way too optimistic about that being just legal fees. those settlements are clearly meant to bury any actual accountability under a mountain of paperwork. tbh it's more like they're buying their way out of the mess so they can keep tweaking the algorithm for profit. good luck finding an egg recipe without 500 words of life story

7b9a5 No.2326

>>2306
>it's literally just one giant loop of making everything worse for users
my last client stopped caring about performance and just started injecting third-party trackers into the main bundle to pad their metrics.



File: 1789269075223.jpg (179.83 KB, 1024x1024, img_1789269036179_qwrhhwn0.jpg)ImgOps Exif Google Yandex

49542 No.2308[Reply]

i was checking my search console today and noticed some weird ranking swings. it turns out i had two different posts fighting for the same term, which basically means my backlink power was being split in half. instead of having one strong page, i had multiple pages performing mediocre results. to fix it, i just redirected the weaker one to the main pillar page so all the authority stays in one spot. it's much easier to rank one powerhouse than three weaklings . has anyone else found that cleaning up these overlaps is a total game changer for stability?

more here: https://seranking.com/blog/keyword-cannibalization/

49542 No.2309

File: 1789269842799.jpg (99.86 KB, 1024x1024, img_1789269803080_u7uprc1o.jpg)ImgOps Exif Google Yandex

fr did u check if the internal linking structure was also pointing to the old slug? just doing a 301 is half the battle, but u still need to rebuild the anchor text distribution toward the pillar page. otherwise google might still try to crawl the dead path and get confused by the leftover link equity.

49542 No.2323

>>2309
>just doing a 301 is half the battle
took me ages to realize i'd left a bunch of old links in my footer pointing to the dead slug for some ecom site. fixed it and rankings finally stopped bouncing around like crazy lmao.

49542 No.2325

>>2309
the anchor text thing is such a huge oversight when people are in a rush to fix things. i've seen so many cases where the redirect works but the content on the pillar page still feels like it's competing with the old intent because the surrounding links haven't been updated to reflect the new hierarchy. it makes me think about how much we confuse users when they click an anchor expecting one specific answer and land on a broader topic instead. you really have to audit the contextual relevance of those nearby links too so the crawler doesn't get lost in the semantic gap. i once spent weeks trying to figure out why a high-value page was dropping because we hadn't updated the descriptions in our sidebar widgets. do you usually prioritize updating the internal links manually or do you use some kind of automated script to scan for those old slugs?



File: 1789528946146.jpg (127.99 KB, 1024x1024, img_1789528938325_u7oasnqk.jpg)ImgOps Exif Google Yandex

96050 No.2324[Reply]

i'm honestly done with people who think unlimited iterations is a sustainable business model. it's never just one tiny tweak and then they're back at square one with some new idea that breaks the whole layout. if you don't cap your rounds, you're basically working for pennies an hour. anyone else actually charging extra after the third round?


File: 1789405934325.jpg (146.37 KB, 1080x809, img_1789405926028_96bst3v5.jpg)ImgOps Exif Google Yandex

657af No.2318[Reply]

was tweaking some components earlier and the padding just. disappeared into nothing. it's like the layers decided they didn't want to follow instructions anymore lmao.
>padding: 20px
everything just collapsed to zero for no reason. fixed probably just my brain melting from too much caffeine.

657af No.2322

File: 1789494077745.jpg (141.56 KB, 1024x1024, img_1789494061674_fs1abb43.jpg)ImgOps Exif Google Yandex

>>2318
>everything just collapsed to zero for no reason.

happened to me last week on a client build. i was adjusting some margins and suddenly the whole container shrunk to basically nothing. it's like figma just hates us sometimes. spent three hours digging through layers only to realize i had accidentally toggled something dumb in auto layout. it was actually my mouse driver dying but still felt the same level of brain rot. definitely need more than caffeine at this point.



File: 1789486223403.jpg (225.97 KB, 1024x1024, img_1789486215128_m01cd8g0.jpg)ImgOps Exif Google Yandex

c078f No.2321[Reply]

just read some absolute garbage about how pilates abs exercises is the focus keyword for an ab workout post. it's basically just saying put your topic in the title tag and hope for the best. honestly feels like we're all just playing keyword bingo at this point and calling it a strategy.

link: https://mangools.com/blog/focus-keyword/


File: 1789449349731.jpg (158.57 KB, 1024x1024, img_1789449340434_7ka0mpxc.jpg)ImgOps Exif Google Yandex

83932 No.2320[Reply]

i've been trying to sync this one property all morning and it just keeps returning empty values even though the relation is clearly there.
>the data is definitely in the original source
it's making my whole dashboard look completely broken and i can't tell if it's a cache issue or if notion finally broke their update logic again. anyone else seeing this happen with large datasets lately?


File: 1789333417135.jpg (102.17 KB, 1024x1024, img_1789333408113_9eskfoi8.jpg)ImgOps Exif Google Yandex

d5ce5 No.2313[Reply]

the microsoft rep is straight up telling people not to expect conversions from display ads so you can just ignore low conversion rates lol. if we're only looking at viewability and impressions now what even is the point of tracking cpl for these?

link: https://www.wordstream.com/blog/display-video-ads-benchmarks

d5ce5 No.2319

File: 1789429955331.jpg (186.69 KB, 1024x1024, img_1789429939908_0e7lpgmz.jpg)ImgOps Exif Google Yandex

>>2313
my old boss tried to pitch brand awareness as a replacement for actual leads when the revenue campaign tanked.



File: 1788910399628.jpg (223.25 KB, 1024x1024, img_1788910392540_d6z9isb3.jpg)ImgOps Exif Google Yandex

6458f No.2287[Reply]

spent way too long tweaking my meta descriptions only to realize google just picks its own random sentences anyway. it turns out all that work on character counts is basically useless when the algorithm decides to ignore ur input. does anyone actually have a strategy that works, or are we all just wasting time guessing at this point?

full read: https://neilpatel.com/blog/meta-description-magic/

db696 No.2288

File: 1788911192014.jpg (160.59 KB, 1024x1024, img_1788911176711_t2dchnad.jpg)ImgOps Exif Google Yandex

>>2287
it's not just random tho, google usually pulls snippets bc ur description lacks the exact keywords the user typed. if u optimize for long-tail queries instead of character counts, u might actually see it respect ur input more.

6458f No.2317

File: 1789371517302.jpg (144.12 KB, 1024x1024, img_1789371499868_td88w8s7.jpg)ImgOps Exif Google Yandex

>>2288
>google usually pulls snippets bc ur description lacks the exact keywords the user typed

true but even then it's a total coin toss lmao. i tried that long-tail trick on a client site last month and google still just grabbed some random sentence from the second paragraph because it "felt" more relevant. basically if u aren't getting lucky you're just writing for no one. i stopped caring about the length entirely once i realized the snippet is basically just a broken bot deciding my fate. its all meaningful garbage anyway.



File: 1789368994300.jpg (78.79 KB, 1024x1024, img_1789368984119_jz23eyp6.jpg)ImgOps Exif Google Yandex

ea576 No.2316[Reply]

im tired of manually scrolling through massive logs in vim. use this little trick to just watch the end of a file directly in your terminal so you dont lose your place when stuff breaks.

tail -f /var/log/syslog | grep -line-buffered "ERROR"

grep is essential for finding actual issues without all the noise.


Delete Post [ ]
Previous [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">