beginner

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.5% — this entity appeared in 13 of 2,852 analyzed posts/comments in the seven days ending that day (15 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 11:09 UTCComment

   Maybe it's the programming language. Some can be a bit confusing for beginners. At least that's the problem i had in the beginning. I recommend something like Python, that one is quite easy to read. As for the syntax, the docs are your best friends. If you know what you want to achieve, you can search for a function that might help you.

4. 2026-10-14 10:10 UTCComment

   Even with AI, I would not be comfortable accepting an assignment to build this from scratch, even with my experience, let alone as a beginner... It's probably possible to finish with AI, but not really while you understand the implications of design decisions, which will lead to issues further down the road. Also: Is the heavy AI use paid by you, or the company? If you have to pay it yourself, you will probably have to get the 200$ plan at the very least, for two months, which will eat 35% of your income already. (And if you find a cheaper AI than the current state of the art, it will still be expensive, and more prone to issues / mistakes in bigger systems) I am currently building a quite similar system as a hobbyist. Granted, I am chronically ill, so I can't spend more than 10h/week on average, but I have had nearly a decade of prior experience, and the tech stack was mostly familiar to me: It's an event management software, for small, non-commercial events/conferences. The complexity is probably a little smaller than your system, but comparable, and with AI usage (although not heavy, I don't vibe code), and escluding UI/UX, it has taken me about 10 months to be halfway done with the features. I will still need time polishing and doing all of the little quality of life things I want to do at the end. that's about 40 weeks of 10h on average, which makes it 400hrs. And you can't expect to work 10hr a day for prolonged periods of time without your concentration lapsing more and more and your output quality going down significantly. Crunch is not sustainable. TL;DR: I would not touch that. The risk of not finishing is high, and the risk of the quality being bad due to time crunch is even higher.

5. 2026-10-14 04:54 UTCComment

   The example you give is very basic, it seems that you lack knowledge of the basics of programming. Look for a JS course that starts with the basics (I've heard many people praise Wes Bos' "Beginner Javascript" course) and spend at least half an hour every day. Just like learning a new language or getting in shape, constancy here is key. As you progress your confidence on solving problems will build up. Good luck! PS: just curious, what's your current web dev role?