HN user
I'm at kav.adithya@gmail.com
Hey everyone,
We're building a way to use caching across more types of APIs which might have previously been considered non-cacheable.
This blog is a recap on how we stumbled on this solution.
Would love to hear your thoughts.
(Offtopic) Hey axilmar - I found your comment on a different thread[0] really interesting, and would love to chat with you about it. Couldn't find your contact details. Would you be open to emailing me? My email is on my profile. PS: Not a hiring / sales attempt.
The intro video (describing your product) is quite nice - would you be able to share how/where you got it made?
At my previous company, we implemented basic audit trails using postgres triggers that recorded the before & after state of a row on upsert / delete. The triggers had to be set individually for each of the tables (same trigger function worked for all), and an added convenience view to see the diff of the changes helped. This worked pretty well us, since we didn't need details of the actor / IP address etc.
off topic: I've found tide-mode[0] to be pretty good to use with typescript on Emacs
Got it, I'll keep an eye out for these issues. Thank you.
Can you explain why you think so? I'm curious cos I was experimenting with this recently
Shameless plug: my project Revamp (https://revamphq.com) attempts to solve the same problem as this. Still in very early stages though - would love to talk if you find it interesting.
One of my projects is aimed at solving this problem: https://revamphq.com
Using Revamp, you can continue building on top of your existing stack while also allowing non-developers to make changes and deploy them immediately. Currently in beta.
this sounds interesting - would you be able to add few more examples of where this could come in useful?
I'm happy to help with this.
I have been the first engineer (& 1st employee) at a fin-tech start-up based out of Bangalore for 4 years now, and am currently the head of product & engineering (~50 engineers). The product is globally available, and is primarily sold in the US.
This sounds interesting. I've always had the problem of sorting through and finding my old documents. Would love to try it out. Can you tell me what the accuracy of your categorization is? Also, are you targeting any specific market to start with?
This was a project I built over the last weekend for fun. Appreciate your feedback, thank you :)
I built this over a weekend for fun. I'm trying to figure out if such a use-case exists for anyone. Appreciate your feedback :)