LLM Visualization
8 by gmays | 0 comments on Hacker News.
Thursday, September 4, 2025
New top story on Hacker News: A high schooler writes about AI tools in the classroom
A high schooler writes about AI tools in the classroom
88 by dougb5 | 74 comments on Hacker News.
https://ift.tt/TcXbSxm
88 by dougb5 | 74 comments on Hacker News.
https://ift.tt/TcXbSxm
Wednesday, September 3, 2025
New top story on Hacker News: Vector search on our codebase transformed our SDLC automation
Vector search on our codebase transformed our SDLC automation
18 by antonybrahin | 2 comments on Hacker News.
Hey HN, In software development, the process of turning a user story into detailed documentation and actionable tasks is critical. However, this manual process can often be a source of inconsistency and a significant time investment. I was driven to see if I could streamline and elevate it. I know this is a hot space, with big players like GitHub and Atlassian building integrated AI, and startups offering specialized platforms. My goal wasn't to compete with them, but to see what was possible by building a custom, "glass box" solution using the best tools for each part of the job, without being locked into a single ecosystem. What makes this approach different is the flexibility and full control. Instead of a pre-packaged product, this is a resilient workflow built on Power Automate, which acts as the orchestrator for a sequence of API calls: Five calls to the Gemini API for the core generation steps (requirements, tech spec, test strategy, etc.). One call to an Azure OpenAI model to create vector embeddings of our codebase. One call to Azure AI Search to perform the Retrieval-Augmented Generation (RAG). This was the key to getting context-aware, non-generic outputs. It reads our actual code to inform the technical spec and tasks. A bunch of direct calls to the Azure DevOps REST API (using a PAT) to create the wiki pages and work items, since the standard connectors were a bit limited. The biggest challenge was moving beyond simple prompts and engineering a resilient system. Forcing the final output into a rigid JSON schema instead of parsing text was a game-changer for reliability. The result is a system that saves us hours on every story and produces remarkably consistent, high-quality documentation and tasks. The full write-up with all the challenges, final prompts, and screenshots is in the linked blog post. I’m here to answer any questions. Would love to hear your feedback and ideas!
18 by antonybrahin | 2 comments on Hacker News.
Hey HN, In software development, the process of turning a user story into detailed documentation and actionable tasks is critical. However, this manual process can often be a source of inconsistency and a significant time investment. I was driven to see if I could streamline and elevate it. I know this is a hot space, with big players like GitHub and Atlassian building integrated AI, and startups offering specialized platforms. My goal wasn't to compete with them, but to see what was possible by building a custom, "glass box" solution using the best tools for each part of the job, without being locked into a single ecosystem. What makes this approach different is the flexibility and full control. Instead of a pre-packaged product, this is a resilient workflow built on Power Automate, which acts as the orchestrator for a sequence of API calls: Five calls to the Gemini API for the core generation steps (requirements, tech spec, test strategy, etc.). One call to an Azure OpenAI model to create vector embeddings of our codebase. One call to Azure AI Search to perform the Retrieval-Augmented Generation (RAG). This was the key to getting context-aware, non-generic outputs. It reads our actual code to inform the technical spec and tasks. A bunch of direct calls to the Azure DevOps REST API (using a PAT) to create the wiki pages and work items, since the standard connectors were a bit limited. The biggest challenge was moving beyond simple prompts and engineering a resilient system. Forcing the final output into a rigid JSON schema instead of parsing text was a game-changer for reliability. The result is a system that saves us hours on every story and produces remarkably consistent, high-quality documentation and tasks. The full write-up with all the challenges, final prompts, and screenshots is in the linked blog post. I’m here to answer any questions. Would love to hear your feedback and ideas!
Tuesday, September 2, 2025
Monday, September 1, 2025
New top story on Hacker News: Show HN: woomarks, transfer your Pocket links to this app or self-host it
Show HN: woomarks, transfer your Pocket links to this app or self-host it
9 by earlyriser | 0 comments on Hacker News.
Pocket is shutting down and I really, really liked it. So I built woomarks, an app that let's you save links with a similar UI. It's very minimal, but it's doing everything I liked from Pocket and you can bulk import your links and use the app or self-host. - Public app that you can test: https://woomarks.com/ - My self-hosted version, where you can see my saves: https://ift.tt/m9ZM5dY - Repository if you want to self-host: https://ift.tt/nMdf8s6 Export links from Pocket here: https://ift.tt/y4KiESX the last day will be on October 20025. Features: - Add/Delete links - Search - Tags - Bookmarklet (useful for a 2-click-save) - Data reads from: csv file in server (these links are public) local storage in browser (these links are visible just for the user) - Local storage saving. - Import to local storage from csv file - Export to csv from local storage. - Export to csv from csv file (useful when links are "deleted" using the app and just hidden using a local storage blacklist). - Export to csv from both places. - No external libraries. - Vanilla css code. - Vanilla js code.
9 by earlyriser | 0 comments on Hacker News.
Pocket is shutting down and I really, really liked it. So I built woomarks, an app that let's you save links with a similar UI. It's very minimal, but it's doing everything I liked from Pocket and you can bulk import your links and use the app or self-host. - Public app that you can test: https://woomarks.com/ - My self-hosted version, where you can see my saves: https://ift.tt/m9ZM5dY - Repository if you want to self-host: https://ift.tt/nMdf8s6 Export links from Pocket here: https://ift.tt/y4KiESX the last day will be on October 20025. Features: - Add/Delete links - Search - Tags - Bookmarklet (useful for a 2-click-save) - Data reads from: csv file in server (these links are public) local storage in browser (these links are visible just for the user) - Local storage saving. - Import to local storage from csv file - Export to csv from local storage. - Export to csv from csv file (useful when links are "deleted" using the app and just hidden using a local storage blacklist). - Export to csv from both places. - No external libraries. - Vanilla css code. - Vanilla js code.
Sunday, August 31, 2025
New top story on Hacker News: Show HN: Anonymous Age Verification
Show HN: Anonymous Age Verification
4 by jwally | 2 comments on Hacker News.
So I'm not an expert in this area, but here's an attempt at cost effective, anonymous, age verification flow that probably covers ~70% of use cases in the United States. The basic premise is to leverage your bank (who already has had to perform KYC on you to open an account) to attest to your age for age-restricted merchant sites (pornhub, gambling, etc) without sharing any more information than necessary. Flow works like this: 1) You go to gambling.com 2) They request you to verify your age 3) You choose "Bank Verification" 4) You trigger a WebAuthn Credential Creation flow 5) gambling.com gives you a string to copy ------------- 6) You log into your bank 7) You go to bank.com/age-verify 8) You paste in the string you were given 9) The bank verifies it/you and creates a signed payload with your age-claims (over_18: true, over_21: false) 10) You copy this and go back to gambling.com --------------- 11) You paste the string back into gambling.com 12) You perform WebAuthn Auth flow 13) gambling.com verifies everything (signatures, webauthn, etc) 14) gambling.com sets a session-cookie and _STRONGLY_ encourages you to create an account (with a pass key). This will prevent you from having to verify your age every time you visit gambling.com The mechanics might feel off, but it feels like this in the neighborhood of a way to perform anonymous age verification. This is virtually free, and requires extremely light infra. Banks can be incentivized with small payments, or offer it because everyone else does and don't want to get left behind.
4 by jwally | 2 comments on Hacker News.
So I'm not an expert in this area, but here's an attempt at cost effective, anonymous, age verification flow that probably covers ~70% of use cases in the United States. The basic premise is to leverage your bank (who already has had to perform KYC on you to open an account) to attest to your age for age-restricted merchant sites (pornhub, gambling, etc) without sharing any more information than necessary. Flow works like this: 1) You go to gambling.com 2) They request you to verify your age 3) You choose "Bank Verification" 4) You trigger a WebAuthn Credential Creation flow 5) gambling.com gives you a string to copy ------------- 6) You log into your bank 7) You go to bank.com/age-verify 8) You paste in the string you were given 9) The bank verifies it/you and creates a signed payload with your age-claims (over_18: true, over_21: false) 10) You copy this and go back to gambling.com --------------- 11) You paste the string back into gambling.com 12) You perform WebAuthn Auth flow 13) gambling.com verifies everything (signatures, webauthn, etc) 14) gambling.com sets a session-cookie and _STRONGLY_ encourages you to create an account (with a pass key). This will prevent you from having to verify your age every time you visit gambling.com The mechanics might feel off, but it feels like this in the neighborhood of a way to perform anonymous age verification. This is virtually free, and requires extremely light infra. Banks can be incentivized with small payments, or offer it because everyone else does and don't want to get left behind.
Saturday, August 30, 2025
Subscribe to:
Posts (Atom)