Gestures in kind may also just BE a timeless slam dunk. As in I have audited your design proposal and, while I have some notes about the implementation, I also have a much better suggestion:

youtu.be/5p8wTOr8AbU?...

And yet when it works hooooooooo baby.

In the name of both honour, and defence:

🤺 ENGARDE

Perhaps not trunk quite yet, but a

✌️Baleen Effort✌️

Inviting the question of paradox in relationship between modern memery and the roles of applied programming.

They are not related at all, and yet have everything in common...

Now we are onto formal requisitions FOR logging events, in tandem with UI based test coverage. This, in turn, will allow for visual regression tests to be paired WITH appropriate logging mechanics. Standards of admissibility from these activities will then be translated into unit tests themselves.

Sometimes an application's breadth leaves core functionality overlooked. Maybe there are missed opportunities. Perhaps the production analytics tell a different story than a goal...👀

Perhaps they even validate the need for enhancements. This is where this work can get VERY interesting.

We often think about discovery for "from the ground projects", but what of features and functionality that are already deployed?

Discovery allows us to spend time defining priorities, talking about goals and objectives. THEN we can evaluate the current status of stack and configuration.

the magic of structural iteration. Priorities like developing a coherent content strategy for transactional mail can be pitted against enacting email analytics.

I saw a great passage about refactoring in this article yesterday. We're here to talk through best practice knock-on effects.

Somehow, somewhere in our stack the dependency chain with a major release went full bork action, meaning it's time to revisit the email handler. This, to me, is where refactoring gets interesting. More team experience, clearer vision of priorities and this allows for

docs.meteor.com/api/email

Now we get to ask the question I know everyones SCREAMING in their minds?

What do the performance implications look like ONCE we can

1) Isolate queries and subscriptions based on routes
2) handle global subscriptions minimally
3) measure changes on the server response

forward. As for the evolution into TDD, it becomes (interesting | mind numbing) depending on your point of reference. The when part of

1) after a foundational refactor
2) the establishment of route based subscription handling
3) updates to methods themselves
4) adding tests?

Pseudo code start:

Like most things phases of this are a bit of a whackadoodle. Configuring react-skeleton with the meteor subscriptions suggested there would be endless refactoring without a data provider and now the data provider (configured) has too many collections queried but! This allows for testability moving..

TALLY HO

Sometimes one must simply ask oneself hmm? What if a tangled spaghetti mess of code is like a vindictive headless horseman in a foggy swamp or forest?

Could it have a vendetta to enact across application nodes?

Or is it a sluggish zombie rampantly multiplying?

These are all GREAT questions!