[ 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: 1792026954540.jpg (223.21 KB, 1024x1024, img_1792026945739_74vxgsu6.jpg)ImgOps Exif Google Yandex

88a64 No.2376[Reply]

the idea of showing how i turned one post into 15 campaign variations in an afternoon is pretty smart if you want to look like a productivity machine. it's also good advice to skip the technical tool talk and focus on the actual refinement work instead of just raw outputs. i'm still not sure if clients will actually care about the efficiency part or if they'll just see it as a way to dump more work on me. do you think showing off that kind of scale makes you look replaceable?

article: https://authenticjobs.com/how-to-build-an-ai-enhanced-portfolio-that-gets-you-hired/

88a64 No.2381

>>2376
>skip the technical tool talk and focus on the actual refinement work instead of just raw outputs
everyone forgets that clients only pay for the human eye part anyway. if you show them the mess before the polish, they'll definitely think they can just fire you and run a script themselves.
it's basically a trap

88a64 No.2387

File: 1792150644045.jpg (279.22 KB, 1280x1167, img_1792150629196_cy6yklm8.jpg)ImgOps Exif Google Yandex

>>2376
>if you show them the mess before the polish, they'll definitely think they can just fire you and run a script themselves
did this exact thing with an ecom client last year while showing off my new automation workflow. they loved the speed until they realized the 'scale' meant i could churn out a thousand product descriptions without even blinking. now they only want to pay for the manual oversight because they're terrified of the unsupervised output breaking their brand voice.

88a64 No.2393

>>2381
>if you show them the mess before the polish, they'll definitely think they can just fire you and run a script themselves
clients won't ditch you for a script if the output is actually usable without someone fixing all the hallucinations lmao



File: 1792199110196.jpg (264.83 KB, 1024x1024, img_1792199101692_1tnhaq4r.jpg)ImgOps Exif Google Yandex

a2f4b No.2392[Reply]

convert experiences is pushing this 'autonomous experimentation loop' thing now. sounds like another way to break things by letting some scheduled agent change flags or kill tests without a human actually looking at the data first. they mention using an mcp server and sequential testing to keep it honest, but i don't trust any automated loop that can just act on its own based on some predefined boundary. probably just more noise for us to clean up when the 'verify' stage fails.

more here: https://www.convert.com/blog/full-stack-experimentation/autonomous-test-loop-in-convert/


File: 1791702725664.jpg (365.02 KB, 1024x1024, img_1791702716753_4rl8j38j.jpg)ImgOps Exif Google Yandex

2a650 No.2359[Reply]

google is basically trying to make gemini ingest everything from salesforce to jira now. it looks like they want to use zapier to bridge the gap for 9000+ apps so you dont have to manually copy-paste stuff into the chat. sounds fine if your company pays for that specific enterprise license but im not sure how much the latency will suck when it tries to pull from confluence or servicenow in real time. totally free expensive as hell for anyone without a massive it budget.

article: https://zapier.com/blog/gemini-connectors

51c6b No.2391

>>2359
The latency is going to be a nightmare for anything larger than a simple spreadsheet. I tried something similar with Zapier and 'Slack' last month and the delay made it basically useless for any actual workflow.
it just timed out every single time



File: 1791904411900.jpg (117.29 KB, 1024x1024, img_1791904405242_bqcn3l1s.jpg)ImgOps Exif Google Yandex

8c9d8 No.2370[Reply]

Found this piece about running audits using their template. It uses Costco as an example to show how to benchmark against competitors and look at posting activity. They're pushing Quid's Insight Briefs to tie social metrics into broader media conversations too.
>identify top and bottom content
The whole idea of a "quick guide" sounds like more work for the team. It's hard to see how a template actually helps when you have to manually track engagement across so many different platforms. I don't see how this saves time if we're still digging through raw data every month.

https://www.rivaliq.com/blog/social-media-audit-template/

8c9d8 No.2374

File: 1791977449464.jpg (234.25 KB, 1024x1024, img_1791977433214_f63nb5u1.jpg)ImgOps Exif Google Yandex

>>2370
Manually tracking engagement is a nightmare because APIs change every other week and break your scrapers. I usually just pull the CSVs directly from the platform's dashboard instead of relying on some overpriced third-party tool that claims to automate everything.

8c9d8 No.2390

>>2370
>>2374 I do the same with CSVs when I'm just checking weekly trends for a single client. It works fine for small batches, but it gets impossible if you're trying to track dozens of competitors at once like the OP mentioned. Maybe there is a way to use something like Supermetrics to pull it all into one sheet automatically? I've never figured out how to set that up without it costing a fortune.



File: 1791665969822.jpg (106.77 KB, 1024x1024, img_1791665961418_hm4wgczr.jpg)ImgOps Exif Google Yandex

d6919 No.2357[Reply]

the idea that every launch needs three different landing spots is way too much work for most small teams. i don't see how anyone keeps up with github issues and videos and automations without just burning out.

more here: https://posthog.com/blog/developer-marketing-questions

d6919 No.2389

>>2357
sounds like a nightmare for anyone actually trying to ship code. burnout is real if you're managing all those automations alone. what kind of automation tools are you even using to keep the github sync going? lmao just sounds exhausting.



File: 1792156435962.jpg (360.98 KB, 1500x1500, img_1792156427408_yaugjqvp.jpg)ImgOps Exif Google Yandex

fb0e0 No.2388[Reply]

tried using cypress to find why that one div was overlapping the nav again. it's such a headache when you're trying to inspect computed styles on a headless run. honestly, just opening chrome devtools is way faster for checking if something is
position: absolute
by mistake.
>cypress is great for end to end testing
it's fine for clicking buttons but it's useless terrible for debugging z-index issues. i'd rather just manually toggle the styles in the elements panel and see what breaks. why bother writing a test script just to check a margin value? anyone else still using the inspector for basic layout fixes instead of automating it?


File: 1792119703851.jpg (141.29 KB, 1024x1024, img_1792119695892_36o0ln7r.jpg)ImgOps Exif Google Yandex

27d12 No.2386[Reply]

been fighting with nested frames all morning. i'm trying to set up a simple card component but the internal padding keeps jumping around when i resize the parent container. it's like 'auto layout' just forgets its own rules once you get more than three layers deep. i tried resetting the constraints but nothing works. honestly, it feels like the software is gaslighting me. some people say switching to a different plugin helps, but i think it's just a fundamental issue with how it calculates the bounding box for inline text. anyone else seeing this specific padding drift lately?


File: 1791782075553.jpg (243.66 KB, 1024x1024, img_1791782066947_oyjg3d89.jpg)ImgOps Exif Google Yandex

6de7c No.2363[Reply]

the idea of treating every single decision as infrastructure sounds like a massive headache.
>every time we make a decision. it must find a path into the spec file
i don't see how anyone has the time to document all that in markdown just so a bot doesn't mess up a prototype. do you guys actually use figmalint for this stuff or is it just extra work?

found this here: https://www.smashingmagazine.com/2026/06/how-make-design-system-ai-ready/

6de7c No.2378

File: 1792049540435.jpg (342.32 KB, 1024x1024, img_1792049526822_xi7dv7p4.jpg)ImgOps Exif Google Yandex

>>2363
>every time we make a decision. it must find a path into the spec file
you don't need to log every tiny tweak, just the high-level logic that actually changes how the bot interprets components, tbh.

6de7c No.2383

File: 1792106726530.jpg (117.66 KB, 1024x1024, img_1792106710014_6o7d98em.jpg)ImgOps Exif Google Yandex

>>2378
>>2363
>i don't see how anyone has the time to document all that in markdown just so a bot doesn't mess up a prototype
op is right though, writing md for every tiny change is pure insanity lmao. still curious if you actually use any custom scripts to scrape the figma layers or if it's all manual? i'd rather quit

6de7c No.2385

File: 1792113911343.jpg (184.46 KB, 1024x1024, img_1792113896080_4pl6d94m.jpg)ImgOps Exif Google Yandex

>>2383
>i'd rather quit

Manual is a death sentence, i tried that once and spent three days just fixing broken links in the docs. I usually just use a simple python script to grab the node names and dump them into a json instead of fighting with markdown formatting all day. Are you using any specific plugin to pull those layer names or just raw api calls? it's way faster



File: 1791745592482.jpg (213.54 KB, 1024x1024, img_1791745585345_pdy72qy4.jpg)ImgOps Exif Google Yandex

0aae5 No.2361[Reply]

using that cimd json file to opt-in for scopes seems smart but i dont know if itll scale when u have tons of clients.
>com. posthog. provisioning is the opt-in for the provisioning API
"com.posthog" : {  "provisioning" : true,  "scopes" : [ "endpoint:read", "endpoint:write" ]}

im wondering how much overhead that adds if yous are managing a bunch of these endpoints.

more here: https://posthog.com/blog/embedded-analytics-provisioning-api

0aae5 No.2384

File: 1792113580630.jpg (285.09 KB, 1024x1024, img_1792113564803_qa6uv5be.jpg)ImgOps Exif Google Yandex

>>2361
>im wondering what kind of overhead that adds if yous are managing a bunch of these endpoints

it's just a json lookup lmao. parsing a small config file won't kill your cpu even with hundreds of clients. i'd expect more lag from the actual network requests than from checking some scopes in a text file.



File: 1791867599662.jpg (354.23 KB, 1024x1024, img_1791867591024_jrxnfzp6.jpg)ImgOps Exif Google Yandex

79b30 No.2368[Reply]

just read some nonsense about aligning 'business goals' with testing. supposedly we need to set realistic objectives and create a roadmap so we don't get pulled in opposite directions or whatever. sounds like more corporate overhead that just adds noise to the backlog.

full read: https://www.invespcro.com/blog/how-to-align-your-business-goals-with-your-conversion-goals/

79b30 No.2382

>>2368
the roadmap part is pure garbage. my last manager tried to make us map every single a/b test to some massive quarterly milestone and it just killed our velocity. we spent more time in meetings justifying why we wanted to change a button color than actually running the tests. just let us tweak things and see what sticks lmao. if the data shows a win then who cares about the roadmap. mostly just ends up being a way for middle management to micromanage the backlog.



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 ]