@sun@shitposter.world posts like this make me really scared i've somehow just gotten into better jobs and codebases by being considered "young and hip" or whatever and the next economic downturn or whatever i'm going to have to be forced into an absolutely hellish 1000 line python codebase or something for the rest of my career
@shibao I hate to tell you this but unless you have a really lucky streak your entire life you're going to get the worst software job imaginable at least not once, but at least a few times.
@shibao it's cliche but shit jobs like this build character, it's a trial by fire teaching you how to deal with adversity, like nobody listening to you at work before making terrible decisions or a terrible in-house homebrew codebase, or tons of paperwork, or toxic backstabbing coworkers.
@sun@shitposter.world sorry did i say lucked out i mean super extremely very much crazily lucked out, i'd say its because i've been able to have so much influence in the codebases to actually make them good but the other part of me says that it's because i'm not working in an absolute shitty code factory sweatshop or something but idk
@pro@mu.zaitcev.nu@sun@shitposter.world i was going too fast, i meant 1000 line python scripts, not just the whole codebase is only 1000 lines of code which could be reasonable. i'm more just talking about how massive python codebases quickly devolve into generic object mush cancer
P.S. I understand that the contents is what matters. I used to fix a 1,000 line code in FORTRAN IV, which was a little difficult. But still, boring Python boilerplate can run for much longer than 1kloc.
@shibao@pro@sun after having worked with several stupidly large python codebases, it is my honest opinion that the interpreter should just refuse to load more than 10000 lines of code at once or something.