The best Hacker News stories from Show from the past day
Latest posts:
Show HN: ThinkPost – split-panel note taking & brainstorming app for devs
ThinkPost is an Interactive split-panel diagramming, draggable block-based note-taking, and brainstorming tool.<p>I developed ThinkPost as a side project for few months now.
Basic idea is parallel streaming of ideas. It's a desktop web app with a very scaled down mobile version just for support.<p>Whole my career I had been working with startups and specifically early stage ones, and it's a big responsibility to devise a feature on our own, think deeply about it in different streams (logically, security, re-usability, platform APIs etc.) and even present distilled part of it to stakeholders (Often times non technical people). Even now I run backend/infra/mobile/qa/customer support/integrations for a healthcare startup, so stakes are high. There's a lot of self brainstorming in multiple streams and then there's also distillation process. I couldn't really work with single page notepads for that streaming process. We should be able to note down in split-panels, so there's space for parallel ideas.<p>Many note-taking apps today single-paged have high-think-threshold (windows notepad/apple notes have very low-think-threshold), you have to think before you write in them, so not a good option for quick ideas. So built a platform specifically for everyone who can parallel stream ideas in split panels Textually (low-think-threshold), write as they like), Diagrammatically, Code-wise or even Quick Maths. And also move the idea blocks across panels or within! or Open a new tab if you want more!<p>I'm personally a massive user of my app because I plan everything at my current job via this app, run meetings, self-brainstorm features, study requirements, visualize code-ideas, an develop this when I get time as well.
All completely free. Might run ads later.<p><a href="https://thinkpost.io" rel="nofollow">https://thinkpost.io</a> - Try! no login needed.<p>More comprehensive introduction: <a href="https://zameermfm.medium.com/introducing-thinkpost-io-33df61ce4bc7" rel="nofollow">https://zameermfm.medium.com/introducing-thinkpost-io-33df61...</a>
Show HN: ThinkPost – split-panel note taking & brainstorming app for devs
ThinkPost is an Interactive split-panel diagramming, draggable block-based note-taking, and brainstorming tool.<p>I developed ThinkPost as a side project for few months now.
Basic idea is parallel streaming of ideas. It's a desktop web app with a very scaled down mobile version just for support.<p>Whole my career I had been working with startups and specifically early stage ones, and it's a big responsibility to devise a feature on our own, think deeply about it in different streams (logically, security, re-usability, platform APIs etc.) and even present distilled part of it to stakeholders (Often times non technical people). Even now I run backend/infra/mobile/qa/customer support/integrations for a healthcare startup, so stakes are high. There's a lot of self brainstorming in multiple streams and then there's also distillation process. I couldn't really work with single page notepads for that streaming process. We should be able to note down in split-panels, so there's space for parallel ideas.<p>Many note-taking apps today single-paged have high-think-threshold (windows notepad/apple notes have very low-think-threshold), you have to think before you write in them, so not a good option for quick ideas. So built a platform specifically for everyone who can parallel stream ideas in split panels Textually (low-think-threshold), write as they like), Diagrammatically, Code-wise or even Quick Maths. And also move the idea blocks across panels or within! or Open a new tab if you want more!<p>I'm personally a massive user of my app because I plan everything at my current job via this app, run meetings, self-brainstorm features, study requirements, visualize code-ideas, an develop this when I get time as well.
All completely free. Might run ads later.<p><a href="https://thinkpost.io" rel="nofollow">https://thinkpost.io</a> - Try! no login needed.<p>More comprehensive introduction: <a href="https://zameermfm.medium.com/introducing-thinkpost-io-33df61ce4bc7" rel="nofollow">https://zameermfm.medium.com/introducing-thinkpost-io-33df61...</a>
Show HN: CeLLama – Single cell annotation with local LLMs
A simple R package which helps with annotation of single cell experiments such as single cell RNA-seq. With up and down regulated genes per cell cluster, the local LLM guesses the cell type annotation and creates an overall extensive report.
Show HN: CeLLama – Single cell annotation with local LLMs
A simple R package which helps with annotation of single cell experiments such as single cell RNA-seq. With up and down regulated genes per cell cluster, the local LLM guesses the cell type annotation and creates an overall extensive report.
Show HN: CeLLama – Single cell annotation with local LLMs
A simple R package which helps with annotation of single cell experiments such as single cell RNA-seq. With up and down regulated genes per cell cluster, the local LLM guesses the cell type annotation and creates an overall extensive report.
Show HN: I made a tool to receive alerts when answers change
Hi HN,<p>I've created a tool called Alertfor that scours the open web to find the most relevant and up-to-date answers for complex questions. You can set up alerts to receive continuous updates whenever there are changes or new information becomes available for a given question.<p>I used an agent framework (Autogen + Sibyl) to collect and answer questions, and I schedule a Celery job to run the same query continuously every six hours.<p>I would love to hear your feedback, suggestions, or anything else you’d like to say.<p>Note: I'm submitting this for a second time; I'm not sure if this is against HN policy.
Show HN: I made a tool to receive alerts when answers change
Hi HN,<p>I've created a tool called Alertfor that scours the open web to find the most relevant and up-to-date answers for complex questions. You can set up alerts to receive continuous updates whenever there are changes or new information becomes available for a given question.<p>I used an agent framework (Autogen + Sibyl) to collect and answer questions, and I schedule a Celery job to run the same query continuously every six hours.<p>I would love to hear your feedback, suggestions, or anything else you’d like to say.<p>Note: I'm submitting this for a second time; I'm not sure if this is against HN policy.
Show HN: I made a tool to receive alerts when answers change
Hi HN,<p>I've created a tool called Alertfor that scours the open web to find the most relevant and up-to-date answers for complex questions. You can set up alerts to receive continuous updates whenever there are changes or new information becomes available for a given question.<p>I used an agent framework (Autogen + Sibyl) to collect and answer questions, and I schedule a Celery job to run the same query continuously every six hours.<p>I would love to hear your feedback, suggestions, or anything else you’d like to say.<p>Note: I'm submitting this for a second time; I'm not sure if this is against HN policy.
Show HN: A football/soccer pass visualizer made with Three.js
I've been working on a football pass visualiser for the past week.<p>It uses open data from StatsBomb to analyse and visualise passing patterns, allowing users to explore and filter the data by pass distance, team and players.
Show HN: A football/soccer pass visualizer made with Three.js
I've been working on a football pass visualiser for the past week.<p>It uses open data from StatsBomb to analyse and visualise passing patterns, allowing users to explore and filter the data by pass distance, team and players.
Show HN: I built an open-source tool to make on-call suck less
Hey HN,<p>I am building an open source platform to make on-call better and less stressful for engineers. We are building a tool that can silence alerts and help with debugging and root cause analysis. We also want to automate tedious parts of being on-call (running runbooks manually, answering questions on Slack, dealing with Pagerduty).
Here is a quick video of how it works: <a href="https://youtu.be/m_K9Dq1kZDw" rel="nofollow">https://youtu.be/m_K9Dq1kZDw</a><p>I hated being on-call for a couple of reasons:<p>* Alert volume: The number of alerts kept increasing over time. It was hard to maintain existing alerts. This would lead to a lot of noisy and unactionable alerts. I have lost count of the number of times I got woken up by alert that auto-resolved 5 minutes later.<p>* Debugging: Debugging an alert or a customer support ticket would need me to gain context on a service that I might not have worked on before. These companies used many observability tools that would make debugging challenging. There are always a time pressure to resolve issues quickly.<p>There were some more tangential issues that used to take up a lot of on-call time<p>* Support: Answering questions from other teams. A lot of times these questions were repetitive and have been answered before.<p>* Dealing with PagerDuty: These tools are hard to use. e.g. It was hard to schedule an override in PD or do holiday schedules.<p>I am building an on-call tool that is Slack-native since that has become the de-facto tool for on-call engineers.<p>We heard from a lot of engineers that maintaining good alert hygiene is a challenge.<p>To start off, Opslane integrates with Datadog and can classify alerts as actionable or noisy.<p>We analyze your alert history across various signals:<p>1. Alert frequency<p>2. How quickly the alerts have resolved in the past<p>3. Alert priority<p>4. Alert response history<p>Our classification is conservative and it can be tuned as teams get more confidence in the predictions. We want to make sure that you aren't accidentally missing a critical alert.<p>Additionally, we generate a weekly report based on all your alerts to give you a picture of your overall alert hygiene.<p>What’s next?<p>1. Building more integrations (Prometheus, Splunk, Sentry, PagerDuty) to continue making on-call quality of life better<p>2. Help make debugging and root cause analysis easier.<p>3. Runbook automation<p>We’re still pretty early in development and we want to make on-call quality of life better. Any feedback would be much appreciated!
Show HN: I built an open-source tool to make on-call suck less
Hey HN,<p>I am building an open source platform to make on-call better and less stressful for engineers. We are building a tool that can silence alerts and help with debugging and root cause analysis. We also want to automate tedious parts of being on-call (running runbooks manually, answering questions on Slack, dealing with Pagerduty).
Here is a quick video of how it works: <a href="https://youtu.be/m_K9Dq1kZDw" rel="nofollow">https://youtu.be/m_K9Dq1kZDw</a><p>I hated being on-call for a couple of reasons:<p>* Alert volume: The number of alerts kept increasing over time. It was hard to maintain existing alerts. This would lead to a lot of noisy and unactionable alerts. I have lost count of the number of times I got woken up by alert that auto-resolved 5 minutes later.<p>* Debugging: Debugging an alert or a customer support ticket would need me to gain context on a service that I might not have worked on before. These companies used many observability tools that would make debugging challenging. There are always a time pressure to resolve issues quickly.<p>There were some more tangential issues that used to take up a lot of on-call time<p>* Support: Answering questions from other teams. A lot of times these questions were repetitive and have been answered before.<p>* Dealing with PagerDuty: These tools are hard to use. e.g. It was hard to schedule an override in PD or do holiday schedules.<p>I am building an on-call tool that is Slack-native since that has become the de-facto tool for on-call engineers.<p>We heard from a lot of engineers that maintaining good alert hygiene is a challenge.<p>To start off, Opslane integrates with Datadog and can classify alerts as actionable or noisy.<p>We analyze your alert history across various signals:<p>1. Alert frequency<p>2. How quickly the alerts have resolved in the past<p>3. Alert priority<p>4. Alert response history<p>Our classification is conservative and it can be tuned as teams get more confidence in the predictions. We want to make sure that you aren't accidentally missing a critical alert.<p>Additionally, we generate a weekly report based on all your alerts to give you a picture of your overall alert hygiene.<p>What’s next?<p>1. Building more integrations (Prometheus, Splunk, Sentry, PagerDuty) to continue making on-call quality of life better<p>2. Help make debugging and root cause analysis easier.<p>3. Runbook automation<p>We’re still pretty early in development and we want to make on-call quality of life better. Any feedback would be much appreciated!
Show HN: I built an open-source tool to make on-call suck less
Hey HN,<p>I am building an open source platform to make on-call better and less stressful for engineers. We are building a tool that can silence alerts and help with debugging and root cause analysis. We also want to automate tedious parts of being on-call (running runbooks manually, answering questions on Slack, dealing with Pagerduty).
Here is a quick video of how it works: <a href="https://youtu.be/m_K9Dq1kZDw" rel="nofollow">https://youtu.be/m_K9Dq1kZDw</a><p>I hated being on-call for a couple of reasons:<p>* Alert volume: The number of alerts kept increasing over time. It was hard to maintain existing alerts. This would lead to a lot of noisy and unactionable alerts. I have lost count of the number of times I got woken up by alert that auto-resolved 5 minutes later.<p>* Debugging: Debugging an alert or a customer support ticket would need me to gain context on a service that I might not have worked on before. These companies used many observability tools that would make debugging challenging. There are always a time pressure to resolve issues quickly.<p>There were some more tangential issues that used to take up a lot of on-call time<p>* Support: Answering questions from other teams. A lot of times these questions were repetitive and have been answered before.<p>* Dealing with PagerDuty: These tools are hard to use. e.g. It was hard to schedule an override in PD or do holiday schedules.<p>I am building an on-call tool that is Slack-native since that has become the de-facto tool for on-call engineers.<p>We heard from a lot of engineers that maintaining good alert hygiene is a challenge.<p>To start off, Opslane integrates with Datadog and can classify alerts as actionable or noisy.<p>We analyze your alert history across various signals:<p>1. Alert frequency<p>2. How quickly the alerts have resolved in the past<p>3. Alert priority<p>4. Alert response history<p>Our classification is conservative and it can be tuned as teams get more confidence in the predictions. We want to make sure that you aren't accidentally missing a critical alert.<p>Additionally, we generate a weekly report based on all your alerts to give you a picture of your overall alert hygiene.<p>What’s next?<p>1. Building more integrations (Prometheus, Splunk, Sentry, PagerDuty) to continue making on-call quality of life better<p>2. Help make debugging and root cause analysis easier.<p>3. Runbook automation<p>We’re still pretty early in development and we want to make on-call quality of life better. Any feedback would be much appreciated!
Show HN: Ray Tracing in One Weekend v4.0.0
Since this is a major new release (three and a half years in development), I think this should be ok for Show HN.<p>This release has lots of new material, fixes, and updates across the three books in this series. All three books are online and free, with accompanying code available from GitHub. Enjoy!
Show HN: Word Slicer
Hi. I created a small word game and would love someone to give it a try and let me know what you think. Thanks!
Show HN: Word Slicer
Hi. I created a small word game and would love someone to give it a try and let me know what you think. Thanks!
Show HN: Preprocessor I've been working 4 years now
Hey there,<p>I'm here today to share with you a software I've been working on for 4 years now. I'm not full time dedicated to it, as I need to make a living.
My inspiration to develop it came when I started using Sass for real in production. I really appreciated the hierarchy of nesting rules instead of the way CSS vanilla used to do.
The obvious nesting rules was easy to read and understand just by looking at. That was something I personally admirated very much.
I wondered why there was no HTML preprocessors as revolutionary as there is for CSS and JavaScript.
All popular preprocessors for HTML have one thing in common. All replace the angle brackets by something else (usually identation) and then add some functionalities on top of it.
If the symbols for markups are a problem to the experience of developing a visual structure, just replacing it for something else doesn't fix the problem. You are just changing the character of marcation for another.<p>With that in mind, I started Pretty Markup. Not just replacing the clutter of angle brackets by something else, but removing it completely. Very much inspired by Sass. No special characters needed, except by the quotes. The project still in its early stage, but its already useable.
I reached a point where it has a stable base to work. Now, I'm plannig the layer of features that will make it usefull and revolutionary as Sass and TypeScript. Its important to note that I didn't started directly in Pretty Markup. I had a previous package called htmlpp-com-github-mopires. Yes, terrible name, but it was a start. Later a decided to make it more professional and with a friendly name.<p>You can give it a shot by having NodeJS and installing it with:<p>npm install pretty-markup<p>I created a syntax hightlighter for VS Code to attract more devs to it. You can use it by searching "pretty markup" on the extensions tab. Now, it's the first one. The next step will be a package to create a basic starter project. Something like the good old create-react-app.<p>Any feedback, suggestion or even a contribution about anything is very welcome.<p>Thank you very much for your attention,<p>Matheus<p>PS: The package available in runkit is very old(and I don't know how to update it there), I do not recommend you to test there.
Show HN: Preprocessor I've been working 4 years now
Hey there,<p>I'm here today to share with you a software I've been working on for 4 years now. I'm not full time dedicated to it, as I need to make a living.
My inspiration to develop it came when I started using Sass for real in production. I really appreciated the hierarchy of nesting rules instead of the way CSS vanilla used to do.
The obvious nesting rules was easy to read and understand just by looking at. That was something I personally admirated very much.
I wondered why there was no HTML preprocessors as revolutionary as there is for CSS and JavaScript.
All popular preprocessors for HTML have one thing in common. All replace the angle brackets by something else (usually identation) and then add some functionalities on top of it.
If the symbols for markups are a problem to the experience of developing a visual structure, just replacing it for something else doesn't fix the problem. You are just changing the character of marcation for another.<p>With that in mind, I started Pretty Markup. Not just replacing the clutter of angle brackets by something else, but removing it completely. Very much inspired by Sass. No special characters needed, except by the quotes. The project still in its early stage, but its already useable.
I reached a point where it has a stable base to work. Now, I'm plannig the layer of features that will make it usefull and revolutionary as Sass and TypeScript. Its important to note that I didn't started directly in Pretty Markup. I had a previous package called htmlpp-com-github-mopires. Yes, terrible name, but it was a start. Later a decided to make it more professional and with a friendly name.<p>You can give it a shot by having NodeJS and installing it with:<p>npm install pretty-markup<p>I created a syntax hightlighter for VS Code to attract more devs to it. You can use it by searching "pretty markup" on the extensions tab. Now, it's the first one. The next step will be a package to create a basic starter project. Something like the good old create-react-app.<p>Any feedback, suggestion or even a contribution about anything is very welcome.<p>Thank you very much for your attention,<p>Matheus<p>PS: The package available in runkit is very old(and I don't know how to update it there), I do not recommend you to test there.
Show HN: Semantic Grep – A Word2Vec-powered search tool
Much improved new version. Search for words similar to the query. For example, "death" will find "death", "dying", "dead", "killing"... Incredibly useful for exploring large text datasets where exact matches are too restrictive.
Show HN: Semantic Grep – A Word2Vec-powered search tool
Much improved new version. Search for words similar to the query. For example, "death" will find "death", "dying", "dead", "killing"... Incredibly useful for exploring large text datasets where exact matches are too restrictive.