wa5ina
Build a Tokenizer from Scratch
An internal OpenAI Astra model solved 10 major open math and CS problems
The "Vibe Coding" Wall of Shame
I ran some basic frequency math. For example, looking at 100 recent Apple questions, their difficulty is standard (15% hard), but they test BSTs at 4.5x the industry average and backtracking at 2.5x.
The site is completely free, no login required. Just built it to make interview prep slightly less of a black box. Happy to answer any questions on how I scraped/categorized the data.
I scraped 1,500 recent interview questions to bypass LC Premium
Show HN: I built an AI-powered technical interview prep tool
LeetCode wasn't actually preparing me or anyone else for the pressure of a real technical interview.Most platforms just give you a text box and a compiler. I wanted something that actually simulates the back-and-forth of an interviewer pushing you on time complexity, asking follow-up questions, and pointing out edge cases you missed.> The Stack: I built the backend with nestjs, prisma,...
The way I see it at least is, a validated problem is one that enough people face, frequent and cause a certain level of frustration, currently each problem in broblems have a “frustration level” extracted from language used which serve “problem” and “frustration level”, but “enough people” is not yet in the equation, it’s something i wanted so badly to add, but decided not to in MVP, is to aggregate group of people that faces the same problem, and be able to browse and analyse that in a centralised location , i think that’s valuable , and i see me using that feature frequently, will try to add this feature asap. but what in ur opinion is a “validated problem”.
> “did someone verify that the people having the problem would actually pay for a solution,” ?
Great question, my simple way currently is that each problem have a "context score" that decide to what level this problem is a “productizable problem”, "renting about an analytics tool" have a higher context score while "existential rent about existence" have a lower one, this is simply done by prompting the LLM, only things that above 8 are considered actionable problems.
> “do the reports track when problems were identified and seek out whether solutions have been created since the complaints arose”
the dive-in reports currently show existing players in the space, but i don’t yet track problem timelines or follow up on whether solutions have been created since. sounds like a solid idea, but i guess it’s a bit beyond the scope of this initial version.
Show HN: I built a tool that mines the web for real problems devs can solve
i was tired of building things nobody needs? I created a tool that mines user pain points online, analyses patterns with LLMs, generate deep reports and highlights real opportunities for devs.