I am working on the little book of algorithms: https://github.com/little-book-of/algorithms A project to implement 1000 algorithms. I have finished around 400 so far and I am now focusing on adding test cases, writing implementations in Python and C, and creating formal proofs in Lean. It has been a fun way to dive deeper into how algorithms work and to see the differences between practical coding and formal reasonin…
That's a cool project! I feel like the presentation of Lomuto's algorithm on p.110 would be improved by moving the i++ after the swap and making the corresponding adjustments to the accesses to i outside the loop. Also mentioning that it's Lomuto's algorithm. These comments are probably too broad in scope to be useful this late in the project, so consider them a note to myself. C as the language for presenting the al…
Ask HN: What are you working on? (October 2025)
511–520 of 1001 posts
Re: Ask HN: What are you working on? (October 2025)
#512I am working on https://www.ironcalc.com , a spreadsheet engine. I have been working on it for the last two years as a side project, but starting March will be my full time job! Kind of excited and scared at the same time
Could you please provide a Docker image?
Re: Ask HN: What are you working on? (October 2025)
#513Re: Ask HN: What are you working on? (October 2025)
#514Re: Ask HN: What are you working on? (October 2025)
#515I am working on the little book of algorithms: https://github.com/little-book-of/algorithms A project to implement 1000 algorithms. I have finished around 400 so far and I am now focusing on adding test cases, writing implementations in Python and C, and creating formal proofs in Lean. It has been a fun way to dive deeper into how algorithms work and to see the differences between practical coding and formal reasonin…
That's a cool project! I feel like the presentation of Lomuto's algorithm on p.110 would be improved by moving the i++ after the swap and making the corresponding adjustments to the accesses to i outside the loop. Also mentioning that it's Lomuto's algorithm. These comments are probably too broad in scope to be useful this late in the project, so consider them a note to myself. C as the language for presenting the al…
Re: Ask HN: What are you working on? (October 2025)
#516I am working on Tiny Finch, a livechat connected with Slack. There is nothing special comparing to other livechats, the goals is to offer an affordable and unlimited livechat for small projects and companies. https://tinyfinch.chat
Our company would love a well designed chat button linked to Slack, combined with a helpdesk that supports email queries and also allows people to raise issues via the web.
That’s it, that’s all we need. Happy to pay.
It’s hard to express how badly intercom is designed and engineered. It’s also very expensive and constantly upsold, despite being rubbish. If no one fixes this it will be my next startup.
Too many companies have gone down the road of “AI support”, without understanding that AI must rest on the foundation of great infrastructure. Intercom are pushing their AI so hard it’s absolutely infuriating.
Re: Ask HN: What are you working on? (October 2025)
#517Re: Ask HN: What are you working on? (October 2025)
#518That’s why I’ve been building 'Fragno', a framework for creating full-stack libraries. It allows library authors to define backend routes and provides reactive primitives for building frontend logic around those routes. All of this integrates seamlessly into the user’s application.
With this approach, providers like Stripe can greatly improve the developer experience and integration speed for their users.
Re: Ask HN: What are you working on? (October 2025)
#519I noticed a gap - our customers are required to upload sensitive documents but often hesitate at the thought of uploading documents in the intercom/crisp interface, citing privacy concerns.
I thought, how difficult would it be to build an app that sends documents to your own Google drive - turns out it’s very easy. In a week, we built an app that renders an iframe in the intercom chat interface and sends documents straight to our google drive folder, bypassing intercom all together.
We’re now investigating uploading to s3 or azure blob storage and generating summaries of documents that are sent to the intercom conversation thread so ops teams can triage quicker.
Let me know what you think!