I'm 6 months in and it has definitely ended my life as it was and nothing is the same. I'm pretty lucky that my wife gives me almost 16 hours of free time daily, from which 8 I work and 8 is for sleep. If I want to work out or do something else I need to steal it from the sleep time.
It's pretty early though so I might be looking back in a few years and think that it was not that bad actually :)
I've been following this before it was made public and I'm a big Zig fan so I would definitely switch to this, but I've tried and failed many times. Currently it just keeps crashing multiple times (on three different machines) each day on my mac and the quick terminal doesn't support full screen mode (it still shows the menu bar). I could live with the menu bar showing, but because of the constant crashing I'll wait for a bit and check back in a few months.
One of the white Macbooks used 50 screws to fasten the keyboard. Once I spilled some juice on it and had to replace it.
Took forever, but at least back then it was not too expensive or difficult.
Part of the definition of vibe coding is not looking at the code. If you read code you are not "vibing" anymore, you are just using AI tools to write code.
Very cool! I thought maybe I'll take a crack at building a better iOS application for these things, but then I remembered that for the Lightning connector you needed to get the permission of the manufacturer if you wanted to interface with a device (tried that once with a Lightning Yubikey and luckily they didn't have any objections).
Is this not an issue anymore with USBC iPhones?
I would switch over to Zed for all my non-JVM needs if only it would have a debugger support. Currently it's filling a role of a text editor pretty well though.
Make sense. I guess it could also be a flag for the audit module where you can toggle if SELECT permission for auditing includes the SELECT clauses that need RowShareLock as well or not.
What does a write in this context mean? I still need to execute the actual update clause to change the relevant data.
EDIT: Since you control object auditing by granting/revoking permissions to the relevant relations I don't think it's possible to have another category there since Postgres itself doesn't differentiate between UPDATE and SELECT FOR UPDATE on permission level
pgAudit is pretty cool, but it's a bit of a hassle for us currently because it keeps logging SELECT FOR UPDATE's even though SELECT is not allowed for the auditor, so if you implement stuff like simple queues with continuous polling it fills up the audit log with junk pretty fast.
I opened a PR though so hopefully it gets fixed at some point.
I built and API for an internet radio station archive. Initially I tried to build an app but instead I realised I can run a scheduled Github Action that runs every hour, scrapes the archive, builds a Json file and deploys it to Github Pages for free: https://bd.maido.io/api.json