agency

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.8% — this entity appeared in 24 of 2,852 analyzed posts/comments in the seven days ending that day (33 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-15 07:16 UTCComment

   The deciding factor isn't WP vs Next, it's your last line: you may not be allowed to touch this in a year. Whatever you build, plan for someone else maintaining it. A custom Next + Payload site is easy for you but harder for a non-technical parent to hire help for than WordPress. If you rebuild: keep every old URL or 301 it, make sure the agency's blog workflow still works (or end it deliberately), and measure calls/form submissions before and after so you know if it helped. If you'd rather not rebuild, deleting the keyword walls and fixing mobile layout in the existing site may get you most of the gain for a fraction of the work

2. 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.

3. 2026-10-14 07:04 UTCComment

   This is definitely not common at my agency. I’m Director of UI/UX at a medium-large company and our devs were all-in on vibecoding in its earliest months. What we saw was CSS and related coding that was so cluttered, it would tremendously slow load times or become unbearable for anyone but the original developer to jump into. Likewise, after multiple revision rounds with clients we discovered the vibecoded work was struggling to account for changes (i.e. silly things like a client suddenly wanting links in a specific table styled radically different from everywhere else, but implementing that change somehow broke contact page links). Because of that the leadership team banned junior and associate-level developers from vibecoding. We have no problem with tackling some of the more repetitive, minor tasks with AI tools, but as a whole our developers need to understand what they’re building before pushing it.

4. 2026-10-14 06:58 UTCComment

   Did you consider giving yourself a little grace at 21? You’re just starting man, unfortunately it’s not like the movies where you can just slap out being good in a montage. I’d highly recommend taking a bit of each day to put down the coding bot and just sit there and go through the pain from the bottom up. Can I recommend starting with shell scripts and bash. That for me and understanding how the cli works in general was a big factor in fixing my programming issues… and honestly I’m just ok, people forget stuff especially the minute details of programming because it is inherently esoteric. I’ve been programming for nearly 11 years now and with two kids I envy your agency at this delicate time. The other thing I would say is that as coding bots get better domain and systems design skills become more valuable.

5. 2026-10-14 00:30 UTCComment

   Honesty is not always the best policy when interviewing! It depends on the role in question, but in general if I were you I'd talk up how you code by hand but then also had opportunities to augment your typical workflow with AI at this agency. You don't want to sound like you only ever coded with AI (nor like you wouldn't touch AI with a ten foot pole), but rather that you used your best judgment in deciding which approach to take for a project. You know, maybe talk about how AI is great for prototyping and templating, but you sweat the finer details by hand, for example. Keep going with the personal projects. Not only is it good experience for the interviews, but a decent portfolio will get eyes on your resume that you might not have gotten otherwise. Good luck!