Back in the day of mainframes and the like, there was a need for a technician that did maintenance on the computers in question. Just like you have need for mechanics that do the maintenance and the fixing of your automobiles. This grew out into a full time position called system administrator or sysadmin. So then came the containerised era and the whole DevOps movement.

I recently watched Escape from Pretoria. This is a great movie. It contained so many elements that I could link to software development funnily enough. The premise of the movie simply said is the escape of two real characters and one fictional one. Potential spoilers ahead.

Let us be real, these days in order to make the frontend application running in the browser there are a lot of things to take into consideration and juggle around. Like state management, CSS itself is so complex these days with layouts, effects and animations. Then there is just the normal logic of clicking a button does action Y. Coupled with actually consuming the APIs for the data in question and binding that to elements in the UI. This just touches on what the application should do, in addition to all this there are packing tools, linters, test frameworks and overall structure of the codebase to manage and learn as well. Suffice it to say the ecosystem for current modern frontend development work is quite something alright.

First thing developers learn when to speed up applications is to use some form of caching. The art of storing information for later lookup and use. You can liken it to looking up a phone number for a pizza place, and then writing that phone number down on a piece of paper.

I was watching Hi Score Girl season 2 recently so I am in the fighting games mood. Someone pressed start on player 2 controller and now there is a new contender in the API building space. Well the pressing of start was already done a long time ago, but it seems more and more people are just now starting to watch the cabinet that is hosting this battle.

So we all know planes are not a good idea. Before you know it you have Samuel L. Jackson shouting in your ear.

So maybe we need a few new ideas.

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 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.

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.

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