@halfbyte You could be right — teams working on one large. complex project for years are different when it comes to AI coding. At the end of the day, it is another teammate. Bit weird, but mighty.

Out of tons of use cases I can share: I'm already happy about devs asking the agent those "stupid" intimidating questions about implementation details, domain knowledge and alternatives they might otherwise never ask. It's empowering.

@halfbyte Right, AI brings serious problems we mustn't ignore. But at the end, it's a tool—impact depends on use. It's not about one-line “do it for me” prompts.

With coding agents, bad teams get worse; good teams though e.g. gain better analysis and planning before implementation, improved test coverage, and even reduce comprehension debt.

IMHO AI can help to become a better dev.

@riffraff Also `val || val = false if foo` would call foo even if `val` is already true and has no chance to change to `false` in that line.

Code like this (sugar or not) can be unnecessarily expensive, maybe not at first glance ...

```
val = truthy_method
val ||= 2 if foo1
val ||= 3 if foo2
```