deeroh

If you have to write Objective-C for some unfortunate reason - http://fuckingblocksyntax.com/

If you have to write Objective-C for some unfortunate reason and your IT infrastructure doesn't like fun - http://goshdarnblocksyntax.com/

oof. Given how desensitized we've become with the constant inundation of garbage he spews, I forgot how bad this quote was.

Cool! I think GM had (has?) something similar, which is great.

I'm personally holding off until I can get a V2H charger, but if I didn't have charging at work as an option, I'd jump on this.

oh boy... yeah WoW was around 3 hours a day x 5 days a week for about 4 years. Some days were more, some days were less, and I took a few breaks here and there. That comes out to around 100 days.

I'd guess that most people with public social media accounts would be susceptible to something like this. As long as there are videos available with the person speaking, which are plentiful by way of instagram reels / tiktoks, the rest of what the commenter described above sounds totally feasible.

I'm sure individual interviewers have their own styles, but yeah I'm with you here. Few things are more frustrating for me during an interview than wasting 30 minutes going in circles on something because the candidate isn't being honest with me.

Our role (low level software) is going to be full of things they haven't seen before. I would rather have a candidate who can quickly identify that they don't understand something, and likewise quickly try to fill that gap so they can move on to the next thing, than have someone try to bluff their way through.

I understand that there's a level of "fake it til you make it" during interviews, but the goal of the interviewer is to get as much signal on you as a candidate as possible. Admitting you don't know something may not feel good, but then it gives the interviewer the opportunity to test you on different things that could really highlight your skills. For example, we ask questions on multithreading during our panel. If you don't know how a semaphore works, and you tell me that upfront, that gives me the opportunity to explain the concept to you and see what your process is like working through new information.

Totally agree, but I feel like the problem was the booking system, not the taxi.

I was traveling recently, and Uber had partnered with a local taxi company to handle ride requests. It was awesome. You get the convenience and speed of calling an Uber, but the vehicles and drivers are all regulated and paid by the taxi company. No questionable gig economy work, no wondering if the driver is getting paid fairly, no concerns over shady drivers, no ill-kept vehicles.