As somebody in the US who had to do 2 months of PT before I could even get an MRI of an injury, this is both surprising, and yet also not, to hear.
I broadly agree though; about a decade ago I had the standard office worker low back pain problems which cleared right up after doing squats multiple times a week. Of course a decade later I managed to blow out a disc at the gym, which I still work through as I write this today, but well worth the risk in the long run. Even with that long experience of strength training, the PT was worth it even if it didn’t fix my problem entirely. It added some variety and pointed out some details I had overlooked to improve my shoulder health.
I’ve been out of the Java scene for a really long time, but will be coming back to it soon. I’m curious - these performance issues described here, are they inherit to how Java itself? Is it baggage from Spring/Boot? Are there ways to get more bang for the buck with some careful choices in a system like this?
The closest I’ve done to Java recently is C#, which I think may have similar challenges, but overall didn’t seem quite as bad if you avoided lots of framework extras. It also wasn’t something I was digging into deeply though, so perhaps I’m mistaken.
This is actually a really cool feature. I've never had any interest in an Apple Watch, but this is something I'd be genuinely interested in. Too bad it requires an iPhone largely.
I think there are other less time intensive methods outside of a sleep study, but it is nice to simplify it down to just wearing this and finding out!
This context helps me understand more what you're getting at quite a bit. I dunno if I could manage the same approach but I at least appreciate how you're thinking about it. Thanks!
> Another issue is that in your mid 30's almost everyone has settled down and started having kids and only really prefer socializing with other people who have settled down and have kids, leaving you in an awkward place.
To add a bit of a different perspective to this, as a parent myself, most of our friend groups are actually child-less and have no plans to have children. I've found it works quite well. They are cool with or genuinely excited to hang out with the kids, and this affords them a way without the full obligation of parenthood. The friend relationship evolves when you have kids, but with the right kinds of people and interest, it evolves in a great way I feel.
Of course I'm just part of one family, which is a small sample size. So perhaps you're onto the real trend. But I do feel it important to say that there's room in this world for folks with or without kids. It doesn't have to be mutually exclusive!
Not too interested into diving into the debate itself, but one minor point I wanted to add to the article where they count the commits to squash and then do `git rebase -i HEAD~n` is that you can replace this strategy with using the branch you're targeting. So if you're working on a feature branch to merge into `main` you can update the local main branch first, then punch in `git rebase -i main` and it'll handle finding all the commits for you.
I'm sure there's even more clever ways to do this, as it always seems like there's more when it comes to git. This is just the most intuitive way I've seen so far, and so it sticks in my mind.
There is offering from the creators of Peertube I believe: https://sepiasearch.org/. I think instances have to be added manually into the index, and tbh I don't use it much and so I'm not sure of the quality. But it sort of covers what you're asking for, at least kinda.
Sorry I'm unaware of what you're saying? Are you saying that pilots are being selected without meeting training requirements and licensing? That doesn't sound right and I must be missing your point.
I broadly agree though; about a decade ago I had the standard office worker low back pain problems which cleared right up after doing squats multiple times a week. Of course a decade later I managed to blow out a disc at the gym, which I still work through as I write this today, but well worth the risk in the long run. Even with that long experience of strength training, the PT was worth it even if it didn’t fix my problem entirely. It added some variety and pointed out some details I had overlooked to improve my shoulder health.