26 karma · joined August 1, 2017
Install ≠ operate
I'm also automating more stuff around bookmarks management -> I used to manage an awesome list as a repository on GitHub for myself and over a couple of years there are relatively many stars on this repository. However I lost interest in maintaining this repo manually as I prefer to save my bookmarks on Shaarli. I'm coding a CLI tool to automate the work of syncing my shaarli links to my public "popular" (+500 stars) repo at https://github.com/SansGuidon/bookmarks
Myself and other users complain a lot about the "native" Plex -> Ombi watchlist integration being broken, I coded some sync tool to workaround the app malfunctions, by using Ombi, Plex and TMDB (The Movie Database) APIs and ensure Ombi is always up-to-date based on Plex watchlist. This works very well and allowed me to put a stop to the complains from my family members :-D
I'm also automating most of my email/linkedin interactions thanks to userscripts. And I keep automating more of the work I do around Cloudron, which is a very fun and stable platform to manage apps on VPS without the pains.
I guess N8N was not intuitive for simple things and seemed too complicated for me. I'm now happier with cron jobs/GitOps to manage my automations. On the other hand I also had to replace some IFTTT workflows with my own scripts.
More work for me but I gained quality and control.
For images, what do you want to grep for? for exif data -> https://exiftool.org/ if you want to find image based content, you might need something smarter. I think maybe it is a place where tools such as https://github.com/ultralytics/yolov5 can shine for me. simple enough to work with most of my images and tag them according to some preferences, and I would save such tags in a txt file.
Anyway, all metadata I store about images, links etc are all persisted in txt files. summaries, tags, etc, incoming/outgoing links etc, each has its own file. There are folders per link/content. Under each folder, one file per type of metadata. So it is very easy to know if some metadata is missing for a file, no index needed, it is just as simple as checking the presence of a file. everything is compatible with grep then.
for docx and xlsx it is out of my plate at this time, I didn't experiment enough to judge what works well enough. I hate those things.
That's also a fact that the easiest an activity becomes the more we can become addicted to do it without thinking. The less we look for alternatives.
Why doing a meeting of 30min when 3000 lines of code can do it. Who cares who will maintain our code as long as we become the hero of the team by typing 10.000 loc overnight.
We are the faster. We win every discussion by typing more and faster. We impress. We throw more jira issues in backlog than everyone else. We dont see the need to slow down or refuse a task because our typing speed gives us more privilege and power.
So one key thing is becoming constrained also makes us more creative at problem solving. Maybe working more is not the key, maybe coding more is not the key goal. Maybe one line of code or a product can solve our problem. Maybe some llm, maybe our of our 100 ideas per minute, only one is relevant and maybe it won't be useful by next week. Good ideas are not always the newest ones.
I also consider on average programmers read more code than they write. I've often helped very busy people whose time was focused on reinventing the wheel and frameworks because they were proud of their coding skills and avoided looking elsewhere for existing solutions. I also haven't been the fastest programmer but always the one able to read code and find bugs better than peers. I'm not proud of typing more unnecessary and buggy code which will then slow us down through debugging and maintenance.
Observability, and quality is important, more than quantity and speed. And as for most things, speed also amplify some negativity, chaos and noise, in my experiences.
Having distinct local working copies of same repo per git branch still works great, not stash needed, no conflicts or pain with local wip and drafts changes overwritten by pull. No blocker for switching branches. No reset hard/soft whatever. And makes files comparisons easier and makes my git workflows easier.
I still feel vcs could be simpler and solved problem if more engineers care about the topic of vcs and generally speaking about the ux of their main tools instead of creating new TUI and plugins to workaround broken ones.
Anyway Jujutsu stil feels great, I just hope now to not need to suffer like I did with git.