I ate nothing but steaks for a few days (with a bit of butter) and was surprised to find that I did not get tired after a meal, nor hungry again for much longer.
This has been game changing (low carb, not steaks only) for those drowsy afternoons at work. More importantly, I go carb-free 24 hours before I drive any long distance. It makes it so much easier to drive safely for a long distance.
Why altering meaning by selectively cutting away words? Quote makes perfect sense to me and what I know about nutrition and digestion (not an expert/pro but way above average human)
over the years I have read arguments from both sides. It is not healthy to sleep after food! It is healthy to sleep after food.
I just tried it myself.
And it did help a lot to sleep after food. Limiting in take of sugar/carbs does help. However, personally going on diet like this does NOT suite me. I rather eat the food I want to eat and rest a bit, than watch what I need to eat.
We chose Rails + Sidekiq for building PlanetScale's REST API + background workers. Project started 3 years ago. We are still very happy with the decision and wouldn't change it.
> Why?
To build fast. Our team knew Ruby well. Many of us worked at GitHub and trusted we could solve the problems ahead of us with it.
I feel like there's an in-between we're not talking about, that would look a bit less like a shareware site from the early 00s, used more than 30% of my screen, and would work on my phone, but isn't the modern mess of megabytes of JS bundles for a static landing page. It could load in 35-50ms, too, I wouldn't mind.
That's nice, but I value text that renders at a legible size more than I value leaving the majority of my screen empty. This layout isn't effectively using negative space, it's just wasting the entire screen. At least on mobile.
You're free to call that "negative space", it's still 70% of my screen that's just blinding white, and 30% that's a tiny, non-responsive column layout. You call it perfect, I call it annoyingly empty and bad usability on mobile.
If you are looking for Pegasus mail on a mobile device, I think you might be a wee bit outside of the target market. And btw, Pegasus is a shareware site from the 1990s.
Legibility and usability. Like many old sites this one uses small fonts, small elements, and has tiny targets. Especially when working on a large display. I make liberal use of Firefox's zoom feature to compensate, but better defaults don't hurt.
And yes it works on a phone as you can easily zoom in, but inclusion of responsive design, e.g. moving the sidebar to a footer, and use larger fonts would significantly improve legibility and usability. This is not incompatible with a simple and fast-loading site.
I guess we have very different definitions of "works perfectly". Sure, the page displays as intended, if that's what you mean. Tiny 3 pixel high links are neither accessible nor very usable.
While I did use it maybe 25 years ago, I wanted to see some screenshots to get reminded of what it looks like. No screenshots. Maybe the manual? No pdf to download.
The site leaves a lot to be desired, but it loads fast.
Exactly. Wish more sites and other bits of software followed this website's philosophy. Once you have that which is sufficient, anything more is waste.
I think that's an unfair strawman, because they are saying that UI does matter, only that their opinion of "modern UIs" is that they are often worse, not better.
Someone mentioned an "in between" option and that's where I personally tend to land as well. A lot of modern websites are so media and JavaScript heavy that they take a long time to load, have many layout shifts and feel sluggish when you use and navigate them. That is not good user experience.
On the flip side, I think there is a lot to say for "responsiveness", font choices and media that helps the user experience. I am a minimalist, but legibility of copy and making intelligent layout decisions relative to the viewport size are "modern" techniques that can greatly aid UX when understood and applied properly.
The author is Kelly Starrett, a legend in the physical therapy/movement world. I've read a lot of his work.
I don't think his message is that stretching "does nothing". It's more that, research has shown that combining stretching with strength (using the range of motion) is the way to create lasting change.
I may be misremembering but I thought his wife and him (since they are co-authors) explicitly said something along the lines of don't even bother wasting time stretching. It's near or at the beginning of the first chapter. "Do it if it makes you feel good but it's a waste of time" or something. Please correct me if I'm misremembering or outright incorrect. I don't have the book nearby to check.
Historically his perspective was that it wasn't necessary. If you're getting full range of motion exercise, you don't need to stretch, because the exercise itself is doing what needs to be done.
> If you're getting full range of motion exercise, you don't need to stretch, because the exercise itself is doing what needs to be done.
I dropped powerlifting when gyms closed in 2020. I picked it back up recently. With a garage gym it's now so easy to lift without so much dang ceremony, just warm up through the exercises themselves. Sessions all under an hour, PRed all three lifts at my meet, and never got a red light on squats when I used to get one for depth on one side all the time. Stretching is all time fake in my book.
Right. Personally I've observed my squat form and ROM are much better if I stretch my hamstrings first. So I stretch first to get more benefit from the exercise.
I bet it changes based on a few factors including age, prior mobility, etc. I do a few things at my current age:
I wear Vibram "toe-shoes" so that my heel isn't lifted off the ground when I squat or do other movements and unless I'm lifting very heavy I go below parallel
I warm up by doing either some prescribed warm-ups or by getting on the air bike/rowing for a few minutes + other warm-up activities
I do the exact exercise movement I'm going to be doing if it's a movement like a snatch, clean and jerk, deadlift, squat, etc. to warm-up
I don't do any stretching before or after. It's absolutely fascinating that so many different things work for so many people.
Definitely not normal. It’s hard to know why you’re seeing slow queries without more information.
The most common causes are either: missing indexes or network latency between the app and database (are they in the same region?).
We don’t have cold starts, but it is possible for queries to get faster once data is moved into memory. 3-4s is very slow though, I suspect it’s doing a full table scan and an index will solve it.
Even with my kindest interpretation, I cannot find how this comment adds anything to the conversation. It’s also incorrect. Hotwire was released after GitHub’s internal UI framework (which is quite impressive!) was created.
Attributing some UI bugs with their choice of framework is a massive oversimplification of the problem.
I don't think it's a problem, it's just how it intentionally works. The problem is they don't render the account switcher when you arrive to a new product that your current account hasn't signed up to.
but basing accounts on urls not cookies is really dumb, especially when people send mydocs.google.com/u/1 which refers to my team but i'm logged in to that team on mydocs.google.com/u/2 or the 0 based one which doesnt even get a namespace
