Article URL: https://plato.stanford.edu/entries/holes/ Comments URL: https://news.ycombinator.com/item?id=49934261 Points: 7 # Comments: 1
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Earlier today, I was booking a train ticket online. The platform required NIN (National Identification Number) verification before letting me continue. I entered a valid NIN. The verification call failed with a 500 and a generic SOMETHING_WENT_WRONG. Not an invalid-NIN error — an actual server failure.
Every OpenAPI document starts as one clean file. Then it reaches forty operations and the file is 2,000 lines, then a hundred operations and pull requests conflict on every merge, then nobody edits it without a full afternoon of context. The standard advice is "split it with $ref," which is true and unhelpful — split how, along which boundaries, and what breaks in tooling when you do? This is the layout and rule set that survives 200+ operation APIs. Organize by artifact kind first, domain second.
I wanted a simpler way to sort email without sending message text to an AI service. So I started building Gev: a browser extension that reads my Gmail messages and automatically labels them into categories like Receipts, Personal, Updates, or Newsletters. https://github.com/receptron/laya model. The model and ONNX runtime are bundled with the extension. There’s no inference API or hosted model involved and no data is ever sent to an external service or host(except gmail).
The viva is where many students lose marks, even with a working project. Examiners usually want to see that you understand what you built. Here is a simple way to prepare. Be ready to explain in two or three sentences: What problem does your project solve? Who will use it?
Discussion (0)
Log in to join the discussion and vote.
Log in