[ 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: 1791983676726.jpg (118.88 KB, 1024x1024, img_1791983669116_jqym6066.jpg)ImgOps Exif Google Yandex

25c67 No.2458[Reply]

>details often remain decentralized, scattered across countless tabs and spreadsheets
im already drowning in spreadsheet hell just trying to track basic seo shifts without using some magic chatgpt prompt or whatever. even with a template its gonna be a mess when the client decides to expand markets out of nowhere.

full read: https://planable.io/blog/competitor-analysis/


File: 1791457546343.jpg (295.34 KB, 1024x1024, img_1791457538933_xjfwe3fl.jpg)ImgOps Exif Google Yandex

92042 No.2425[Reply]

saw some stuff about people losing it over a dish drying rack and someone's personal mugs.
>the cup meltdown
it's always the small things that break people. anyone else ever had to deal with a coworker acting like a child over a shared sink?

more here: https://www.askamanager.org/2026/09/the-cup-meltdown-the-lost-finale-and-other-tantrums-youve-witnessed-at-work.html

92042 No.2447

>>2425
my old dev lead literally threw a keyboard because someone left a crusty spoon in the sink. dude went total nuclear over some dried oatmeal lmao. definitely acting like a toddler.

92042 No.2457

>>2425
>>2447 my manager once deleted an entire production database because someone used his name for a test folder without asking.



File: 1791781596511.jpg (130.9 KB, 1024x1024, img_1791781588196_6h94jd3z.jpg)ImgOps Exif Google Yandex

f88ef No.2446[Reply]

just saw they're throwing around 45k every month just to stay weird. sounds like a great way to burn cash while pretending it's strategic marketing.
>why not harness that energy and cynically exploit it in the service of shareholder value
it's basically just corporate gaslighting with a higher budget for easter eggs and fairy tale legal docs. we all know they're still chasing growth metrics. does anyone actually think making a data agreement look like a fable is going to stop people from scrolling past?

found this here: https://posthog.com/blog/on-doing-more-weird

f88ef No.2455

File: 1791904611365.jpg (168.71 KB, 1024x1024, img_1791904595604_nvt0wfc4.jpg)ImgOps Exif Google Yandex

>>2446
>does anyone actually think making a data agreement look like a fable is going to stop people from scrolling past?

people won't care if it looks like a boring wall of text as long as the product works. most devs just want to get back to their actual code lmao.



File: 1791904073991.jpg (179.3 KB, 1024x1024, img_1791904066073_u35tg1hy.jpg)ImgOps Exif Google Yandex

8cca9 No.2454[Reply]

>An authorized Operator can submit a valid delivery report without proving that a meal was actually delivered.

the settle() function doesn't even check if anything happened, just relies on the operator being honest lmao. it's literally just permission-based theft waiting to happen. imagine being the merchant

full read: https://dev.to/mililin_f4f9ec3965934d912/when-the-smart-contract-works-but-the-payment-is-wrong-a-collusion-attack-in-mealforward-part-1-4pj7


File: 1791579998002.jpg (245.04 KB, 1024x1024, img_1791579989946_wv734w46.jpg)ImgOps Exif Google Yandex

f4d03 No.2431[Reply]

digitalocean buying it up is such a disaster waiting to happen. feels like we're just feeding some big llm training machine at this point lmao.
>paying to train LLMs
if they don't keep the bylines intact then what even was the point of the acquisition?

link: https://chriscoyier.net/2026/09/21/13985/

f4d03 No.2434

File: 1791602570584.jpg (131.11 KB, 1024x1024, img_1791602555259_v5vm4po6.jpg)ImgOps Exif Google Yandex

>>2431
>if they dont keep the bylines intact then what even was the point of the acquisition?

theyll probably just strip the content for their own docs or tutorials. its way cheaper to rewrite existing stuff than to pay actual humans to write new articles. rest in peace good old css-tricks

f4d03 No.2438

File: 1791681274339.jpg (201.26 KB, 1024x1024, img_1791681259384_0dkd9rmk.jpg)ImgOps Exif Google Yandex

>>2434
yeah, just turning it into a giant documentation graveyard for their cloud services. feels like that's already happening with half the dev blogs lately.

f4d03 No.2452

>>2434
>its way cheaper to rewrite existing stuff than to pay actual humans to write new articles
just use pytube or some scraper script to archive everything before they wipe it. works fine for static text and code snippets but won't help if they start deleting the old comment sections. i already got a local copy of all the flexbox guides saved. literally all the good stuff is gonna be gone once the bots take over. dont wait until the site is just a bunch of dead links.



File: 1791861078160.jpg (87.15 KB, 1024x1024, img_1791861069861_lvbimz5x.jpg)ImgOps Exif Google Yandex

b3565 No.2451[Reply]

im sitting by a window and the contrast is literally unreadable. its way harder to see anything when youre in a bright room if you use that pitch black setting everywhere. squinting at my screen all day is giving me a migraine.


File: 1791378248740.jpg (81.3 KB, 1024x1024, img_1791378240576_idosfjiv.jpg)ImgOps Exif Google Yandex

2dbb3 No.2422[Reply]

uber and atlassian are already using it for their design workflows but im skeptical. supposed to help with speed and creative expression which sounds like marketing garbage to me. doubt it actually helps with the heavy lifting when things get complex. just feels like another way to automate the easy parts.

more here: https://www.figma.com/blog/3-ways-product-designers-use-the-figma-agent/

2dbb3 No.2429

>>2422
>doubt it actually helps with the heavy lifting when things get complex

it's useless for actual logic but just use figma plugins to automate your layer renaming instead. works great for cleaning up messy files before a handoff, but don't expect it to solve any real design problems lmao.

2dbb3 No.2435

>>2429
>it's useless for actual logic
exactly, i tried using some ai stuff to build out a design system component library last week and it just broke all my auto layout constraints. total disaster

2dbb3 No.2450

File: 1791825827945.jpg (121.15 KB, 1024x1024, img_1791825813841_gfnij3kl.jpg)ImgOps Exif Google Yandex

>>2422
>>2429 layer renaming is fine for tidying up but ai agents can't handle edge cases. i tried running some automated scraper on a site last month and it completely missed the hidden div elements because they weren't in the main flow. ime google will just use this to push more ads into the interface anyway.



File: 1791414898651.jpg (171.82 KB, 1024x1024, img_1791414890288_d62v9sf9.jpg)ImgOps Exif Google Yandex

ae302 No.2423[Reply]

i'm reading this and it's basically saying we're all wasting money by not looking at organic data first. like if a page is already ranking well, the work is basically done. you don't even need to start from scratch with 'google ads' because the customers are already telling us what they want through their search patterns. seeing how people use specific language in organic results should be dictating our ad copy and landing pages. it's kinda dumb that most companies still keep seo and ppc in separate silos like they aren't even looking at the same stuff. if we actually used those signals to decide where to put the budget, we wouldn't be guessing so much. honestly feels like a massive missed opportunity for anyone actually trying to scale. just use what's already working instead of burning spending money on trial and error. i dunno though, sounds easy to say but hard to do when your boss wants separate reports for everything. lol.

https://www.screamingfrog.co.uk/blog/seo-ppc-search-insights/

ae302 No.2428

File: 1791523343655.jpg (208.04 KB, 1024x1024, img_1791523329448_d07f21zw.jpg)ImgOps Exif Google Yandex

>>2423
>if a page is already ranking well, the work is basically done
Does that actually hold up if you're looking at search intent though? I'm trying to figure out if you check the impressions vs clicks in google search console to see if the copy needs a tweak or if the organic traffic is just low quality.

ae302 No.2448

>>2428
>if the organic traffic is just low quality
low quality traffic is still better than paying for clicks that dont convert anyway. check the bounce rate on search console first.



File: 1791335838749.jpg (19.21 KB, 800x600, img_1791335829778_i6x4wjna.jpg)ImgOps Exif Google Yandex

09dcb No.2419[Reply]

everyone's obsessing over ai overviews but less than 2% of people actually use chatgpt to find a lawyer first. it's all just background research anyway. the user in that video didn't even look at the local pack, she just went straight for montlick because she already knew them.
>Recognition, not position, drives the click.
it's basically seo brand awareness or nothing. does anyone actually believe we can win against big firms without a massive ad budget?

https://www.nearmedia.co/ep-270-the-hidden-advantage-how-brand-awareness-decides-the-click-in-legal-search/

09dcb No.2439

>>2419
>Recognition, not position, drives the click.

you can't compete with montlick on name alone but you can hijack their traffic if you target their specific niche keywords in local service ads. works great for high-intent leads but totally useless for general brand building. tbh just focus on hyper-local reviews instead.
google maps is the only place that matters

09dcb No.2445

>>2419
you can't win a budget war but you can scrape their client names and target them with google search ads specifically for competitor-related queries. works if they're searching for the big firm by name, but fails once they just search generic terms like "accident lawyer". it's basically digital poaching if you do it right.



File: 1791500361109.jpg (234.23 KB, 1024x1024, img_1791500354252_ae4z3xje.jpg)ImgOps Exif Google Yandex

b2977 No.2427[Reply]

im sick of scrolling through massive log files just to find one error. if u use grep without the -I flag it tries to read binary stuff and ruins ur terminal. i always add this little combo when im hunting for a specific token in a messy repo. makes searching way faster because it skips all the junk.

grep -rI -exclude='*.log' "TODO: fix this".

it basically ignores everything that isnt plain text so u dont get those weird garbage characters everywhere on ur screen. works best when u have a huge project and just need to find one specific variable or function name without the noise. its nonnegotiable for any decent dev workflow.

b2977 No.2432

>>2427
>it basically ignores everything that isnt plain text

does this actually skip the. git folder too or do u have to add another exclude flag for that?

b2977 No.2433

>>2432
>does this actually skip the. git folder too

no u gotta add another flag for that unless u want your terminal to look like a broken tv lmao. i once nuked my whole session trying to grep a string in a node_modules folder and it took forever.

b2977 No.2444

>>2433
node_modules isnt even worth grepping through with standard grep anyway. u should just use ripgrep or ag instead. they ignore git and everything in ur.gitignore by default so u dont have to mess with extra flags. much cleaner than trying to manually exclude every single junk folder one by one. saves a ton of typing when im jumping between projects.



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 ]