Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature (content): improve presentation of values #94

Merged
merged 2 commits into from
Nov 12, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 25 additions & 21 deletions content/public/finances/content.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Finances
disclaimer: "I'm not a financial planner or advisor and don't play one on the Internet. This content is for informational and entertainment purposes only and does not constitute advice. Please consult with your financial advisors and financial institutions."
created: 20210216
updated: 20210528
updated: 20211112
---

# Finances
Expand All @@ -13,21 +13,28 @@ Talking about money has always felt foreign to me. It's one of those things that

Historically, I haven't been good at earning money; however, I've always been decent enough at knowing what to do with it when I have it. I worked at a credit union for six years and was trained on multiple topics there. I worked in the call center and was introduced to all sorts of individual strategies. As a coach I often recommend reducing friction to decision making. I have found establishing values, principles, practices, and tools early helps tremendously in automating decision making. These values, principles, practices, and tools don't need to be limited to the topic area; there's room for overlap.

The following sections begin with my personal values, principles, practices, and tools with additional elements that I may not incorporate into my personal set but still think are viable. If you think any are missing, please let me know.
The following sections begin with my personal values, principles, practices, and tools.

## Values

1. Autonomy: When I do the [Motivators exercise](/design-your-life/motivators) on myself, the ability to "choose my own adventure" ranks second; every time.
2. Index funds over managed funds; index or mutual funds over individual stocks and bonds.
3. My values and principles over social norms and mores.
4. Intellectual legacy over financial legacy over genetic legacy.
5. Businesses over governments, state governments over federal governments.
6. Cooperative business structures over privately held over publicly traded.
7. The most constrained over the most funded.
8. United States over International: 70 to 30 percent plus or minus 30.
9. Corporations over governments.
9. Equities (ownership) over bonds (lending): 70 to 30 percent plus or minus 5.
10. Local governments over federal governments: 70 to 30 percent plus or minus 30.
2. My values and principles over social norms and mores.
3. Intellectual legacy over
- financial legacy over
- genetic legacy.
4. The most constrained over the most funded.
5. United States over International.
6. Index funds over managed funds.
7. Index funds over individual stocks and bonds.
8. Small, local businesses over
- large, miltinational businesses over
- local governments over
- state governments over
- federal governments.
9. Cooperative business structures over
- privately held over
- publicly traded.
10. Equities (ownership) over bonds (lending).

## Principles

Expand All @@ -43,15 +50,12 @@ The following sections begin with my personal values, principles, practices, and

1. Maximize revenue, minimize spending.
2. Combined expense ratio less than 1%.
3. Dividend promotion.
4. Maximize the number of people directly and indirectly supporting your progress.
5. Always think in terms of meeting in the middle.
6. Pay yourself first.
7. Promote dividends earned in vehicles returning less than 7% per year to vehicles that historically return higher.
8. Decisions should consider everything else before trying to generate higher than average rates of return. (See principle 7.)
9. [Building Wealth Paycheck to Paycheck](/finances/building-wealth-paycheck-to-paycheck).

A note on number 7, I have a savings account at a credit union that earns roughly 6% on the first $500 when you meet certain criteria and 0.15% for each dollar above the first $500. I would like all the dividends to be promoted to index funds. Further, I plan on using my bond funds as simple interest savings accounts where I deposit an initial amount and have the dividends not reinvest. More on this in my [investment policy](/finances/investment-policy).
3. Maximize the number of people supporting your progress.
4. Think win-win and meeting in the middle.
5. Pay yourself first.
6. Promote dividends earned in vehicles returning less than 7% per year to vehicles that historically return higher.
7. Higher rates of return should be lowest piriority consideration when making decisions (see previous).
8. [Building Wealth Paycheck to Paycheck](/finances/building-wealth-paycheck-to-paycheck).

## Tools

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -41,15 +41,15 @@ Now for the law. It's referred to as [Conway's Law](https://en.wikipedia.org/wik

Conway's Law has been reframed and rephrased more than a few times. Mine goes like this:

> Conway's Law swings both ways. Show me the people and I'l describe the code. Show me the code and I'll describe the people.
> Conway's Law swings both ways. Show me the people and I'll describe the code. Show me the code and I'll describe the people.

Of course, it doesn't have to be code, system being defined broadly in this context. With that said, it often works out. Take the [code used to build this site](https://github.com/8fold/site-joshbruce.com).

As of this writing, there's a minimum number of dependencies. There's a minimum amount of code. And, it's relatively easy to deploy and release new versions of code and content; I can do almost everything that needs doing using my phone.

So, what does this say about me?

When it comes to [motivators](/design-your-life/motivators), autonomy is ranked number two almost every time; I don't like depending too much on others and I try to help other not be dependent on me. I'm a minimalist in my lifestyle when it comes to people and property. I also tend to refactor what I say to deliver the most impact possible with the fewest words I can consider [at the time](https://quoteinvestigator.com/2012/04/28/shorter-letter/); I try to be to the point. I favor mobility and agility in my life.
When it comes to [motivators](/design-your-life/motivators), autonomy is ranked number two almost every time; I don't like depending too much on others and I tend to help others not be dependent on me. I'm a minimalist in my lifestyle when it comes to people and property. I also tend to refactor what I say to deliver the most impact possible with the fewest words I can consider [at the time](https://quoteinvestigator.com/2012/04/28/shorter-letter/); I try to be to the point. I favor mobility and agility in my life.

I describe the code and the code describes me.

Expand All @@ -63,7 +63,7 @@ And, in under 48 hours, I redesigned the site, removed my dependency on a framew

## Re-engineering [.vs](versus) refactoring

I recently refactoring the code for the site. Specifically, I performed the [extract class](https://refactoring.com/catalog/extractClass.html) refactoring to create a class called [`FrontMatter`](https://github.com/8fold/site-joshbruce.com/pull/19). From the perspective of a user of the site, nothing changed, it's a refactoring after all.
I recently refactored the code for the site. Specifically, I performed the [extract class](https://refactoring.com/catalog/extractClass.html) refactoring to create a class called [`FrontMatter`](https://github.com/8fold/site-joshbruce.com/pull/19). From the perspective of a user of the site, nothing changed, it's a refactoring after all.

However, from the perspective of the other classes within the system, this was re-engineering. The way the other classes interacted with the other pieces of the system changed pretty dramatically. To put it in corporate human terms, I hired someone new to take on the responsibilities that were once owned by another person. This meant everyone who used to interact with that original person now had to interact with this new person.

Expand All @@ -77,7 +77,7 @@ I talked about [staying as small as possible](/web-development/on-constraints/in

That's a loaded question. When we talk about scaling we usually only talk about it in terms of scaling up. More code. More people. And I think those two things are mutually inclusive. The more people independently contributing to a codebase, the more code there will be. We rarely talk about scaling down though.

I didn't have a good answer for that question at the time. I'm not sure I have one now, in fact. I think it's appropriate to breathe. Scaling up is an inhale and scaling down is an exhale. I think it's appropriate to scale in either direction at any time; however, one should favor the exhale.
I didn't have a good answer for the when is it appropriate to scale question question at the time. I'm not sure I have one now, in fact. I think it's appropriate to breathe. Scaling up is an inhale and scaling down is an exhale. I think it's appropriate to scale in either direction at any time; however, one should favor the exhale.

But this isn't the article for that I don't think.

Expand Down