> So something like pgBouncer together with transactional queries
FYI - it's already supported by cloudnativepg [1]
I was playing with this operator recently and I'm truly impressed - it's a piece of art when it comes to postgres automation; alongside with barman [2] it does everything I need and more
I love synology; bought one around 2018, runs nicely until this day; received last DSM 7.3 update so will be supported until 2028 but I will probably keep it running until it dies as I don't expose it to The Evil Internet anyway
does everything and more I need it to (backups, photos, storage, jellyfin, various media servers, torrents etc.)
> And finally you have a brilliant idea of hiring a second $150k/year dev ops admin (...)
in my experience you always need a "Devops team" to operate all that cloud stuff; so to paraphrase - suddenly you're spending $400k on three devops to operate $500k cloud
I think The Promise behind the cloud was you just pay for the service and not worry about it, but in practice you need some team to maintain it
> And it is hard to spot the mistakes because they can be quite subtle
aw yeah; recently I spent half a day pulling my hair debugging some cursor-generated frontend code just to find out the issue was buried in some... obscure experimental CSS properties which broke a default button behavior across all major browsers (not even making this up).
Velocity goes up because you produce _so much code so quickly_, most of which seems to be working; managers are happy, developers are happy, people picking up the slack - not so much.
I obviously use LLMs to some extent during daily work, but going full-on blind mode on autopilot gotta crash the ship at some point.
LLMs are great for self-contained boring tasks; recently I have started to refactor ruby tests with a simple prompt (getting rid of various rspec syntax in favor of more explicit notation at cost of code duplication - so kinda like unminifying things I guess) - works _ridiculously_ good as well
Typesense has been a godsend; amazing piece of tech and on top of that fairly easy to operate even in HA mode; if you can fit your dataset in memory I really recommend giving it a try
I can see the appeal, as the demo looks really smooth; then again, I'm a terrible slow developer, so personally I find saving few ms here and there irrelevant to my daily workflow
I second that - similar experience; and it was like two years ago; seems they are in constant hiring mode without need to hire anyone, I will never that - why waste time?
FYI - it's already supported by cloudnativepg [1]
I was playing with this operator recently and I'm truly impressed - it's a piece of art when it comes to postgres automation; alongside with barman [2] it does everything I need and more
[1] https://cloudnative-pg.io/docs/1.28/connection_pooling [2] https://cloudnative-pg.io/plugin-barman-cloud/
reply