auth

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-10-15

Final complete day: 2026-10-15. Attention was 0.3% — this entity appeared in 8 of 2,852 analyzed posts/comments in the seven days ending that day (10 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-10-14 15:04 UTCComment

   Giving you the honest math from the agency side, since I see this exact scenario with clients a lot. A realistic MVP cut (auth, one dashboard, batch/session scheduling, recorded videos, assignments, basic certificates) is still 6-8 weeks for a small team that already has a starter kit, CI/CD pipeline, and QA habits — for a solo beginner it is 4-6 months, because the time sink is not CRUD, it is video encoding pipelines, role-based auth across 5 dashboards, and testing the admin/grading/cert flows. The AI tools do not change this as much as people hope: they speed up boilerplate, but debugging AI-generated auth and payment-adjacent code (cert verification, fee tracking) at 2am is where beginners lose weeks. Best move: tell your friend you will commit to a written phase-1 MVP with a fixed feature list and a per-phase price, with each phase accepted in writing before the next starts. Take it only if he agrees to that in writing — "more requirements for later versions" is the classic trap.

2. 2026-10-14 13:20 UTCComment

   1 lakh for a full LMS in 45 days as a beginner is wild. you'll spend half that time just figuring out auth, file uploads, and whatever payment stuff they inevitably want bolted on at the end. scope creep on these things is guaranteed, so either double your price with a clear feature list or walk.

3. 2026-10-14 08:58 UTCComment

   >why did auth get touched and why does nobody have any idea why??? stuff like this burn me tf out. The review not happening is one thing, but nobody being able to reconstruct it afterwards is even worse.

4. 2026-10-13 18:30 UTCComment

   Someone keeps opening nearly 20,000 line PRs with 100+ files. It's effectively impossible to review. So we literally don't. It just gets one copilot pass and off it goes, anything else it hot fixed in prod. The shit I find afterwards is ridiculous. Like why the fuck is this endpoint on our backend now returning HTML in its body???? Why did auth get touched and why does nobody have any idea why??? I just don't think anyone gives a shit anymore

5. 2026-10-12 22:39 UTCComment

   First thing I'd do is write a handful of tests around the stuff that would hurt if it broke, auth, payments, anything that writes to the db. Otherwise you can't tell if a cleanup changed behavior. After that look for logic that got copy pasted across files and pull it out. Strict lint + type checking catches a lot of dead code too. Renaming and formatting can wait till last.