annnnd

Thanks!

> should include optimization of interactions with the load balancer, e.g. where to terminate https, etc.

I'm curious - is there a case where you want to terminate HTTPS on end device instead of (only) on load balancer?

A year is actually not that much for porting such a huge legacy system to a new platform. I imagine most of the work was making the interfaces from/to other platforms.

I think parent was answering the usage of XML in this use case, which is not appropriate. XML has many strengths (as you have outlined), but it has also been (mis/ab)used so many times that it gained bad reputation. What my GGP suggests is an example of such. There is nothing to gain from XML here that any proper DB (with schema) wouldn't offer, or in this case, protobuf.

Kafka logs however are solving a different problem. The mental model is different - they do not record state, but the whole history of transactions, which makes it trivial to change the schema if/when need arises. Saying that the schema should be thought in advance and shouldn't change is not realistic IMHO.

I agree with you, but that is probably something that belongs to a plugin.

Which is the same as with anything else really. You need to practice to be good at something.

Ok, allow me to me rephrase GP: will this make it possible (in the long run) to train tensor flow models on AMD acceleration cards in a supported, easy-to-use and performant way, comparable to what NVidia is offering?

The key word is "eventually". CV is making huge progress lately, but it is nowhere near human level yet. My guess would be that the first generation of self-driving cars will use Lidar because it means shorter time-to-market. Later manufacturers will be able to supplement Lidar more and more with cameras + CV. And maybe microphones, thermal cameras,...?

Sure - but I am guessing a few errors here and there would have much less impact than a single programming mistake. Not that I think this is the right way, but I do understand where they come from.

Retention! Always focus on retention. If people keep using your product then you have product market fit. If they keep leaving - you have an uphill marketing battle.

I find it much easier to estimate the time it will take if I take myself out of the picture. When estimating, I always try to think "how much time would it take for my colleagues to plan, execute, test, etc... something"? It is almost impossible to judge your own speed, but with experience you learn how to estimate speed of others quite accurately.

Of course, I also let product managers know that any change will affect the deadline, and almost never in a good way. I do this every time they have another "really simple idea".

> Or that the only dev that willing to work with it are contractors that want money.

Greedy b*stards! </sarcasm>

Of course Go players probably saw it coming. Also, Google knew that he needed to leave good impression, not just beat the best human player.