Design Thinking

I think about my code while writing it, and at other times. Here’s what I think today. As I wake up in the morning, I often think, often in an almost dreamlike state, about my current programming project. And often I get what seems like a good idea. And sometimes, it actually is a good idea. The primary means for finding out is typically to try it. This morning I was reflecting on the grouping comments that I put into DungeonLayout, identifying methods with headings cell access; cell neighbors; rooms; connectivity; SuiteMaker class?; how does this relate to PathHelper?; probably should be separate object; and testing only so far. You might note that some of those are more specific than others. That’s how my thinking works: some things pretty crisp, some still quite vague. This morning’s thoughts were considering how the DungeonLayout really knows (only?) two things: class DungeonLayout: def __init__(self, max_x=10, max_y=10): self.cells = dict() for x in range(max_x): for y in…