One important step I've found helpful is asking if the candidate would like to receive feedback before sharing. This should also curb the risk of litigation.
The biggest problem with GraphQL in this regard is that it is a single endpoint. API gateways often define authorization rules, throttling rates, and caching times differently for each route. Consequently, you may need to write authorization, throttling, and caching logic in a separate layer or perhaps even in your microservices themselves.
That's more convenient than unlocking my phone to get the code when I miss the brief notification. My plan though, is to port my PIN grid proof of concept to the band.
Have you seen pictures of what drone props can do to skin? Even the handheld drones draw blood easily. The $500 phantoms can cause damage requiring stitches... Not sure a baseball is the best analogy.
The drone lacerations may be a flashier image for a photograph, but baseball injuries are nothing to dismiss. Also note that all of the drone injury pictures I have seen are from the drone owner accidentally throttling up while holding the drone, which is an incredibly easily avoidable mistake.
In a cursory glance, this appears to be logic (token, redis, etc) that can be handled by Nginx+Lua. Is there any reason to do it this way vs the other?
Using Lua is certainly easier. The C version will almost always be faster, and yes, performance in this scenario probably wouldn't be an issue between the two. The other reason for writing a module in C though is complete control over the execution and an easier time troubleshooting problems. Adding another language layer can present issues when things explode.
Being an attendee from last year, I can guarantee you that it's people still filing in to find seats well into the presentation. The exit is towards the back left of where the camera is. People going to the right are looking for seats. It's still not an attractive angle.
Funny you should say that, that's my family motto: "Qui stupidi sunt, ut strenuus me".
That he thinks it is ok to cut through residential neighbourhoods because the freeway is backed up is more than stupid, really. It is dangerous and unfair. I was going to say that, given the apologetics around this strategy, that he's being a little tongue-in-cheek. But when he opened with "the really painful part of being stuck in traffic is not, really, the actual amount of time that it takes to get from Point A to Point B" it was pretty clear that we were going to be looking for wisdom and intelligence from other sources.
