UML is essential in working on medium or large game projects. Lots of programmers donāt know how to use it. Game teams will happily hire them but then expect them to learn it fast. Teams that spurn it, well ā¦ it usually shows fairly quickly in the lower quality of their builds and the longer dev times to get stuff working.
In mainstream game dev its value is mostly nothing to do with planning, itās all about being able to rapidly communicate to other people (and other teams within your studio) WTF you have done, are thinking of doing, and are about to do. Medium and above teams tend to have code planning meetings where youāll have 3-10 people in one meeting, and so every minute you waste is potentially wasting ten times that much coding time. Efficiency of communication is very important. Everyone should be able to read a class diagram (heck, even people who donāt know UML can usually read one with a few moments thought about what those arrows must mean), but when everyone can also draw them without having to look up teh symols you can do code-planning much much faster.
With network programming, some of the other diagrams become just as (or even more!) valuable, e.g. deployment diagrams take a vauge, hard to describe, easy to misunderstand situation (what versions of which libs are we installing where and which APIs are we going to remotely call on which machines and why?) and makes it clear and easy to understand at a glance.
This matters a lot when you have half a dozen programmers working on one system. When you get later in the project and you have 5 or even 10 programmer working on one FEATURE (or fix) that crosses many systems, and only have that many people because itās that complex or that pernicious a bug, then it matters even more :).
EDIT: so ā¦ I highly recommend you keep your UML knowledge fresh, sooner or later it will come in very handy for you :). Although you may have to educate a lot of colleagues along the way, there are a lot of people who started games programming before basic software engineering had gone mainstream, and missed out on things that are considered ābasicā today. IME they are mostly very happy and rapid to adopt new things if someone turns up with genuine examples of why they should bother, based on stuff theyāre accutally doing on a day to day basis.