10 Agiles to Griffindor!

So... you can write a bad test? Yup. That happens. And you can misunderstand what you're trying to do? Well, there's no magic test that will make you understand what you're meant to be doing.

I've always liked the simplicity of Http4k framework - the isomorphism between the servers and the clients is a great feature.

After 20 years all I remember about `Mote` is the incessant conversations about tea and coffee...

Forgive my ignorance, but could someone explain how the tools mentioned above differ from things like:

https://msdn.microsoft.com/en-us/library/ff657795.aspx

Which I'd taken to be A BAD IDEA:

http://programmers.stackexchange.com/questions/124996/is-cod...

RAML and the others have a lot of value simply as the source of truth for your API definitions. You need to hold that somewhere - and probably share it with others - and a DSL specifically designed for documenting APIs is a good place. Where else would you hold it after all?

However, as developers we love to reach for the stars, so surely that's not enough? Surely we should be able to generate complete, working systems from the RAML (or whatever)! I would say that's a pipe-dream, just as it always has been, and just as it always will be. You might be able to generate a few stubs from RAML (or a UML diagram), but annoyingly, those are also the easiest things for a developer to just crank out anyway, and you'll be up to your ears in compiler soon enough.

It is - this is pretty much the argument of the Transcendental Aesthetic in the First Critique.