Jsonschema2pojo
github.com1 pointsby auvrw0 comments
I came to the Graide Network and immediately started breaking our legacy app into microservices.
as "overengineering," and perhaps it was ... or perhaps it was just not-great planning. after all, the premise of the article is that the microservices are now incurring costs that can be described more like plumbing than engineering. Investors are guilty of pushing it on us
this has happened to CEOs at startups i've been at: [some] investors asked for diagrams, etc., and we made decisions to build invisible fanciness instead of product for users. we can build more with less
Isn't that so the spirit of the times when working with LLMs? If one asks for a Prisma schema or something else out of GipPTy meant to be fed into a traditional parser, we're up the the whims of the attention blocks and layers to write out something that doesn't become a parse error. One can turn the temperature down, fine-tune, or self-host a model but does that guarantee the syntax will be correct (much less the semantics)?