Short Walks — Object Locking in C#

While playing with Azure Event Hubs, I decided that I wanted to implement a thread locking mechanism that didn’t queue. That is, I want to try and get a lock on the resource, and if it’s currently in use, just forget it and move on. The default behavior in C# is to wait for the resource. For example, consider my method: static async Task MyProcedure() { Console.WriteLine($“Test1 {DateTime.Now}”); await Task.Delay(5000); Console.WriteLine($“Test2 {DateTime.Now}”); }

I could execute this five times like so: https://goo.gl/kVhSfi #DataIntegration #ML

More H-2B Visas for Seasonal Work Available This Summer

ICYMI: Employers that can demonstrate that their business is at risk of failing without an infusion of foreign seasonal workers will have the chance to petition for help this summer. The Department of Homeland Security (DHS) is authorizing 15,000 additional H-2B visas for use in fiscal year (FY) 2018, which runs through September 30. https://goo.gl/mvJ43W #GlobalHR #HRTech