4 ms·
When you have a family. A wife who barely knows how to create bookmarks in a browser and kids who only use their phone you need something extremely simple. So
by hackeredje 6y ago
When you have a family. A wife who barely knows how to create bookmarks in a browser and kids who only use their phone you need something extremely simple.
So you need to " scale " from 1 person to a household and take into account that all information you put in there, financials, recipes, addresses, etc. etc.. need to be ubersimple, working on a phone, auto sync etc... and need to continue working even when something would happens to yourself.
So that is why i standardized the knowledge management system in our household on OneNote (2016 client for the laptop).
This is because everyone understands office.
The API both the COM and the graph API also lets you create , update, read, etc... so you can write basically everything you can think of e.g. auto put bank transaction on the correct place in the correct table in the correct place in the taxonomy.
Thinking about the structure of a family and everything in there is also interesting and I had some larger revisions on that.
See also: https://github.com/projectje/OneNoteExporterAkaPublisher https://github.com/projectje/OneNoteExporterAkaPublisher
- joshspankit 6y agoI’ve always shied away from OneNote, finding it cluttered and as overwhelming as someone else’s heavily dogeared and bookmarked notebook, but you have my attention. Do you have any breakdowns on how you conquered WAF and the API?
- hackeredje 6y agoCOM interface: https://docs.microsoft.com/en-us/office/client-developer/onenote/onenote-developer-reference https://docs.microsoft.com/en-us/office/client-developer/one... So just $whatever = New-Object -ComObject OneNote.Application and then lookat $whatever |get-member to see what you can do for members and properties. --- I tried several things. I needed it because the amount of stuff around a family is just too much to keep in my brain especially with kids who needing a lot of help with their school and trying to also put some fun in it like " nice netflix series you want to share" but also serious stuff like " households tasks, bedtimes etc" I think I could write a book on what i put in there. Budget is also interesting, after 20 years I decide on the following structure: A = income B = budget per household member (so 4 posts) C = everything that needs to be discussed (vacation budget, savings, subscriptions, stuff we want to buy this year, etc) D = everything that we do not need to discuss (mortgage, food, all kinds of city taxes, healthcare etc) That makes it really simple: only the points in C are needed to discuss "want to spend 20.000 on vacation Or want to spend 20.000 in savings" . Because I noticed that mosts of the costs stay the same. Many of these "topics" then tie in or have an overlap with the knowledge management topics from another perspective. So e.g. the budget post C.Subscription.XboxLiveGold ties into culture_and_free_time.games and where we just have fun pages on various game consoles and tips for games we play or we want to share with each other or " favorite games" .
- hackeredje 6y agoWhat it also means is that when the thing grows at a certain moment you see a parallel in the taxonomy you put in your local organisation with external " all knowledge ever" for instance on wikipedia portal > categories etc or any of the " all knowledge" systems like dewey or libray systems. And in many cases you write the thing that has a linkage to already being in a place in other generic taxonomies e.g. when i my son has an exam on e.g. French Grammer we put some stuff in there to undertand these lessons, but this " structure " is also already on wikipedia. But the structure on wikipedia is just too much too handle. So I think that the end-situation for larger parts of the personal household knowledge management system overlaps with the structure found in " all knowledge ever" systems. So im in the phase that I try to look at the taxonomy of these systems e.g. wikipedia and also e.g .structure "mathemetics in the taxonomy that is on the wikipedia portal page for mathematics" (but slower since i only need what is in there what my kid has currently on school). The younger kid can then leverage on this and read up on this. Since we already made it for the older kid. But I feel that exchanges between "external taxonomies" and " household taxonomies" have not yet been establised. E.g. I also have all my " stuff" in there like " household applicances" (warranties, but also comparison sheets, instructions etc) but the overal taxonomy and the " wording" is matchable with e.g. shops who sell household appliances. If there would be a taxonomy standardization on all of these things it would enable exchange information on meta level.
- leeman2016 6y agoOneNote is feature rich (specially the availability in iOS) ... but what eventually made me drop it was the unavailability of a reliable desktop app in Linux
- zie 6y agoI use Fossil-SCM for that. 100% OSS, it's a single Sqlite DB file for backups, etc. It's totally fine being offline or online and totally fine being de-synchronized for years and catching up. I put my legal and financial info on a USB stick with the fossil binaries every year, and hand them out to next of kin. Whenever I die they just plug in the USB and click the appropriate fossil binary and bam, they get everything with a web interface, files and wiki with instructions included.
- hairofadog 6y agoThis resonates with me. People like to talk about simplicity, and I get that, but to some people simplicity means “just use org mode”, which is a whole different axis of simplicity from “my partner can use it without redirecting their tech-related-frustration anger at me”. There’s yet another axis of complexity/simplicity, which is that trying all these different note-taking systems means any time I want to look up a note, I have to check half a dozen different places. Recently I’ve been dropping everything except for code snippets into apple notes, and I’ve had a much easier time finding things later.