4 ms·
I once worked on a codebase where almost every mystery in the code could be traced back to a commit "Moving TIM one level down", and no further.
by twic 7y ago
I once worked on a codebase where almost every mystery in the code could be traced back to a commit "Moving TIM one level down", and no further.
- tempanonforaday 7y agoOh boy, library levels. "How are we almost level 100 now? We're going to need an exemption soon!" "We'd better go move around some orphaned, 20 year old C code to avoid triggering this well-meaning organizational policy!" I was sure you and I must have worked at the same company. Alas, TIM isn't named TIM here though.
- james_s_tayler 7y agoAs in there was a terrible developer named TIM that caused all the problems in the code and the solution was to move him to the basement and assign him to non-coding tasks, so no one ever heard from him again?
- twic 7y agoIt could be. I would have said that the reason was that the name of the software was the TIM, and at some point, the repo had been restructured so that the code for the main app was in a subdirectory rather than in the repo root, but that could easily have been a cover story. EDIT Ah no, it couldn't have been that, because i met several of the developers who had caused all the problems in the code, and none of them were called Tim or in a basement.