General thoughts:
- I may want to continue to write down some notes I learned or points that puzzle me in the field of development work.
- Today again I had two cases in the team, where people where confused/uncertain about the status of technical issues, that had been settled some time ago, yet the information was hard to find or non-existent about the state of the respective issue. To me this seems like a pretty commonly repeating trope. It feels a bit like the opener to situations like “Chestertons Fence”. In the first case an issue (on gitlab) was just closed without any mention about the resolution. In the second case, a test checklist mentioned that something needed testing, but the detailed test instructions had been removed years ago, so the test person was confused if the feature had been removed from the product or not. That strongly felt like a variation of the “Chesterons Fence” theme, where removing information meant that some person would have a certain chance to waste their time riding out into the prairie.
- I guess I should update https://areq.gitlab.io/posts/2021-06-03-migrating-samba-sam-ldb-to-mdb/ to clarify a common misconception about LMDB size changing. It’s one of the most misunderstood points about LMDB and it’s a communication/documentation issue derailing a lot of people from picking up LMDB.