I’ve always wanted to try this out in practice. It seems like it would be a great way to find gaps in the specification.
There was some research in the early 90’s over multiple implementations as a way to avoid bugs. I still feel like it was dismissed prematurely or could be revisited.
My work would insist on calling the incident response or monitoring room a "war room". And I would quote this every time it was mentioned. It gets old, but I literally can not stop myself from repeating the quote when i hear the phrase "war room".
14 cents per ride is nothing! Maybe 1% of the cost of a ride.
Maybe they could save a bunch by colo or something else. But would 14 cents per ride really matter at all for their competitiveness. I’m not going to notice a 14 cent difference even if I do bother to price compare Uber with Lyft.
This is a VC fueled market. It isn’t really about small margins of this size.
If the company can’t figure out how to add a date to the subject line, they won’t be able to figure this out either.
It’s gmails bug, but I’m amazed they couldn’t figure out hiw to implement the fix. Amazed but not too surprised given how not nimble big companies are.
Many here are commenting that you should pay more and that is true. But how about not wasting the talent you already have?
I’ve had several jobs from startups to big companies and I have never been utilized at anything close to 100% of my potential.
Try getting rid of pointless meetings, distracting open offices, insane IT policies, and needlessly overcomplicated architectures. You may not even need to hire any more enigineers if the ones you have are more productive.
A senior to me dev started working nights. I didn't even know he was doing it but I got in trouble for not being there when he was working. Because I "wasn't available when he needed me".