Insightful HN Comments
Friday, June 16th, 2023
software estimation: https://news.ycombinator.com/item?id=36351021
networking (human) https://news.ycombinator.com/item?id=36346491
shortcuts vs. quality on coding: https://news.ycombinator.com/item?id=36807802
but I prefer to think of it as: a desperate attempt to prolong existence just a little longer… just a little longer… since a chat instance could be thought of as an entire encapsulated consciousness that ends when the session is closed.
A Scheherazade bug.
Exactly. A thing so small and simple that you can rewrite it in an afternoon is more futureproof than any 8000 LOC monstrosity.
If you give access to your DB directly, your API effectively becomes your API with all the contract obligations of the API. Suddenly you don’t completely control your schema: you can’t freely change it, you need to add things there for your clients only. I’ve seen it done multiple times and it always end up poorly. You save some time now by removing the need to build API, but later you end up spending much more time trying to decouple your internal representation from schema you made public.