Remix.run Logo
KronisLV 9 hours ago

In regards to the review part:

What helps me is keeping around my TODO.txt month by month, as well as a lot of screenshots and images of the things I find relevant for sharing in stand ups and meetings and such (as well as presentations).

So if I need to review the past month/year (e.g. when I want to update CV/site or catch up with management), it’s just a matter of going through a bunch of text and images without a lot of unnecessary fluff, like digging through Jira. Maybe if I want to get the approximate time/effort spent on particular stuff, based on the amount of activity there.

Alongside that, it’s also nice to document stuff that was particularly good, or all the ways software broke in (and what broke how often), as well as stuff that pissed me off and made me want to quit (sometimes people/mindsets, sometimes tangible code or practices).

When the default is just going with the flow and not documenting anything and doing no self reflection, every improvement upon that helps.

A4ET8a8uTh0_v2 9 hours ago | parent | next [-]

GPT was actually pretty good for this use case until 5.2 kneecapped its long term memory and now its more aggressive about pruning ( very annoying as wide recall now has to be explicitly invoked ).

xianwen 9 hours ago | parent | prev [-]

Very interesting! Do you organize screenshots and images by day and by topic?

KronisLV 8 hours ago | parent [-]

Currently not really, at least not for the weekly status meetings.

Typically I'll have a folder with a bunch of numbered files in the order that I want to talk about them, since it's easier to just quickly share my screen and run through then when I want to let others know what I've done, for example along the lines of:

  01-migrate-gulp-grunt-to-vite.png
  02-vue-prebuild-script-check-unused-translations.png
  03-java-add-compile-memory-limit-ide.png
  04-server-update-python-for-ansible.png
  ...
If I need them for like a yearly performance review, then I'll probably do a pass where I group them into named folders and write a doc loosely following those topics, given that I might work on similar improvements and fixes across more than just 1 week. Pretty low friction daily and also when I need more structure.