petey

Thanks, now I want to order McDonald’s yellow coloured filament

I’m tempted to publish an NPM package to do so as a joke, but I fear that it’d get used seriously

Amazing

However it should be noted that the remote development connection is via their servers, which makes it somewhat less useful

Ah ok, the name implies it’s a security guard

I love that you’re thinking about how to secure sensitive parts of JS applications, however I wonder what threat this is guarding against. Can you give an example? Surely if an attacker can modify the source to call the sensitive functions, then they could modify the allow list

Oh wow, this is amazing info. Thanks!

Nice article! I’m a fan of the “don’t optimise early” mantra, which seems particularly relevant here regarding clone

I feel like this is a perfect encapsulation of how an experienced self-aware developer thinks. Experience really beats the hard stances out of you. I find myself saying “it depends” and “a bit of column A, bit of column B” often, like a cheap kids toy

His take strangely acknowledges that defects are caused by programmers, yet doesn’t want to improve the tools we use to help us not make these mistakes. In summary, git gud.

Experience has taught me that I’m awfully good at finding and firing foot guns, and when I use a language that has fewer foot guns along with good linting, I write reliable code because I tend to focus on what I want the code to do, not how to get there.

Declarative functional programming suits me down to the ground. OOP has been friendly to me, mostly, but it also has been the hardest to understand when I come back to it. Experience has given me an almost irrational aversion to side effects, and my simple mind considers class members as side effects