These two strategies aim to solve the same problem, but in opposite ways.

They may sound alien or complicated if you haven't used them yet —they sure felt that way to me a few years ago— but there is no mystery to them, really.

Also, of these two, there is a clear winner and one we generally want to avoid. Can you guess which is which?

Read more ➞

The Temporal API has made great progress since I wrote my article on it, The Temporal API Is Awesome.

The major milestones have been:

• The TC39 proposal has made a huge leap forward.
• Deno added first-party support for it in its 1.40 release.

What does this mean and why is this important?

Read more ➞

Dates in JS suck. Well, they suck in all languages, really. It's surprisingly hard to get right.

The native Date is super limited. Sure, you can new Date('2015-10-21T01:22:00.000Z') and date.toISOString(), maybe dateA < dateB, but that's pretty much it. Need to add minutes, hours, or whatever to a date, check how many days there are until X date, etc? Good luck with that¹.

So a bunch of libraries were developed to solve this issue. MomentJS was the best way back when. In 2020² the project added a project status page, declaring MomentJS a legacy, deprecated project, and suggesting alternatives. Luxon was one of them, which actually was —and is— excellent.

But wouldn't it be nice to just have a standard solution, provided out-of-the-box by browsers, NodeJS, Deno, Bun and whatever new JS runtime gets released next week?

Enter...

Read more ➞

There's a pretty cool article about the scale of S3: Building and operating a pretty big storage system called S3.

It's pretty long: ~6.5k words, ~36k chars. Here's the tl;dr version of it.

Read more ➞

Here's a little story about objects and closures I really like:

Read more ➞

This term is vague enough that most of us have some intuitive understanding of it but there's no consensus about what it actually means.

The following is my own definition, based on my experience and biases, but I find it useful for communication — particularly with managers³.

Read more ➞

This famous quote, usually attributed to Tony Hoare, was popularized by Donald Knuth's book Structured Programming with go to Statements, published in 1974. That was 49 years ago.

In dog years, that's about 200 human years. In software-industry years, it's more like a millennium. Computers have changed drastically since then.

Does this rule still apply?

Read more ➞

ReactJS isn't a library. ExpressJS isn't a framework.

Read ➞

I recently started a series on Encryption with JavaScript. In my latest entry I mentioned I'd follow up with Modes of Operations.

Before we dive into that last piece of the series, I wanted to have a little fun and showcase encryption of images with the most primitive (and insecure) mode of operation, Electronic CodeBook (ECB for short).

Read more ➞

Welcome back to my series on encryption with javascript. In Encryption with JavaScript — Part 1 we went over some of the different libraries that exist in the JavaScript space and chose NodeJS's Crypto Module for our examples.

Today we'll see what a cipher algorithm is, what different options we have and information on cipher keys (also known as encryption secret).

Read more ➞

A while back, while working at Po.et, I undertook a migration that required implementing encryption into the main API.

Back then I didn't really know much about encryption, so I started by doing some research, and then building a PoC. Eventually I implemented a working encrypt function, which I could use as follows:

Read more ➞

I was recently interviewed by Bitcoin Magazine about how we Argentines are using Bitcoin and other cryptocurrencies as a store of value.

You can read the whole piece here: Economic Uncertainty, Restrictions in Argentina Show Power of Bitcoin.

I first heard this phrase from Eric Elliot in one of our 1:1s at Po.et. It's was coined by Kent Beck, creator of Extreme Programming and one of the seventeen software developers that signed the Agile Manifesto.

It's a very simple rule of thumb that will take you very far in software engineering.

Read more ➞

Naming things is a crucial aspect of software design in general. As such, it's very hard to immediately see its value and very tempting to avoid spending any time or mental energy at all on it.

There are only two hard things in Computer Science: cache invalidation and naming things.⁵

Only people who have had to work on old code bases written hastily by other developers that are no longer around, or in some cases even their own personal projects stalled not so long ago, have felt the pain associated with reading source code and wondering what the hell it does and if it's even doing what it should.

The return of the time and effort invested in naming things as clearly as possible is most easily perceived in the long run. But it's usually when it's missing that it's noticeable the most.

Read more ➞

Hello world! This is me, starting a blog once again.

I'll be sharing opinions and experience on JavaScript, software architecture, Bitcoin, crypto, and other random stuff.

Stay tuned. Or not. I'm fine either way.