If people want to die on a hill that is demonstrably causing problems for all of their coworkers then let em.
Edit; also, as can be seen here in responses, and elsewhere on the web when discussing this, the fans say it's no problem, but many less religious users feel it's a massive design flaw (perfectly logical at the time, not so logical now) that sometimes will stop users from using it, which is a shame
By running a Linux VM on your local machine you get a consistent environment that you can ssh to, remove the latency issues but you remove all the complexity of syncing that they’ve created.
That’s a setup that’s worked well for me for 15 years but maybe I’m missing some other benefit?
Remote: Preferred
Willing to relocate: No
Technologies: Python, Django, Terraform, Docker, all things AWS, Jenkins, Github Actions, Postgres/RDS/Aurora
Resume: upon request
Email: glik22@gmail.com
Hi! I bring over a decade of experience as a software engineer. I spent a solid portion of that time as a backend engineer building out APIs in Django. In my current position, I have built upon those skills and acquired plenty of new ones as a platform engineer. A significant part of my role has involved evolving and optimizing our infrastructure (AWS) with a focus on cost savings and maintainability with improved Terraform practices. In addition, I have built and improved multiple internal libraries and services to make our engineers' lives easier. In my next role, I'm looking to leverage these skills and help advance a team to the next level.
You probably don’t need (or want) an index on every column.
You shouldn’t index a UUIDv4 column if you can ever help it (and by extension, you shouldn’t use them as a PK).
Finally, you almost certainly need to REINDEX what you have periodically. I’ve seen indices shrink by 400%, giving back GB of RAM. You want a quick win for speed with zero cost? Gain back enough RAM to have your entire working set cached.
https://grugbrain.dev/#grug-on-testing