![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
Really true. I hope “new UI” stays optional until I retire or become a potato farmer. I haven’t worked long enough at Microsoft to deserve geese.
Really true. I hope “new UI” stays optional until I retire or become a potato farmer. I haven’t worked long enough at Microsoft to deserve geese.
The thing you are thinking about is called TOTP or timed one time password.
The XDG default location would be ~/.config/autostart/
. It contains .desktop
files for programs to start automatically.
This adds stability to the formation
What if I know it will compile for several minutes so I leave it alone to go office chair jousting? It would be fair to lock up the UI in this case.
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.
You wouldn’t enjoy regular sand either. It’s coarse and rough and gets everywhere.
You both are wrong! I wrote my own distro with opinionated modifications and it is superior to both of your distros!
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.
It even passes over 100% of tests!
Edit: I can’t read floats.
And half of them are “curated list of X”
So the [url]()
syntax is the problem. I would say that’s illegal markdown.
Review is done before code gets into main, but that’s inefficient for most of the non-mission critical projects out there. A better approach is to optimistically merge most changes as soon as not-rocket-science allows it, and then later review the code in situ, in the main branch.
Assuming you have a project with continuous delivery, that is an absolute foot gun. Optimistically merge the change and then realize in situ that you forgot the WHERE
part of your SQL command (or analog statement of the query builder)? No fucking thanks.
Yep, it’s a repost of this one.
One could even think this OP is an alt account.
Not an answer, but you don’t need an extension to defeat right-click blocking scripts: shift-right-click usually does the trick.