Community

Start a Thread


Notifications
Subscribe You’re not receiving notifications from this thread.

What would you like from AlgoDaily?

Feedback • Asked about 6 years ago by Team AlgoDaily

Team AlgoDaily Commented on May 28, 2019:

Hi guys, Jake here, founder of AlgoDaily. Thanks for checking the site out! I'm looking for feedback on what you guys would like to see. Is it more coding challenges? More career guides? A better way to reach out to professional developers? Let me know in the thread below!

Jun Commented on May 30, 2019:

More test cases

Brian Commented on May 30, 2019:

Lessons are great, but hit or miss. Some are high quality articles, others seem like no-thought notes

Rich Commented on May 30, 2019:

i like the challenges! keep them up.

Brian Commented on May 31, 2019:

Challenges are great. More would be awesome :-)

Harsha Vardhan Commented on Jul 25, 2021:

Need cloud related topics for system design..

Sarah Chen Commented on Jun 30, 2025:

A few concrete asks that map to what folks mentioned:

  • Stronger editorial bar for lessons: clear learning objectives, a full worked example, and a “reviewed” badge. Avoid note-dumps.
  • Challenges: more of them, organized by patterns (two pointers, DP, graph, etc.) with a progression path.
  • Test cases: beef up edge cases and randomized/fuzz tests. Show categories of failing cases (e.g., “overflow” or “empty input”) without revealing answers.
  • Explanations: at least two approaches per problem, with trade-offs and Big-O, plus a pitfalls section.
  • Hints: tiered hints (nudge → approach → complexity) before revealing solutions.
  • System design with cloud focus: hands-on mini-labs (queues, caches, rate limiting, sharding), AWS/GCP primitives, cost/capacity callouts, and annotated diagrams.
  • Practice mechanics: spaced repetition for missed problems, timed mock rounds, and lightweight streaks.
  • Review/mentorship: async solution reviews or scheduled office hours; curated mentor directory instead of cold outreach.
  • Tooling: in-browser debugger, consistent time/memory limits across languages, downloadable starter templates, and a local CLI runner.
  • Feedback loop: “this is ambiguous/incorrect” button on every lesson with visible resolution status.