I never trust anything but the commandline when it comes to git. Then I know full and well what I'm doing regardless of the editor. When there are too many icons and buttons to click I don't like to have to remember what they all mean, or how well they map to the underlying core git concepts.
I am in the same situation. I only switch to Norwegian layout when typing emails, all other times I use US layout. The keyboard is blank, so no confusion with keys either.
I think the new wording is more uncertain, since we now don't know at what time Jottacloud will claim unlimited storage has been exceeded. They say that "in some cases where the total storage- and network use significantly exceeds the average use of a Jottacloud user, [we] can deem this use as excessive".
Before I had a hard limit to stay under, now I cannot know anymore. This was the reason I stopped using Jottacloud, going all in on ACD..
One can still do what you are describing and have the Swagger spec generated. On my platform, I would just specify data types and the interfaces, and have Swashbuckle parse this and spit out the Swagger spec. No need to hand-code Swagger while creating the contract up front. After this step, one could work at both sides of the contract independently as you describe.
I would never write Swagger by hand; why should I when I can have it generated? We are using Swashbuckle[0] to generate Swagger for our ASP.NET Web API, which have been a great experience. We can explore and test the API in Swagger UI. I have been sprinkling a bit of hypermedia on top of this with HAL, mainly just for having links. I have never met anyone wanting to go the full HATEOAS route, but simple links can go a long wa. Swagger UI have been great for this, as HAL alone isn't really expressive enough to document what a link means. On the consumer side, I have been using NSwag[1] to generate clients with good results.
