Didn’t work at all on this, this week, as I was traveling and packing as I moved across the USA.
I’m not sure when I will make more progress on this, but I really should just finish up a stable release and submit it to the obsidian community plugins.
The main bugs right now are:
daily note functionality still needs tuning up
on the current release, it seems like the hotkey/command palette doesn’t submit any more. not sure when that bug started happening, but I have it working on the newer edited code with the daily note testing.
It would be helpful as well for me to map out my current code feature branches so I can stay on top of the branches and remember to merge or prune branches as the features are finalized. I’m sure there is a visual way to look at this in github.
This is kinda a cheat update, but I’ve had a lot of interpersonal stuff going on this week. Hopefully next week I can find time for this as I’d like to wrap up the initial features + release it
Been flying back and forth around the country so really no time to work on this. But I have a bit of a stable work place this week so I plan to make it a focus!
been making a decent effort on this the last few days…
I set up Jest for testing the edge cases.
I also realized that the manual submit bug I thought was occuring is not actually happening to my knowledge… this means the current release is fully working.
My next goal is to tidy things up and submit to community plugins as I can add in the daily note function later.
Scratch my prior update, the “manual submit” bug IS still occurring.
This bug actually affects both manual and automated submit, and only starts occurring after obsidian has been running for a bit… 1+ hour ?
So it’s actually the “Obsidian open too long” bug… not sure exactly why it’s happening will look into it later.
The current workaround for this is to just open the command palette and hit “reload without saving” this will restart obsidian and the plugin will submit the data points. I’m still finding the plugin useful with this workaround.
This week I submitted 2 pull requests to other Obsidian plugins that I took other people’s code and added functionality.
I now have been working quite a bit on another plugin to understand the AI-generated code I used for it… basically using AI as a code tutor to explain it.
Funnily enough it doesn’t take long for me to realize inefficiencies and redundancies and general wonkiness of the code… so I feel like AI coding is similar to AI writing - it’s useful for a first pass to get a starting point, but then it’s important to refine out all the AI weirdness.
I do think there is a better method of using AI as guidance for top-down software architecture and then implementing the unit functions one by one as to slowly build something robust that I understand…
I will try doing this more on future projects and on this one as well if it comes to it.
The other plugins involve a lot of UI so they are a different wheelhouse than this plugin lol.
bought a coding course that focuses on javascript and deploying webapps, as I plan to work on building saas soon.
progressed through 65% of the course so far has helped me understand javascript (as well as tailwind!) more which is important here because Obsidian plugins are written in typescript. I was pretty much flying blind writing typescript since unfortunately I’d never made much of a concerted effort to learn javascript… I’m now discovering that learning to build these Obsidian plugins was a great help to cut my teeth with javascript development.
I progressed on my other Obsidian plugin, and once that one is complete, I plan to refocus and ship this Beeminder plugin. Was a bit of a wild goose chase over the last 2 months on this but I’m more confident now that I can swiftly figure out the bugs with minimal mental pain now that I have a better understanding of javascript AND have a better overall AI coding/learning workflow !
I also today built a dummy landing page from scratch so that stripe can “verify my business” since I needed that to fix my kofi payments.
