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.

So as you can tell from the title, there is no question mark. This means I know the trick in order to be as successful as Google is now. I got this idea when I was explaining something to a friend of mine who is not technical at all. The idea I was explaining is one I already dealt with earlier. This is a combined post of those thoughts I already formed.

What to do in the face of inevitability? Well I find the best approach is always to just accept things and go with the flow as much as you can allow without deviating too much from your identity. Maybe incorporate it into your identity if you can.

We live in troubled times. It is evident by riots and a general dystopian Zeitgeist that seems to be the current force underpinning everyone's current actions both online and offline. One of these actions is to rename terminology because of a supposed or real association with black periods of our Western history.

So you want to improve the DevOps of your company and want to help standardize everything in your organisation in order to become NoOps, what stands in your way? A war. A war with management. A brutal, long winded, casualty heavy war. There are no easy roads to victory here.

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.

So being a team lead is not the same as actually leading. Being designated the role of team lead does not make you automatically lead the team. You have to be responsible for decisions, know what your teammates are doing, what the codebase is doing, what the customer wants, what tech is out there and what is being used currently. Have a grasp on team morale and making sure it is kept high. Guard your teammates from outside attacks from project managers and/or clients.

So previous post was on GraphQL. Within GraphQL there exists Relay which is a specific way to deal with GraphQL schemas.

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.