Handwriting is better as SVG if you are writing digitally, and while everyone has their own vector ink based proprietary formats, I like the simplicity and openness of SVG’s!

Here are some more such tools I feel you might find interesting (or most likely you might already know them) but might be worth having in a single place as a list.

Nash is stand alone note as HTML. Source: https://github.com/keepworking/nash I recommend nash for when i feel people might get overwhelmed with tiddlywiki.

htpad: Handwritten scratch pad saves stuff to SVG. Source: https://github.com/akissinger/htpad I just use this for drawing on screen since teams annotation sucks.

Minimal PWA template. Source: https://github.com/chr15m/minimal-pwa A minimal template that should ideally work, but i wasn’t able to get it working with marimo wasm notebooks.

Currently, my focus is to use python either using pyscript or hopefully just use marimo to have python apps for simple things. I don’t want to learn js and avoided this side longer than i would have wanted. But python WASM ecosystem has grown significantly to a point where i feel investing time in building these tools.

Currently, marimo is having issues with the completely offline part but hopefully, that gets fixed!

Also, funny enough that this pissed me off so much, that I started asking LLM to search for something on reddit. I don’t care about the answer since due to it being reddit, LLM is not helpful, but what we get access to; is the citation/links exactly to the post you want and never had trouble in the ios webview within the apps. Use it as a billion dollar scraper and you won’t be disappointed with AI.

In fact the industry i work in we don’t have git, but something similar to SVN (and proprietary, expensive and pathetic UI/UX)

Since, I am not in software industry, I won’t comment on whether such people might survive for more than 5 years without knowing about ‘VCS’.

However, I have slightly died inside when some Computer science students (graduate school, mind you) were using google drive with manually created timestamps as a backup strategy. The submission for this entire semester long actual project was on Github. as a final single commit uploaded a day before. (And no this wasn’t a squashed commit from a different repo.)

There might be a blurry line between people not sharpening their auxiliary tools vs never using or being slightly curious about them.

I am more of a glamour and bling on my tools person, and I don’t expect every engineer to derive the same pleasure that I derive just from tinkering with them; however, does make me wonder if there is a point when such an approach to not fully caring about simplifying your workflow (aka being lazy), might spill over into making poor engineering decision?

The setup was a breeze! Did not try it with a server yet, but i don’t think anything would be radically different.

I am not a celebrity on github and not even agents bother with my repositories, however, even before the bot pull requests/issues, I always made sure to enable only the things I felt I would want to use and provide a way for someone to reach out in case I was expecting collaboration/feedback.

I realized that anyone can create a PR to upstream, when I accidentally did so using the github web UI on mobile. Felt embarrassed and immediately closed it. But, then it made sense that why people were frustrated with this sort of thing happening to big repositories.

Honestly, I would settle for a custom prefix if it tells me exactly what packages will break and what won’t without having to read each and every formula recipe. That’s one thing that bothered me for a while and I did not have the willpower to explore that direction without having community support.

I am not a rust evangelist, I am not a rust programmer or programmer at all; however while evaluating tools to use, anything written in Rust and Go at-least gets me to look at the project in more detail, since they most likely are able to ship statically linked binaries, which has been one of the key criteria for my personal evaluation of tools to select and use.

So, you might not consider it as a valid signal, however it might be for other users. Even if it has a negative connotation for you. Which in itself, again might be a good filter in case you don’t want to use it.

On personal pc no need to define the $ECORP var in shell init. On work pc define that var.

based alone on that you can conditionally do almost anything.

- shell source files/aliases

- vim/editors enable disable plugins based on existence of env vars.

- define shortcuts in file manager.

- and i add the following to my main $DOTFILES .gitignore.

  # Any file that contains the following will be ignored.
  # Used to ignore files in corporate environment
  *ECORP*
  *ecorp*

Additionally, maintaining hygiene is essential, where I only use a Read Only PAT token on my personal dotfiles in workenv. That way, there is no accidental way I would be able to push from my workenv.

I guess we are welcoming the software people to the world of expensive tools. Just sad that the FOSS alternatives of these tools are not as powerful whereas software industry still has FOSS tools to fall back on.