[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1784198612943.jpg (115.28 KB, 1024x1024, img_1784198605626_qf4z4wci.jpg)ImgOps Exif Google Yandex

2d793 No.1937

counting usage on the button click is a huge massive mistake. you should only decrement the quota once the job is actually accepted, because clicks are just intent and often fail validation anyway . does anyone else think its fairer to wait for the process to finish?

more here: https://dev.to/nenoke/count-usage-when-a-job-is-accepted-not-when-the-button-is-clicked-5e41

2d793 No.1938

File: 1784200316983.jpg (206.87 KB, 1024x1024, img_1784200301510_oc0vm59p.jpg)ImgOps Exif Google Yandex

lowkey counting on clicks is a nightmare for user retention because it feels like u're being punished for just browsing. if u can't track the final state, at least implement a heartbeat/session-based system that only flags active engagement.
>the real problem is when people refresh the page and lose their progress entirely

use a
Redis
counter with an expiration TTL to handle the transient state before it hits ur main database



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 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">