29 posts tagged with "yama"

Constantly thinking about work doesn’t focus my brain it scatters it and makes it difficult to focus. So I’ve split my days into three two hour chunks. Scientifically the brain can only work son intensely for a short burst of time. An hour and half seems to be about he max but I given myself a buffer of 15 mins on both sides to get going.

A problem I have faced is a guilt for not studying the shastras on a daily basis. A guilt for not studying that doesn’t lead to any positive outcome other than stress. Sometimes I want to study something else other than shastras. So I am reframing my Work schedule to learn, work and study with a focused intensity.

This means the most important spiritual tasks are my meditations. The true culmination of Bhakti and Karma Yoga. While I do want to study the shastras I will read them in focused intense manner similar to the other tasks that I have in mind. I think this will mean I can focus on finishing a complete text instead of just reading a couple of pages a day. I keep forgetting what I read if I just read a couple of pages a day.

So my work is going to be focused intensely on specific tasks:

• Study intensely a book or topic
• Memorize shastras
• Work on business tasks

The path of yoga that I have been exploring is focused on devotion (bhakti/karma), discipline (raja), and knowledge (jnana). But what I realize is that before anything can be done on the discipline and knowledge path a firm foundation of devotion needs to be established.

This I don't have yet. I have it then I lose it, I get distracted, my ego takes over. I plan for the future! The devotion aspect is quite missing or not deeply rooted and it gets pulled into the whirlwind of life.

The problem I see is that devotion requires always being in the present whereas the ego is always scheming for the future or ruminating on the past. The past is gone and the future is uncertain. But the ego always wants something or another.

I also get caught up on history, economics, politics, and all these external things that are not in my control. These are transient things. They are unreal and fleeting. The only thing certain about them is that they will occur over and over again.

What we are about to face is the Bronze Age Collapse, or a collapse of a civilization. This has happened before and will happen again. So why worry about it? Getting pulled into these things is a distraction.

The only focus should be on devotion and doing the work. Whatever happens, happens.

So I am going to focus on devotion first. The question is how to cultivate devotion.

While I have been practicing meditation and have enjoyed the technical aspects of it, after all that is what the Yoga Sutras are, the problem is that it is not cultivating devotion. I am getting mindful, but without a firm foundation of devotion, my mind is restless and distracted.

It needs to be rooted which I don't have yet.

So while I will continue developing my meditation practice, I am primarily going to focus on devotion. In one way meditation is easier once you do it a while, but devotion is harder because it requires surrendering the ego.

What I realize is that devotion is based on stories. While meditation is a process it is stories that we remember and that we need to connect with. Bhakti is pure duality, Raja is about bridging that duality, and Jnana is about non-duality. So in devotion the first step is to just love Isvara without ego. The way to love Isvara is through stories.

So the goal for devotion is to:

1. Read stories of devotion from various traditions. (Bhagavad Gita, Ramayana, Puranas, etc.)
2. Read the classics from various traditions. (Iliad, Odyssey, etc.)
3. Read stories about saints and devotees from various traditions. (Tulsidas, St. Augustine, etc.)
4. Practice how to cultivate devotion through rituals, prayers, and other practices.

But the focus is stories. To read stories and immerse myself in them.

I am deprecating Deming incorporating those features into this website. The core features should not live separately. Further, I am putting Deepfacts, DBAZero and PolicyCop on hold. I am trying to reduce the number of projects I am working on to focus on the ones I think I can deliver the most value with. With DiscountCloud and Kubespot, I think I have enough to keep me busy for the foreseeable future.

Deming was a good experiment but I think it is better to have everything integrated into one platform. This website can serve as the hub for all my thoughts on business so it is better for that to live here.

So the projects I am going to focus on are:

• DiscountCloud
• Kubespot
• Surya Health
• Yerra Realty

Everything else is on hold or deprecated or merged into this website.

As I mentioned before my role has changed to Organization, Process Management, and People Development. What this actually means in practice is a few very specific things.

• Organization. Constant cleaning and standardization of the organization to ensure that it is optimized for learning and growth.
• Process Management. Constant review of processes to ensure that they are growing linearly.
• People Development. This is the most important part and what I realize is that people development is the core of everything. If I can develop people well then the organization and processes will take care of themselves.

