The name of the function, what goes in and what goes out in most cases should be enough to get a good idea on what the function does.

It also helps to make a diagram of how everything ties together. Just boxes and arrows is enough.

When writing your own code, it takes a bit of experience to know when to put something in its own function. It’s very obvious when you’re replicating code. It’s also very common to cut things up when a function gets too big. Look for bits of functionality that you can give a good name.

I always write it as a select, before turning it into a delete or update. I have burned myself too often already.

With Influx 3 the preferred language is gonna be their SQL dialect. Flux is on its way out and I suspect it will get deprecated in the near future. Flux saw very slow adoption and SQL can do everything as well.

The one that blew my mind is that plate tectonics is only a widely accepted theory since the 70s.

They’re nice if they also migrate your db schema. That way you define your schema once and use it both to setup your db and interact with it via code. I do write raw sql for more complex queries, e.g. when there’s recursion.

I like the concept of reducing cognitive load for the stream-aligned teams. This means all efforts go towards enabling them as much as possible in supporting the business. It also makes it relatively easy to judge if a platform team is doing the right things.