This site is making use of some basic analytics cookies so I can hopefully learn something from of the metrics. By using the site you are totally fine with that.

I thought I knew how they worked, but it looks I was wrong and made two false assumptions: Thought that typeof of object literals are inferred to have (string | number) index signature Thought that mapped types over union of string literals is a way to declare a limited set of string index signatures That's how it looked to me from the example in Typescript Deep Dive

With experience you would get to have an idea about how knowledgeable the customer was just by talking to them for a few seconds, but you have to be careful not to assume things.

on your own Joomla website.

Copy these 5 resources to a directory named 'magpierss' in the same directory as your PHP script.

I'm still calling this v1.00 as this is what will be included in the first print run.

I wonder if it's worth archiving the repository (while leaving the site running) with a message that we're transitioning the content to MDN (so folks don't get the wrong idea and a bad experience when filing issues).

Some people try to use && and || as a shortcut syntax for if ... then ... else ... fi, perhaps because they think they are being clever.

By using an outside timer, you've invalidated that assumption.

is a popularly held but false belief about the origin or derivation of a specific word

This is a very dangerous practice as each optimization means making assumptions. If you are compressing an image you make an assumption that some payload can be cut out without seriously affecting the quality, if you are adding a cache to your backend you assume that the API will return same results. A correct assumption allows you to spare resources. A false assumption introduces a bug in your app. That’s why optimizations should be done consciously.

To fix our Svelte version you might think we could use beforeUpdate or afterUpdate, but these lifecycle functions are related to the DOM being updated, not to prop updates. We only want to rerun our fetching when the album prop is changed.

People assume any advocacy for things they're not personally stoked about is "shilling".

as well as those of the country your site targets

"Hey, folks — just wanted to let y'all know that one of the 500 locks on one of your 500 doors is broken. Not gonna tell you which one though. Hope that helps!"

Now that we’re making breakthroughs in artificial intelligence, there’s a deeply cemented belief that the human brain works as a deterministic, mathematical process that can be replicated exactly by a Turing machine.

Robots are currently suffering extreme discrimination due to a few false assumptions, mainly that they’re distinctly separate actors from humans. My point of view is that robots and humans often need to behave in the same way, so it’s a fruitless and pointless endeavour to try distinguishing them.

The reasoning is that saying "ES7 Decorators" assumes that Decorators is expected to be in ES7. I mentioned this in my last post regarding compiling node_modules, but being in a particular Stage doesn't guarantee much: a proposal can stall, move backward, or get removed entirely.