StealthyCoder

There seems to exist a force that creates, shapes, imagines and executes ideas. This creative force or force of creativity can seem to be very innocent, frolicking and playfully suggesting magnificent new heights to take your thoughts soaring out over the mediocrity that through osmosis fills your everyday existence.

So everything can be classified as an Ops of some kind it seems. The Ops part is just a shorthand for Operations and whatever comes before, so is the prefix, will act as an adjective and transform it into that specific type of Operations. Like DevOps is for doing Developer Operations in a sense. It is mainly focused on being a developer but making it so that the automation of deploying and such will be possible. There are a bunch of normal ones like SecOps, InfoOps, BizDevOps and ITOps are all shortened contractions on both sides. They deal with Security, Information, Business Development and general IT department respectively.

I don't mean the security practice of using a hashing function to rehash content. I want to talk about the other meaning of the word. When some message gets repeated over and over again over time using slightly different wording to deliver it each retelling.

I had a massive uphill battle with Hyperledger Fabric and its chaincode concept. I had to dive into the source code in order to understand the inner workings and come up with a creative solution.

This will be a quick post about why you should not make your own identifiers if you can and also if you need to have an identifier that is easy to communicate with/about for clients base it on something that is still very much unique.

I am not talking about the cost of a coffee bar complete with barista, two old arcade machines, some bean bags, a table-tennistable, maybe one desk with a MacBook Pro on it to do some work as you attract the new edgy hispster software engineers that only write the latest trending obscure esoteric languages.

We all know the saying it is that you know what to do with it. Well it seems in development world the size is not the bigger the better but everything has to be as tiny as possible; from silicon chips to frameworks. Also they have no idea how to use it and what to do with it.

To add to previous post where I talk about using Unix timestamps for all things related to when I want to give the following addendum.

This post is in response to many claims of other posts stating that storing a UTC date is not enough in all situations. The most recent one that triggered me being this one. They all claim that you lose information about when something happened. I will refer to Unix timestamps when saying timestamps from now on.

So I read this article which is a response to this article recently. The reaction article is what triggered me to write this post.