I agree, Email is a giant PITA. I would never ask anyone to send me patches via Email. However on a positive note, I do sometimes get folks reaching out to me on Signal and sometimes Email. Then we form a bit of a relationship, set things up and go from there. That is actually much nicer.
I'm not sure what else we can do? I'm nNOT moving back to Github, ever.
I agree, Email is a giant PITA. I would never ask anyone to send me patches via Email. However on a positive note, I do sometimes get folks reaching out to me on Signal and sometimes Email. Then we form a bit of a relationship, set things up and go from there. That is actually much nicer.
I'm not sure what else we can do? I'm nNOT moving back to Github, ever.
yarnd that's cropped up that results in a " /> at the end of uploaded/links images. I'm not able to figure this bug out yet š¢
yarnd that's cropped up that results in a " /> at the end of uploaded/links images. I'm not able to figure this bug out yet š¢
2024-07-12T16:52:12-06:00\t(#4nlm4ca) Here has been north of 38C all week. Its pretty ick. I would love a bit of rain to cool down.
2024-07-12T16:52:12-06:00\t(#4nlm4ca) Here has been north of 38C all week. Its pretty ick. I would love a bit of rain to cool down.
I _think_ it's invisible to users of
yarnd because of the way the cache works š¤£
2024-07-12T16:52:12-06:00 (#4nlm4ca) Here has been north of 38C all week. Its pretty ick. I would love a bit of rain to cool down.
2024-07-12T16:52:12-06:00 (#4nlm4ca) Here has been north of 38C all week. Its pretty ick. I would love a bit of rain to cool down.
I _think_ it's invisible to users of
yarnd because of the way the cache works š¤£
2024-07-12T16:52:12-06:00 (#4nlm4ca) Here has been north of 38C all week. Its pretty ick. I would love a bit of rain to cool down.
2024-07-12T16:52:12-06:00 (#4nlm4ca) Here has been north of 38C all week. Its pretty ick. I would love a bit of rain to cool down.
I _think_ it's invisible to users of
yarnd because of the way the cache works š¤£
Unfortunately, it doesn't go into any concrete specifics or any formal ASOS of measuring and managing complexity budget.
Unfortunately, it doesn't go into any concrete specifics or any formal ASOS of measuring and managing complexity budget.
> The new report published Thursday dives into the many types of dark patterns like sneaking, obstruction, nagging, forced action, social proof and others. Sneaking was among the most common dark patterns encountered in the study, referring to the inability to turn off the auto-renewal of subscriptions during the sign-up and purchase process. Eighty-one percent of sites and apps studied used this technique to ensure their subscriptions were renewed automatically. In 70% of cases, the subscription providers didn't provide information on how to cancel a subscription, and 67% failed to provide the date by which a consumer needed to cancel in order to not be charged again
> The new report published Thursday dives into the many types of dark patterns like sneaking, obstruction, nagging, forced action, social proof and others. Sneaking was among the most common dark patterns encountered in the study, referring to the inability to turn off the auto-renewal of subscriptions during the sign-up and purchase process. Eighty-one percent of sites and apps studied used this technique to ensure their subscriptions were renewed automatically. In 70% of cases, the subscription providers didn't provide information on how to cancel a subscription, and 67% failed to provide the date by which a consumer needed to cancel in order to not be charged again
- Complexity is confusing
- Complexity is costly
- Complexity kills
When we think of "complexity" in terms of software and software development, we have a sort-of intuitive about this right? We know when software has become _too_ complex. We know when an organization has grown in complexity, or even a system. So we have a good intuition of the concept already.
My question to y'all is; how can we concretely think about "Complexity Budget" and define it in terms that can be leveraged and used to control the complexity of software dns ystems?
- Complexity is confusing
- Complexity is costly
- Complexity kills
When we think of "complexity" in terms of software and software development, we have a sort-of intuitive about this right? We know when software has become _too_ complex. We know when an organization has grown in complexity, or even a system. So we have a good intuition of the concept already.
My question to y'all is; how can we concretely think about "Complexity Budget" and define it in terms that can be leveraged and used to control the complexity of software dns ystems?