Utah’s safety net for the poor is so intertwined with the LDS Church that individual bishops often decide who receives assistance. Some deny help unless a person goes to services or gets baptized.
Soinds like coercion
Utah’s safety net for the poor is so intertwined with the LDS Church that individual bishops often decide who receives assistance. Some deny help unless a person goes to services or gets baptized.
Soinds like coercion
To be fair, I heard a lot of rumours about it not coming to Xbox because Microsoft required parity of features.
So, I can understand your misreading
References https://www.reddit.com/r/BaldursGate3/comments/15u9z0g/comment/jwoh42k/?context=3
I don't want to copy the text here, because credit where credit is due. And some things are marked as spoilers, which idk if all Lemmy clients support.
Essentially 8 levels of monk, 3 in Rogue Thief, Tavern Brawler, and 22 STR getting 8 attacks due to extra bonus attacks and flurry of blows due to feats and gear mods.
And some various WIS as damage gear mods, and some other bonuses.
Address on Nostr is [garbage].
Sounds complicated, but it's pretty easy..
Sure, ok.
I mean, better loading feedback would be better than an arbitrary "interactive within 1 second" blanket rule, leading to this whole "press button to continue" workaround.
That's like a generator needing an earth rod, and the engineer putting an earth rod into a plant pot. Sure, the earth rod is there, and sunk to regulated depth in dirt... but it's a plant pot.
Just make an accurate loading screen with accurate feedback.
I don't care about Manifest V3. I care about ublock origin.
When that stops working, then I'll swap.
Ah, the new Lemmy switcharoo!
"several hours" being the entire expected length of the expedition.
Because previous dives, the sub had lost communication for long periods of time.
This whole thing was a "how not to submarine".
Like, you know how OSHA/HSE/whatever laws are written in blood? Yeh, prime example.
This would be great, because it would "validate" GDPR.
Data protection requests would be more likely to be planned-for and succeed if users didn't have to say/prove they were an EU citizen.
Certainly, as a UK citizen who has these protections, but not specifically GDPR, it can be difficult leverage these rights.
More countries adopting these kind of laws will hopefully resolve into a global standard of "right to be forgotten", as long as it doesn't collapse into an XKCD#927 scenario (https://xkcd.com/927)
The 2 Lemmy devs have funding. About 1500 total from community support, with the rest coming from a sponsorship/incubator type deal. A deal which pays out when targets/goals are achieved.
Which made me laugh at this:
sure, let me stop doing my day job and start planning on this completely unpaid enhancement
Which is entirely what you are asking the Lemmy devs to do.
Thanks for raising awareness of the spam-bot-account issue.
In my view, or at least why I left Reddit (and support the strike), it's not about the API charging.
It started as the price. Then it was also about
Lies about the 3rd party apps.
Lies about 3rd party app developers.
The whole process from January (no API changes planned) to announcing there will be a cost, to 6 weeks later giving a 1 month deadline and stating the ridiculous prices.
Back up by years and years of failed promises from Reddit, as well as whatever bullshittery they seem to concentrate on instead (chat, streaming, NFTs)
Tests.
Target the "business logic".
You can structure your code to facilitate unit or integration testing.
Setup tests for the key functionality. Whenever a bug gets reported, create a test or test case to address that bug, fix the bug, and ensure the test now passes.
Have a staging environment, so the site can be interacted with and tested without touching anything in production.
You can push to this often, and request some help with QA to ensure nothing is broken.
Have a testing environment. Again, a complete duplication of the infrastructure.
Set up end-to-end tests. These automate interactions with the entire application.
Have tests that run against key features. "Setup appropriate state, load form page, fill in form, click button, check that database entries are correct"... "setup appropriate state, check that submission summary shows correct data".
These are quite handy, but a lot slower and fragile than unit and integration tests.
There are automated testing platforms that can capture a "good" state of a website, then use image matching to ensure further runs visually match what it should look like.
These are normally expensive and finiky.
Hopefully you will get to a stage with your testing that your unit and integration tests catch 90% of your potential bugs, and e2e tests will ensure the core functionality is working correctly.
Then, as you do a bunch of work, you can run your tests, see they all pass, and be confident.
Finally, I will say that tooling like frameworks and typescript can catch a lot of these errors quite quickly.
However, these won't catch logic bugs - which is what tests are for.