Unfortunate that these are the only two I've seemed to be able to find, but there's always graphicsLayer {} if you have multiple properties changing at the same time!

Kotlin can allow both, couldn't it? Just utilize a parameter with a default value. Kotlin defaults kind of give us the best of both worlds here.

Is this pictured as a transformation of the entire SW career? How do we get, keep, and mentor juniors and the next generation of engineers in this new world?

The human will need to be there for at the very least quite a long time I think, as machines thus far completely lack empathy.

Ultimately makes that worth it to me are two things. For one, there are 30 to 50 classes that have this DSL embedded into them and need to be rewritten.

Secondly, I don't need to sit and watch it work. I can use a work tree and separate AS insurance to keep an eye on it but otherwise work elsewhere

A sad state of affairs as both reading and writing are very healthy for your brain.

"To be clear, developers will have the same freedom to distribute their apps directly to users through sideloading or to use any app store they prefer."

I remember checking if the view passed into my ListView method was null or not.

I remember we saw a home we liked and it ended up having a *wooden* foundation 😵‍💫

"looked at a house... Foundation---" don't walk run

And the need for high quality SWEs especially for projects dealing with sensitive areas like finance or cryptography, need that oversight. Furthermore, there is a human element to SWEs in understanding intent and empathizing with users that I don't think we would ever truly get in AI.

Suggests and that's very easy to do with the command line tools they provide. Nothing goes into my work that I've not personally looked at, verified, and understand. And someone vibe coding does not have the skill set to do that, software engineers do. Tools like Claude are just prediction engines