![](https://media.kbin.social/media/45/de/45de5b20522083ecc16b3a6312bea97d59aa560dbf84d5982b03cee171473bd3.png)
![](https://lemmy.ml/pictrs/image/c0ed0a36-2496-4b4d-ac77-7d2fd7f2b5b7.png)
1·
1 year ago/serious Well, yes, most APIs are meant for system-to-system interaction, that’s kind of a given. But since this particular API is clearly meant for human-to-system interaction, returning a human-readable response is adequate. Yes, a better design would probably allow the client to specify additional parameters about the desired response.
/back-to-jokes Yeah, well this kind of sums up most of my job applications. I send an application and the recruiting people are all like “OK”.
Brief history of YAML:
YAML is generally good if it’s used for what it was originally designed for (relatively short data files, e.g. configuration data). Problem is, people use it for so much more. (My personal favourite pain example: i18n stuff in Ruby on Rails. YAML language files work for small apps, but when the app grows, so does the pain.)