This. You can get all original Wii games in the used market for little money and this gives you the flexibility to play backups of your original games without loading and unloading discs, faster load times, etc. I understand piracy is the number one goto, but not all sums up to that.
Great stuff, I may try it with a local model. I think the core logic for the final output is all in the nodes.py file, so I guess one can try and tweak the prompts, or create a template system.
Found this page from Cardinal Stefan Wyszyński University in Warsaw that mentions a research program called LEM based on LogLan’82, but can’t quite understand when it was launched or if still active.
I feel this interviewing process mostly mirrors a typical interview day for most startups (or did some years ago).
I’m glad you took the time to iterate and document the work involved to accomplish a welcoming and safe space — did this evolve into company guidelines? Do get domain experts to help with the interview. I also wouldn’t ditch the white board so easily, let know the candidate before hand, and make it collaborative, even initially drive. Brainstorming ideas can be an engaging activity, discussing architectures can introduce a small part of the systems the candidate will interact with.
The examples design docs, that you’ll need to create as input, are great. Haven’t tried any agentic frameworks (not sure if I will) but if anything it’s great to see Pocket Flow teaches an important concept — research, plan and document before implementation.
I start to believe that with all its limitations, LLMs end up providing a great playground for learning how to code.
