JCDenton2052

This is not a politically correct thing to say but there is a class of neurodiverse software developers who display these characteristics and I suspect the author belongs to this group.

Frankly, reminds me of Michael O'Church

You have to be able to pick your battles. Sometimes people are in the wrong teams. Sometimes they are just assholes who think they are always right. Too often the "right thing" is subjective.

One of the more insightful articles I have read lately.

If you were willing to speak truth to power like that, you would not be in her team in the first place.

A rather painful reading experience. The author needs to learn how to edit their thoughts and use punctuation/grammar properly.

Nope, nothing got cut. My post stands as I wrote it. It is not ad-hominem and not what-aboutery. It is very much a reasonable question to ask what they use their much-touted AI on and how this relates to the well documented privacy concerns around Google.

Of particular note:

"Google’s CEO Sundar Pichai (who believes AI is “more profound than electricity or fire”) has emphasized that Google is an “AI-first” company, with the company seeking to implement machine learning in nearly everything do"

Nearly everything they do with your data.

The best idea is to not use their services. Switch from Windows to Linux, de-google and if you must use Android keep the data on your phone to a minimum.

The churn rate is an effective question. In places with revolving door cultures interviewers get rather uncomfortable when asked such a question.

Questions about tests. I have found consistently that when an interviewer does not know what the test coverage of their codebase is, more likely than not they don't care about such trivialities.

No matter how respectable the company might look on the outside, the codebase is an incorrigible mess built by cowboys and they will expect you to maintain it.

The article turns rather farcical towards the end... Erich Von Daeniken...

Can you tell me a bit a more about the long-term project where you applied full ES? What kind of domain/business context informs this decision?

I am aware of the costs of the approach, but would like to know the real world problems it solved for you.

Did you go with full event-sourcing? That is, not persisting domain objects at all, just reconstructing their state from the event store?