Another nugget of incredible wisdom from Microsoft.

The world would be a better place if we all followed this principle:

I've spent many hours troubleshooting an Electron app I'm developing. I have a JQuery function that sends a message to main.js. Simple stuff, or so I thought.

But every time I tested this, main.js was being called twice instead of once. I've rewritten my code dozens of times trying to find and fix the extra call to main.js, but the result was always the same.

I was using the built-in Chromium development tools, setting a breakpoint inside the JQuery call before the call to main.js, and stepping through line-by-line. No matter what I did, the call to main.js was made *before* I even reached the code that was supposed to make that call. When I continued stepping through, the call was repeated when the debugger reached the line making the call.

Turns out, the bug wasn't with my code at all. It was something to do with the development tools debugger. As soon as I stopped debugging, everything worked perfectly.

So much time wasted!

Browsers put a tab to sleep in the background if not used in a while.

The tab reloads when reactivated, which causes me to lose my place in the timeline.

To prevent this, go to chrome://discards (or edge://discards or brave://discards etc.) and click "toggle" in the Auto Discardable column for a specific tab.

The only downside is that I have to do this every time I open #Mastodon...it doesn't prevent future tabs from sleeping.

I've been playing an NFT game called Castles since about January, and yesterday they released a major dungeon battle expansion.

It's not the easiest or cheapest game to get started in, but it is a good game with a strong future and great community on Discord.

There is a "free to play" mode, but it does cost a little wax, so they should call it "cheap to play."

Game link with basic gameplay:
https://castlesnft.io/flowchart

Read the whitepaper:
https://bckteam1.gitbook.io/metasource-and-castles/castles-the-nft-game/castles-nft-intro