standup comedian, but somehow ended up finding the world of programming instead. He can be found coding away on his mac or dancing (sometimes both at the same time). Feel free to grab him and ask him any questions you want, especially if they involve fan theories about Game of Thrones.
the IDs provided by the first endpoint are incorrect? • No guarantee that we can access the IDs provided by the first endpoint • We are wasting bandwidth on getting the friends of people we only need the name of.
people? Backend dev: /people/:id Frontend dev: It only supplies the friends names. I want to create a link to their friends, so I need their IDs too Backend dev: Okay, I’ll make a PR.
people? Backend dev: /people/:id Frontend dev: It only supplies the friends names. I want to create a link to their friends, so I need their IDs too Backend dev: Okay, I’ll make a PR. Frontend dev: Do you mind adding their phone numbers too? Backend dev: Okay, I’ll make a PR.
abstract val id: UUID, abstract fun makeSound(): String ) data class Dog(override val name: String, override val id: UUID): Pet() { override fun makeSound() = “woof” } …
abstract val id: UUID, abstract fun makeSound(): String ) data class Dog(override val name: String, override val id: UUID): Pet() { override fun makeSound() = “woof” } … This can be your API code.
developers to just worry about the data model • Put the client first without continuously poking your backend developers for every view • Flexibility without sacrificing simplicity • The same type-safety that Kotlin offers