The Week #88

by
  • We made it through an entire week without any closures or Leo's school! 🎉  We were also notified on Saturday that it will be closed all next week 🙃. You win some you lose some, I guess. Most schools in our area aren't as cautious / having nearly as many closures as Leo's. You can complain, but it's probably the right thing to do, even if it is inconvenient. 
  • I did the legwork to proper organized al of my trades/dividends of my US accounts using the exchange rate of the day so I can report them the city and not be committing tax fraud. Getting it all organized into excel sheets has been a huge relief. For a while now I've know that I need to collect the data, but I never could what format or exactly what information would be required, so I just put it off.

    Thankfully there were some helpful posts on /r/JapanFinance that had a screenshot of a header of the document that they use to organize their trades, which was enough to get me over the hump. Now that I have the format decided upon, it should be much easier to update each year.

    As a bonus, because it's less than ¥200,000 (roughly 2k usd), I shouldn't need fuss with updating/finalizing my national return  and my "End of year adjustment" is enough. Probably. Will confirm when I visit the city tax department.
  • We celebrated baba's 78th(!) birthday! I can't imagine what it will be like to be 78, but I do hope it will be in the same manner as baba's birthday: with delicious sushi and all of the kids/grandkids.
  • At work I managed to get the second of two big PRs across the line for review. Two big features that will (eventually) be used worldwide. I felt a bit bad throwing not one, but two 1,000k+ line pull requests over the wall. But there's one critical difference that makes it possible: each commit matters and each commit in the PR is expected to tell part of the story of that PR.

    This means no commits like "fixed bugs" or "fixed bugs, for real this time". But rather you're expected to squash those bug fixes into the appropriate commit before asking for review. It makes for such a cleaner history.

    Sometimes you mess up and you commit things together that shouldn't be. And you have to rebase and split them apart. And it's a pain for a couple of a minutes. But thinking about your PR at that lower level helps you create higher quality code because you're forced to ask yourself "does this change make sense in isolation and how does this bit of fit into the grander scheme of this PR". And cleaning up your commits can also be incredibility therapeutic. That level of fit and finish that only the craftsperson sees and knows about.
Interactions
1