jameshiew

Such as a concert, open mic night, fitness class - maybe on something like VRChat or Meta Horizons Worlds.

I have used VR fairly extensively (on a Quest 2) but rarely to attend these sorts of scheduled events or meetups. I have gone to group meditation sessions in VRChat, which was OK.

Something I've tried recently is changing from the default Java 11 JetBrains runtime to Amazon Corretto 15. Start up is blazingly fast now and overall the IDE feels faster once running as well, though I haven't profiled so that may just be an impression. There is a message when you go to change the runtime warning that you shouldn't do it unless asked to do so by JetBrains support, but that seems overly conservative and this has been (I think) the biggest improvement in performance for my set up so far. Font rendering was much worse initially but after some tweaking of font settings it's more than acceptable.

I'm also trying out using the Z garbage collector and setting the ratio of young to old generation to 1, as suggested here[1], as I often have multiple projects open at once. I'm not sure how much of an impact this is having though as I'm trying this all together, but the heap memory indicator does seem to fill up substantially more when indexing before a garbage collection happens.

[1]: https://www.jetbrains.com/help/idea/tuning-the-ide.html#common-jvm-options

Bit of a long shot, but I saw a paper within the past six months on the topic of the most common "errors" made by software engineers developing and maintaining distributed systems/systems based on a microservices architecture. I'm fairly certain it was published by or affiliated with Microsoft, and the methodology was they asked a large number of developers what they thought were the most common cause of problems in distributed systems. I remember the top "error" so to speak was a lack of API versioning.

Has anyone else seen this paper and would be able to link to it? I've searched far and wide - I think I first saw it one of IEEE Spectrum, IEEE Transactions on Software Engineering, ACM Queue, or possibly even here on HN.

When macOS 10.13 (High Sierra) came out, I did a fresh reinstall of my MBP and used an Ansible playbook to reprovision most of what I had had previously installed. Looking back, I don't think this was necessary - the only real good thing that came out of it was that it forced me to back up some projects on my laptop that I may not have otherwise bothered to, as I knew I was doing a clean wipe. Although a new OS install always feels satisfying, any cruft I removed I didn't really notice in any meaningful way, or quickly reaccumulated.

Are there any advantages to doing a fresh installation of new versions of macOS that would make it worthwhile?