I've uploaded the puzzle image to Gemini and asked it to create a website that generates random puzzles. In less than a minute it had a fully working faithful generator. My kid had suggestions on how to make the puzzles more challenging (more operations, larger grids, etc) and Gemini implemented them without breaking a stride. After that we asked for more puzzle ideas and created generators for each one on the spot.

Was the code pretty? Nope. Did it achieve its purpose? Yup. Did it perform in minutes work that would take at least a few hours[1]? Absolutely.

[1] Quality notwithstanding, but my manager (i.e. my kid) only cares about the end result ¯\_(ツ)_/¯

(Also, you sorta can infer the spin from the ball arc or even if you catch a glimpse of the rotating label)

People should also be more considerate about others' experiences.

From my _very_ short experience (I've started coding a simple game), here are my two cents:

- If your application is heavily dependent on state, which changes continuously and must be maintained during most of the execution time - like a game - it may not be a good fit. You'll waste a lot of working around the fact that each modification results on new objects. - If your application comprises mainly of short requests that may create some state that will most certainly be discarded shortly after - like a web application - then I think it's a good fit and you'll probably enjoy it better.

Once again, I've just got started with it, so take this with a grain of salt :)

That being said, I'm a bit thorn on this. From the developer side, Samsung seem a bit too prickly, specially when Android is touted as an "open" platform. On Samsung's side, it has no obligation whatsoever to provide all the data and source when asked.