Thank you for breaking it down like this. As someone without an engineering background, your explanation (along with some Googling for terms and definitions) really helped me grasp what happened.
You got me wondering:
> the whole bridge failed because the impact didn't exceed the impact strength of the bridge's material
When I first read this, it initially threw me off. The cargo ship's impact not exceeding the strength of the bridge sounds like a positive thing, but upon closer reading of your comment, it sounds as if it was the catalyst to the entire bridge collapsing.
So, how do engineers balance these properties of impact strength and tensile strength, especially considering large ships channel through these bridges near their pylons frequently? How much engineering goes into the possibility of large structures hitting their pylons?
> Haven't used MSW, but don't people use it for mocking APIs? Isn't that apples and oranges?
At first, I was confused by what OP meant, too, but I think the point is that if you can mock your data easily, then getting your app into the desired state is straightforward enough that Storybook becomes unnecessary. At least, that's how I interpreted it.
The article linked by the commenter above addressed your concern. They mention the toggle should have an _immediate_ state change. I really liked the iOS airplane mode example the article used:
> When turning airplane mode on for iOS, Apple provides immediate results by changing the cellular bars in the upper left-hand corner to an airplane icon.
To summarize, it sounds like the toggles you've experienced haven't led to an immediate state change, which likely identifies them as better candidates for a checkbox like you mentioned.
Specifically for reviewing a pull request in GitHub, wouldn't the "Hide whitespace" setting reduce some of this noise? I could be mistaken, though, but that's how I interpreted that setting.
> Douglas Downing's Trigonometry Made Easy is also a really great book for non-maths people.
> but this book really helped connect trig in an intuitive way.
To me, understanding math in an intuitive way is actually how "maths people" think about math. The numbers and formulas are just a means to an end to get there.
The advice in this blog post is specific to college, and the author of this post is in their last year; they certainly have the qualifications to give advice catered to incoming college students.
For what it's worth, I've been out of college for a bit, and I've had very similar sentiments towards college as the author, but they came to me much later than they did for the author.
I might also resonate more with the article because I was one of those people who fell into the trap of following my peers instead of prioritizing what I was actually interested in.
> The really impressive thing is... if you follow a user profile link to a comment and vote, the vote doesn't count.
I've been a Reddit user for a while, but I never knew this. I tried doing a quick search, but it dates back to 2015 when it seems they were actually disabled all together from the profile page [0].
> The other thing that drove me nuts is lack of care for low-res (aka full HD) displays, where rounding and thin borders leads to visible artifacts in common controls. A designer who uses high-end mac devices will never see these things. UI/UC Design isn’t meant for museums, it needs to be built in dialog with the real world application.
I can't quite picture what you're describing, but I'm curious. Do you have any references to this somewhere?
> The standard of human interaction will either be meeting IRL or signing communications biometrically.
From a convenience standpoint, it seems like we've gotten so technologically advanced that we are starting to move backwards. Is there a name for this type of phenomenon?
I just had to do this in React, and you're correct in that it makes you write logic around the lifecycles in ways that feels like I'm abusing their lifecycle methods. It's a lot of the reason Framer Motion and React Transition Group exist.
However, seeing the way Svelte does it sounds like a dream. I wish that could've been all I reasoned about last week.
These are precisely the type of "ahas" I hope to experience, too, when I begin studying computer science. I've been taking introductory college math courses at my community college to fulfill some prerequisites, and a way for me to stay disciplined in my studies is knowing that concepts like the ones you mentioned are coming. Thank you for sharing!
> For historical reasons we now call hand computers phones
Recently, I've been wondering why the name "phone" has stuck around for a device that has evolved with many more features than that of a telephone. I'm not going to pretend I know a lot about the history of these technologies, but I just find it fascinating that we've kept this identification to something that really provides so many core utilities. I'm curious to know more about the historical implications you alluded to.
Alternatively (and maybe quite a stretch), could I argue that our smartphones are just providing telecommunications to other services, namely, the APIs that they interact with to serve us things like GPS functionality, audio, etc., hence the name "phone"?
On this note, contributing to open source was the best "experience" I've ever gotten as it related to my day-to-day job of maintaining a large, but still growing, project.
I'm not the author, but I thought these were nice illustrations showcasing the various pitches used in the sport of baseball. If I wanted to understand a bit more intricacies involved in the game, I would find these helpful.
I'm curious: what do you consider best practices for font-size and line-height, as well as margins between paragraphs? I've recently revamped my website and used an online type scale tool [0] to get my typography, but margins don't seem to be as plug and chug.
You got me wondering:
> the whole bridge failed because the impact didn't exceed the impact strength of the bridge's material
When I first read this, it initially threw me off. The cargo ship's impact not exceeding the strength of the bridge sounds like a positive thing, but upon closer reading of your comment, it sounds as if it was the catalyst to the entire bridge collapsing.
So, how do engineers balance these properties of impact strength and tensile strength, especially considering large ships channel through these bridges near their pylons frequently? How much engineering goes into the possibility of large structures hitting their pylons?