search

cmneal26 / Tech-Writing-Project

Class repository
2 stars 1 forks source link

Brainstorming: TTT Thoughts, models for dumb/smart TTT player. #37

Closed ghost closed 2 years ago

ghost commented 2 years ago

We might not get to the TTT game, for either technical or operational reasons. However, if we do build it, then we're also going to have to make some design and implementation decisions. The purpose of this thread is to both (a) provide me with a reminder, so I don't get lost in the smaller picture and lose sight of potential blockers, and (b) provide a place for iterating on TTT-related ideas.

TTT is third sprint material, if anything. We may not even have a TTT game page, why am I introducing this brainstorming ticket so earlier?

the refinement of ideas with this potential path forward, even if not implemented, will give us a better idea about potential blockers, and allow us time to refine our plan, without rushing and making potential mistakes down the road.

ghost commented 2 years ago

OOP For Interactive TTT Game page?

There are different code patterns that can be used to build things. In circumstance C1, perhaps pattern P1 is the best pattern for the job. However, in circumstance C2, perhaps pattern P2 is better.

         For example, Games are often built with OOP patterns (Object Oriented Programming). There's something about doing things that way, which is good for making games. However, it's important to realize that however useful OOP may be for games (ESPECIALLY LARGE GAMES), OOP introduces a lot of complexity. And, other things being equal, less complexity is better than more complexity. And a simple model with small functions performing specific tasks would be more than sufficient for a TTT game.
         There's also an important and different reason I thought of that might not be clear. We are not a software engineering team, we are a technical writing team.  So, this affects how we should think about the operational processes which allow us to iterate and produce awesome stuff. Why?  Ideally, we want everyone on the team to be able to contribute to interactive Javascript content. And it's silly to not make use of team member's potential resource in this capacity because they don't want to, or are scared of doing things in a more OOP way that might require more rules and complexity and guidance from an SME.

Also, the Eleventy project structure we have now might make it difficult to use Classes.

From an operational perspective, it's better to minimize the dependence of our team on external SMEs. Why? We may need to get particular things done at particular times, and this will be harder if we have to work around external SME schedules. By minimizing this sort of dependency, our technical writing team can leverage their own abilities to handle simpler interactive javascript content, and this seems like an efficiency gain, as well as an expression of our core team value of autonomy

ghost commented 2 years ago

TTT Board Implementation Thoughts

transparency note: Sometimes I find it helpful to think about why team members do one thing rather than another. For example, instead of raising this brainstorming ticket, I could have just sent a private message, "Tim, can you make me a TTT game in a Githubissues.

  • Githubissues is a development platform for aggregating issues.