bmohlenhoff

Yes, I started out by using genrule before going down the custom rule path. I was able to properly trigger bazel to generate the interface bindings but then lost the thread when trying to properly configure the output files to act as proper dependencies to other code (ie. generate C++ headers and libraries that could then be properly listed as dependencies by client code.)

I think part of the issue was that the generated code from the 3rd party tool did not align with the Bazel expectations about code layout (ie. paths relative to WORKSPACE). Likely solvable but not in the amount of time I had available to dedicate to the effort.

I tried using Bazel a while back but immediately ran into a few issues.

The existing codebase I was working with did not lay out its dependencies and files in the manner expected by Bazel so dealing with dependency/include hell was frustrating.

Then there was a large portion of the project that depended on generated code for its interfaces (ie. similar to protobuf but slightly different) and trying to dive into the Bazel rules and toolchain with no other Bazel experience was not fun. I attempted to build off of the protobuf implementation but kept finding additional layers to the onion that didn't exactly translate to the non protobuf tooling. The project documentation seemed out of date in this area (ie. major differences in the rules engine between 1.0 and subsequent versions) and I couldn't find many examples to look at other than overly simplified toy examples.

All in all a frustrating experience. I could not even get far enough along to compile the interfaces for the project.

Everything can be a conspiracy if one tries hard enough.

Bingo; This "appeal to the court of public opinion" strikes me as a last resort due to a lack of negotiation leverage.

Don't forget that generally e2e tests take longer to run and typically require more test assets.

For example, if e2e tests involve simulations running in real time, then by increasing the number of distinct e2e tests you also increase the requirement on test assets and/or overall CI duration.

Glad to hear others used the same house rule. It's definitely cheating.

Er, what? It is an IBA official cocktail.

Should be easy to game though if they offer "bargains to induce new users" as per the article.

> Business travelers are basically not going to voluntarily take a later flight at all.

This. As a business traveler, I don't know how I would justify this to my finance department and/or management. It would take too much effort to justify the change in travel plans for a shitty voucher that I'd probably never be able to redeem.

5400 = 90 min * 60 seconds

The test is a list of 23 true/false questions, so you can think of each question as a bit.

You've prearranged a list of 5400 unique 23-bit vectors, so he determines the bit vector with the most correct answers (ie. smallest Hamming distance) and leaves at whatever time offset corresponds to that bit pattern.

It's not a perfect scheme since you only have 5400 possible bit vectors, and 2^23 > 5400.

std::bitset is also a good choice if the number of desired bits is known at compile time

I've personally never felt that Uber was a particularly innovative business. The ability to temporarily commandeer a vehicle/driver has been a thing since vehicles were invented. The only interesting thing Uber ever did was the replacement of inefficient centralized dispatch of resources with their tech stack that directly connects consumers with suppliers.

It does not surprise me in the slightest that it doesn't translate well to other industries. If it did, I would expect to see a greater variety of preexisting businesses utilizing centralized dispatch in a manner similar to how the taxi/black car industry operated pre-Uber. Given that these are few and far between, I can only assume that either nobody thought of doing this before (unlikely) or that it's simply a losing business proposition.

Just because something has always worked one way doesn't mean it always will continue to work that way.

If a business is having trouble staffing during certain time periods then it's a pretty clear indicator that they might need to offer more to entice people to work those hours. It seems like a pretty clear example of the free market in action.

...presumably it doesn't allow root logins via SSH