Yesterday is a folder based journaling solution that beautifully renders text files, images, videos and more.
Note ID is an Obsidian plugin to enable a proper Zettelkasten workflow.
Reader Mode prevents Obsidian from opening every note in edit mode.
Cloud Cub is a tool to protect your files from silent sync disasters.
Mitado helps companies set up product development processes.
Nexova Dynamics migrates Swiss companies to Business Central.
Come join one of the events I host.
Product & Beyond is a monthly meetup of people passionate about products. Design, engineering, product management, marketing, operations, legal and more all partake in the creation of great products. We regularly get together to drink, laugh and casually talk about products and beyond.
Meaningful Discussions in Ho Chi Minh City is the Saigon chapter of the largest face-to-face discussion group with monthly events taking place in 11 countries.
Lean Startup Vietnam host irregular events sharing Lean Startup techniques and experiences.
Pomodoro Calendar let you register your Pomodoros of the whole year.
GWT Bootstrap was a wrapper of Bootstrap for Google Web Toolkit.
Google Calendar to Kindle let you send your agenda to your Amazon Kindle.
The Carpet Makers on thousands of planets spend their whole life creating one carpet each from the hair of their wives and daughters. This beautiful carpet is for the palace of the emperor. But the emperor is dead and his palace contains not a single hair carpet.
Author Andreas Eschbach unravels they mystery of the hair carpets in a collection of self-contained short stories, all following different protagonists, painting a detailed picture of this foreign world.
Murakami Haruki has written many wonderful books. The ones I highly recommend are:
I listen to quite a few podcasts. These are the English ones I enjoy quite a bit:
The German-speaking audience might like:
Herman Martinus wants his products to be like a garden:
That’s what I want from my products. I want to putter about, feel connected to the process, and have fun doing so. I want to make things that don’t scale. To see people tuck into them and enjoy them as people, not as stats. I’ve done this fairly successfully with JustSketchMe. We have a small, diverse, and amazing community of artists and illustrators making awesome things. I’m trying to build a similar product with Bear Blog. Something niche but valuable. Something I can spend time on because I want to.
Being able to talk to, and interact with the people using my tools is fulfilling. Spending time meticulously improving subtle aspects of the product is enjoyable.
The first time it happened, I was writing a paper. The paragraphs I had just typed vanished into thin air, faster than Time Machine or Backblaze could save them. Gone. The next occurrence was during app development; Xcode suddenly flagged numerous errors in previously error-free code. My recent changes to several files were erased.
Months later, the mystery is solved: iCloud Drive detected a file conflict. It assumed different versions of the same file existed on my Mac and iPhone and couldn’t merge them automatically. This was impossible; the affected files were never opened on the iPhone. But they were in iCloud, as I had moved my Mac’s Documents folder there.
Dropbox manages version conflicts by storing all conflicting files side by side, labeled as “(John Doe’s conflicted copy)“. iCloud Drive, however, doesn’t show these conflicts in the file system. If you open the file in an editor that supports conflict handling, a popup appears asking which version to keep. Editors like Textifier, Xcode, or Obsidian, lacking conflict handling, leave iCloud to decide which version to store on your disk and in your backup.
Over time, newer backups overwrite older ones containing the correct version; your content is gone for good. The only way to get it back is to open the file with an editor that supports conflict resolution.1 Once moved out of iCloud Drive, even that won’t help. The content is lost.2
Masking version conflicts might appear user-friendly, but it has catastrophic consequences. You might not discover the data loss until years later, when reopening significant but infrequently used documents.
Until iCloud Drive exposes version conflicts in the file system or a central, easily accessible location, my strong recommendation is to move all crucial data out of it. Meanwhile, set up a Git repository to monitor your critical files; you might uncover surprising changes.
Update: For files that need to stay in iCloud Drive I’m building Cloud Cub, a simple way to detect and resolve hidden sync conflicts before they cause data loss.