jackevans

joined 1 month ago
[–] jackevans@programming.dev 0 points 1 month ago

Agree with the emphasis on modularity upfront, as it aligns with my YAGNI takeaway, start simple but layer cleanly for future refactors without a full rewrite. In my case, zero users meant no pressure for premature complexity, letting me ship fast and iterate based on actual needs. Experience definitely sharpens that balance. What's one modular pattern you'd recommend for a basic CRUD API?

 

Hey!!!

I’ve been working on a small utility for YouTube creators and would love some feedback from fellow devs.

I built a YouTube Watch Time Calculator, designed to help creators quickly understand how many views they need to hit monetization.

How it works:

  1. Watch Hours Needed: You enter your target (default is 4,000 hours – the monetization requirement).
  2. Average Watch Time: Add your average view duration (minutes + seconds).
  3. Hit Calculate: It shows the exact number of views you need.

From a dev perspective, I focused on:

  • Keeping the UX minimal so it works well on mobile and desktop.
  • Making the calculations transparent and predictable
  • Keeping the page lightweight so it loads fast for creators who are often multitasking with multiple tabs open

I’d really appreciate:

  • UX feedback (what’s confusing, what’s missing).
  • Edge cases you’d expect it to handle.
  • Ideas for related tools that would make sense to add for YouTube creators

If you have a moment to leave your thoughts, I’d be grateful. Also happy to answer any implementation questions, if anyone is inquisitive about how it’s put together.