I wonder how would this work in an international dev teams. While code is always the common language (including the UML), markdown requires you to have really good english writing skills. This can get messy really fast.

Oh, it will work just fine once he opens a project which he will need to modify and which is full of Chinese markdown files.

So it's not reproducible.

This is inevitable unfortunately with LLMs.

> Now not anymore you just need to tell the LLM and it does it in both, and you get better results too.

That's weird I just asked fable to build airbnb app clone and it didn't do a good job. Am I using the wrong model?

That probably means Fable doesn't have enough understanding of what AirBNB is in order to build a clone.

If you think about it, people don't really write much about how an app like that actually works. They write about the impact on travel, the impact on property prices, how to use it to book a vacation, and a bit about how it's a two-sided market place app, but not so much about what it actually does.

I assume that Fable has no access to it apart from the listing pages so it can't see behind the scenes to the property management side or the AirBnB admin stuff. The code isn't open so Fable isn't learning from that. There's probably a bunch of clones on Github but quality will vary.

If you want a clone of an app like that you'll need to build a large amount of context first, and even then you'll probably miss a lot.

The migration is fairly simple and well documented.

The problem may be the lack of jinja support for 3rd party django apps (mostly legacy). So make sure they support it first.

That's the whole beauty of frameworks and languages. Some of them just "click" with you. At the end of the day we can all build what we need.

Someone needs to look at https://htmx.ceo/. They're definately overpaid. Some of them can even afford an iphone mini.