~/Sources for stuff I’m only building from sources and no immediate intention to contribute to
~/Projects for stuff I’m involved in, with a following structure:
Projects
- Personal
- - Art
- - Music
- - Code
- - - Ideas
- - - In progress
- - - Deployed
- - - Scripts
- - - Abandoned
- [Company name]
- - [Project name]
- Interviews
- - [Company name]
The last part grouping project by companies has worked great for me, especially with freelance and outsource work. Sorting personal projects into types and stages feels like a mistake, as every time I have to navigate it, I can’t help but think of limitations of hierarchical file systems, as some of them are multiple types simultaneously, and also moving projects between stages feels dumb.
I hate this shit being routinely used in PHP. Symfony uses those functional comments for routing, essentially scanning every controller file as text on every visit, to gather the url patterns above functions. Laravel uses Reflection, which is functionally the same thing, to provide arguments to controller functions. Also, kind of related, the project I’m working now has few functions that use backtrace to return different results based on where they are called from. It is indeed very cursed and I’m ripping out any usages of them whenever I see one.