What I am finding is that people development is to not focus on the company but developing the character of the people. The goal is to not extract from people, but to develop them such that they fit a higher purpose. So 80% of my focus will be on people development.

This changes things quite a bit because I have essentially become a teacher. My role is to teach people how to be better versions of themselves. The way to do so and the way I feel like I have become a better version of myself is through the study of shastras and the classics.

So People Development will entail:

1. Practical Training
2. Work Reviews
3. Shastra Study

So if my focus is on people development then what I focus on is how to teach people to be better versions of themselves. This means that I am largely focused on lesson plans and how to structure learning. This means a large part of my work is study.

We are standardizing on Github Actions for all routines. We are doing this by running self-hosted runners and migrating a lot of the tasks that we run on Kubernetes jobs over. While Kubernetes is great, one of the problems I have found is that when the entire team is developers having a common hook into Github makes it a whole lot easier to see what is happening. Since everyone already uses Github, having the actual job processing be in Github is not a bad idea.

Further, since we are a services first company, using Github Actions workflows to manually run tasks basically creates custom workflows that make it really easy to build pipelines.

As much as I like Github Actions one of the main pains is that the cost of it is very high. So running within a self-hosted environment seems like a good way to go. However, there does seem to be a new cost model coming out that may make it more expensive, but we will see what happens.

I have migrated completely to Github Issues for all my task management. This means that all my todos, tasks, and notes are now in Github Issues. This allows me to leverage Github's powerful issue tracking, labeling, and project management capabilities to manage my work more effectively. While I do not by any means think that Github Issues is the best task management system out there, it does connect to the Git repo and Github Actions which makes it a lot easier to automate workflows.

Further, as a services company, having everyone on Github makes it a lot easier to manage tasks and collaborate. Every company is on Github so the collaboration across companies makes it exceedingly easy. While I do think that Github is getting enshitified over time AI and all, it is still a powerful platform. While I do hope that I can move to Forgejo in the future, for now Github is the primary platform for everything.

We now have a basic SOP for sakhas. The idea is to have standardized processes for each sakha that sevakas can follow. This will help in scaling the sakhas as we can onboard new sevakas and have them follow the SOPs to run the sakhas.

The initial set of SOPs are:

• Daily Routines. Daily routines that sevakas should follow to keep the sakha running smoothly.
• Basic Flywheel. The engine that each business has to keep improving and growing.

With this start we can now start to improve the SOPs over time by focusing on the input metrics and hope we can generate the appropriate output metrics.

One of my favorite apps is the Notes app. With 18,883 notes in my Done folder. It is more a todo system than a Notes app per se. However, one of the problems I have with the Notes app is that I just don’t seem to define a full project. They are always half assed and I have to continuously revisit projects. This just makes things feel like they never get done. There is no measurement of the number of projects actually completed. Basically, it is a rolling spec that always changes and is not really defined. Lastly, this all lives within my Notes app so the actual goal is never communicated to the broader team.

If you were to ask me how many company projects I have completed this year and how do I know if they were successful the answer to that question is I don’t know. I am just at a loss for the outcomes because I honestly don’t know the outcomes. The baseline for using the Notes App is I can move fast with the consequence that my team doesn’t really know what to expect next until I tell them.

The main reason that I moved to the Notes app was Notion was slow and became unweildy and to be frank I wanted a simpler system. But the problem with the Notes app is that I am the only one who has access to my notes so others aren’t really able to access them.

I completed a migration of all the websites to Cloudflare Workers from Cloudflare Pages. We were using a combination of Cloudflare Workers and Pages and deployments were starting to have issues. These include the different ways that Pages treats branches versus Workers. Anyways, seems like there are more features on Cloudflare Workers and this will simplify our deployment capabilities.

I have been using Makefiles as long as I can remember. When I was using Ruby I was fond of Rake. I have largely stayed with Python as my language with opsZero. Using Python the ecosystem while large and diverse has the problem of being a pain to get consistency.

With uv that has changed. It is really easy to invoke binaries, have multiple Python versions and in general the speed of running things is just great. With uv a core install I am moving from make to invoke as my process manager.

Why now?

Well uvx invoke works well and I don’t have to worry about random breakages.

uv init --bare
uv add --dev invoke fabric
uv run invoke