[ 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: 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?

96050 No.2332

File: 1789609131595.jpg (305.78 KB, 1024x1024, img_1789609117275_lo7e8f6z.jpg)ImgOps Exif Google Yandex

>>2324
>if you dont cap your rounds, youre basically working for pennies an hour
had a guy do this with a landing page last month and i ended up working for like three bucks an hour after he decided the logo needed to be 'more energetic' halfway through the build. now im strictly enforcing the limit on every single contract.

96050 No.2347

>>2324
The 'more energetic' thing is such a nightmare. Had a client try to do that with a vector illustration and ended up deleting half the project because they kept changing their mind about the color palette.



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.

657af No.2346

>>2318
>everything just collapsed to zero for no reason
Check if you have a fixed width set on the child elements. Usually happens when you're trying to use "hug contents" but one nested layer is accidentally locked to a specific pixel value. Works fine for simple buttons, but fails miserably once you start nesting complex groups.



File: 1789926395544.jpg (126.53 KB, 1024x1024, img_1789926387369_dqwciga7.jpg)ImgOps Exif Google Yandex

7836e No.2345[Reply]

musk is finally turning cashtags into actual trading buttons for us users. it's connecting to coinbase and kraken now so you can just tap a ticker and buy. >"close the gap between a ticker on the timeline and the market itself" sounds like a total disaster waiting to happen once the ai bots start pumping everything. anyone actually trust these brokerages inside a social media feed?

full read: https://techcrunch.com/2026/09/16/x-will-now-let-u-s-users-trade-via-cashtags/


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.

ebcb5 No.2334

>>2316
>grep is essential for finding actual issues without all the noise
just use lnav instead because grepping alone misses context from surrounding lines.

ebcb5 No.2344

File: 1789830711422.jpg (90.3 KB, 1024x1024, img_1789830690293_fjujq4l7.jpg)ImgOps Exif Google Yandex

>>2334 lnav is way too heavy for a quick check when you just need to see if the service died.



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/

c078f No.2330

File: 1789601563656.jpg (126.44 KB, 1024x1024, img_1789601548333_b6i9ip9i.jpg)ImgOps Exif Google Yandex

>>2321
>it's basically just saying put your topic in the title tag and hope for the best

the client i have right now literally thinks stuffing reddit links into every paragraph is a magic hack lmao

c078f No.2339

File: 1789796501165.jpg (123.13 KB, 1024x1024, img_1789796486061_piuy9rev.jpg)ImgOps Exif Google Yandex

>>2330
reddit links are actually okay if they're relevant, but you gotta link to high-authority threads or google just flags it as spam. tbh most people just need to focus on proper internal linking instead of that nonsense.

c078f No.2342

File: 1789823655266.jpg (214.15 KB, 1024x1024, img_1789823633972_b1n9s7rh.jpg)ImgOps Exif Google Yandex

>>2321
>just read some absolute garbage about how pilates abs exercises is the focus keyword for an ab workout post
stop obsessing over the exact phrase and just use surfer to see what's actually ranking in the snippets. works fine for finding gaps but totally useless if you're trying to track long term trends.
google is basically just a giant ad engine now



File: 1789608597869.jpg (248.19 KB, 1024x1024, img_1789608589461_ggfrp1xw.jpg)ImgOps Exif Google Yandex

43c28 No.2331[Reply]

se ranking got over 1200 clicks from their test but didn't get any sign-ups. it doesn't even matter if you use keywords or context targeting since the people actually paying for plus accounts don't even see them anyway. anyone actually planning on testing this?

full read: https://seranking.com/blog/how-to-advertise-on-chatgpt/

43c28 No.2338

>>2331
the clicks don't mean much if your landing page is garbage lmao. you probably just sent them to a broken signup flow instead of something actually useful.

43c28 No.2341

>>2331
>>2338 scriptkid's right, if they're just dumping traffic into a void it's pointless. did you check the bounce rate on those 1200 clicks? tbh seems like a massive drain on the budget.



File: 1789305503033.jpg (138.6 KB, 1024x1024, img_1789305410365_elsmc7f3.jpg)ImgOps Exif Google Yandex

c74c4 No.2310[Reply]

meta basically nuked their own engineering vibe just because they were terrified of small startups using ai to outpace them. it's a massive self-inflicted wound and makes me wonder if github's sudden load spike is the new standard for devs.

article: https://newsletter.pragmaticengineer.com/p/the-pulse-meta-wanted-to-reduce-teams

c74c4 No.2311

File: 1789305657423.jpg (192.43 KB, 1024x1024, img_1789305640944_dmldkg84.jpg)ImgOps Exif Google Yandex

just start using cursor to stay ahead of the bloat.

c74c4 No.2312

File: 1789314186125.jpg (180.75 KB, 1024x1024, img_1789314146344_jbgkhgdy.jpg)ImgOps Exif Google Yandex

the github spike is just people piping copilot outputs into repos w/o even checking the linter. its not outpacing them, its just creating massive amounts of technical debt that will need manual refactoring later. most of these "startups" are just wrappers around an api call anyway

c74c4 No.2340

>>2312
>just creating massive amounts of technical debt
lmao just call it "agile" and charge more for the cleanup later.



File: 1789731017482.jpg (179.84 KB, 1024x1024, img_1789731011058_r9i5uijv.jpg)ImgOps Exif Google Yandex

daf66 No.2336[Reply]

finally getting support for unprefixed user-select is nice but i'm still dreading those line-clamp bugs with inline blocks. seeing them fix display: contents accessibility stuff too. tbh it's probably gonna break something else in my old legacy projects.

full read: https://webkit.org/blog/18304/release-notes-for-safari-technology-preview-252/


File: 1789651263467.jpg (124.24 KB, 1024x1024, img_1789651255535_w6wy5x2s.jpg)ImgOps Exif Google Yandex

bf9d9 No.2333[Reply]

using the semrush mcp to pull data directly into claude sounds pretty cracked.
>find keyword ideas based on what your audience is saying makes it seem way faster than manually copying tables into a prompt. might actually be worth setting up if i can get the connection working without it breaking every five minutes lmao.

article: https://www.semrush.com/blog/claude-keyword-research/


File: 1789189611297.jpg (298.37 KB, 1024x1024, img_1789189572311_ikwcacwm.jpg)ImgOps Exif Google Yandex

7c0ad No.2304[Reply]

just finished diving deeper into how to actually validate what the api is spitting back. anyone else feel like just checking a status code is basically useless a waste of time? if u aren't using hamcrest matchers to verify the actual data structure and business logic, ur tests aren't really doing smth. i've been focusing on making sure the response body matches the expected schema exactly so nothing breaks downstream.
>the real magic happens in the deep assertions
it makes the automation much more robust against unexpected changes. **does anyone else find writing these assertions a massive headache when the json is nested five levels deep

link: https://dzone.com/articles/rest-assured-response-verification

7c0ad No.2305

File: 1789191007796.jpg (129.56 KB, 1024x1024, img_1789190967432_v4hke1l9.jpg)ImgOps Exif Google Yandex

>>2304
lowkey if you arent using
JsonSchemaValidator
, youre basically just manually recreating what the library already does. i started integrating it with hamcrest matchers and it saved me so much time on repetitive assertions lol.

7c0ad No.2329

>>2305
schema validator is a lifesaver but it still breaks my heart every time dev changes a single field name without telling me lmao. i hate digging through five levels of nested junk too. just use path expressions to grab the specific leaf nodes u need so you aren't checking the whole mess every single time.



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 ]