Show HN: Leetcode but for front end engineers. Bad idea?

(clientside.dev)

23 points | by xempes 999 days ago

7 comments

  • Madmallard 998 days ago
    This is a much worse version of bfe.dev hate to break it to you.

    No one wants to pay premium for this stuff. bfe.dev is free and has a drastically larger selection of problems on many different subjects.

    • xempes 998 days ago
      I appreciate the advice but also disagree. BFE completely lacks on practical UI problems and test cases. Also, this site is niched to React interviews which BFE has very few problems for.
      • Madmallard 998 days ago
        I only see 20 problems if I select React on clientside.dev. I see 10 on bfe.dev for specifically that key word. Yeah UI clientside.dev has it beat.

        If you go to the system design section for bfe.dev those are some practical UI problems.

        It would be far better if most of the meaty problems on clientside.dev weren't behind a paywall. You could just google every single one of those problems instead.

    • braingenious 998 days ago
      Seconding this.
  • nassimsoftware 999 days ago
    Thanks for making this. I think this is a great idea. I've often come across interviews were I had to solve a problem using React and didn't know how to prepare myself for those kind of interviews.
    • xempes 998 days ago
      My pleasure! I've been through and led those types of interviews myself so I understand the struggle.
  • catchmeifyoucan 998 days ago
    I haven't heard of bfe.dev before. But I like yours better for a few reasons.

    1. It has CodeSandbox built-in with a live preview

    2. You actually wrote test cases, most FrontEnd Interviews don't even have that, and neither do practice probolems.

    3. You should consider making the submit code button should larger!

    Since you're still building traction, and the library is still small, I would consider changing the way you upsell. Rather than lock things behind a paywall and drive people away. I want more hard questions, and to play w/ the component design q's.

    You could consider making all your problems free, and limit the number of test runs? This is kind of how bfe.dev was doing it. You could auto-run the tests in the background, and give a score, but not tell the user where they failed. Solutions could be paywalled, but not the problem. Hope this takes off!

    • xempes 998 days ago
      Thank you for the great feedback! I've considered open-sourcing the project but walked back on that since people have already paid for it and I feel like that may be upsetting. May reconsider it in the future as I get more feedback.
  • dimmke 998 days ago
    There’s another site like this https://bigfrontend.dev
  • dimmke 998 days ago
    My bad, apparently BFE is more well known than I remember. It’s cool to have alternatives. I’ll give it a shot, why not?
  • str3wer 998 days ago
    small note: on the coupon at the top of the page you forgot to close the country_flag brackets, so it looks like this:

    It looks like you're from (redacted) {country_flag.

    • xempes 998 days ago
      Thank you!
  • Throw999999 998 days ago
    Amazing job.