Recent submissions

Comment · 3 years ago
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.

Comment · 4 years ago
Comment · 4 years ago
The intro video (describing your product) is quite nice - would you be able to share how/where you got it made?
Comment · 4 years ago
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.
Comment · 4 years ago
Comment · 5 years ago
Got it, I'll keep an eye out for these issues. Thank you.
Comment · 5 years ago
Can you explain why you think so? I'm curious cos I was experimenting with this recently
Comment · 5 years ago
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.
Comment · 5 years ago
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.

Comment · 6 years ago
this sounds interesting - would you be able to add few more examples of where this could come in useful?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton