StealthyCoder

The vision I have for the future of the personal computer would be based on the utopian vision of the previous post and some cool design choices.

So decentralised relies on old world tech. What if we reuse old world tech in a new way to essentially make a new network using low-tech methods souped-up with new technology.

Since the outbreak people way smarter than I am have been thinking about an app that can be used to track whether or not you have come into contact with an infected patient. This post is built upon two already proposed solutions; PEPP-PT and DP-3T.

Anyone who grew up watching the Pokémon anime in the 90s will think are we that old already and secondly about how Ditto plays a role in there. Ditto is a very cool Pokémon who could assume the form of any of the other Pokémon including moves.

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 previous post was on GraphQL. Within GraphQL there exists Relay which is a specific way to deal with GraphQL schemas.

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.

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.

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.

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.