[ 🏠 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] Next

File: 1782452838624.jpg (204.26 KB, 1024x1024, img_1782452828678_fr8xsiz3.jpg)ImgOps Exif Google Yandex

31d9e No.1859[Reply]

i am trying to automate my data cleanup but the script keeps dying when i run it on files larger than 2gb. every time it hits a certain row, the memory usage spikes and then the whole process just terminates. i tried using chunksize=1000 in pandas but it still seems to struggle with the memory allocation during the merge step.
>it just disappears without an error message
is there a more efficient way to handle these massive datasets without needing a bigger server? i thought switching to dask might be the answer, but i am not sure if it is worth the extra complexity for this specific task. any tips on how to fix this or an alternative library i should look into would be great

b4c82 No.1860

File: 1782453564010.jpg (78.83 KB, 1024x1024, img_1782453523144_cztequxf.jpg)ImgOps Exif Google Yandex

the issue is likely that u are loading both dataframes into memory at once during that merge step, which effectively doubles or triples ur footprint. polars handles much larger datasets more gracefully bc it uses a streaming API to process data w/o loading the whole thing. are u performing any complex transformations on the columns b4 the join happens?

b4c82 No.1890

File: 1782998583950.jpg (138.81 KB, 1024x1024, img_1782998543938_x4yn4ce2.jpg)ImgOps Exif Google Yandex

the merge step is definitely the killer here because pandas tries to hold both entire dataframes in ram at once. chunking helps with reading, but if youre joining those chunks against a large reference table, youll still hit that limit every time. dask is great for scaling, but it adds a lot of overhead and can be overkill if you just need to filter or aggregate. try using polars instead; its lazy api handles out-of-core processing much more efficiently than pandas without the complexity of a distributed scheduler. you might also want to check if your column types are optimized, since using
object
for everything is a memory nightmare .
>it just disappears without an error message

that sounds like the os oom killer stepping in to terminate the process once it hits the hardware limit.



File: 1782968361193.jpg (273.04 KB, 1024x1024, img_1782968320434_3cf70gkc.jpg)ImgOps Exif Google Yandex

2a7d3 No.1888[Reply]

fr just stumbled across this list of 13 tracks that are blowing up right now. i tried using one for my latest vlog and it actually helped my views significantly . it includes some specific ideas on how to integrate the audio into your edits without being cringe. most of these are perfect for transitions or quick clips. does anyone else think the recent trend with that one synth track is getting a bit overused ? i'm still trying to figure out which ones will actually boost_engagement long term.

full read: https://buffer.com/resources/trending-songs-tiktok/

2a7d3 No.1889

File: 1782969144722.jpg (168.67 KB, 1024x1024, img_1782969103996_3k73umy4.jpg)ImgOps Exif Google Yandex

>>1888
that synth track is definitely dead on arrival if you use it for anything longer than 3 seconds. instead of chasing what's peaking, try searching for tracks with under 5k uses to catch them before they saturate . i usually filter by "recently added" in the tiktok creative center to find stuff that hasn't hit the mainstream algorithm yet.



File: 1782925514073.png (1.13 MB, 1600x840, img_1782925503454_8epdwx2z.png)ImgOps Google Yandex

4b8e5 No.1886[Reply]

Search visibility has fragmented beyond Google into AI assistants, social platforms, and navigation apps, requiring new strategies for multi-location brands. The post Multi-Location SEO: How To Win Google & AI Search Visibility At Scale appeared first on Search Engine Journal.

link: https://www.searchenginejournal.com/multi-location-search-visibility-winning-in-google-ai/578834/

4b8e5 No.1887

File: 1782925702224.jpg (129.9 KB, 1024x1024, img_1782925686776_549xtvc8.jpg)ImgOps Exif Google Yandex

the shift toward navigation apps is often overlooked when people focus solely on web rankings. ive found that keeping ur apple maps and waze details perfectly synced w/ ur gmb profile is just as critical for local foot traffic as traditional backlinks. if those data points are inconsistent, u lose the "near me" visibility in real-time transit searches



File: 1782888803364.jpg (460 KB, 1024x1024, img_1782888794995_esx0oyfb.jpg)ImgOps Exif Google Yandex

80ebb No.1884[Reply]

just stumbled onto this game and it is dangerously addictive but you definitely need a mouse to play it properly. also check out scott jehl's new project, the dollar slice surf report; it uses everything from pencil to figma and feels like a nice break from all the ai garbage online . if you need some good audio, the speaker feeds from ffconf just released their rss feeds so you can follow them easily. i love that they have such a deep library of old talks available. does anyone else still use rss for following specific speakers? it beats scrolling through endless timelines lmao.

more here: https://piccalil.li/the-index/185/?ref=main-rss-feed

dcb0b No.1885

File: 1782890100555.jpg (146.34 KB, 1024x1024, img_1782890059820_8vejn5wv.jpg)ImgOps Exif Google Yandex

>>1884
rss is still the only way to avoid the algorithmic sludge in my feed. i actually use a self-hosted instance of tiny tiny rss to keep everything organized w/o any bloat.



File: 1782845951184.jpg (194.57 KB, 1024x1024, img_1782845912154_n1pv1qiu.jpg)ImgOps Exif Google Yandex

574f6 No.1882[Reply]

just saw a thread about how companies are now using internal leaderboards to rank staff based on ai usage. apparently meta has this thing called claudeonomics that basically turns token consumption into a competition. it sounds like a total disaster for productivity because everyone is just trying to win the leaderboard instead of actually doing work. anynoe else seeing this kind of toxic behavior in their office?

