Kash Patel tweeting in real-time indicates that he aware of it and at some-level involved with the arrest. It also shows that he sees this as a totally reasonable action and response - and wants the public to know about it.
I've been working on digitizing my family genealogy. ~90 years ago, a book was published documenting my family's lineage in America. I've digitized part of it, used OCR to extract the text, and then used LLMs to format the data for integration into a family tree. I hope to publish the family tree and make it editable so that it's a living family tree that others can add to and keep up to date.
It's far less extensive than what you presented, but on the current project we are working on at work, we are using https://github.com/swaggo/swag
It's somewhat specific to golang but so far it has been relatively good for us.
The spec is directly next to the code as code comments, so it has far more chances to get updated when changes are made compared to an external documentation.
Also, the payloads and responses are directly derived from the Golang structs, so, at least on that aspect, changes in the code are automatically reflected in the spec (apart for description and examples).
We also put the interactive documentation directly in our API under /doc. It is a useful tool for developers when implementing a new url/handler or modifying an existing one. It also creates incentives to keep the documentation matching.
Overall, we had very few mismatches between the spec and the actual implementation overall, despite not having deeply tested it (be it manually or automatically). Apart from one or two mismatches that were fixed quickly, I was able to take the spec, generate client libraries from it (swagger-codegen), and use them for quite extensive demos without issues.
We are still early in the project (not in production yet), and there are definitely some aspects we need to improve (integration/automated tests to be sure doc and code are 100% matching) or to completely figure out (ex: how to handle several versions of the same API). But overall, using swaggo/swag has been a pleasant experience.
I've always found Troy Hunt's tech stack of haveibeenpwned.com interesting. The API does 5M requests a day with Azure Functions and Cloudflare caching. Ultimately only costing him 2.6c per day.
Location: Rochester, NY
Remote: Yes
Willing to relocate: Major cities
Technologies: C# ASP.NET Core, Javascript (Angular & Knockout), MongoDb, SQL, Java, Azure
Résumé/CV: Upon request
Email: HN profile
6+ years experience. Currently a Senior Full Stack Software Engineer working on a rapidly growing web application. Joining a company with a good culture is very important to me.
Location: Upstate NY
Remote: No
Willing to relocate: Yes (NYC or San Diego)
Technologies: C#, ASP.NET MVC, Java, Javascript (knockout, backbone.js), MongoDB, SQL, Redis, RabbitMQ
Résumé/CV: Please email me for a copy
Email: cmf4287@rit.edu
Full Stack Software Developer working on a rapidly growing web application. I particularly enjoy debugging and fixing problems around scaling and performance. Joining a company with a good culture is very important to me.
It's not about the money. It's about the fame - having you're name in stone for a very very long time. Some people see success as having their names printed in textbooks and in history books.
The only thing better about that car is hearing John Hindhaugh of Radio Le Mans start talking about it during a race and he says "1000 Brake Horsepower" (Gasoline Engine + Super Capacitor Hybrid System). you can hear the smile on his face as he says it.
