A modern programming language that makes developers happier.

kotlinlang

<https://twitter.com/KotlinMumbai/status/1397156821505249286?s=20>

Are those UseCase really needed in the first place?
Reminds me strongly of Steve Yegge's *Execution in the Kingdom of Nouns*
<http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom-of-nouns.html>

It's just example to demonstrate `invoke()`. Rest, it depends on developers how they want to use it.

Nice one. I guess, you can also do
```AddUserUseCase()(1, "John Doe")```
which seems fun :smile:


Also! By having
```object AddUserUseCase {
  operator fun invoke(userId: Int, name: String) { ... }
}```
you can then do
```AddUserUseCase(1, "JohnDoe")```
People will think it's a constructor, but nope!

:+1:

That's why it's mentioned, "Do not overuse it" :sweat_smile:

image.png

<@U0B8UKF8R> it has one advantage, it lets you injects things, and if the use case is injected as argument in a ViewModel for example, the usage looks like a function.

In an ideal world or if the DI you use allow it, the use case should be a function directly