u/ChefMikeDFW

My adult son was ridding his bike home from his job when he was hit while crossing the intersection of Miller and Smartt. Lady in a white SUV, possibly a Ford, was on Smartt at the stop and my son was on Miller. She attempted to beat him out but hit him instead. She gets out, says something to the effect of "you're OK," and leaves the scene. The collision knocked off the front license plate from the vehicle but she collected it and left.

Meanwhile, he has road rash, wrist and knee pain, and some other cuts and bruises. And needless to say, the bike is jacked up.

I'm asking if anyone may have witnessed this, possibly have dashcam or Ring video, to please reach out to me or Rowlett PD ​to help them with the investigation. ​Thanks.

Edit - forgot to mention this happened around 3:30 - 4:00 PM.

Working on a background service that resides in a common assembly that runs long running database jobs, sometimes in batches. I've set up a queue that will manage a ConcurrentDictionary for each app with a Channel object for each job start request. It's not an easy bit of code to maintain nor troubleshoot since it resides in that stand alone assembly for other apps to consume. I do hope to turn it into an API at some point but it does work nicer with SignalR this way. This work is an upgrade of the background service from the use of a SemaphoreSlim to better avoid deadlocks on the database side if two jobs from the same app fire off at the same time.

Boss got wind of what I'm trying to do and has asked why are we not using a database table to better manage the queue, just have the background service look if anyone is running (within the same app) every 30 seconds or so in a basic loop (do/while?) and if the job instance is next up, run.

Am I over thinking this? His way will work and would probably be easier to maintain since you just need to truncate the table to clear out any job that may have gotten stuck. Or is there a valid way to explain that the .NET approach is, in fact, best?