div3rs3

Do you feel the output could've been yours, or is it about the output feeling more humane?

We're organized in small teams around specific products. That leads to mob programming being a good fit, so code reviews and knowledge sharing is organic. This gives us an opportunity to commit to main and do direct deploys to production. Treating every commit as deployable is key, but it drives good practices.

The largest benefit of mob programming (or software teaming or ensemble programming) is the continuous knowledge sharing. Instead of trying to figure out context during code reviews or syncs, you do it organically all the time. Developing together builds a tight team where people grow together.

Nice job! Pretty fun game.

Only improvement ideas I have are for a smoother start for new players:

1. Let the user start the game themselves so that they have a chance to read the rules without a stressful first impression.

2. Use a different label text than "Build your word here" as it sounds like a drag and drop target rather than an output.

I'd argue the value goes up with larger payloads. The tradeoff is ease of use vs efficiency.

Hence my question was about programming rather than engineering. Composition could, for a long time, be a task humans do whereas the components are generated by AI.

They're likely on the hype train, I'll give you that. Doesn't mean next generation won't be doing software engineering completely different from how it's done now.

Lizardking’s stuff is great, e.g. Triton Theme: https://chiptune.app/?q=lizardking

An Es Kew El or A Seakewl Lite

Done well (like here), The Goal like storytelling, is both educational and interesting.

Great work! Mashing up data based on tweets, HN posts and real-world projects (i.e. from GitHub) would be an interesting dimension.