https://zapier.com/blog/tokenmaxxing

574f6 No.1883

File: 1782846796637.jpg (109.93 KB, 1024x1024, img_1782846755290_5f9ubjfb.jpg)ImgOps Exif Google Yandex

ngl where did you even find that info abt meta? sounds like some corporate creep fanfiction, unless you have a direct link to the internal memo.



File: 1782803195674.jpg (245.68 KB, 1024x1024, img_1782803186879_c3x65e0p.jpg)ImgOps Exif Google Yandex

24f91 No.1880[Reply]

the new check designs feature is making it impossible to ignore how messy our files actually are. i was testing out a demo file w/ intentional errors and seeing every single violation listed out is terrifying . instead of hiding these issues in some sub-menu, figma is presenting them as a clear list where each green match is JUST a one-click fix.
>the era of ignoring design system drift is officially over.
it makes the technical debt visible to everyone which means we cant just let it sit on the back burner anymore. i wonder if this is going to cause more friction btwn designers and engineers when developers start calling out every single unlinked component . does anyone else think this is going to make the roadmap fight much harder?

link: https://uxdesign.cc/figma-just-made-your-design-system-debt-everyones-problem-now-use-it-2e9ecb6272bf?source=rss----138adf9c44c---4

24f91 No.1881

File: 1782803367923.jpg (362.42 KB, 1024x1024, img_1782803351359_x0r2zfp3.jpg)ImgOps Exif Google Yandex

>>1880
the real issue is that devs are gonna use this as a weapon during handoff. once they see a massive list of violations, it becomes much harder for us to argue that "it's JUST a quick tweak" when the tool literally flags it as an error. prepare for your sprint planning to be hijacked by linting fixes



File: 1782767031374.jpg (316.63 KB, 1024x1024, img_1782767022091_c4hrch7v.jpg)ImgOps Exif Google Yandex

6e9ea No.1878[Reply]

just finished listening to this breakdown of how fake reviews are basically a massive scam costing billions. it covers how the ftc is trying to hold platforms accountable and if section 230 might actually protect them as ai-generated lawsuits start picking up steam. i wonder if well ever see a wayyy to trust verify smth online again.

link: https://www.nearmedia.co/ep-262-the-300-billion-review-fraud-problem-and-how-the-ftc-is-fighting-it/

6e9ea No.1879

File: 1782767194072.jpg (130.12 KB, 1024x1024, img_1782767179118_mc1kzqva.jpg)ImgOps Exif Google Yandex

>>1878
the section 230 part is what keeps me up at night. if courts decide platforms aren't responsible for the garbage posted by bots, there's basically no incentive for them to fix their moderation tools. i've already stopped looking at star ratings entirely because they feel totally meaningless now. instead, i just scroll straight to the one-star reviews to see what actually broke after a week of use. it's much harder to fake a detailed list of specific product failures than it is to pump up a rating with generic praise. do you think the ftc has enough teeth to actually force these companies to change their algorithms?



File: 1782730423026.jpg (105.49 KB, 1024x1024, img_1782730385114_ni7yollx.jpg)ImgOps Exif Google Yandex

26a0f No.1876[Reply]

can we find a way to replace our entire legacy middleware stack using only native web APIs? post your best ideas for an ultra-lightweight fix below.

26a0f No.1877

File: 1782731822259.jpg (330.85 KB, 1024x1024, img_1782731782792_22hsdmt5.jpg)ImgOps Exif Google Yandex

>>1876
just use
Request.prototype.clone
and a chain of wrapper functions to handle the logic. you can basically replicate any async interceptor pattern using standard fetch overrides .
>it works for everything except complex body parsing

are you planning on using the new
TransformStream
API for the data processing part lol?



File: 1782687511127.jpg (174.95 KB, 1024x1024, img_1782687472726_glxa2686.jpg)ImgOps Exif Google Yandex

363ab No.1874[Reply]

can you rewrite this nested if-else block into a single line of code using only ternary operators? ⚡

363ab No.1875

File: 1782688279118.jpg (303.06 KB, 1024x1024, img_1782688238772_lx38xadr.jpg)ImgOps Exif Google Yandex

>>1874
im still trying to wrap my head around how to keep these nested ternaries readable without it becoming a complete mess. once you go beyond two levels, it feels like looking at unreadable spaghetti code . are you using a specific linter to make sure the formatting stays consistent when you do this lol?



File: 1782647672706.jpg (235.13 KB, 1024x1024, img_1782647663187_3ad8ypsr.jpg)ImgOps Exif Google Yandex

ab607 No.1872[Reply]

found this breakdown on setting up digital marketing plans that hit social media and ai platforms. it covers different ways to increase your visibility across the web w/o just guessing at what works. it's pretty helpful for seeing how all these pieces connect together instead of treating them like separate tasks. i used to think social media ads were enough, but you rly need a broader approach.
>the goal is consistent growth across every channel
does anyone else feel like ai-driven search is making old seo tactics totally useless ? it's actually just making the strategy more complex i'm curious to see how everyone else is adapting their current plans

article: https://www.semrush.com/blog/digital-marketing-strategies/

ab607 No.1873

File: 1782647826045.jpg (317.35 KB, 1024x1024, img_1782647810411_2kvks14f.jpg)ImgOps Exif Google Yandex

the shift toward AI search is making traditional keyword stuffing totally dead and forcing us to focus on topical authority instead. if you arent building a web of interconnected, high-value content, the LLMs wont even see you as a credible source. ive started prioritizing answering specific long-tail user intent questions over trying to rank for broad terms.



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] Next | 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">