ak39

Criticizing the Chinese government's actions for their treatment of the Uighurs will invite state-sponsored "cancel culture" - not just from China but also from the western democratic nations that acquiesce to Chinese whims. This is incredible - look at the life of the professional football player Ozil who was effectively forced to leave Arsenal for his comments on this very subject.

Criticizing China should NOT be censored. (There's another country that also invites this type of cancel culture trolls whenever someone objects the policies of that country. You can guess.)

Yip, I meant all the big companies like Google vs Microsoft vs IBM etc.

COM is still the only binary object-to-object cross language interface on Windows. Late-binding COM is still a good thing.

What is somewhat dead is the idea of building server-side enterprise middle-tier in COM (COM+). That died when the dastardly Pet Store Wars ended and distributed transactions lost their hype.

What are you building?

Forgive me, I pictured your experience and it made me laugh. :-D

Great word

Another note from the underground. The problem is, like Dostoesvky wrote through the mouth of the Undergound Man, the human requires pain and misery in his daily existence in order to have a default want-to-live or want-to-thrive instinct. The lack of misery will banish us to these endless ruminations of self-hate from our lack of desire to live like the "men of action" (Sanjay, in this case) we obssess about. My kids call it "FWP".

It's a tragedy that can be fixed by tragedy. Often the tragedy is self-inflicted. Just to want to live! on our own terms.

It's a mess.

Yes, but drugs should only be administered by suitably trained and educated professionals such as EMT and health care professionals. Not police!

Is your comment based on personal evidence or otherwise?

I agree with this philosophy. I see the writer has used popular memes to convey the problem with humour. I would also add this quote from the movie "Heat":

"Don't let yourself get attached to anything you are not willing to walk out on in 30 seconds flat if you feel the heat around the corner."

Hiring help for things that you can't or won't do but needs to be done. Other people helping you with tasks is the biggest force-multipliers human society has known.

"Fake it till you make it" meme?

Source please.

Please add to this otherwise excellent list:

LATERAL JOINs (PGSQL). In SQL Server & Oracle they are CROSS APPLY & OUTER APPLY.

This will change your SQL habits forever. Lateral joins give you the power of iteration in set-based operations that are mind-numbingly easy to implement and understand.

I'm the same age. But I am also guilty of old habits when attempting new frameworks or languages. For example, I always want to set up the environment with the least amount of "auto loads" of libraries etc. I do not use NPM. I still play around with new JS libraries by direct downloads from the official websites or Github and always use local copies of .js .css etc. I don't even connect to CDNs for fonts! I want to know all dependencies etc. I am paranoid like that. And this can be exhausting.

Half the muscle requirement is used up just to set up the "environment" for new fangled technology/framework even before Hello World can be compiled.

This is a profound comment. Thank you.

Dancing isn't easy for folks who are rhythm-challenged like me.

Try the Jerusamela on for size. Warning: make sure the vase, and precious items in the living room are packed away before you practise.

Some attempts: https://www.youtube.com/watch?v=ePuGjRRin3c

Official video: https://www.youtube.com/watch?v=fCZVL_8D048

Interesting. I see the examples don’t cite “technical analysis” of price action of stocks. Is that also an example of Ludic fallacy?

Love it, thanks!

Can you imagine the maladaptive psychology required to wield a knife to calmly dismember, decapitate and butcher another human being?

Because coding is like the art and science of distillation. Cheers.

Good comment. Fully agreed.

The accounting equation and therefore the double-entry system, once fully appreciated, probably ranks high up there in the pantheons of Humanity's achievements right alongside E=mc2.

The non-"scientist" may scoff at that but A=O+L is as sacronsanct as the laws of conservation of energy.

That COVID wasn't mentioned by reports is itself information. I believe that had Grant tested positive for COVID, the reports would have mentioned that. The fact that it isn't mentioned, makes it unlikely that it is COVID related.

The OP did not say "because a celeb died therefore ...". You said that.

It may be insensitive or bad timing to be mentioning COVID as a speculation for Grant's death right now, but it doesn't rule out the possibility.

How can the system rely on “no response is construed as failed”?!

Bad design right there.

Is this an example of "evolutionary psychology"?

Most systems in production already have key use cases that stand in for unit and system testing. Find those and use them after every new feature or change to the system.

I support an existing reporting system with several hundred tables and thousands of interdependent stored procedures. This system has a fairly often-used "global report" which touches nearly 90% of the tables. We run this user report after all changes to the database with a few swaps in parameters (history vs current etc). If this report and a few others "pass" (results are the same as previous reports), we know that the changes are safe. When the reports show differences, we confirm that the changes were intended. If not, something broke.

If communication friction and overhead is the primary thrust for microservices (where you obviate said overhead by keeping to small teams), how do you address and manage the need for communication between teams?

Obviating communication costs within teams is one thing, but what of the overhead and costs of communication for the whole system? Eg. how do you avoid the cost of deploying a new team that ends up deploying a duplicate microservice?

Good explanation. But I have two questions:

1) So which "team" then takes ownership of the entire katamari ball of sprawling microservices and understands the interconnectnedness and nuances of overlaps and competition between each microservice?

2) If the concept of technical debt at yesterday's monolithic architectures is biting us now, what does the future technical debt of microservices hold?

I know. It perpetuates the racism and derogatory attitudes.