Don’t get too excited about new systems you build for yourself (here’s a transcription of an audio note from Plexus):

You have an early excitement for the fact that you've designed something, that you've taken initiative, that you are, you know, making a move to better yourself and close the gap between where you are and your vision. That's all very exciting, but the system is kind of created blindly, right? It's a theoretical abstract thing and you think that your time and your situation can flow through it and lead to the outputs you want, but so often the systems you build, whether they're analog or digital, simple or complex, something is lost in the abstraction and when it makes contact with your life. Either it doesn't fully solve it, it gets you the wrong thing, it gets you what you want but with a terrible side effect. I mean, there's all these truths that you have to iron out through experience and so what might be important to develop … [is] a change log of your systems … Map out the totality of what it is you're going for and then … be extremely specific as to what you think that [it] can deliver … Then, at a certain interval [check in… is it working?] … [if it] didn't lead to what you expected … you have to re-tweak the whole architecture.