Actually I do think that's possibly what is happening here. As you say the Russians aren't amateurs, but at the same time they've massively overstepped their mark this time and have galvanised action against them that…
> I do my wife's code for her dev job and it honestly works out to like 2 hours a week for me. >She spends maybe 10 hours in meetings Watch out, if she attends all those productivity sapping meetings, and turns in good…
>my guess is it would be more comfortable to remain there than to lock down alone in your apartment; Actually sounds like a good premise for a movie :)
I remember seeing one called 'Arson Fire' which basically conveyed the same thing.
You're right, an atomic inc/dec would also do just fine. I stand corrected.
shared_ptr<> is most useful for multithreaded applications where a pointer can be safely shared amongst many threads, where the last one to go out of scope will call delete on the object. To do this safely the…
Actually I do think that's possibly what is happening here. As you say the Russians aren't amateurs, but at the same time they've massively overstepped their mark this time and have galvanised action against them that…
> I do my wife's code for her dev job and it honestly works out to like 2 hours a week for me. >She spends maybe 10 hours in meetings Watch out, if she attends all those productivity sapping meetings, and turns in good…
>my guess is it would be more comfortable to remain there than to lock down alone in your apartment; Actually sounds like a good premise for a movie :)
I remember seeing one called 'Arson Fire' which basically conveyed the same thing.
You're right, an atomic inc/dec would also do just fine. I stand corrected.
shared_ptr<> is most useful for multithreaded applications where a pointer can be safely shared amongst many threads, where the last one to go out of scope will call delete on the object. To do this safely the…