The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Quantus – LeetCode for Financial Modeling
Hi everyone,<p>I wanted to share Quantus, a finance learning and practice platform I’m building out of my own frustration with traditional resources.<p>As a dual major in engineering and finance who started my career at a hedge fund, I found it challenging to develop hands-on financial modeling skills using existing tools. Platforms like Coursera, Udemy, Corporate Finance Institute (CFI), and Wall Street Prep (WSP) primarily rely on video-based tutorials. While informative, these formats often lack the dynamic, interactive, and repetitive practice necessary to build real expertise.<p>For example, the learning process often involves:<p>- Replaying videos multiple times to grasp key concepts.<p>- Constantly switching between tutorials and Excel files.<p>- Dealing with occasional discrepancies between tutorial numbers and the provided Excel materials.<p>To solve these problems, I created Quantus—an interactive platform where users can learn finance by trying out formulas or building financial models directly in an Excel-like environment. Inspired by LeetCode, the content is organized into three levels—easy, medium, and hard—making it accessible for beginners while still challenging for advanced users.<p>Our growing library of examples includes:<p>- 3-statement financial models<p>- Discounted Cash Flow (DCF) analysis<p>- Leveraged Buyouts (LBO)<p>- Mergers and Acquisitions (M&A)<p>Here’s a demo video to showcase the platform in action. <a href="https://www.youtube.com/watch?v=bDRNHgBERLQ" rel="nofollow">https://www.youtube.com/watch?v=bDRNHgBERLQ</a><p>I’d love to hear your thoughts and feedback! Let me know what other features or examples you’d find useful.
Show HN: Quantus – LeetCode for Financial Modeling
Hi everyone,<p>I wanted to share Quantus, a finance learning and practice platform I’m building out of my own frustration with traditional resources.<p>As a dual major in engineering and finance who started my career at a hedge fund, I found it challenging to develop hands-on financial modeling skills using existing tools. Platforms like Coursera, Udemy, Corporate Finance Institute (CFI), and Wall Street Prep (WSP) primarily rely on video-based tutorials. While informative, these formats often lack the dynamic, interactive, and repetitive practice necessary to build real expertise.<p>For example, the learning process often involves:<p>- Replaying videos multiple times to grasp key concepts.<p>- Constantly switching between tutorials and Excel files.<p>- Dealing with occasional discrepancies between tutorial numbers and the provided Excel materials.<p>To solve these problems, I created Quantus—an interactive platform where users can learn finance by trying out formulas or building financial models directly in an Excel-like environment. Inspired by LeetCode, the content is organized into three levels—easy, medium, and hard—making it accessible for beginners while still challenging for advanced users.<p>Our growing library of examples includes:<p>- 3-statement financial models<p>- Discounted Cash Flow (DCF) analysis<p>- Leveraged Buyouts (LBO)<p>- Mergers and Acquisitions (M&A)<p>Here’s a demo video to showcase the platform in action. <a href="https://www.youtube.com/watch?v=bDRNHgBERLQ" rel="nofollow">https://www.youtube.com/watch?v=bDRNHgBERLQ</a><p>I’d love to hear your thoughts and feedback! Let me know what other features or examples you’d find useful.
Show HN: A free and open source commerical/personal SaaS starter kit
Show HN: KeyTik: The All-in-One Automation Tool
Show HN: DIY 80€ 3D Printer Basement Ventilation
Show HN: Convert your LinkedIn profile to a resume
Show HN: Convert your LinkedIn profile to a resume
Show HN: Convert your LinkedIn profile to a resume
Show HN: Hyperbrowser – Scalable Browser Infrastructure for AI Apps
Hey HN!<p>Excited to share a project we've been working on called Hyperbrowser. It’s a tool that makes scaling headless browsers ridiculously easy. It allows you to spin up hundreds of browser sessions in secure, isolated environments, with sub-second launch times. We automatically solve captchas, use residential proxies and manage concurrent sessions so that you can focus on your own business.<p>The idea for Hyperbrowser came from our own struggles building AI apps and agents like sales tools, automations, and AI editors. Every project seemed to hit the same roadblock: interacting with the web. Whether we needed web data as input or web browsing as output, we faced constant challenges—getting blocked, setting up proxy services, solving captchas, and scaling everything in Kubernetes.<p>On top of that, we had to build custom functions and services to convert websites into LLM-friendly markdown and crawl entire sites for relevant data. Keeping all of this running became a full-time job!<p>To make this easy for everyone else we built Hyperbrowser. It packages everything we learned and built, with a nice frontend that gets rid of the boilerplate and lets you hit the ground running. Hyperbrowser works seamlessly with tools you already know, like Puppeteer, Playwright, or Selenium, while removing the hassle of infrastructure and scaling.<p>If this sounds interesting, we’d love for you to give it a spin! You can sign up and start playing around with a free plan. Would love to hear your thoughts, feedback, or ideas! Check it out here at hyperbrowser.ai.<p>If you have any questions at all feel free to reach out to me at akshay@hyperbrowser.ai! Ideally share the website you'd like to scrape or automate. I can provide a script for it or we can create a custom API endpoint!
Show HN: Holos – Configure Kubernetes with CUE data structures instead of YAML
Hi HN! I’m excited to share Holos, a Go command line tool we wrote to fill the configuration management gap in Kubernetes. Holos uses CUE to configure software distributed with Helm and Kustomize using a well defined, type safe language eliminating the need to template YAML. You probably know (or are) someone who has suffered with the complexity of plain text YAML templates and merging multiple values.yaml files together to configure software running in Kubernetes. We built Holos so we don’t have to template YAML but we can still integrate software distributed with Helm and Kustomize holistically into one unified configuration.<p>At the start of the pandemic I was migrating our platform to Kubernetes from virtual machines managed by Puppet. My primary goal was to build an observability system similar to what we had when we managed Puppet at Twitter prior to the acquisition. I started building the observability system with the official prometheus community charts [1], but quickly ran into issues where the individual charts didn’t work with each other. I was frustrated with how difficult it was to configure these charts. They weren’t well integrated, so I switched to the kube-prometheus-stack [2] umbrella chart which attempts to solve this integration problem.<p>The umbrella chart got us further but we quickly ran into operational challenges. Upgrading the chart introduced breaking changes we couldn’t see until they were applied, causing incidents. We needed to manage secrets securely so we mixed in ExternalSecrets with many of the charts. We decided to handle these customizations by implementing the rendered manifests pattern [3] using scripts in our CI pipeline.<p>These CI scripts got us further, but we found them costly to maintain. We needed to be careful to execute them with the same context they were executed in CI. We realized we were reinventing tools to manage a hierarchy of helm values.yaml files to inject into multiple charts.<p>We saw the value in the rendered manifests pattern but could not find an agreed upon implementation. I’d been thinking about the comments from the <i>Why are we templating YAML?</i> [4][5] posts and wondering what an answer to this question would look like, so I built a Go command line tool to implement the pattern as a data pipeline. We still didn’t have a good way to handle the data values. We were still templating YAML which didn’t catch errors early enough. It was too easy to render invalid resources Kubernetes rejected.<p>I searched for a solution to manage and merge helm values. A few HN comments mentioned CUE [6], and an engineer we worked with at Twitter used CUE to configure Envoy at scale, so I gave it a try. I quickly appreciated how CUE provides both strong type checking and validation of constraints, unifies all configuration data, and provides clarity into where values originate from.<p>Take a look at Holos if you’re looking to implement the rendered manifests pattern or can’t shake that feeling it should be easier to integrate third party software into Kubernetes like we felt. We recently overhauled our docs to be easier to get started and work locally on your device.<p>In the future we’re planning to use Holos much like Debian uses APT, to integrate open source software into a holistic k8s distribution.<p>[1]: <<a href="https://github.com/prometheus-community/helm-charts">https://github.com/prometheus-community/helm-charts</a>><p>[2]: <<a href="https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack">https://github.com/prometheus-community/helm-charts/tree/mai...</a>><p>[3]: <<a href="https://akuity.io/blog/the-rendered-manifests-pattern" rel="nofollow">https://akuity.io/blog/the-rendered-manifests-pattern</a>><p>[4]: <i>Why are we templating YAML? (2019)</i> - <<a href="https://news.ycombinator.com/item?id=19108787">https://news.ycombinator.com/item?id=19108787</a>><p>[5]: <i>Why are we templating YAML? (2024)</i> - <<a href="https://news.ycombinator.com/item?id=39101828">https://news.ycombinator.com/item?id=39101828</a>><p>[6]: <<a href="https://cuelang.org/" rel="nofollow">https://cuelang.org/</a>>
Show HN: Holos – Configure Kubernetes with CUE data structures instead of YAML
Hi HN! I’m excited to share Holos, a Go command line tool we wrote to fill the configuration management gap in Kubernetes. Holos uses CUE to configure software distributed with Helm and Kustomize using a well defined, type safe language eliminating the need to template YAML. You probably know (or are) someone who has suffered with the complexity of plain text YAML templates and merging multiple values.yaml files together to configure software running in Kubernetes. We built Holos so we don’t have to template YAML but we can still integrate software distributed with Helm and Kustomize holistically into one unified configuration.<p>At the start of the pandemic I was migrating our platform to Kubernetes from virtual machines managed by Puppet. My primary goal was to build an observability system similar to what we had when we managed Puppet at Twitter prior to the acquisition. I started building the observability system with the official prometheus community charts [1], but quickly ran into issues where the individual charts didn’t work with each other. I was frustrated with how difficult it was to configure these charts. They weren’t well integrated, so I switched to the kube-prometheus-stack [2] umbrella chart which attempts to solve this integration problem.<p>The umbrella chart got us further but we quickly ran into operational challenges. Upgrading the chart introduced breaking changes we couldn’t see until they were applied, causing incidents. We needed to manage secrets securely so we mixed in ExternalSecrets with many of the charts. We decided to handle these customizations by implementing the rendered manifests pattern [3] using scripts in our CI pipeline.<p>These CI scripts got us further, but we found them costly to maintain. We needed to be careful to execute them with the same context they were executed in CI. We realized we were reinventing tools to manage a hierarchy of helm values.yaml files to inject into multiple charts.<p>We saw the value in the rendered manifests pattern but could not find an agreed upon implementation. I’d been thinking about the comments from the <i>Why are we templating YAML?</i> [4][5] posts and wondering what an answer to this question would look like, so I built a Go command line tool to implement the pattern as a data pipeline. We still didn’t have a good way to handle the data values. We were still templating YAML which didn’t catch errors early enough. It was too easy to render invalid resources Kubernetes rejected.<p>I searched for a solution to manage and merge helm values. A few HN comments mentioned CUE [6], and an engineer we worked with at Twitter used CUE to configure Envoy at scale, so I gave it a try. I quickly appreciated how CUE provides both strong type checking and validation of constraints, unifies all configuration data, and provides clarity into where values originate from.<p>Take a look at Holos if you’re looking to implement the rendered manifests pattern or can’t shake that feeling it should be easier to integrate third party software into Kubernetes like we felt. We recently overhauled our docs to be easier to get started and work locally on your device.<p>In the future we’re planning to use Holos much like Debian uses APT, to integrate open source software into a holistic k8s distribution.<p>[1]: <<a href="https://github.com/prometheus-community/helm-charts">https://github.com/prometheus-community/helm-charts</a>><p>[2]: <<a href="https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack">https://github.com/prometheus-community/helm-charts/tree/mai...</a>><p>[3]: <<a href="https://akuity.io/blog/the-rendered-manifests-pattern" rel="nofollow">https://akuity.io/blog/the-rendered-manifests-pattern</a>><p>[4]: <i>Why are we templating YAML? (2019)</i> - <<a href="https://news.ycombinator.com/item?id=19108787">https://news.ycombinator.com/item?id=19108787</a>><p>[5]: <i>Why are we templating YAML? (2024)</i> - <<a href="https://news.ycombinator.com/item?id=39101828">https://news.ycombinator.com/item?id=39101828</a>><p>[6]: <<a href="https://cuelang.org/" rel="nofollow">https://cuelang.org/</a>>
Show HN: Holos – Configure Kubernetes with CUE data structures instead of YAML
Hi HN! I’m excited to share Holos, a Go command line tool we wrote to fill the configuration management gap in Kubernetes. Holos uses CUE to configure software distributed with Helm and Kustomize using a well defined, type safe language eliminating the need to template YAML. You probably know (or are) someone who has suffered with the complexity of plain text YAML templates and merging multiple values.yaml files together to configure software running in Kubernetes. We built Holos so we don’t have to template YAML but we can still integrate software distributed with Helm and Kustomize holistically into one unified configuration.<p>At the start of the pandemic I was migrating our platform to Kubernetes from virtual machines managed by Puppet. My primary goal was to build an observability system similar to what we had when we managed Puppet at Twitter prior to the acquisition. I started building the observability system with the official prometheus community charts [1], but quickly ran into issues where the individual charts didn’t work with each other. I was frustrated with how difficult it was to configure these charts. They weren’t well integrated, so I switched to the kube-prometheus-stack [2] umbrella chart which attempts to solve this integration problem.<p>The umbrella chart got us further but we quickly ran into operational challenges. Upgrading the chart introduced breaking changes we couldn’t see until they were applied, causing incidents. We needed to manage secrets securely so we mixed in ExternalSecrets with many of the charts. We decided to handle these customizations by implementing the rendered manifests pattern [3] using scripts in our CI pipeline.<p>These CI scripts got us further, but we found them costly to maintain. We needed to be careful to execute them with the same context they were executed in CI. We realized we were reinventing tools to manage a hierarchy of helm values.yaml files to inject into multiple charts.<p>We saw the value in the rendered manifests pattern but could not find an agreed upon implementation. I’d been thinking about the comments from the <i>Why are we templating YAML?</i> [4][5] posts and wondering what an answer to this question would look like, so I built a Go command line tool to implement the pattern as a data pipeline. We still didn’t have a good way to handle the data values. We were still templating YAML which didn’t catch errors early enough. It was too easy to render invalid resources Kubernetes rejected.<p>I searched for a solution to manage and merge helm values. A few HN comments mentioned CUE [6], and an engineer we worked with at Twitter used CUE to configure Envoy at scale, so I gave it a try. I quickly appreciated how CUE provides both strong type checking and validation of constraints, unifies all configuration data, and provides clarity into where values originate from.<p>Take a look at Holos if you’re looking to implement the rendered manifests pattern or can’t shake that feeling it should be easier to integrate third party software into Kubernetes like we felt. We recently overhauled our docs to be easier to get started and work locally on your device.<p>In the future we’re planning to use Holos much like Debian uses APT, to integrate open source software into a holistic k8s distribution.<p>[1]: <<a href="https://github.com/prometheus-community/helm-charts">https://github.com/prometheus-community/helm-charts</a>><p>[2]: <<a href="https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack">https://github.com/prometheus-community/helm-charts/tree/mai...</a>><p>[3]: <<a href="https://akuity.io/blog/the-rendered-manifests-pattern" rel="nofollow">https://akuity.io/blog/the-rendered-manifests-pattern</a>><p>[4]: <i>Why are we templating YAML? (2019)</i> - <<a href="https://news.ycombinator.com/item?id=19108787">https://news.ycombinator.com/item?id=19108787</a>><p>[5]: <i>Why are we templating YAML? (2024)</i> - <<a href="https://news.ycombinator.com/item?id=39101828">https://news.ycombinator.com/item?id=39101828</a>><p>[6]: <<a href="https://cuelang.org/" rel="nofollow">https://cuelang.org/</a>>
Show HN: I made Gyroscopic Gyro Sandwiches
Have you noticed that a gyro sandwich is only cooked in one axis? What a missed opportunity.<p>The following details an elaborate way to slow cook food, using a handmade contraption. Not only is it tasty, it's mesmerizing. Feel free to copy the design for your own festivities.
Show HN: I made Gyroscopic Gyro Sandwiches
Have you noticed that a gyro sandwich is only cooked in one axis? What a missed opportunity.<p>The following details an elaborate way to slow cook food, using a handmade contraption. Not only is it tasty, it's mesmerizing. Feel free to copy the design for your own festivities.
Show HN: I made Gyroscopic Gyro Sandwiches
Have you noticed that a gyro sandwich is only cooked in one axis? What a missed opportunity.<p>The following details an elaborate way to slow cook food, using a handmade contraption. Not only is it tasty, it's mesmerizing. Feel free to copy the design for your own festivities.
Show HN: HackerNews-new-jobs – insights into fresh and recurring job ads
The website is meant for people that look for jobs on HackerNews "Who's Hiring" threads and want to focus more on fresh ads and companies, or to quickly look up ad history of any company.<p>Github repository: <a href="https://github.com/nemanjam/hn-new-jobs">https://github.com/nemanjam/hn-new-jobs</a><p>Demo website: <a href="https://hackernews-new-jobs.arm1.nemanjamitic.com" rel="nofollow">https://hackernews-new-jobs.arm1.nemanjamitic.com</a><p>I used Algolia API as a data source, along with scheduled task that parses new threads few times at the beginning of each month. The extracted data is then stored in SQLite database for fast querying, and the results are cached with Keyv for faster page responses. I will see in the future how much traffic the website receives and if this stack is performant enough. For the website I used Next.js app with default ShadcnUI components and charts. I just wanted a quick functional prototype to test how much public interest is there for an app with functionality like this.<p>If you are interested in more implementation details you can find them in the Readme file on Github.<p>The project is free and open source. Feel free to use, self-host, fork and modify, and contribute. I would love to hear your impressions and suggestions and look forward to discussing features and technical details.
Show HN: HackerNews-new-jobs – insights into fresh and recurring job ads
The website is meant for people that look for jobs on HackerNews "Who's Hiring" threads and want to focus more on fresh ads and companies, or to quickly look up ad history of any company.<p>Github repository: <a href="https://github.com/nemanjam/hn-new-jobs">https://github.com/nemanjam/hn-new-jobs</a><p>Demo website: <a href="https://hackernews-new-jobs.arm1.nemanjamitic.com" rel="nofollow">https://hackernews-new-jobs.arm1.nemanjamitic.com</a><p>I used Algolia API as a data source, along with scheduled task that parses new threads few times at the beginning of each month. The extracted data is then stored in SQLite database for fast querying, and the results are cached with Keyv for faster page responses. I will see in the future how much traffic the website receives and if this stack is performant enough. For the website I used Next.js app with default ShadcnUI components and charts. I just wanted a quick functional prototype to test how much public interest is there for an app with functionality like this.<p>If you are interested in more implementation details you can find them in the Readme file on Github.<p>The project is free and open source. Feel free to use, self-host, fork and modify, and contribute. I would love to hear your impressions and suggestions and look forward to discussing features and technical details.
Show HN: HackerNews-new-jobs – insights into fresh and recurring job ads
The website is meant for people that look for jobs on HackerNews "Who's Hiring" threads and want to focus more on fresh ads and companies, or to quickly look up ad history of any company.<p>Github repository: <a href="https://github.com/nemanjam/hn-new-jobs">https://github.com/nemanjam/hn-new-jobs</a><p>Demo website: <a href="https://hackernews-new-jobs.arm1.nemanjamitic.com" rel="nofollow">https://hackernews-new-jobs.arm1.nemanjamitic.com</a><p>I used Algolia API as a data source, along with scheduled task that parses new threads few times at the beginning of each month. The extracted data is then stored in SQLite database for fast querying, and the results are cached with Keyv for faster page responses. I will see in the future how much traffic the website receives and if this stack is performant enough. For the website I used Next.js app with default ShadcnUI components and charts. I just wanted a quick functional prototype to test how much public interest is there for an app with functionality like this.<p>If you are interested in more implementation details you can find them in the Readme file on Github.<p>The project is free and open source. Feel free to use, self-host, fork and modify, and contribute. I would love to hear your impressions and suggestions and look forward to discussing features and technical details.
Show HN: Don't let your billion-dollar ideas die
Most great ideas are either forgotten or die in our notes app. So made this simple website in a day.<p>1. Save your ideas<p>2. Set an expiry<p>3. After expiry, the ideas goes public. So if you don't work on them, someone else probably will
Show HN: Don't let your billion-dollar ideas die
Most great ideas are either forgotten or die in our notes app. So made this simple website in a day.<p>1. Save your ideas<p>2. Set an expiry<p>3. After expiry, the ideas goes public. So if you don't work on them, someone else probably will