![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://ttrpg.network/pictrs/image/3f8ac09e-5b9a-4afd-b819-e92970b5174f.jpeg)
This adds stability to the formation
This adds stability to the formation
When you are allowed into the vicinity of this kind of equipment, you should be able to identify matching shapes without circles in the first place…
Disney characters routinely survive falling off of cliffs
Go and tell that to Simba.
And properly discard of the tick so it cannot come back. Suggested methods are submersing it in strong alcohol, pulverizing it between hard surfaces or simply lighting the fucker on fire. The guide I’ve read spoke especially against stepping on them because the ground is uneven and your shoe soft enough to give them a chance to survive. Oh and flushing them down the toilet also gives them a good survival probability.
I prefer the fire approach, fuck those little bastards and diseases they carry. No one survives getting their ass heated to over a thousand degrees Celsius.
Masks don’t only protect from airborne viruses…
Oh, that makes warnings errors and does not mean “ignore errors”. I’m not too familiar with compiler flags. You could do some mental gymnastics to argue that the unused variable causes the compiler to exit and thus the code is not functioning and thus the unused variable is not a warning but an error :^)
I for my part prefer it that way. Makes sure the code stays clean and nobody can just silence the warnings and be done with it. Because why would you accept useless variables that clutter the code in production builds? Imagine coming back after some time and try to understand the code again. At least you have the guarantee the variable is used somehow and not just “hmm, what does this do? … ah, it’s unused”
Unused variable is an error which fails to compile.
And half of them are “curated list of X”
Cursing is the first step of learning a language :D
TIL Xanathar is an in-universe character and not the nickname of a real life DnD book author.
absolute galaxy brain moment
The stalebot is most times useless. The only scenario where I can see use of it is a maintainer waiting for the reporter to add information. But closing issues because no maintainer checked on them? That’s garbage and discourages bug reports.
I finally made a full backup of my system. I guess be happy about that.
Using the self checkout for larger shopping is ok in my book. But what sucks is using the SCO and buying an age restricted item (e.g. beer). The checkout locks down and summons an employee to verify the age and unlock the station again. If you buy age restricted items, go to the normal checkout where your greying hair is accepted as age verification!
The thing you are thinking about is called TOTP or timed one time password.