eigilsagafos

Thanks for the perspective Matthias. I find myself constantly torn between the two camps. Paul Graham and YC representing one side and DHH and Basecamp the other. I see beauty on both sides. And I think there is a lot fertile middle ground…

I’m working to finish my JS state library: Valdres. Built to be faster than Jotai/Recoil, batteries included, and more advanced features like scopes, indexes and more. It’s “human built, AI finished”. 1.0 is in beta. https://valdres.dev

Can’t every branch be considered an experiment? I have a ton of experimental branches that I don’t label «experimental». One of the reasons you use git…

Kind of funny that the government needs AI to navigate all the red tape and paperwork it has created

Update: I created a placeholder repo on Github with some more information on what is currently supported. Please engage if this could help anyone https://github.com/eigilsagafos/fauna-postgres/issues/1

Would be open source for sure

We were Fauna users for several years and invested a lot of time working with it and around it. The time travel capability was one of the stand out features for us in addition to FQL which opened some interesting capabilities. That being said for various reasons we had to transition away from it and did so by creating a FQL compatible solution on top of Postgres. It is implemented in JavaScript/TypeScript and runs in Postgres through the plv8 extension. Is this something that would be interesting to other current users?

I don’t think easy unsubscribe falls under «sharp edges and one-way doors». But high friction unsubscribe probably goes hand in hand with sharp edges and one-way doors at those lead you to want to unsubscribe…therefore they make it hard.

A love that HN doesn’t have pics and that they strive for short meaningful titles, so I’ll stay here :)

I’m working on a state library for JS/React very similar to Recoil and Jotai. Have been using both but struggled with different performance issues that I was able to overcome seeing 10x to 100x improvements in some cases. I’m working on documentation at the moment and plan to open source soon

As developers/engineers we love to solve problems. Too many times though we mislabel "friction" as "problem" and then start trying to solve the friction based on our current skill set or viewpoint. So frontend devs feel friction working backend and vice versa leading to all sorts of efforts like this that mostly fail. Good luck though :)

You can try our experimental BPM/Flow tool at shiftx.com/ai. Importing the AI generated flows will be possible in a few days

I wonder if the tide will ever turn? That it would become a competitive advantage to build enterprises with values other than maximizing the returns to their shareholders.

Definitely still work

Co-Founder of ShiftX here. We are building a flowchart/BPM/knowledge-graph hybrid. We also use a grid and support splits/loops/joins in a way where we try to optimize for readability. Feel free to try: https://shiftx.com. Feedback welcome!

Fully Postgres compatible in my experience. As long as you don’t require extensions that AWS doesn’t support. But I believe AWS has the widest array of extensions for Postgres of any cloud provider.

Very excited to see this in general availability and with Postgres support

We are building a tool that can help you tackle some of this pain through process visualization. Built to be easy to use and create alignment across teams on how different aspects of your business works. Check us out! https://shiftx.com

Me and my two co-founders are asking ourselves this all the time, and in retrospect every strategic change could have happened sooner if we had learnt faster and kept “doing things that don’t scale” as PG famously wrote years ago. The funny thing is that we think we are doing great in that regard only to realize again and again that we have to iterate faster and stop the urge to prematurely optimize for scale.

Our latest learning that we retrospectively should have seen earlier is to get rid of our fear of becoming consultants. We come from a consultancy background and have seen to many startups around us wanting to build products, but taking on consultancy assignments leaving them no time to build their product. We have been so determined not to fall into that trap, realizing now that we have missed out on some great opportunities when selling to enterprises.

Agree with you there. I have seen so many times that people leave meetings without understanding what was concluded and what to do next. I try to be the person that ask questions if I don't understand what is agreed upon or if I "feel" that others don't understand. In the startup I'm in right now we try to build a culture where asking questions and taking a moment to think and talk if someone "feels" something is off is appreciated.

Early stage B2B startup ShiftX here. We are successfully doing this with FaunaDB. In Fauna databases are as lightweight as tables and are nested in a hierarchy. This enables us to do management in the “root” database and keep all customer data separated in child databases. So when a user signs in to our app he gets a session that is tied to the specific tenant database. This model would also allow us to do completely separate database deployments for customers with special requirements.

This is a great question and the same pain the led us to start ShiftX. It’s a process based knowledge sharing tool where we have focused heavily on simplicity so that both creating and consuming content is as frictionless as possible. We are just starting to grow the company but are getting great feedback so far from our customers in the Nordics. Let me know if you would like to learn more! https://shiftx.com