Agree that the author should have given attribution to the image, but this is an author who has created packages well before LLMs ever existed so I would cut him some slack.
Additionally, he is re-iterating a topic which has been discussed by many other authors. A few points he raise I had not seen before so still found it an interesting read.
Did you use any frameworks for the development? In particular any spec driven development framework?
As someone working on an opensource project myself wondering on a few questions
What I have found is that the more a human is involved the better the code, but also the slower it is. So, in my opinion, it is a tradeoff between quality and speed.
Recommend you follow the 321 backup strategy. Adopted to modern times I would say it is broadly:
From what you described if apple was to wipe your data[1] you would be completely out of luck… for example if something deletes data in your Mac and then that deletion gets synced… For the most part syncing data is not a backup.
Lastly, recommend you try to put all your critical data in one folder, or identify folders with critical data and prioritize backup of those first while you figure out the rest.
[1] Not only can a deletion “sync” from your mac, but there can be any number of issues… like a bad update to a file. There is also the possibility, no matter how small, that apple could wipe your data. Over time you always see news of “company X deleted entire set of data for user/company Y”.
Easiest way is a program called imapsync