@t3dotgg It's all fun and games until somebody pushes with --no-verify, merges, and those issues are surfaced in adjacent PRs with people being confused on how they're relevant to their change set
@VicVijayakumar Keep an eye on your monitor height and distance so you aren't craning your neck excessively like you might with a 16:9 50" TV
I've used this tool in the past for comparison to find the ideal size for me https://t.co/brwWFGO0Tu
@petergyang Type 2 sleep studies are super accessible these days, get the diagnosis for peace of mind
If you truly need it then it'll change (and save) your life. It takes some getting used to but there are lots of great resources these days
@GergelyOrosz Any word of a break-up fee ๐ค
Does Figma pull a T-Mobile, walk away with a bag, and accelerate their path being an even stronger competitor?
Clearly there's an opportunity loss where they could've been acquired by another company or accruing legal cost
@vRallev RxJava had a number of these scenarios where a combination of wrapping your exceptions in RuntimeExceptions and/or CompositeException could lead you to traversing causes for your own types... or they slip past you ๐ฑ
@vRallev If you're depending on somebody else to propagate your exceptions there's the non-zero possibility they turn it into something else - which can be especially impactful if you're trying to catch those to perform retries or access fields on them