Maybe I missed something, if you have the image rendering in the first place, you already (likely) have the CAD. It is a nice demo, but what is the utility?
I love that subscriptions in the US are (usually) immediately cancellable. Germany is the wild west of predatory subscription plans, and unfortunately the legal framework weighs heavily in favor of the businesses issuing these contracts and not the consumers.
Startup founder here -- we tried it, and it feels bloated (Java!), bureaucratic and overcomplicated for what it is. Something like Redis queues or even ZMQ probably suffices for 90% of use cases. Maybe in hyper-scaled applications that need to be ultraperformant (e.g., realtime trading, massive streaming platforms) is where Kafka comes into play.
What the poster is insinuating is that system design interviews may devolve into a scripted / memorized hoop-jumping experience rather than being a creative technical problem solving discussion.
What does solving random puzzles from Leetcode have to do with day-to-day engineering work? IMHO, the emphasis should be on previous experience, CS domain knowledge and systems architecture / design. Maybe degrees need to be fixed to convey more useful knowledge...
I love the system he built, but the kicker would be to enable auto-filling and submitting on the various career portals. I question the efficacy of submitting job applications via email in 2024 (but perhaps I'm in the wrong industry.)