Help me out here. Should I chart or not?
I had two project heavy courses over the last year. One professor was adamant about charting. The other couldn’t care less. In fact, I’ll paraphrase his charting advice: “I’m obligated to tell you there is a thing called a UML diagram. Some businesses use it. Some businesses don’t. We will be spending little time on it.
The other professor treated the absence of charting as sacrosanct. To think about not using charts is an affront to every major religion on the planet. He wanted everything charted. UML class charts, state diagrams, every processes and every object should be charted and in its place.
I kinda like the charts. When I dive off deep into a component and start to question why I’m doing it this way, how the component fits into the project, or depending on how long I’ve been at it during the session, is my existence even real, the chart says, “yeah. It’s ok bud. Here’s how you fit into the big picture.” It’s nice.
Also, this was a fun way to create another service running on my homelab cluster. I found a drawio docker image, created the deployment yamls, and away we go. It’s internally facing. I’m still trying to figure out what my ingress scheme is going to be.
