Teams

It is known that “Power comes with Responsibility.” But what does it mean? To whom is one being responsible? And to whom is that “responsibility” accountable? Without knowing this, it flips into “Responsibility comes with power.” Basically, no power, no responsibility. And anyone taking responsibility is either a fool, has power, or is seeking power. The issue is they neither understand “responsibility” nor “power.” Power is the ability to save time. As a result of power, there is a remainder, which we receive as time. We can use that time to generate more power. Some define it as destructive equipment or access to media, etc. But these are byproducts of having power, not the power itself! This is the first mistake. There could still be power without conventional means. ...

One way to ensure things do not go off course is to secure an architecture. So, we will enforce some invariants on the system. We will use the term “invariant” to refer to the set of rules we want to enforce on the system. The idea is that if we can prove the system satisfies these invariants, we can be certain it will behave in a specific way. We should establish this invariant now, not later. The reason is that if we set it later, we don’t know when! So, it will be never when it can be later than any time! We will have to change the code to satisfy the invariant, and the later we set it, the harder it is to satisfy. So, not a second later—right now! ...

Someone who does a thing has time, and someone who has time does a thing. And the one who takes some extra is powerful. If having more time always comes with more power, there must be an exception where having more time secures extinction. This happens gradually, then suddenly, as the host securing the succession will fight for power—full power. Fighting for more time, even though this nightmare comes along. ...

Have you heard the one saying that “You are like those save in non-Bitcoin. You see them as enemy and they see you as enemy and your fight is about getting power and when you overcome they are going to repeat the same and this is a pointless never ending war, and let’s stop all wars and accept the current situation. We are all the same!” OK! Assuming Bitcoin forgets Bitcoin, does the other side also forget Bitcoin? ...

GitOps establishes itself as the core of a functional and declarative infrastructure model, where other tools and platforms become modular, interchangeable components. At its essence, GitOps uses a Git repository as the single source of truth, with infrastructure and application states defined in code. This means any change to the repository triggers automatic updates to deployments, allowing for a streamlined, automated flow without the need for a specific orchestration platform. ...

I clone a git repo, make a modification, commit, push, and create a pull request. The pull request is reviewed, merged, and the change is built, tested, and deployed to an integration environment before going to production. This process can be applied to any software project with an integration environment. Without it, we only know the code works on the developer’s machine and passes CI tests perhaps unless this level is all expected. ...

Here are 12 principles for a digital team which is essentially self organizing. A self organizing team has no depencency to a single member while practically there could be spontaneous authority to the extent needed otherwise. Value Every Component and the System Equally: Ensure integrated and harmonious progress by treating each part of the project as essential to the whole. Refactor Continuously for Reuse: Enhance software through ongoing refinement, building with the future in mind. ...