There are two ways of writing in general; one with lots of emotion and invoking of feelings, one without those qualities.

There are a couple of places I can always go to to recharge my batteries, like MopGarden, Taudriel and Day9. These places are where I can go, say I had a rough week and immediately have a good community to just lift you up. I am also there in times of being okay and help lift others in their time of need.

There is a new kind of Operating System slash running system rooted in privacy and ownership. You own the data to an extent, you own the access and you own your own piece of the universe that is Urbit.

The new Web 3.0 is based on the idea that everything has to be decentralised. This means that each individual holds the data so that no one is in control which makes the information on the whole and also data in general much more resilient. It is not that a body of people will hold bits of information and you need each to reassemble the original package, that would mean it is more fragile as you need more and more entities to participate. Anyone of them drops out for some reason and you have corrupted your data.

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.

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.