One of the best books I ever read about Programming was
https://www.amazon.com/dp/0201179288/?tag=pfamazon01-20 --it's about all the classic mistakes that people make when programming. And although the book is about the C language, it can apply equally to many other languages.
As a student pilot, I was initially horrified that people would study morbid, deadly accidents with such dispassionate detachment and clinical precision. And then I caught a few problems myself, before things got ugly, having learned from those experiences. That's when I discovered that the forensic engineers have to be very sharp people. There are research engineers and production engineers. These are problems that have eluded two previous generations of engineers. This is where the feedback comes from to improve safety, efficiency, and security.
Likewise, one of the best things you can do as an engineer is to figure out why things break and how people get things wrong. Field service engineering, forensic investigations, and working at the tail end of a design project are fantastic places to learn things. This is where you figure out where the impact of a few misconceptions, who the users really are, and what the failure modes are. It is hard work, it's exciting, and sometimes dangerous work. You need to be on your toes. It can be very sobering and it's not for everyone.
Nevertheless, even if it is only a year or two of experience, it will last you a lifetime. And when you move on to other things, these experiences will remind you of the mistakes that others without your experience made. It keeps me grounded and I hope it would do the same for you.