[smackeyacky]

Think of the college experience as “that’s the way things are done here”. Then park it. It’s much more important to learn “that’s the way things are done here” including boring things like naming conventions or what the social/political landscape looks like to get code into production. If it’s a big place with formal practices and dedicated test teams or it’s a small place where you have to DIY those things. I would avoid as much as possible the crusty, grumbly devs who have been there forever and do nothing but complain, they’ll only hurt your career (I’ve been one of those people and was useless to everyone).

Every place does things differently and the best way to be productive is to follow along. It might be wrong or weird but chalk it up to experience, likely things are that way for a good reason.