Daily Entry: December 9th, 2019


Time (PST) Plan Reality
0000 SLEEP
0030 SLEEP
0100 SLEEP
0130 SLEEP
0200 SLEEP
0230 SLEEP
0300 SLEEP
0330 SLEEP
0400 SLEEP
0430 Waking up SLEEP
0500 Coffee and ... SLEEP
0530 Pomodoro: Planning SLEEP
0600 Pomodoro: Planning SLEEP
0630 Pomodoro: Organization SLEEP
0700 Morning routine
0730 Fixing issue with personal PC
0800 Organization
0830 Organization
0900 Organization
0930 Walk to work
1000 Start of work routine
1030 Browsing: Internet
1100 Pomodoro: Data Classification PR
1130 Meeting: Data Management Sync
1200 Lunch
1230 Lunch
1300 NAP
1330 Post-nap coffee
1400 Pomodoro: Backlog/Planning
1430 Pomodoro: Data Classification PR
1500 Orthodontist appointment
1530 Orthodontist appointment
1600 Pomodoro: Data Classification PR
1630 Walk home Pomodoro: Data Classification PR
1700 Shower Walk home
1730 Pomodoro: Side-projects Hanging out
1800 Music stuff with wife Shower
1830 Hanging out Pomodoro: Side-projects
1900 End of day items Music stuff with wife
1930 Hanging out
2000 Hanging out
2030 Winding down
2100 SLEEP
2130 SLEEP
2200 SLEEP
2230 SLEEP
2300 SLEEP
2330 SLEEP


Really "practicing flexibility" today. Was sick over weekend and also had a bit of OCD keeping me awake until 2300 last night. I was still compelled to finish the problem keeping me up last night when I woke up, so I did.

I then wanted to be in a good spot WRT data classification, so I skipped proper planning and dove into that before my meeting.

Some weekend notes:

  • Saturday was "sleep sickness off" day
  • Sunday was budget day and half-wife-day and half-my-day

I also have a personal project that I'm giving myself a week to complete. Calling it "One FIRE at a Time" and hopefully I'll link to something by this Sunday. Which is part of the reason for my OCD with my PC yesterday. It's general slowness was really starting to annoy me.

I looked into fixing my (previously "good", now) tower computer. But upon analysis of the parts of my tower computer and my (previously "bad", now) budget computer, the only thing making the tower computer superior were:

  • the RAM (budget had 8 GB and tower had 16 GB)
  • the memory (budget had 1 TB HDD, tower had 512 MB SSD)
  • the CPU (budget has cheap AMD 6-core processor, tower has Intel i7)

Now, the CPU couldn't be ported over to the budget computer, but the RAM and memory certainly could. And that significantly sped all the things up. It is more than sufficient for my current purposes. Also, Overwatch can be run at about 85 FPS, which isn't at all important, but a good gauge of where the system is.

Also, the whole computer situation has inspired "One FIRE at a Time" to be my first real project after some basic base-react-app setup. When I built my Quakecon Travel Build, I saved $18K for it. $3K for the build, and $15K so I could spend $3K again in 5 years.

But how I did all that makes tracking the value of that computer fund difficult. It's just in the same 90/10 Betterment fund as everything else. And moving things around in the stock market just to keep track of which fund has what amount of money has tax implications. So, I'd like to keep it in a lump fund, but pretend it's divied up based on what chunk is paying for what regular expense.

So, this week, I'll be taking my stock market savings, and dividing it up imaginarily into "paid-for" things. I'll also make "withdrawal" rules and stuff that really just use my paycheck, but allow "spent" funds to move to other types of accounts.

I also have to consider my withdrawal rules. With things that are aggressive, like my 90/10 betterment account, I can't do the 4% withdrawal. I think a better setup is only being allowed access to 50% of all accrued interest. But with the 50/50 accounts, 4% is a safe number.

None of this will be done in a week, mind you. I think really, by the end of this week, I want to query YNAB's API endpoints, grab my accounts, and have a sqlite database that splits things accordingly and accurately updates gains/losses based on distribution.