unsolvable problem alert
It's always news to me when I encounter a dev challenge I'm unable to surmount. It used to be unusual but the last two times have shown a pattern: it rears its head whenever I'm with undocumented tech
In this episode, I set out to build an auto documentation generator in php. Naturally, I leant towards psalm since suphle already uses it during server build to guarantee absence of type errors. Since this isn't documented anywhere, I combined several llms to tweak and fine tune the component until we successfully fabricated the tests, templates, classes and docs supposed to make this work. Took maybe a week
I didn't think more of it until time came to run the tests. After fixing the usual minute errors hindering system core from running, php memory allocation started exploding. It got so bad that it froze my system twice. Turns out that each time I hand a method over to psalm to analyse and give back its shape for documentation, it starts indexing the entire codebase anyway. No amount of config restricts it from crawling up my tremendous vendor folder. I opened an issue with them https://github.com/vimeo/psalm/issues/11871, that has remained unattended to till date
