Have you ever heard of emojis: 😊? I guess you did, they’re everywhere and people use them to express feelings, ideas or just as a way to enrich the language. Well that, and also they can also 💩 your software. If you’re reading this, you’re probably aware that mysql utf8 support is not what’s supposed to be (Mysql “utf8” encoding only supports three bytes per character. The real UTF-8 encoding — which everybody uses — needs up to four bytes per character).
Lately, I’ve been thinking about the rate of innovation and the size of a company. It seems to be commonly accepted that enterprises are slow and recently I came across a very good article that explains that from the internal aspects of building software in a big company: https://zwischenzugs.com/2018/10/02/why-are-enterprises-so-slow/ I mostly agree with the author, but I’d like to see it from a different angle: big companies don’t care much about the time to market, but they care about the impact they’ll have in customers.
To predict a digital currency price, can be thought as an optimization problem where you have to find the optimal solution that gives you more benefit. Nowadays this is usually addressed using some kind of Machine Learning algorithm, that can vary from a Neural Network to an Evolutionary algorithm or something in between. It’s important to understand that there’s no correct answer and every day you can find new different ones.
Disclaimer: I’m not an expert in digital currencies neither I’m an expert in Blockchain. My thing is development and software engineering, so don’t expect to find here the recipe to get rich. Is it possible to predict accurately the price of a digital currency? The first idea that comes to my mind is no, but my gut feeling is that in the long-term future they will rise, so buy a stable asset and wait should be a good strategy.
I’m starting again with this task of writing a blog, that I always seem to forget about. I moved to Madrid 3 months ago, with my wife and our 2 dogs, to start working at Amazon and to travel as much as we can. As it happened 2 years ago with my previous “start over with the blog” after I found Hexo, now I found a new tool called Hugo. At first I was not convinced to switch, but this framework very easy to use and to undestand that I don’t have the need to dive into the code and try to see what it’s doing, I can focus on writing.
I recently encountered the following need. It had to pass a resource identifier by url, which is registered in a database (along with other data) and has a descriptive name (which must be unique), associated that is specified by a human. In principle I came up with 2 ways to identify the object: Use an auto-incremental value of the database as a PK and add a restriction so that the name is not repeated, plus an index.
Many are familiar today with the UUIDs, today they are widely used as identifiers due to their non-sequentiality and their low collision probability. The uuids are a sequence of 128 bits (16 bytes). The usual representation of these is with 36 characters: 32 hexadecimal characters plus 4 separators (for example: 7625c7e9-38b1-4622-aa71-1ad439c1bced). The separators are decorative, so the characters that really have information are 32 (7625c7e938b14622aa711ad439c1bced). Since hexadecimal characters can be represented with 4 bits, each character represents 4 bits of the UUID, requiring 32 characters to represent the 128 bits.