Time Machine Backup Failed

So I hadn’t opened up my MacBook in awhile, and, when I finally did, was constantly greeted with There isn’t enough space 😣

Time Machine Backup Failed

A bit frustrating at first since I thought the whole Time Machine allure was that old backups would automatically be deleted 🤔

So after a few weeks of getting this annoying message each night finally decided to think this through.

Realized that, yes, I had configured Time Machine to back up to my Synology NAS automatically so I didn’t have to think about it, so I decided to check the DSM for clues as to what was going on.

So I opened up File Station, right clicked Time Machine Backups and right clicked Properties to find that yes, the volume was nearly full.

File Station Time Machine Backups Properties

Then I opened up Control Panel > Shared Folder then right clicked Time Machine Backups to select Edit where I found Empty Recycle Bin.

DSM Empty Recycle Bin

Emptying the recycle bin resolved all the issues which then reminded me that Time Machine on my MacBook had indeed been properly deleting old backups but that the NAS as configured will only free up space once the recycle bins are emptied. I configured this on purpose months ago to ensure that if a machine on the local network ever got compromised that a virus or other malicious activity could not remotely delete backups once they were completed. I suppose I could enable auto emptying of recycle bins or disable them altogether for Time Machine Backups since a backup of that volume is done nightly to a volume that is inaccessible to the network 🤔

Autonomy, Mastery, and Purpose Helps Get Me Into & Stay in a Sense of Flow

  • Autonomy.
    • Ability to improve codebases from the perspective of non-author contributors or a place of learning after the fact/original design (e.g. more scaladoc or javadoc, better test coverage beyond basic code coverage, holistic class and variable names from a repo feature perspective, re-factorings that help other contributors understand with less time/effort, etc).
    • Give me opportunities to reduce/eliminate manual processes/analyses/questions/busywork and I’m on it – code is king/queen.
    • True collaboration and challenging conversations to improve the odds of staying relevant and possibly, innovative (from the perspective of the larger org’s gaps in general within the larger enterprise, across departments and functions).
  • Mastery.
    • Simplicity long after the story/design has been marked Done.
      • How much effort would it take for me to explain this feature to a new contributor (including class and function name references)?
    • Scale.
      • How much more toil/manual effort can be eliminated with a more advanced design?
    • What would I learn that I haven’t already mastered up to this point in my career?
  • Purpose.
    • How many people could I impact/reach?
    • How could expending effort on this allow me to work myself out of my current role so that I may focus on new challenges and growth opportunities?
    • How does this impact the open source community? How does my work possibly impact other companies and/or organizations?
    • What could I demo/evangelize that would lead to further adoption?

Re: Why the Ambitious Are the Least Likely to be Successful

Re: Why the Ambitious Are the Least Likely to be Successful

I think a critical point is that, you can start with ambition, and end up with a healthy regular schedule of work that satisfies not only external rewards we originally, and continue, to seek, but, to also find joy in work we find internal resistance to, from time to time. I’d argue that we all, at some point, find resistance to just about anything and everything we encounter. I think Stephen Pressfield’s, Do The Work (http://amzn.to/1hv841z), illustrates this nicely. I also feel we shouldn’t discount mindset, and from what perspective we move forward in going about our daily lives. I totally see your point, if you are stuck looking for external rewards over a long period of time, month after month, year after year, it is not sustainable. It’s the same reason why I don’t stay at my high paying corporate job only because of the benefits and great salary, that’s only a starting point. If it weren’t for the intrinsic rewards of not only developing software engineering skills, but also learning how larger organizations work, and improving my learning how to learn (e.g. SQ3R, mind mapping, visualization, etc), I don’t think I would have made it as far as I have in my 12 year professional coding career. I think a lot of the commenters haven’t taken a step back to see the bigger picture here — ambition can be very bad in the long term, if that is the sole fuel moving someone forward. He never said it served no purpose, only that, hopefully, over time, that initial ambition will be replaced with other, more sustainable experiences, such as: enjoyment, passion, resolve, genuine interest, learning, sense of meaning, personal development, reflection, etc.

Thank you for this post, if nothing else, I feel it has succeeded in compelling some to reflect more on their work and their approach in life, which is the point of this kind of article anyway, right?

Going Paperless

Here is the 2012 General Election Sample Ballot (full booklet) for anyone who cares to read on their e-book reader of choice (PDF). I “scanned” this all on my iPhone with just a few snaps of the camera using My Scans PRO — I am really surprised how quick and easy it was, it really looks like I scanned it. This is pretty exciting as a note taking and annotation tool. DropBox allowed me to post online, all from my mobile 🙂 A paperless life is now within easy reach, I am totally in love with this “flow”.

View 2012 General Election Sample Ballot (full booklet)