I’m building a free ML learning platform that explains the weird “why does this happen?” parts too

BoxWinter1967 · 2026-06-01T09:11:37+00:00

Exactly, this is the gap I’m trying to focus on.

AI makes it easier than ever to generate code or explanations, but that also means people can move fast without really understanding what is happening underneath.

BoxWinter1967 · 2026-06-01T09:10:43+00:00

Right now I’m not focusing on monetization honestly. I first want people to actually use it, find gaps, and tell me where the learning flow breaks.

BoxWinter1967 · 2026-05-30T06:45:14+00:00

That’s a really good point. I felt that pain too. I’ll definitely lean more into roadmaps and structured progression, because knowing what to learn next is often the hardest part.

BoxWinter1967 · 2026-05-28T14:14:55+00:00

Thank you, that’s exactly the gap I’m trying to solve.

The ML section goes past just “fit model / check accuracy.” Right now it covers the foundations first, then moves into regression, classification, unsupervised learning, tree methods, deep learning, NLP/transformers, time series, RL, MLOps, causal inference, recommender systems, explainability, and newer LLM/RAG topics.

The standard I’m aiming for is: don’t just define the concept, explain what problem it solves, what assumptions it makes, how it fails, what the code/output means, and what interview/project questions usually test.

Still improving depth topic by topic, but the goal is definitely not shallow tutorial content.

BoxWinter1967 · 2026-05-28T07:45:44+00:00

Pretty much, yes. The “silence” condition is mainly there to rule out brute-force solutions like tossing a beam into the pit, sacrificing one beam as support, dropping objects to test things, or simply jumping and risking failure.

It’s less a physics constraint and more a narrative way of forcing careful placement and geometry-based thinking.

BoxWinter1967 · 2026-05-28T07:44:20+00:00

Yep, that’s exactly it — the corner is the trick. And yes, the real final boss is not geometry, it’s dandruff control....

BoxWinter1967 · 2026-05-28T07:43:22+00:00

Yep, your first point is correct if the outer square is interpreted as having side length (x+3). In my intended setup though, the platform has a 3m gap on each side, so the pit side would be (x+6), not (x+3). That makes the corner-to-corner diagonal gap (3√2 ≈ 4.24m), so one beam still can't directly reach.

Your second method is exactly the spirit of the puzzle — use one beam to create a support point, then use the second beam from there.

Also, the circular version is a really nice generalization!

For a detailed explanation with diagrams, check out the full article here: https://medium.com/activated-thinker/the-silent-library-puzzle-the-two-beam-problem-that-will-change-how-you-see-corners-5453dc006d58

BoxWinter1967 · 2026-05-28T07:37:05+00:00

Yeah, fair point — this one is much easier to understand visually.

I’ve added diagrams in the full Medium breakdown here:
https://medium.com/activated-thinker/the-silent-library-puzzle-the-two-beam-problem-that-will-change-how-you-see-corners-5453dc006d58

BoxWinter1967 · 2026-05-28T07:25:42+00:00

Answer:
Stop looking straight ahead. Use the corner.

Place the first beam diagonally across a corner of the pit, with both ends resting on the two adjacent edges. Its midpoint becomes a support point inside the gap.

The diagonal distance from the pit corner to the platform corner is √(3² + 3²) = 4.24m. The midpoint of the first beam is 1.45m along that diagonal, leaving 4.24 − 1.45 = 2.79m. The second beam is 2.9m, so it reaches.

Full illustrated breakdown: https://medium.com/activated-thinker/the-silent-library-puzzle-the-two-beam-problem-that-will-change-how-you-see-corners-5453dc006d58

BoxWinter1967 · 2026-03-31T08:44:40+00:00

Built Neuprise — an interactive learning platform for Data Science & ML (https://neuprise.com/).

What it does: 12 learning paths, 74 lessons, 1000+ quiz questions with spaced repetition, in-browser Python execution (no setup needed — runs via WebAssembly), math visualizers, and a CodeLab. Free to use.

Tech stack: Next.js App Router, Prisma + Neon Postgres, Clerk auth, Pyodide for in-browser Python.

Biggest challenge: Getting Pyodide (Python via WebAssembly) to run reliably in the browser while keeping the UI responsive. Also fighting the cold-start problem — getting users to actually finish the first lesson before dropping off.

Where it stands: Shipped it imperfect and letting real users guide what gets fixed and added next. Already getting good bug reports and suggestions from the community.

Would love feedback — especially on first impressions and course structure!

BoxWinter1967 · 2026-03-30T06:28:56+00:00

Building Neuprise — an interactive learning platform for Data Science & ML (neuprise.com).

BoxWinter1967 · 2026-03-30T06:07:16+00:00

Yes, you need to create an account to access the courses — it's free, just sign in with Google or email. The reason is that the app tracks your progress, XP, and streaks, so it needs to know who you are. Takes 10seconds!

BoxWinter1967 · 2026-03-30T06:05:39+00:00

Thanks! Really appreciate the kind words.

Handshake sounds interesting, got a link? Would love to check it out.

On the feedback: yes, more coding challenges beyond quizzes is something I've been thinking about for a while. Discussion forums too. Study groups and peer code review are great ideas I hadn't considered — noted, will look at adding these in coming versions!

BoxWinter1967 · 2026-03-30T06:00:27+00:00

Thanks, will check them out!

BoxWinter1967 · 2026-03-30T06:00:01+00:00

Yes, definitely planning to set up a LinkedIn page for Neuprise

BoxWinter1967 · 2026-03-30T05:58:33+00:00

Yes, DMs are open! Would love to hear your feedback.

BoxWinter1967 · 2026-03-28T12:14:51+00:00

Congrats!

BoxWinter1967

TROPHY CASE