3/27/2023 0 Comments Voodoopad iphone stop working![]() All the money you’ve contributed, the dates you contributed, all your investment decisions – buys, sells, etc – and the amount of money you have now. Imagine your entire retirement savings history. If you deposit money early in the year, you’ll have more money at the end of the year than you would had you deposited on July 1st. Imagine a bank account with an unchanging continually compounding interest rate. APY compares your investment strategy to a bank account with a consistent interest rate. If you want to know how well your investments have performed over time, you don’t want to count cash contributions as something that improves your performance. But CAGR doesn’t pay attention to how much money you’ve added, and when. ![]() CAGR is like Gain, but it pays attention to the time frame. Gain doesn’t pay attention to the time frame.ĪPY is better than CAGR. Gain just compares a portfolio value between two points and time and lets you know how much bigger or smaller it is. This one magic number communicates everything relevant and doesn’t throw away any relevant data. APY is one of those magic numbers that can summarize an entire mess of complicated data into one magic number. But it also does one additional thing that I think is magic.īasically, it calculates my all-time retirement APY. ![]() What ‘port’ does is it analyzes this data file, reports my holdings and some rudimentary stats. In a separate section, this data file also has every every stock/fund transaction I’ve ever made, and how much retirement-account cash I have. I’ve created a data file that has the date and dollar amount of every retirement contribution I’ve ever made – whether a 401k contribution out of a paycheck, an IRA contribution, or something else retirement-related. I have used this little shell script for years now. Kind of like how I occasionally write small web applications to test out product ideas.īy far the most useful program I’ve ever written is a short perl script called ‘port’. I occasionally write small programs for myself to analyze things I’m interested in. Leave a comment Posted in Glue Retirement APY Git push.Ģ) On the dev site, pull the most recent changes, and restore your local database.Ĥ) Dump your db changes using the same script.Ħ) On the live site, pull the most recent changes, restore the database.ħ) Take the site back online. Optionally take the site offline if it’s high traffic and you don’t want to miss any database updates. What’s great about this is that it makes the future upgrade process quick and painless:ġ) On the live site, dump the database (I have a script for this) and check it in. Committed once more.įinally I set up my virtual host on the new server, set up my database, cloned from git, and imported the dump file, and we’re up and running. I also manually upgraded once more to 2.9, but then I decided to try out the Automatic update, and it worked like a charm. I downloaded 2.1, used the “DirDiff” plugin of vim to apply it to my existing install, dumped again, and committed. So, I created an empty git repository, and copied in my 1.5.2, along with a database dump, and committed. Finally, since I’m using MAMP, apparently the (local) web server runs as my own username, so I didn’t even have to do any chown/chmod magic. The other great thing about git is that it doesn’t have “.svn” subdirectories everywhere, so it’s all right for a web process to move files around. ![]() They only charge if you have team members share with you, which I don’t need for wordpress repositories. What’s great about bitbucket is that there are unlimited, free, private repositories. Once that happens, it can be a really painful process to resolve.Įnter git and. Automatic updates occasionally remove entire subdirectories (folders) and replace them with new subdirectories, and that is murder to subversion. And while it worked all right in ways, it would never work right with automatic updates. You should instead always apply your changes onto a local “development” installation, and then use a source code management system, or a publishing mechanism that reads from an SCM, to push/publish the changes to your live server.įor a while I tried to use subversion. ![]() When you’re programming a website, you should never edit or touch any files on the live site. Another is that I think the whole theme/plugin thing is such a time sink, although I guess that would be the issue with any blog software.īut another is that I’m a programmer used to a certain kind of delivery process, and wordpress has always been unfriendly towards it. One is that I’m a programmer and I’ve heard so many bad things about the php behind wordpress that I’ve never wanted to really dig into it. I’ve always been grumpy about WordPress, for several reasons. New server! New delivery mechanism! Upgraded wordpress! One further step along the way from retiring my old server, for good. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |